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. 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.
  2. 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\Uninstall\{E799CA03-7E46-4AE7-A7B6-E904CCFD1529}VMware: HKLM\SYSTEM\ControlSet001\Services\VMToolsVMware: HKLM\SYSTEM\ControlSet001\Services\VMwareToolsVMware: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FE2F6A2C-196E-4210-9C04-2B1BC21F07EF}VMware: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{96B74176-0BA4-4F5D-B3A5-466EAD9E73BD}Oracle: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Oracle VM VirtualBox Guest Additions
  3. 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.
  4. 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
  5. 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 look at what the client is doing.
  6. 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.
  7. 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 into BIOS and set the name Windows needs to use, and then boot into SmartDeploy and let the unattended deployment do it's thing. While those work, I'd get to unboxing the next round. You can also configure your Answer File to shut down after the initial deployment. This will allow you to grind through the first stage a bit faster. Then, as you need to deliver laptops to any person, or lab, the next time you turn them on, they'll complete the sysprep portion of the deployment.
  8. 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 isn't externally accessible from the internet. Lastly, you may need to block access to your console host via VPN if you want to use the remote/cloud deployments. (You can create a CNAME alias for you to use as an administrator if you need to RDP to the host yourself.) This is because the clients need to fail to reach the console host to switch to the cloud. If they can reach the host, it can get stuck in a semi-functional state, and fail to appear in the console.
  9. 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.
  10. 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 this command line installation as System, as it will be installed by SmartDeploy. You will be able to test your install parameters and package a lot faster. Then once you get it, you can put it in an Application Pack. This process is detailed in this article: (At the bottom) https://support.smartdeploy.com/support/solutions/articles/48001062096-troubleshooting-application-pack-deployments
  11. 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.
  12. Please reach out to support either via email, (support@smartdeploy.com) or the ticket for to request this script; https://support.smartdeploy.com/support/tickets/new
  13. You want to download the O365 source files ahead of time, and include them in the Application Pack. Then you would be running the command "setup.exe /configure configuration.xml" in the app pack, with your custom XML.
  14. We'd have to see some logs, but when the Deploy wizard prompts for an image, it's because the credentials saved in the Answer File are no longer valid, the deployment media was made without the updated Answer File, or there's a networking issue in SmartPE. Are you saying that you deployed with USB media, and following that the machine appeared in Computer Management, but you're not able to deploy an image then? We'd need to know more about this scenario. Is the client local or cloud, not connected via VPN, etc. Would be best to reach out to support via email or the form for investigating.
  15. I would first check that all traffic to *.smartdeploy.com is allowed, and that the traffic there is exempt from SSL Inspection.
  • Create New...