Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Posts

    846
  • Joined

  • Last visited

Everything posted by SmartDeploySupport

  1. Hi Ric76, We'll follow up via email - we'd like to troubleshoot this further. Glenn SmartDeploy Support
  2. Hello, Please send us the following log from an endpoint that has gone offline and then not returned: C:\Program Files\SmartDeploy\ClientService\SDClientService.log That should provide us with more information. Send to support@smartdeploy.com and refer to this thread when you submit it. Thanks, Devon SmartDeploy Support
  3. This is a v3 bug that we are working to fix in the next release. It has to do with the length of time that has passed since the media was created. For now, recreate your boot media via the Media Wizard and boot from it. You should not receive that error anymore. Sorry for the inconvenience. Thanks, Devon SmartDeploy Support
  4. We're in touch with Nate via email, but for anyone else who runs into this issue: Update to the latest version of SmartDeploy, recreate your media, and retry deployment. If the issue persists, grab a logset from the same PE session (if you can) and email us at support@smartdeploy.com, or submit a ticket via the support form. Glenn SmartDeploy Support
  5. Hi DJ, The 3.0.1005 installer is not too large - about 97MB. Assuming the endpoints at the remote site are connected with a Cloud connection type (which they probably should be), then it shouldn't bog down the connection between offices, but rather, each endpoint would individually reach out to your cloud storage provider to download the installer. If the clients are connected with a Local connection type, that could be the concern - and if that is the issue, I might suggest you configure those endpoints to use Cloud communications only. We can provide a script for this, so reach out to support@smartdeploy.com if you'd like to go that route. Throttling client updates is not currently a feature of the console, but if it's a feature you'd find useful, please shoot an email over to feedback@smartdeploy.com. Our engineering team does read all feedback and feature requests that come to this address. Glenn SmartDeploy Support
  6. I've emailed DJ back about this, but putting it here as well for everyone's info: This is a known bug in V3.0.1000, and it has been fixed in the latest release. Update to the latest version (V3.0.1005 as of this writing) and you should be all set. Feel free to reach out to support@smartdeploy.com if you have any questions or issues. Glenn SmartDeploy Support
  7. UEFI requires FAT32 and we can only make that work up to a certain size. This Toshiba device must be too big, probably 1TB or greater? Need a flash drive, 64GB, 128GB, 256GB all work.
  8. Yes, you need to create your boot media or deployment package with the platform pack for the model you are deploying to selected in the Media Wizard. If you continue to have trouble, please submit a ticket. https://support.smartdeploy.com/support/tickets/new
  9. Hello, Once you get that error, cancel out of the Deploy Wizard, then Collect Logs and submit them to us in a ticket. https://support.smartdeploy.com/support/solutions/articles/48000984846-collect-logs https://support.smartdeploy.com/support/tickets/new
  10. Hi Joel, That is concerning to hear - I wouldn't expect you to have this much trouble with the automatic client upgrade given that your other Computer Management features are working normally. It is possible to disable the automatic client upgrade feature, so it's possible this was done at some point in the past on this console host. It's not the sort of thing you could've done accidentally (it involves editing a line in a .config file), but I'm not seeing any record of this on your previous tickets, so it would've had to be someone else in your environment. If you run into any issues with the V3 Client, or if you want to troubleshoot this further, please reach out to us at support@smartdeploy.com and we'll be happy to dig into this. Glenn SmartDeploy Support
  11. Hi Joel, Thank you for reaching out. First off, I should mention - the normal behavior of the SmartDeploy Client is that it will update itself automatically with no action required on your part. It's supposed to be a process that's entirely free of headaches - or indeed, any work whatever - for you. The recent exception on this has been the release of SmartDeploy V3, which features completely redesigned client-console communications, and installs alongside your existing V2 (2.0.3090) console. The new communication protocol should mean much more reliable communications and message history between your V3 Clients and the V3 console - but since it was such a drastic change to the software, we didn't want to automatically push out all of the V3 updates only for those endpoints to not be able to talk to the console due to the change in ports and so forth. This side-by-side installation should allow you to upgrade a small number of test clients to V3 (using whatever method you prefer, including manually or using Group Policy, or using the "Upgrade Client to V3" option in the V2 console) and confirm that these endpoints are able to report into the V3 console, and that you're able to perform operations from Computer Management to these endpoints, and then you can upgrade the rest, and uninstall your V2 console. I realize that doesn't address the why of your question under normal circumstances, when we're not rebuilding the software from the ground up. For about half the lifespan of the SmartDeploy console, we actually did allow backward compatibility. However, we eventually came to recognize this as a potential security concern. The console has the ability to send commands to a client which can execute those commands on any endpoint with administrative permissions. This includes administrative functions such as installing software, changing boot options, or changing user permissions. Consequently, we need to make sure that this communication protocol is as secure as we can make it, and that unfortunately means disallowing backward compatibility as a best practice. This helps us ensure that older clients do not stick around carrying vulnerabilities that we have already patched on the console side. I hope that helps address your concern. Our engineering team always welcomes your feedback, and if you have any further thoughts on the matter, please feel free to reach out at feedback@smartdeploy.com. Likewise, if you're running into any support questions, you can reach out to support@smartdeploy.com. And finally, here are few articles from the support portal which may help if you're upgrading to V3: How to upgrade SmartDeploy from V2 to V3 How to troubleshoot SmartDeploy Client upgrades from V2 to V3 Glenn SmartDeploy Support
  12. You're using Ethernet, correct? We will need to take a look at your C:\SmartDeploy\Logs\MediaWizard.log from the SmartDeploy host to see if the driver injected correctly. Please send it to support@smartdeploy.com and reference this thread. Thanks, Devon SmartDeploy Support
  13. Hi Milos, In order to make use of this network driver, you will need to figure out how to extract the driver files (the .inf and any other required files that accompany it) from the .exe or wherever else they may be stored among the package you downloaded. Unfortunately, there is no standard method, as this process varies significantly between manufacturers, who use many different installer types for this purpose. If you would like further assistance on this, please submit a Platform Pack request via the Support Form. Glenn SmartDeploy Support
  14. Hello, Just to verify, you originally got the computers imported into Computer Management in v3? Then once you restarted the host, they disappeared? Please email the following logs to support@smartdeploy.com. C:\SmartDeploy\Logs\SDConsole.log C:\SmartDeploy\Logs\SDAPIService.log That should provide us with more information. Please refer to this thread in the email. Thanks, Devon SmartDeploy Support
  15. Hi George, Please send us your C:\SmartDeploy\Logs\Console.log from the SmartDeploy host to support@smartdeploy.com. Reference this thread and we can take a look. That being said, we release version 3.0 of SmartDeploy today, so you may want to upgrade to that and attempt to re-download your Application Pack and see if that works. https://support.smartdeploy.com/support/solutions/articles/48001188577-how-to-upgrade-smartdeploy-from-v2-to-v3 Thanks, Devon SmartDeploy Support
  16. Hello, We will need to take a look at some deployment logs in order to see what is causing the error. When you boot to the SmartDeploy boot environment, do you see the internal storage disk in the bottom right corner listed? Reproduce the error (so it's saved in memory), then dismiss the error and close out of the Deploy Wizard to return to the main menu. Click Collect Logs and save the zip to a USB or network share. Send us that zip. You can submit a ticket here. Refence this thread in the ticket. Thanks, Devon SmartDeploy Support
  17. SmartDeploy fully supports SecureBoot, and changing it won't effect if the internal storage shows up or not.
  18. You'll need to create your boot media with the platform pack for this model selected in the Media Wizard. That will add the storage driver into the boot environment and allow the internal storage to show up. This is because Dell ships their machines with RAID on. If the machine has a single NVMe drive, then the other option it to turn it to just AHCI in the BIOS, then the native NVMe controller will be used and not require an additional driver
  19. Hello, We will need the following from the SmartDeploy host: C:\SmartDeploy\Logs\Console.log C:\Windows\System32\winevt\Logs\Application.evtx From the endpoint we will need the following log: C:\Windows\SysWOW64\SmartDeploy\ClientService.Console.log Please zip those logs and send them to support@smartdeploy.com and refer to this thread and we can take a look. Thanks, Devon SmartDeploy Support
  20. Hi Sezell, We have seen this occur. Please refer to this article. https://support.smartdeploy.com/support/solutions/articles/48001064039-error-sysprep-was-not-able-to-validate-your-windows-installation- If you still have issues, send a deployment log set to support@smartdeploy.com and you can refer to this thread. https://support.smartdeploy.com/support/solutions/articles/48000984846-collect-logs Thanks, Devon SmartDeploy Support
  21. Hi Steve, I'll reach out to you via email about the script. Just to answer your question for the room: only one console hostname or IP can be specified for the client - it is not possible to specify both. Glenn SmartDeploy Support
  22. Hi Dayne, Sorry you're still encountering capture issues. Try the following as I've seen it help capture issues such as the mounting and access issues you are receiving. Start the virtual reference machine and run disk cleanup, including system files. Once completed, restart the virtual reference machine gracefully via the start menu. Once back at the desktop, open an administrative command prompt and type: shutdown.exe /s /t 0 Be sure any anti-virus is disabled and recapture and let us know your results. If you still have issues, please send us your C:\SmartDeploy\Logs\Capture.log from the SmartDeploy host to support@SmartDeploy.com and reference this thread. Thanks, Devon SmartDeploy Support
  23. Hello, The process you've laid out is certainly one way to do it - and if you want to reimage your endpoints each month, there's no reason why it wouldn't work for that purpose. You'll just want to make sure that you do not install any feature updates/in-place upgrades onto your reference VM. The Windows 10 Release Information page will give you the current servicing dates for each release of Windows 10 - the general rule (for Enterprise and Education SKUs) has been that the release in the first half of the year (such as 2004 and 21H1) will be serviced for 18 months, and the release in the second half (such as 1909 and 20H2) will be serviced for 30 months. This means that a particular version of Windows 10 can be kept completely up-to-date and security-patched even as several more versions are released in the interim. If you want to manage Windows Updates without reimaging your endpoints, you'll want to look at setting up a WSUS server, as this will allow you to control Windows Update installation behavior and compliance on domain-joined endpoints without reimaging them. If you have questions, feel free to reach out to support@smartdeploy.com. Glenn SmartDeploy Support
  24. Hi Dozer, Thanks for reaching out. Language selection is one of the standard options in Deploy Wizard which can be configured with a SmartDeploy Answer File - your language selection should be passed through to Windows without any part of the OOBE wizard appearing. So this is unexpected behavior. We'll want to take a look at a logset from this deployment and see what went on here - please expect an email from us shortly. Glenn SmartDeploy Support
×
×
  • Create New...