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

10,281 profile views
  1. Hi Jemin, The short answer is no - enabling kiosk mode is not a SmartDeploy product feature, but there are several options available for this, and we will follow-up via email with more details. Glenn SmartDeploy Support
  2. Hi Aaron, Unfortunately, we were not able to reproduce this issue. We'll be in touch via email. Glenn SmartDeploy Support
  3. Hello, How are you changing the language now? Through the answer file and it's not working? Do you have the United Kingdom Language Pack installed on your image? Try setting the language via a post image task. In this example the script would use the following: Set-WinSystemLocale en-GB Set-WinUserLanguageList en-GB -Force Then if your script is in C:\Temp\MyScript.ps1 the task command would look like: Powershell.exe -NoProfile -NonInteractive -ExecutionPolicy bypass -file C:\Temp\MyScript.ps1 If you still have issues, email us at support@smartdeploy.com a
  4. Hi Aaron, That's no problem - I'll send you an email shortly - please note you can always submit logsets via email (support@smartdeploy.com) or the Support Form : https://support.smartdeploy.com/support/tickets/new If a file exceeds 20MB, just shoot us an email and let us know, and we can provide a method for you to submit it. Glenn SmartDeploy Support
  5. Hello, Please email us at support@smartdeploy.com and we can get your account created. Thanks, Devon SmartDeploy Support
  6. Hi Aaron, Ah, you had referred to imaging "through the Console" so I assumed you meant console-initiated deployment (from the Computer Management view). I'd suggest you try the same thing for WDS - build a new answer file, build new WDS boot media, replace the boot image in the Boot Images node on the WDS server, and retry deployment. If the issue persists, go ahead and pull a logset (you can do this by booting back to your SmartDeploy media, canceling any pending deployment, and clicking Collect Logs. Save the zip file to an external location (such as a USB stick), and submit it via the
  7. Hi Aaron, This appears to be a photo of a WindowsPE environment - is that right? So if I understand the issue correctly, you're still able to initiate deployments from the console, and your endpoints reboot into SmartPE, but then they throw this error? Does Deploy Wizard launch and does the deployment proceed, or does it halt with this error? If you click Deploy an image, does the deployment proceed? From the text of the error, I'd say the most likely issue here is a syntax problem in your answer file. Try re-running Answer File Wizard to create a brand new one (do not edit the previo
  8. This can't hurt, but it is not necessarily required. Some Platform Packs include additional WindowsPE drivers (which may be needed for the Ethernet or Storage controllers, or occasionally other components), for the device to have full functionality while deploying in WindowsPE. If you're adding support for a model whose pack contains WindowsPE drivers, then you must indeed recreate your media, selecting Platform Packs for all devices you plan to support, so that these new PE drivers can be injected automatically into the WindowsPE boot image. Then replace the boot image on the WDS server, and
  9. Andejo5, 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
  10. Sorry about that, missed you were saying letters. The hash signs are random numbers, don't believe we don't have a way of doing random letters.
  11. The hash signs do represent random characters.
  12. 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
  13. 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
  14. 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
  15. 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
  • Create New...