Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

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

Recent Profile Visitors

8,701 profile views
  1. Hi WyliKioti, This error is usually caused by a mistyped or invalid Windows product key - however, it would affect all of your devices that deploy this image (if the product key was added in Capture Wizard) or all devices that deploy using this answer file (if the product key was added in Answer File Wizard). So, for this error to occur in a model-specific fashion is unusual. We'll need to see a logset from this deployment to determine what's going on. Please boot to SmartDeploy media on the affected device (ideally with USB boot media with no answer file, to avoid starting another deployment and wiping the previous logs), click the Collect logs option, save the resulting zip file to an external location, and email to us at support@smartdeploy.com. Note that some organizations restrict sending zip files over email, so you may want to check with your IT department to make sure the email made it out with the attachment. Alternately, you can submit it via the Support form, which includes a file upload option. If you submit a new ticket, please mention my name so that your ticket is routed correctly. Glenn SmartDeploy Support
  2. https://support.smartdeploy.com/kb/article/33-how-does-decommissioning-work/
  3. Hello, Yes, you can include Office 365 on your image. Simply install it on the virtual reference machine. Be sure once it's installed not to launch any of the office programs. You can find more information here.
  4. Hi Chris, Antivirus software running on your host can cause some of your VM files to be in use, and can trigger this error. Try disabling a/v and retrying capture. If the issue persists, please send us your Capture Wizard log - C:\SmartDeploy\Logs\Capture.log Send to: support@smartdeploy.com Glenn SmartDeploy Support
  5. Always annoying when that happens, but glad to hear you were able to resolve it. Please feel free to reach out to support@smartdeploy.com if you need any further assistance. Glenn SmartDeploy Support
  6. Hi Tim, Are you able to successfully PXE boot other models on this network without issue, or is this your first attempt at PXE boot in this environment? Glenn SmartDeploy Support
  7. Hi Romulo, We'll need to see a logset to help troubleshoot this further - I've opened up a support ticket, and you'll hear from us shortly. Glenn SmartDeploy Support
  8. Hi Amanda, I've gone ahead and created a support ticket to address this issue - please expect our email shortly. Glenn SmartDeploy Support
  9. Hi Nagaraj You're certainly free to decommission any device as long as you will never again reimage it with SmartDeploy, and as long as you won't be using any other SmartDeploy product features such as computer management with the SmartDeploy client, driver updates, application deployment (beta), etc. We generally recommend (and that it's generally lower-risk) to wait until a device is physically leaving the premises to decommission it, however - if a decommissioned device is ever reimaged or has the SmartDeploy client installed, it would become "recommissioned", meaning it would consume another SmartDeploy license seat - but this time, the license cannot be removed from the device, and it would simply be lost when the device retires. If you have any questions about licensing, please feel free to reach out at licensing@smartdeploy.com. Glenn SmartDeploy Support
  10. Hi Ted, This is an interesting result - thank you for posting your solution. I'm curious, were you able to verify whether the original version of that image was usable? Glenn SmartDeploy Support
  11. 2013 is pretty old and would have to be tested with Windows 10. We also created a video on this process everyone can view here:
  12. Hi argnt, I've opened a support ticket for you - we'll be happy to discuss in further detail! Glenn SmartDeploy Support
  13. Hi there, It's likely that whatever restrictions you're applying are not surviving the Sysprep process. Since Sysprep is a mandatory part of deployment, there's unfortunately not a lot we can do about this. The recommended method for this sort of thing would be to apply the restrictions to the endpoints instead - this way, you can be sure that they are being applied to the current computer, current account, current SID, etc. Depending on what restrictions you're looking to impose, you may want to look at using Group Policy on your domain. Please feel free to reach out to support@smartdeploy.com if you have any questions. Glenn SmartDeploy Support
  14. Hi wajtech, The most reliable way to do this would be with Group Policy once the computer is domain-joined - this is the method Google recommends as well. https://support.google.com/chrome/a/answer/7009292?hl=en Feel free to reach out if you have any questions or issues to support@smartdeploy.com. Glenn SmartDeploy Support
  • Create New...