Jump to content
DeployCentral

Jeff Harris

Administrators
  • Content Count

    190
  • 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. 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.
  2. 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.)
  3. 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
  4. 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.
  5. 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.
  6. 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.
  7. Hi Melissa, SmartDeploy doesn't quite work like that. You can use additional features to back up and restore the user data on that system, and install applications post-deployment, but SmartDeploy will otherwise erase the contents of the disk, apply the image captured from your Reference VM, and then restore the user data and install additional application packs (if configured to do so.)
  8. Jolew, Please email support to open a new ticket. We'd likely want to connect you with a member of the dev team to look at your console host for more information.
  9. The place to look for information is C:\Windows\Debug\NetSetup.log. If this file isn't present, it's possible that the sysprep mini-setup is crashing, which means we'd want to look at the image source.
  10. Hey Tim, I'm not sure what you mean by repository, but we do have a growing list of Application Packs available for download via the console.
  11. Ariel, It's possible that the Deployment Package you're using for console-initiated deployments may not have the Platform Pack for that device, if it was made before you downloaded the Platform Pack. Try creating a new Deployment Package, and make sure that you see the Platform Pack for that model in the list in the Media Wizard, and then re-try the deployment.
  12. That action is going to attempt to read the metadata of those files and reflect changes to them in the console. Are you finding that you've made changes to a VM or image that's not being reflected in the console?
  13. Additionally, you will need to download the Platform Pack for that model, and make that it’s selected when you create new WDS boot media, And replace what’s in your WDS host if you haven’t don’t that already. This will include the storage driver that is likely needed.
  14. We see that error often when an image was captured from a Reference VM that had 2 virtual disks connected to it. When this is the case, even if the second disk isn't selected in the Capture Wizard, SmartDeploy will expect there to be a second disk on the physical computer.
  15. When you create your Answer File, you'll be prompted to specify the location of your image, Platform Packs, and Answer Files. These shares do not have to reside on the SmartDeploy console host, they can be anywhere. When you create your Deployment Package, you'll include that Answer File. Any network deployments you start with that Deployment Package will use the paths in the Answer File to find your everything.
×
×
  • Create New...