Jump to content

Jeff Harris

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral


About Jeff Harris

  • Rank
    Support Team

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In cases like this, if you're going to place any scripts or files to run as tasks, it's best to put them in a folder such as C:\Temp\.
  2. That is correct; we are working on how to better address a previously failed Application Pack deployment. The presence of the !sdspk folder in C:\Windows\Temp\ is a good indication that an installation is stuck, along with any files in the C:\Windows\syswow64\SmartDeploy\sources folder. We do check for those when we're troubleshooting any deployments.
  3. First I’d check the Application log in Event Viewer for any errors related to SmartDeploy. You may need to reach out to Support depending on what you see. Additionally, check this URL for port information and some powershell commands to test them. https://support.smartdeploy.com/support/solutions/articles/48000968329-which-ports-are-required-by-smartdeploy-
  4. First, I would check C:\Platform on the target system to make sure the Platform Pack was copied there. Then check the System log in Event Viewer so see if drivers are being injected.
  5. This is likely due to a problem with the certificates created by SmartDeploy. Unfortunately you'll need to clear them out and re-install SmartDeploy to repair this issue. Uninstall SmartDeploy. Click Start, search for Certificates, click on Manage computer certificates In the left pane, browse to Certificates - Local Computer | Personal | Certificates In the center pane, locate the certificate that shows SmartDeploy Console/Client Service Root CA in the Issued By column. Right-click this certificate | Delete, and confirm deletion if prompted. In the left pane, browse to Certificates - Local Computer | Trusted Root Certification Authorities | Certificates. In the center pane, locate the certificate that shows SmartDeploy Console/Client Service Root CA in the Issued By column. Right-click this certificate | Delete, and confirm deletion if prompted. Close the certificates console, then reboot the computer and re-install SmartDeploy
  6. Please email support with your company email, and we can assist in helping you. Your additional users should be able to provide the email address that you currently use to log into SmartDeploy. You'll receive an email to approve the addition of their accounts.
  7. Our Platform Pack download endpoints are hosted in Azure, and thus we don't have much in the way of investigating bandwidth. Are any other packs downloading as slow?
  8. Keep in mind that SmartDeploy won't upgrade Windows 7 to 10. It will wipe the disk and apply your image as configured in your Reference VM. You can migrate the user data in 1 of 2 ways; configure it in the Answer File as you mentioned, or install the SmartDeploy client on the Windows 7 client, and use the Computer Management workspace to capture the user state before deploying your image, and then restoring it the same way. SmartDeploy uses Microsoft's User State Migration Tool for this process.
  9. Hi Sean, There isn't a way to track the process of a deployment aside from going and looking directly on the machine. 4 hours is certainly to long. I'd be interested to know what's on-screen on the device, and would want to see logs collected by booting back into SmartDeploy and clicking Collect Logs on the main menu. You'll probably want to reach out to support for more guidance.
  10. You can create Application Packs for running PowerShell scripts, and push those to your SmartDeploy clients. Here's our KB article for creating custom Application Packs; https://support.smartdeploy.com/support/solutions/articles/48000960633-create-your-own-custom-application-pack You'll need to add PowerShell.exe -NoProfile -NonInteractive -ExecutionPolicy bypass -File to the start of the executable path after selecting your script,, per the documentaiton.
  11. Hi Bryan, We'll need you to email support, detailing how it's breaking, along with logs from a failed deployment so that we can investigate what's happening.
  12. Please email support for more help with his issue.
  13. Did you receive an error when you mapped a network drive to the share where your image is kept?
  14. If you have a valid IP, you should be able to click the Network button and specify a \\HostName\ShareName to map a network drive, then browse back through "This PC" to see the drive and pull the image off the network.
  15. I was wrong; that Platform Pack doesn't include a WinPE node, which means it wasn't expected to need additional drivers when booted into WinPE. All you should need to do is boot the VM to the ISO, and the default network settings should allow the VM to reach your network. Is there no IP address listed in the bottom right corner?
  • Create New...