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. This isn't supported in SmartDeploy. Creating a virtual machine and using that for your image is going to give you a much "cleaner" hardware-independent image.
  2. Here's a link for an Application Pack that I made for another customer to install the Dell Command Update util. Reported back and said it works, so hopefully it does the trick for you as well! https://drive.google.com/file/d/1zXTNqB3DcYIMsKAxfLRmcmt64Qj52ka7/view?usp=sharing
  3. Correct; there is a specific bug in Windows/Sysprep following an in-place upgrade to v2004. You always want to create a new VM, installing the new version of Windows you want to deploy from ISO.
  4. The name is generated/specified during the deployment phase, before the restart occurs. It is set into the Answer File for Windows Sysprep that is created by the Deploy Wizard.
  5. Unfortunately, that is a current limitation of SmartDeploy; that you must be logged into the console host with local administrator rights, and only one instance of the console can be open at at a time. This is feedback that we've received from numerous customers, and it is on our roadmap. It does likely mean a substantial re-write of SmartDeploy, which I believe is underway. I don't have a timeline or expected ETA for this to share unfortunately.
  6. You can install VMware Tools to work on the VM, but you do want to uninstall them before you capture. The problem is that sometimes VMware tools leaves things behind, and the Capture Wizard thinks they're still installed. I can put the RegKeys that we check for at the bottom of this post, but my recommendation would be to just leave them off, and RDP into your VM and perform your configurations that way. RegKeys; Microsoft: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B0950C40-269A-11DD-BD0B-0800200C9A66}Microsoft: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion
  7. Any common applications that will be going on the devices to deploy to would be worth installing on your Reference VM. You'll have fewer potential points of failure, and you'll reduce the deployment time.
  8. It's always been my recommendation to customize the Start Menu and Task bar layout, and leave those other apps hidden down in the app drawer rather than try to actually remove them. They're only going to be seen if someone scrolls down through the app drawer, which most people wont be doing. We have an article and video that explains how that's done, and it's far easier than trying to remove them and not break Windows sysprep. https://support.smartdeploy.com/support/solutions/articles/48000967003-customize-the-start-menu-and-taskbar
  9. Clients that check in with your console should receive a message to update themselves automatically if the console was updated. This process can break if the clients are connecting via VPN, or there is a problem uninstalling the current one. I'd first give one client a test by uninstalling/installing manually to see if there's any issues. Then on the next client, restart the client service, check the application log in Event Viewer for errors, and wait about 5-10 minutes to see if it updates itself. Following that, you'll want to reach out to Support to we can take a more in-depth
  10. It is purposefully not set to be automatic, as we want to avoid any unintentional overwriting of files. I can share your post with our feedback team for evaluation.
  11. USB is probably the best way to go, if you're unboxing new laptops. Unless you have a WDS host that you can upload your SmartDeploy boot image to, and PXE boot your new systems. The 3rd method for deploying with SmartDeploy involves pushing the deployment from the console to clients, which would require you to unbox the new systems, step through OOBE, then install the client, and get them connected to your host. I would first configure my Answer File to use the BIOS Asset Tag field for the computer name, if I hadn't done that already. Then I'd unbox a few laptops at a time, boot in
  12. If you're talking about clients on the same local network as your console host, then it should be within about 3-5 minutes after the service starts. (It is on a delayed start, so give it extra time if the client has just booted.) If it's not connecting, then check that the service started successfully, and look for errors in the Application log in Event Viewer. If you're talking about off-site clients and connecting through the cloud, you want to make sure that you used the non-fqdn name of your console host, and not an IP. Additionally, you want to make sure that your console hostname i
  13. I've seen instances where the prefix and serial number comes to 16 or more characters, which is rejected by Windows. When this happens, it will move to the next naming convention in line. Less frequently, the serial number field is blank.
  14. It looks like TeamViewer has some extra steps to jump through for what you're trying to do. This link below has instructions to visit; Design & Deploy page to set up your customization within the TeamViewer Management Console. You'll likely need to start there. https://community.teamviewer.com/t5/Knowledge-Base/Mass-deployment-improvements/ta-p/39639 Here's another link for the customized "Full Client" installation. https://community.teamviewer.com/t5/Knowledge-Base/Create-a-Custom-Full-Client/ta-p/73157 Lastly; I think you'll want to the using PsExec to test running
  15. I've also seen this error, related to the specific file I was trying to save in the Files folder of the Answer File. Confirm this by creating the pack first without any files, and save it. Then try adding the MSI and trying again.
  • Create New...