Jump to content

Jeff Harris

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Jeff Harris

  • Rank
    Support Team

Recent Profile Visitors

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Please email support for more help with his issue.
  6. Did you receive an error when you mapped a network drive to the share where your image is kept?
  7. 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.
  8. 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?
  9. We do have a VMware Workstation 12 Platform Pack. I would download that, and make sure it's included when you re-create your SmartDeploy ISO to re-try the deployment. Typically it's not required, however I don't have v12 to install and test.
  10. Hi Ted, I can confirm that there were some instances observed where the "SmartDeploy" service was stuck on 'Starting" on systems deployed with .3060. This is a service that's used in deployment and should be expected to be disabled, and not running. To be clear, this is different than the "SmartDeploy Enterprise Client Service" service that will only be present if the option to install the Client was enabled in the Answer File, or manually installed after deployment. This service should be set to Automatic (Delayed), and running.
  11. Our official recommendation is to always install the version of Windows 10 that you want to deploy, direct from ISO. In-place upgrades often cause problems. These are problems that are usually too complicated to bother fixing, (Or the update simply broke sysprep) resulting in building a new Reference VM anyway. That being said, I have tested (as I usually do) performing an in-place upgrade to v1909 and capturing and deploying my test image successfully. I should note, that this was a VM with zero additional software installed. I would make a back-up of your virtual machine before trying the update and capture/deployment. (You can use snapshots, you'll just need to use a warm capture to capture your image.)
  12. You won't be able to initiate any actions from the console to clients that appear greyed out like that. It may be that the service needs restarting, or the required ports aren't open. (Sometimes restarting the Console service helps too) When you look at the services, you should see the SmartDeploy service only if an image was deployed to that device with SmartDeploy. (It's only used during deployment.)The service below that, the SmartDeploy Enterprise Client Service should be running, if the client was installed. You can check the ports using these PowerShell commands; Test-NetConnection -Port 8734 -ComputerName [Your SD Console Host IP/Name] -InformationLevel Detailed Test-NetConnection -Port 8735 -ComputerName [Your SD Console Host IP/Name] -InformationLevel Detailed
  13. Melissa, this would certainly require looking at your deployment logs to determine what's happening. You should certainly see that the OEM installation of Windows is removed after deployment. Please collect logs and email support and we'll take a look and help you out.
  14. Aaron; I'm not seeing a reference to a certificate, which means you may be having an unrelated issue. Please email Support so that we can request logs and investigate what's going on with your SmartDeploy console.
  15. Unfortunately, we cannot target partitions like that. I've not heard of anyone using or testing SmartDeploy in this scenario, but I do not recommend testing on this machine, assuming that it's a production workstation.
  • Create New...