All Activity

This stream auto-updates   

  1. Last week
  2. Hi there, I guess this is a feature enhancement request. I think it would be useful to be able to apply a platform pack to an existing device without having to image it. It would be a helpful way to get drivers updated on a device. It would be cool if you could double click on the platform pack and it would update all the drivers. Additionally, it would be equally cool to be able to send out the platform pack via the console so you could update drivers on your remote devices without having to image the device and wipe everything out. Just a suggestion. Thanks for listening. Barry Weiss
  3. Hello, I started the trial with build 2060 and saw a fix related to languages in build 2080 so I upgraded, recaptured the image and recreated the WDS boot image and I still have the same issue. Here are the relevant tasks I run: <task> <phase>FIRSTBOOT</phase> <command>C:\Windows\System32\lpksetup.exe /i fr-FR en-GB en-US /r /s /p C:\Template\LP</command> </task> <task> <phase>FIRSTBOOT</phase> <command>C:\Windows\System32\reg.exe import C:\Template\International.reg</command> </task> <task> <phase>FIRSTBOOT</phase> <command>C:\Windows\System32\reg.exe import C:\Template\Keyboard.reg</command> </task> I copied the language packs in C:\Template\LP and the 2 registry files are attached to this post. I'm not sure if this is relevant, but the unattend.xml file in C:\Windows\Panther is showing en-US as the InputLocale, SystemLocale, UILanguage and UserLocale. International.reg Keyboard.reg
  4. Hello, What version of SmartDeploy are you running? Also, can you let us know your task command as well as the phase? Thanks, SmartDeploy Support
  5. Hello, SmartDeploy is completly ignoring any regional settings I set. The default user config of the reference VM, the keyboard layout and regional settings are all reset to en-US. I've tried to set it in the answer file but there is no granularity and the parameter is completly ignored. I've tried to manually edit the answer file with your blog post information : <regional_settings skip="0"> <time_zone>(GMT+01:00) Brussels, Copenhagen, Madrid, Paris</time_zone> <input_locale> <ui_language>en-US</ui_language> <system_locale>fr-FR</system_locale> <user_locale>fr-FR</user_locale> <input_locale>fr-FR</input_locale> </input_locale> </regional_settings> But that gets ignored as well (the timezone is set but the rest is discarded). I've tried to use a task to import a reg file in HKEY_USERS/.DEFAULT but it seems to be overwritten. I'm deploying using WDS. How can I specify my regional settings?
  6. Thank you! Email has been sent!
  7. Hi there, Sure - shoot us an email and we'll send you a script that will accomplish this. Please be sure to reference this thread. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  8. Could you share how to autologin to a user after the machine is imaged? I set the machine to do it in the base image but I believe sysprep wipes away those settings. Being after the image is completed, I am sitting at the login screen.
  9. Earlier
  10. Hi Daniel, The local administrator account is automatically deactivated as a part of the Windows Sysprep process, but you can override this behavior using the checkbox in the Deploy Wizard (or Answer File Wizard) advanced options. You have an opportunity to set a local administrator password when you capture the image - an optional field in which to enter a password, and this will be hashed and stored inside the image. It is possible to set up automatic logon with a script during the POSTIMAGE phase (which, as you indicated, does require the password to be stored in plaintext), but it really shouldn't be necessary for the tasks you've indicated here - activating Windows and Office can be done via Tasks as well. In the Deploy Wizard (or Answer File Wizard) advanced options: · Click Tasks tab · Click Add · Select First Boot as System for the phase · For Command Line type the following: (for Office Activation) cscript.exe "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs /act" (note that you may need to change Office14 to whichever the correct install folder is for your Office version) · Click OK · Click Add · Select First Boot as System for the phase · For Command Line type the following: (For Windows Activation) cscript.exe c:\windows\system32\slmgr.vbs /ato · Click OK · Proceed through deployment wizard and proceed to deploy. You mentioned there were "a couple other build tasks" you were looking to do - if you want to avoid using the autologon script with the plaintext password, you'll want to figure out how to script those in an unattended manner, and run them during FIRSTBOOT. If there's a particular setup task you're looking to accomplish and aren't sure how to proceed (or if you'd like to try the autologon script anyway), shoot us an email with details (and reference this thread) and we can advise further - support (at) smartdeploy.com Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  11. also having this issue at the moment... frustrating... I was working fine most of the day yesterday and all of a sudden computers can't map the drive
  12. Hi, I am trying to get the deployed machine (windows 7 x64) to log on as local administrator after deployment. This is to activate windows and MS office and perform a couple of other post build tasks. I cannot store the password in plain text. I did see an article from 2013 explaining how to do this but the passwords were required to be entered in plain txt. Is there an alternate way to do this? Kind Regards
  13. I received an email about v2.0.2070 available, I previously skipped over v 2.0.2040. I'm up to date prior to that. Do I need to create new boot media for any supported version of Windows or update any of my images when upgrading to v2.0.2070? NOTE: We currently use 2 deployment methods, one via WDS for PXE booting and the other for booting from CD/DVD.
  14. (Passing thru) - I believe (correct me if I'm wrong) as long as you boot UEFI and setup, you're golden. If you're trying to set up the disk for GPT, shift+f10 (diskpart, convert GPT) after language selection. I haven't checked GUIDs, but my boots show up as UEFI (didn't have to do anything fancy VM - just add programs and capture)
  15. Did anyone find out an solution for this issue. My error code is 3240165637 when trying to multicast. I can unicast fine. Help!!!!!!
  16. Awesome thanks
  17. Hey EBurnett, I'm interested in your problem deploying with the 7370 platform pack. If you like, please email us at "support (at) smartdeploy.com" with some more details and we can work to find the cause of the problem with that pack. Thanks, SmartDeploy Support
  18. Here's the log from the last test deployment. Thanx! Deploy.log
  19. Will be interesting if you get around that m.2 - We have a unit that (I believe) the firmware is not updated causing the drive not to be recognized, and we have no plans going forward stepping back for this model to legacy OS. But on another unit, properly patched m.2 (was already updated) works like any other drive. My issue is with the package on SD site, something in the 7370 package is hosing my deploy, was hoping for a forum thread to report an issue with packages - Once I add the 7370 package I get stuck at getting ready screen, never finishes - without package, SD deploys.
  20. Please send us your C:\Windows\Debug\Deploy.log from the deployed machine and we can take a look. support @ smartdeploy .com Thanks, SmartDeploy Support
  21. We have been trying to resolve this for over a month now. After a deployment, the Start menu is full of broken tiles and links. This has been reported in other threads and across the Internet, but we have not been able to resolve the issue after trying everything posted elsewhere. We even went so far as to create a fresh VM, disable the NIC, install Windows 10 1703 fresh, make a fresh image, and deploy that to no avail. The broken links still show up after the machine is deployed. On a broken deployment, if we run a Windows 10 "Upgrade" Install from the Windows DVD, that will resolve the issue for that machine, but this is not a viable option when trying to deploy Windows to 100+ computers... How do we resolve this definitively at the time of deployment? What is the Windows 10 "Upgrade" doing that fixes the machine, and is there a way to run that after the image is dropped?
  22. Sorry that is not what I meant....I used PDQ Deploy to send out a job to install the SDE client, that's all. I then work with SmartDeploy to try and deploy my image. Sorry for the confusion.
  23. When you say you want to image via PDQ deploy, what do you mean? SmartDeploy does not integrate with PDQ deploy. Thanks, SmartDeploy Support
  24. I have installed the SD Client on the machines I want to image via PDQ Deploy. The machines show up under Computer Management in SmartDeploy no problem and not grayed out. I right click on a single tower and select "deploy now" Nothing happens. Logs attached. WIN7-026 7_6_2017 2_59_48 PM.log WIN7-026 7_6_2017 3_14_00 PM.log WIN7-026 7_6_2017 3_30_12 PM.log WIN7-026 7_6_2017 10_00_07 AM.log WIN7-026 7_6_2017 10_23_28 AM.log WIN7-026 7_6_2017 10_36_41 AM.log
  25. I am having the same issue. You will have to go back to the boot options and turn legacy method ON. I will post a new thread to see if I can modify anything (answer file, etc.) in order to have the image automatically boot without this issue.
  26. I am having the same issue. Is there a command line that can be executed on each target computer from PDQ Deploy (not group policy) that will tell each PC the Host name. I have copied the SD Client to all my target computers but I still have to remote in to launch the client and enter the Host name.
  27. Hello, Please restart the machine back into the boot environment and click the Collect Logs button. Save that zip to a USB/Network share and send it to support @ smartdeploy .com. Refer to this thread in the email. Thanks, SmartDeploy Support
  1. Load more activity