Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Posts

    855
  • Joined

  • Last visited

1 Follower

Profile Information

  • Gender
    Not Telling
  • Location
    Seattle Washington
  • Interests
    Deploying Windows with SmartDeploy

Recent Profile Visitors

11,383 profile views

SmartDeploySupport's Achievements

Apprentice

Apprentice (3/14)

  • Dedicated Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare
  • First Post Rare

Recent Badges

0

Reputation

  1. No problem, glad to hear it. Glenn SmartDeploy Support
  2. Hi R, We do not recommend installing feature updates/in-place upgrades on your reference VM, and that may well be the cause of the issue. If you wish to deploy Windows 10 21H1, you'll want to download the latest ISO from the Microsoft Volume License Servicing Center (VLSC) or some other official source, and build a new reference VM using that ISO. Then retry capture and deployment. Windows should generally activate on its own within a couple of days without any intervention required, assuming that a valid product key was provided (either via the Answer File or when you captured the image). It's unclear exactly what is happening when you activate the licensing troubleshooter, but you can try just running a normal activation command after deployment, to see whether it throws an error. Open an admin command prompt and run this command: wscript.exe slmgr.vbs /ato Assuming this command works as expected, it can even be added as a Task in the answer file, to occur during First Boot as System, if you wish. But you will want to test it first. If you have any questions or issues, feel free to reach out to support@smartdeploy.com. Glenn SmartDeploy Support
  3. Hello, We have seen this issue sometimes - generally, if there is an issue accessing a particular cloud provider due to an API change, we address it in a subsequent SmartDeploy version, so I would suggest that you update to the latest version and recreate your media, and see whether the slow connection persists. I might also suggest that you try one of the other supported cloud providers besides whichever one you're trying - they all generally offer a free tier, so you would be able to see if you're getting better bandwidth on another provider before purchasing. All I can say with certainty is that it's definitely possible to get much faster speeds than that for cloud operations on all of our supported platforms, and it sounds like something may be interfering with your connection - I would suggest checking antivirus and firewall settings, making sure there isn't any sort of bandwidth limit applied to unauthenticated endpoints, etc. If you have any specific questions or want us to take a look at logs, feel free to reach out to support@smartdeploy.com. Glenn SmartDeploy Support
  4. Hello, If you want to add more models to your environment and want to deploy to them, you will want the Platform Packs for those models selected when you create the WDS boot media. That will inject drivers needed to complete deployment such as ethernet and storage drivers. Not all Platform Packs have Windows PE drivers, but a lot of the newer models do. https://support.smartdeploy.com/support/solutions/articles/48001198942-when-do-i-need-to-re-create-my-boot-media- If a Platform Pack does not have PE drivers, you can simply place the Platform Pack where the answer file points to. Default is \\SmartDeployHost\C$\SmartDeploy\PlatformPacks Thanks, Devon SmartDeploy Support
  5. Create boot media in the Media Wizard with only the platform pack for this particular model selected. That should allow the RAID controlled drive to show up.
  6. Hi DeJeon, Thanks for reaching out. If both newly reimaged and existing (not recently reimaged) endpoints all stopped checking in at once, there's a possibility that there is a common cause - perhaps some change in your security environment (antivirus or firewall settings). I'm going to go ahead and open a ticket for you, because there are a lot of potential variables to dig into here, and we'll want to see some logs from the affected endpoints. You may expect an email from us shortly. Glenn SmartDeploy Support
  7. Could depend on what version of Windows 10 it is, if it was upgraded, how it was captured. Please open a support ticket with us and we'll help you get to the bottom of it. https://support.smartdeploy.com/support/tickets/new
  8. It should work, WinRE just needs to be working. So long as the VM your image was created from was a clean install of Windows 10 from a Microsoft .iso for the version of Windows 10 you want it to be. If the VM was upgraded from one version of Windows 10 to another, then that can make WinRE not work. Check it with "reagentc /info" from the command line. If you still have issues, contact us at support @ smartdeploy.com
  9. This is an issue we've seen, but have never been able to replicate. It is a bad cold capture of the image, and it has something to do with the host that SmartDeploy is installed on. You can try a warm capture of the image, and see if that fixes it.
  10. Hi Ric76, We'll follow up via email - we'd like to troubleshoot this further. Glenn SmartDeploy Support
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
×
×
  • Create New...