Jump to content
DeployCentral

Jeff Harris

Administrators
  • Content Count

    172
  • 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. This morning I checked for updates on the virtual machine that I re-produced this sysprep error, a cumulative update (KB4512508) was available. I installed this and found that my VM was once again able to sysprep.
  2. I've confirmed that this update does indeed break sysprep. I've circulated logs with the team, we'll take a look at it but it may be up to Microsoft to correct this. Until then we'll have to ask users to rollback the update before capturing their image.
  3. Dave, First, you'll want to make sure that the client you're pushing the app pack too appears in the Computer Management workspace with bold text. This indicates that the connection is healthy. When you deploy an application pack, it's copied to the client, and extracted to C:\Windows\Temp\!sdspk\Application Manager\appname\Files. You can watch that folder to confirm that the installer files are being copied over and extracted correctly. If they are, then that's a good indication that something is holding up the installation process, or that the arguments in the pack are incorrect and it's not silently installing.
  4. When deploying applications with App Packs, the best place to look for troubleshooting is the Application log on the target machine. That's a good sign that the pack is being copied to the \Windows\sysWOW64\SmartDeploy\Sources\ folder. Since 2.0.3050, the location of extraction is now C:\Windows\Temp\!sdspk\Application Manager\appname\Files. Are other Application Packs installing successfully?
  5. I'd download the SDESetup.exe from SmartDeploy.com again, and confirm that it's 1,395,359KB on disk. Then right-click the exe and click Properties to check for an Unblock button on the General Tab. If it's there, click it and then click OK and try again, Additionally, different anti-virus and other security software has been known to block or partially block the installation, so it may be worth while to temporarily disable it while you install.
  6. You can email support and we can provide you with a script that will handle this for you.
  7. You'd first want to make sure you're able to sun the installation via command line on a test client, which a successful silent installation. Then try making a new pack, filling out all the informational fields and saving it before you add files. Then add the installation files and the set up the executable path, save, and try again. At deployment; .spk files are copied to the C:\Windows\SysWOW64\SmartDeploy\Sources folder, and extracted to the C:\Windows\Temp\SmartDeploy\Scratch folder where the installation is then run on the target machine. Also, it's always worth a test to deploy one of the application packs we provide for download to make sure that App Deployment is working correctly.
  8. The first thing you should do if you haven't, is test an Application Package available for download from the console. This will make sure that the service is working as intended, then you can dig into why your custom pack isn't working. The next step is to try your App Pack deployment, watching the C:\Windows\Temp\SmartDeploy\Scratch folder on the target. Your App Pack contents will be extracted here. (It's removed after the install, or after a failure.) If you see the folder appear here, then you know your app pack is being copied and extracted successfully. This means that there's a problem with your syntax, or something else is blocking the installation. At this point, you can contact Support and send in your App Pack for us to test and we can see if it's related to your target, or the App Pack itself.
  9. In the Application Manager window you have in your screenshot, right-click the Files node on the left, and click Add File to add your MSI file. Then, to the right of the executable location click Select, and select the msi file. This should automatically change your executable location in that field. Then edit it so that it looks like this; msiexec.exe /i "[ApplicationsFolder]\Zoom Video Conferencing\Files\ZoomInstallerFull.msi" You can leave your arguments as-in in the arguments field, and then you should see a successful deployment of the application.
  10. You'd need an XML file, with the instructions for excluding files. I've attached a sample. Then you'd edit your SmartDeploy Answer File, the migration section specifically, to add additional scanState arguments, as below: Exclude-Sample.xml
  11. In the Answer File Wizard, you'd move the WMI query to the top of the list, and set the query to SELECT SerialNumber FROM Win32_SystemEnclosure
  12. When deploying in UEFI mode, you'll want Secure boot to be enabled. Sorry, we do not have a BIOS settings matrix, no.
  13. When investigating why USMT is failing, you'd want to look at the ScanState log file, which would go in C:\Wndows\Temp on the target computer. If you're initiating the capture from the console, make sure that you've checked the box for "ignore access errors."
  14. Hey Dale - When you capture your image, you have an opportunity to specify the Windows product key. If you do, the Answer File Wizard will detect this, and won't ask you for it again. You'll need to re-capture the image, to a new WIM file. If you prefer, you can skip the key in the Capture Wizard, and instead put it in the Answer File, where it will be easier to change going forward should you need too.
×
×
  • Create New...