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. 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.
  2. 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
  3. 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.
  4. 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
  5. 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.
  6. 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.
  7. I would first check that all traffic to *.smartdeploy.com is allowed, and that the traffic there is exempt from SSL Inspection.
  8. In cases like this, if you're going to place any scripts or files to run as tasks, it's best to put them in a folder such as C:\Temp\.
  9. That is correct; we are working on how to better address a previously failed Application Pack deployment. The presence of the !sdspk folder in C:\Windows\Temp\ is a good indication that an installation is stuck, along with any files in the C:\Windows\syswow64\SmartDeploy\sources folder. We do check for those when we're troubleshooting any deployments.
  10. First I’d check the Application log in Event Viewer for any errors related to SmartDeploy. You may need to reach out to Support depending on what you see. Additionally, check this URL for port information and some powershell commands to test them. https://support.smartdeploy.com/support/solutions/articles/48000968329-which-ports-are-required-by-smartdeploy-
  11. First, I would check C:\Platform on the target system to make sure the Platform Pack was copied there. Then check the System log in Event Viewer so see if drivers are being injected.
  12. This is likely due to a problem with the certificates created by SmartDeploy. Unfortunately you'll need to clear them out and re-install SmartDeploy to repair this issue. Uninstall SmartDeploy. Click Start, search for Certificates, click on Manage computer certificates In the left pane, browse to Certificates - Local Computer | Personal | Certificates In the center pane, locate the certificate that shows SmartDeploy Console/Client Service Root CA in the Issued By column. Right-click this certificate | Delete, and confirm deletion if prompted. In the left pane, browse to Certificates - Local Computer | Trusted Root Certification Authorities | Certificates. In the center pane, locate the certificate that shows SmartDeploy Console/Client Service Root CA in the Issued By column. Right-click this certificate | Delete, and confirm deletion if prompted. Close the certificates console, then reboot the computer and re-install SmartDeploy
  13. Please email support with your company email, and we can assist in helping you. Your additional users should be able to provide the email address that you currently use to log into SmartDeploy. You'll receive an email to approve the addition of their accounts.
  14. Our Platform Pack download endpoints are hosted in Azure, and thus we don't have much in the way of investigating bandwidth. Are any other packs downloading as slow?
  15. 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.
  • Create New...