Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Seattle Washington
  • Interests
    Deploying Windows with SmartDeploy

Recent Profile Visitors

9,981 profile views
  1. Hello Chad B, Unfortunately, the only way to confirm that an application pack properly deployed and installed would be to check on the target machine. If you're experiencing any issues with any of these custom application packs, please send a request to support@smartdeploy.com and we can further troubleshoot. -Chris M. SmartDeploy Support
  2. Aaron is quite right - whenever you create SmartDeploy media of any type and select an answer file, a copy of that answer file is written into the WindowsPE boot image. It is that copy of the answer file that is loaded when you boot to SmartDeploy media - the copy back on the console host is not involved. Thus, if you make any changes to the answer file, you also need to recreate your media. Likewise, if you update the SmartDeploy console version, you also need to update your media - otherwise the media would still be using the old version of Deploy Wizard to apply your image. For WDS bo
  3. Hi Tim, We do have customers ask about his every once in awhile. The reason we include Lenovo's and not Dell's or HP's is because the Lenovo utility is the only one that is good at detecting installed driver versions when those drivers have been installed via PnP. What I mean by that is that on a Dell Latitude 5490, where all the drivers are up to date via PnP, the Dell Command Update software will want to reinstall the same versions of the Intel Management Engine, Intel Ethernet, and Intel Wireless. This would be true if you used their SCCM pack as well. Always hoped this would improv
  4. Hi wsova, We'll want to see a complete logset to troubleshoot this further, and I've opened a support ticket with you to troubleshoot this further. Unfortunately, there is no single, specific answer to domain join failure, but broadly speaking, the failures tend to occur due to bad credentials, a bad FQDN for the domain, a bad Distinguished Name for a specified OU, or a failure to connect to a domain controller during the SPECIALIZE phase (which can occur with certain network adapters that fail to initialize without a reboot). The logs can usually tell us where to look, so that's wher
  5. Hi Dejeon, We will need to take a look at some deployment logs. Boot the 5480 from your SmartDeploy boot media and select Collect Logs. Save the resulting zip and send it to support@smartdeploy.com. The subject: 5480 Issues Be sure to reference this thread. Thanks, Devon SmartDeploy Support
  6. Hi Dave, When you push the Application Pack out to an endpoint, all of the files in the pack will be extracted to a folder on the target device, which can be referenced using the path variable [ApplicationsFolder]. So in this case, in the Arguments field, you can reference the MST with the path: [ApplicationsFolder]\Files\\FoxitPhantomPDF100_enu_Setup_Website_FCT.mst I've opened a ticket for you and will send you an email with this information shortly, so please follow up with us via email if you have any questions. Glenn SmartDeploy Support
  7. Hi Chin, Client machines should automatically update themselves. If they're not, then something is causing a disconnect in communication to the host. We can certainly take a closer look at this. Please submit a request to support@smartdeploy.com and we can further troubleshoot the issue. -Chris SmartDeploy Support
  8. Hello Brad H, We try our best to update the Platform Packs routinely, but generally our customers notify us if one needs to be updated or experience issues. If there is a Platform Pack you'd like us to update, please definitely submit a request including the make and model to support@smartdeploy.com and we can take a look. -Chris M. SmartDeploy Support
  9. Please see the following KB: https://support.smartdeploy.com/support/solutions/articles/48001064039-error-sysprep-was-not-able-to-validate-your-windows-installation- If you still have issues, email us at support@smartdeploy.com. Thanks, Devon SmartDeploy Support
  10. Hi all, If anyone reading this needs assistance scripting a custom computer name, please reach out to support@smartdeploy.com and we'll be happy to assist. Its feasibility depends on your specific scenario, but we'll be happy to assist if we can. Glenn SmartDeploy Support
  11. Hello Aaron@Shared, What we recommend doing is to install another instance of SmartDeploy on a physical workstation. Then you can create USB media, using your Answer File, Image, and Platform Pack via network shares from your main console host. If you have any further questions, please submit a request at support@smartdeploy.com -Chris M. SmartDeploy Support
  12. Hi Mark, Apologies for the delayed response. You can see this information in the Release Notes (available on the SmartDeploy.com portal or via the Tools view in the console), which will list when support for specific versions was added along with a new version of the SmartDeploy software. When a new version of Windows 10 is released, our testing process takes time, and depending on whether or not changes to the software need to be made, it may be a few weeks following general availability before we support that version. 1903 and 1909 did not require any changes to SmartDeploy to support
  13. Hi all, Yes, that is correct - SmartDeploy version 2.0.3080 was released today, and it does support Windows 10 Version 2004. Please note that as with any new version of Windows 10, we do not recommend performing in-place upgrades on an existing reference VM that was created with an older version of Windows 10 Version 2004. You should create a new, blank VM and install Windows 10 Version 2004 using OS media from an official Microsoft source (such as the VLSC or the Media Creation Tool) which includes that version. If you have already created a suitable reference VM and captured it usin
  14. Thanks! Yes, I do expect we'll be sending out an email to announce when Windows 10 Version 2004 is officially supported. Glenn SmartDeploy Support
  15. Hello, As of this writing, Windows 10 Version 2004 is not yet supported in SmartDeploy. Microsoft made several changes to the default partition structure which has required some changes on our end as well. We're working on a version that will support Windows 10 Version 2004, and it should be out in the next week or two. What you're describing sounds like a Sysprep error, which is interesting - it's not an error we've seen in our testing. We'd like to take a look at a logset from this deployment if you're willing to send one in - I'll reach out via email with instructions for that. If
  • Create New...