All Activity

This stream auto-updates   

  1. Yesterday
  2. Ok so i was able to update smart deploy, re capture, recreate my boot media and import into WDS. I now receive an error stating that "the platform pack location does not contain support for this computer manufacturer, model and operating system." I have been deploying these machines over the last month with no issues regarding platform packs. Kinda not a good place to be when you have to image 18+ machines before the end of the week.
  3. Hi GCW, Here's a list of ports we use, if you'd like to monitor those and confirm the traffic is coming from our services. TCP 80 - HTTP TCP 443 - HTTPS TCP 8732 - ConsoleServiceWCF TCP 8733 - ClientServiceWCF TCP 8734 - ConsoleServiceSLWCF TCP 8735 - ConsoleServiceMCWCF If you're seeing what seems to be an unusual level of traffic on these ports, go ahead and reach out to us via email, and we can troubleshoot in more detail. support (at) Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  4. Only thing plugged in is a keyboard and mouse. I will try a reboot with no devices plugged in. My smartdeploy app is version 2.0.2050 I am going to try updating to 2.0.2080 and recapturing again.
  5. We have seen this issue with some machines if there is any USB devices connected after the first restart (When the Deploy Wizard finishes). If you haven't already, try removing any USB storage devices from the target machine after the Deploy Wizard finishes and let us know your results. Thanks, SmartDeploy Support
  6. Im having a bit of a strange issue on a new image i am rolling out. After smart deploy finishes its deployment, windows displays a "Just A Moment" message as if it is finishing updates. I let a machine run for about 2 hours yesterday and nothing changed. I tried again this morning with a fresh capture and Media, but the issue still persists. Has anyone else ran into issues with deployments since the creator update recently? Background information: The image is a windows 10 post windows creator update deployed with WDS. I copied the VM from an existing image and made a few changes and ran updates. I rebooted and checked for updates a few times to make sure that the VM has no pending updates and is ready to be captured. I have captured the machine 4 times so far using smartdeploy bootable media and the normal smartdeploy application capture mode. The only difference between the new and old images is windows updates. Any idesas? Thanks
  7. Last week
  8. The agent for windows appears to communicate frequently with the SmartDeploy Server. How do we configure the agent settings to reduce this unnecessary network traffic? Our network team is concerned with the volume of apparently useless traffic being generated by all of these agents. What port, protocol, frequency, etc. does it use? What does the agent actually do that it needs constant communication to the server?
  9. This is also a common issue in my environment. There are times when it will deploy so I know that my settings should be correct, but lately it just hangs after i've clicked "Deploy Now." It shows the icon that it is imaging, but upon checking the end-user's computer, no imaging is initiated. I also do not receive any error. Any ideas?
  10. 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
  11. 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
  12. 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
  13. 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?
  14. Earlier
  15. Thank you! Email has been sent!
  16. 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
  17. 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.
  18. 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) Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  19. 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
  20. 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
  21. 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.
  22. (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)
  23. Did anyone find out an solution for this issue. My error code is 3240165637 when trying to multicast. I can unicast fine. Help!!!!!!
  24. Awesome thanks
  25. Hey EBurnett, I'm interested in your problem deploying with the 7370 platform pack. If you like, please email us at "support (at)" with some more details and we can work to find the cause of the problem with that pack. Thanks, SmartDeploy Support
  26. Here's the log from the last test deployment. Thanx! Deploy.log
  27. 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.
  28. 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
  1. Load more activity