Jump to content
DeployCentral

Jeff Harris

Administrators
  • Content count

    84
  • Joined

  • Last visited

Everything posted by Jeff Harris

  1. Jeff Harris

    Symbols in SmartDeploy console

    I've attached a key for those icons. We're working on the documentation update for these now. SmartDeploy - Icon Definitions_v2a.pdf
  2. Jeff Harris

    NVMe Script

    Sorry for the delayed response. You do want to open a command prompt as administrator, and then run the the script there.
  3. Jeff Harris

    NVMe Script

    One thing I would do, is make sure that the zip file containing the script and accompanying files isn't blocked, by viewing the Properties of the zip file and making sure there's not an Unblock button or checkbox. If so, unzip it again and try again.
  4. If you collect logs and contact support, they can help narrow down the issue. It could be related to the clipsvc service issue with Sysprep. This was addressed in v2.0.3005, but it was found that certain models required additional tweaking, which will be addressed in the soon to be released 2.0.3006 build. I would also recommend creating a new VM and installing Win 10 v1803 directly if your current Ref VM was in-place upgraded from 1709 to 1803.
  5. You changed your SmartDeploy folder away from the H: drive? Do you have new Ref VMs in the new folder location?
  6. It's also worth testing with a warm capture to see if you get the same message.
  7. Jeff Harris

    Platform Pack stuck downloading

    C:\Program Files (x86)\ would have been the default location and would have been used unless manually changed by whomever installed. If you find that it was installed there and those DLLS are missing, please re-install SmartDeploy after checking the Properties of the SDEsetup.exe file to make sure that there isn't an 'Unblock' prompt on the General tab of the Properties menu.
  8. Jeff Harris

    225 Error During Image Capture

    Hi Brad, Do you have anti-virus or other security software installed on the Reference VM? If so, you may need to uninstall it. A/V in images often breaks the capture/deployment in unpredictable and unusual ways. If you have it installed on your SmartDeploy host, you may also need to temporarily disable it as it sometimes incorrectly flags some of the activities that SmartDeploy as malicious. If neither is the case; then the next thing I would try is a warm capture. You can mount the C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SmartDeploy_x64.iso to your virtual machine, and boot to it to get to the SmartDeploy boot environment, and start the Capture wizard. /Jeff
  9. Unfortunately, SmartDeploy is not able to do that. It will always wipe the contents of the drive, and apply the image that you captured from your reference VM. That being said, you can use the User State Migration Toolkit (USMT) option in the Answer File which will copy the user files and some settingsback onto the device after the image is applied. Here's a link to some Microsoft documentation on USMT. This is the tool that SmartDeploy uses when you enable it in the Answer File.
  10. Jeff Harris

    Platform Packs Stuck Downloading

    One other user was stuck in this state, and we were able to get it going by re-registering some DLLs. Can you Open a command prompt and try the following commands? After that, please restart your system, remove the erroneous packs and try the download again. regsvr32 "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\Resources\SmartCOM.dll" regsvr32 "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SDK\Bin\64bit\SmartCOM.dll”
  11. Following deployment, if you create a new profile are the apps still broken/missing?
  12. Jeff Harris

    Unexpected error while deploying

    Have you successfully deployed this image before? The things to check would be that no in-place upgrades have been done on the VM, that there's no anti-virus software on the reference VM, there are no pending updates, and that it was shutdown with the shutdown -s -t 0 command.
  13. Ah I see. I misunderstood that you were running sysprep generalize, shutting down and capturing the image. I've attached our instructions for using copy profile, just in case. CopyProfile.zip
  14. Hey guy. First, you never want to sysprep/generalize your Reference VM before you capture your image to use with SmartDeploy. We do that for you at deployment. And in short; The settings you enter into the Answer File wizard are in turn applied by SmartDeploy to the answer file that's used by sysprep.
  15. Jeff Harris

    Windows 10 - 1803

    Yes, this is our recommendation, as well as Microsoft. However we are working on a version of SmartDeploy that will hopefully address some of the issues that arise from sysprepping Windows that was upgraded from 1709 to 1803.
  16. Jeff Harris

    Windows 10 - 1803

    You do not want to do in-place upgrades on your VMs in between major versions of Windows 10. If you wish to deploy v1803, you will want to create a new VM and use the v1803 ISO to install that version of Windows directly.
  17. Jeff Harris

    Windows 10 - 1803

    If you're able to, boot that system back into the SmartDeploy boot environment and Click Collect Logs, and send them into Support.
  18. Usually the only real catch is to avoid opening any Office apps after installation. You mentioned the user guide, but just want to make sure you caught that. Here's the link to Microsoft's guide for installing O365 on a reference system for deployment. It's got a little bit more information; https://docs.microsoft.com/en-us/deployoffice/deploy-office-365-proplus-as-part-of-an-operating-system-image
  19. Jeff Harris

    Trouble Deploying Dell Latitude 7490

    Are you able to enter the system settings and enable Secure Boot?
  20. Jeff Harris

    Why do I have to...

    That's pretty odd that it's only happening to the platform packs. The next time this happens, try moving the ppk files out of C:\SmartDeploy\Platform Packs\ to some place like C:\Temp, and then cut/paste them back. You don't need to walk through the import option inside the console for each one. (Also; I am assuming you didn't change your SmartDeploy directory from the default C:\SmartDeploy)
  21. Jeff Harris

    Cross network deployment

    Correct, the network deployment package contains the SmartPE boot image and your answer file. Provided you've walked through the steps to create an answer file for a cloud deployment, SmartDeploy will look to the cloud for the image and the platform pack.
  22. Jeff Harris

    Cross network deployment

    When you right-click a computer and click deploy, the network deployment package containing the SmartDeploy boot image and answer file is copied to the target computer (a few hundred MB). Then it will restart and boot into SmartDeploy and should your answer file have the instructions for an unattended cloud deployment, that's what would happen. I believe the recommendation is still to avoid this sort of scenario by keeping SmartDeploy installed on a VM on-site to act as the hub for console initiated network deployments. Maintaining connectivity without a site-to-site VPN can be problematic and may cause more work for you.
  23. I believe the problem is related to the AppX apps and sysprep in v1709 specifically, and not the profile. Hopefully this is fixed in the next large update. We actually went through this same thing a few versions back with Windows 10.
  24. We have seen issues with Windows 10 v1709 Store appx packages (and the Windows Store itself) not functioning after deployment. The first thing we recommend is that you try to fix your current VM. Power on your reference VM, launch the Windows Store, and install all available app updates. Once the updates have all completed, gracefully shut down the VM (shutdown /s /t 0), then retry capture and deployment. For some users experiencing this issue, it has resolved it. We’ve also seen success in creating a new local administrator account, or using a domain account. The process of creating a new profile allows for the Start Menu apps to re-provision. Unfortunately, if that does not fix the issue, the only workaround that we can recommend would be to rebuild the VM in the manner specified below. To build a new VM and ensure that no apps are updated in the process, complete these steps: Build a brand new VM. Set the network adapter to either be disabled or not connected. Install Windows 10 1709 from MS VL .iso (or any other official media which has not been customized for specific hardware). Go through OOBE. Once you reach the desktop, open an administrative command prompt and run the following command: reg add HKLM\Software\Policies\Microsoft\WindowsStore /v AutoDownload REG_DWORD /d 2 This registry value will prevent the Windows Store apps from auto updating. Once this is set you can open the VM settings and enable the network connection (and provide internet connectivity), then continue setting up your VM. Once your VM is setup, do a clean shutdown (command line SHUTDOWN /S /T 0) and capture. You will want to add a Task to the deployment to remove the AutoDownload setting, so that the apps will update properly on the deployed device. You can add this in Deploy Wizard (or Answer File Wizard), Advanced, Tasks.
  25. Jeff Harris

    Deployment Wizard - Not enough disc space?

    I've seen this sort of failure with Wipe and Load in instances where the target devices previously had Windows 7 installed, and the image is for WIndows 10. The reason is that the system partition for Windows 7 is smaller than 10, and thus it can't fit. We always recommend using Wipe and Load whenever possible.
×