Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by SmartDeploySupport

  1. Hi vlee14, Please refer to this: https://docs.microsoft.com/en-us/surface/ethernet-adapters-and-surface-device-deployment Based on this, your dock and dongle should work. You won't need to disable SecureBoot.
  2. Hi vlee13, I found that with using PXE boot, you still need to enable the "Enable boot from USB devices" option in the boot options list. Did you by chance do that?
  3. Aaron, Glad it works in your case. This issue doesn't occur with all imported WDS images, but we have seen it come up quite a bit.
  4. Hi Ted, That return value doesn't look like a success - just to confirm, is the client installing properly now? Glenn SmartDeploy Support
  5. Hi Ted, To troubleshoot this, we'll need to see your Application event log from the endpoint where you tried to deploy the application. C:\Windows\System32\winevt\Logs\Application.evtx I've created a support ticket and will email you shortly with instructions to submit the file. Glenn SmartDeploy Support
  6. Hi Jason, This is a known issue and not related to a disc issue. You will not want to install vmware tools on your virtual reference machine. It occurs if the Windows 10 image is 1803 or greater. There is a chance that it won't import correctly into WDS on Server that isn't 2016. But, not all images have the issue, so you may have luck recreating the image. The older version of Wingapi.dll isn't handling some of the new file properties in 1803. Unfortunately this is something we cannot fix and it even happens when importing a .WIM that isn't create by SmartDeploy but even dism.exe. Are you deploying 25+ machines at the same time? If not, you won't benefit from using multi-cast. You have the original .wim, which wasn't imported into the WDS role correct? Perhaps on the SmartDeploy host? If you do, I would open the WDS role and delete the install group of Windows 10. That should delete Y:\Images\Win10x64\. Then if you still want your original image there you can manually create that file path via file explorer. Copy your original .WIM to that location. Then create a new answer file to point to that image again, but this time it wasn't imported via the WDS role and will use uni-cast. Create new WDS boot media. Delete your old wds boot media from the WDS role. Import the new one. That will get you deploying and you can still use the PXE functionality, but still deploy via unicast.
  7. Hi Ted, Yep, you guessed it. Deployment Packages need to be recreated as well with the new version, but you can use the same answer file as before, unless you're utilizing any new Deploy Wizard features that did not exist in the previous version (I don't believe there are any such changes in .3040, but this has been the case in some previous versions). Glenn SmartDeploy Support
  8. Hi Ted, In order to perform console-initiated deployments, the clients must be on the same version as the console. No action should be required, however - the clients should install the latest version automatically, starting within a few minutes of when you upgrade the console. Please feel free to reach out if you have any questions or issues - support@smartdeploy.com. Glenn SmartDeploy Support
  9. Hello Aaron@Shared, Can you confirm this is happening on a client? Is this client connection to the host in a good state? If you look in the console in the Computer management workspace, is this clients listing in bold-face letters? How often does this occur? Does this happen to more than one client?
  10. Hi Jeff, We will need to take a look at some log files. 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 support@smartdeploy.com and reference this thread. Thanks, Devon SmartDeploy Support
  11. Hello cdonald2, Depending on the version of Office you're trying to install, there is some additional work to automate the installation. Here's a link to the Office 2016 Deployment tool documentation. https://docs.microsoft.com/en-us/deployoffice/overview-of-the-office-2016-deployment-tool In short, you'll want to have the installation parameters pre-set in a file and invoke that file as part of the installation. I recommend testing this manually on a system before building it into an application pack.
  12. Hi Sarah, Recreate your boot media via the Media Wizard and only the Precision 3510 Windows 10 pack during the process. That will inject the storage drivers into Smart PE and hopefully resolve this issue. Thanks, SmartDeploy support
  13. Please ensure the following ports are opened on your network: TCP 80 - HTTP TCP 443 - HTTPS TCP 8732 - ConsoleServiceWCF TCP 8733 - ClientServiceWCF TCP 8734 - ConsoleServiceSLWCF TCP 8735 – ConsoleServiceMCWCF
  14. Hi there, Please refer to the link I've provided (below) that has our instructions as well as a short video for more guidance. https://support.smartdeploy.com/kb/article/3-customizing-the-start-menu-and-task-bar/ If you have any further questions, please reach out to support @smartdeploy.com
  15. Hi Paul, You can download the virtual disk to your SmartDeploy host, and capture it that way, or perform a warm capture, which most of our customers do that are using VSphere. This process is detailed in our Knowledge Base article: https://support.smartdeploy.com/kb/article/35-performing-a-warm-capture/
  16. 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
  17. https://support.smartdeploy.com/kb/article/33-how-does-decommissioning-work/
  18. 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.
  19. 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
  20. 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
  21. 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
  22. 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
  23. Hi Amanda, I've gone ahead and created a support ticket to address this issue - please expect our email shortly. Glenn SmartDeploy Support
  • Create New...