• Content count

  • Joined

  • Last visited

Everything posted by SmartDeploySupport

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. In addition to a number of fixes and performance improvements, SmartDeploy Enterprise v1.1.4000 and later supports UEFI enabled devices, such as the Microsoft Surface Pro 3. If you’re upgrading from a previous version of SmartDeploy, you may notice a few changes. We’ve prepared this blog post to help you understand what has changed in order to make your upgrade process as smooth as possible. Simple SmartDeploy upgrade Simply download and run the installer. That’s it! Your previous SmartDeploy license key automatically carries forward into the new version. If you need to install SmartDeploy on a different computer and do not have your license key on file, email Track your SmartDeploy license utilization SmartDeploy, like most enterprise software offerings, is licensed on a per-machine basis. You need a license for the total number of computers that you deploy with the software. You can login and see what devices that you’ve deployed through the SmartDeploy Licensing Portal. UEFI support requires Windows PE x64 There is a new dropdown available in Media Wizard to create x86 or x64 boot or deployment media. Support for UEFI requires an x64 WinPE environment, and this is now the default option in SmartDeploy. Optionally, you can still select an x86 environment to deploy x86 or x64 Windows operating systems to legacy devices. UEFI requires FAT32 media formatting UEFI is an industry standard replacement for legacy BIOS. All UEFI-enabled USB media must be formatted with a FAT32 file system. SmartDeploy has always used NTFS formatting for boot media but in order to support UEFI devices, we had to make this change. Existing customers that have WIMs or PPKs larger than 4GB should be aware of this change. As you may already realize, the FAT32 standard does not support single files larger than 4GB. If you select offline deployment media, SmartDeploy will automatically split WIMs that exceed the 4GB size limitation when you run the Media Wizard. However, if you have a PPK larger than 4GB, you will need to use individual PPKs. SmartDeploy can still process a Default.ppk file that is less than 4GB, but you no longer need to combine PPK files. Simply download each PPK and place them in the same directory. When you run the Media Wizard, browse to that directory and SmartDeploy will take care of the rest. Please note, if you’re currently using network (PXE) boot to distribute your boot image over WDS, or if you’re using USB boot media to point to an image that is stored on a mapped network drive, you don’t need to worry about 4GB FAT32 file size limitations. Your WIM files and Platform Packs will continue to work exactly as they did before. Download the latest Platform Packs We have updated nearly every PPK in the library to support the newer versions of our product as well as new drivers from the manufacturers. Please check the version of the PPK that you have against the latest version on the website. If there is a newer version available, it is recommended that you use that version. After you’ve updated you PPK library, simply re-run the Media Wizard before your next deployment.
  7. 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
  8. 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
  9. When you say you want to image via PDQ deploy, what do you mean? SmartDeploy does not integrate with PDQ deploy. Thanks, SmartDeploy Support
  10. 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
  11. Restart the machine back into the SmartDeploy boot environment and click Collect Logs. Save the zip to a USB/Network share then send it to support @ smartdeploy .com and refer this thread and we can take a look. Thanks, SmartDeploy Support
  12. Hello, Just to clarify, you upgraded from 1607 -> 1703, or built a brand new VM with the 1703 Windows 10 media and captured/deployed that? Does this happen on all devices or just a specific model? Thanks, SmartDeploy Support
  13. With unicast, it's essentially the same as 10 different user's trying to unzip a 10GB compressed file across the network. If that effects your network too much, then might just want to do multicast, or stagger the times at which the unicast deployments are happening. Below ~25 clients, mulitcast is supposed to be slower overall because Microsoft's WDS mulitcast first copies the image to the local disk, and it's then applied from there. But, it will only impact the network as a single file copy. Thanks, SmartDeploy Support
  14. Ensure you created your boot media with the HPElitePro600-800-G3-Windows7.ppk file selected. If you did, but also had many other packs selected, then try creating boot media with only the HPElitePro600-800-G3-Windows7.ppk file selected. If you still have issues, email your c:\smartdeploy\logs\media.log from where you ran the Media Wizard to support @ Thanks, SmartDeploy Support
  15. The only way I can think it would end up like that is you used the VMware "Easy Install", which automates Windows setup and forces Windows to use a single partition. Then perhaps this VM was upgraded from one version of Windows 10 to another, like 1511 to 1607, and that process created the 450MB recovery partition at the end of the drive. Can't really fix the partitions now. Would need to create a new VM, not use the Easy Install, I.e. just select "I will install the OS later". Once the VM is created attach the latest Windows 10 .iso and install Windows. Or, you can just use the SmartDeploy Build Wizard to create your VM. Thanks, SmartDeploy Support
  16. The console is expecting the partitions to be in the default Windows 10 order of a 500MB system and the rest of the drive as the boot partition. So, we've filed a bug to have the console find the correct index of the .wim that contains the Windows node and use the name of that Index. But, curious how your VM was created to end up with that partition structure? Thanks, SmartDeploy Support
  17. Can you run diskmgmt.msc in the VM this image was captured from and send us what it looks like? Thanks!
  18. Need the SmartDeploy.sdf, not SmartDeploy.log. Also, the image metadata would be helpful. Open the "SmartDeploy Enterprise Command Prompt" as admin, and run the following command against the image in question and send us the output. smartwim /info your.wim
  19. You could try right-clicking on that image and select refresh. If that doesn't work could you send the following to support @ and we'll take a look. c:\smartdeploy\logs\console.log c:\windows\system32\SmartDeploy.sdf Thanks, SmartDeploy Support
  20. Hi all, This just came up on an unrelated support thread, and I just wanted to let everyone know that as of several months ago, we've added several bugfixes and performance improvements to SmartDeploy to address this issue, so if you're experiencing it, go ahead and update to the latest version of SmartDeploy, recreate your media, and retry deployment, and let us know if the issue persists - support (at) Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  21. Hi there, Domain joining failures can occur for a variety of reasons relating to network connectivity, syntax, or user permissions. On a target device that has experienced this issue, boot to SmartDeploy media and click the Collect logs button. Save the resulting zip file to an external location, and send it to support (at) Once we have your logs in hand, we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  22. What error message are you receiving? Is this error happening when attempting to import your install image into the WDS role? If so, ensure when you captured your virtual reference machine you selected For Use With WDS. That will strip off any additional volumes such as the system reserve so you can import it into your WDS server. WDS only allows one volume images. Thanks, SmartDeploy Support
  23. Hi there, For reference, here is our white paper on how to integrate SmartDeploy with WDS - you'll want to make sure that you're adding the WIM that you captured to the Install Images node in WDS. If you're receiving this error while adding your image, this most likely indicates that your image file is invalid or corrupt. Please reach out to support (at) and we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  24. Hi there, There is a script to automate this process - you can review Network Deployment starting on P. 39 in the User's Guide. The section on deploying with Group Policy (which includes the script that you can download and modify to specify the host name) is on P. 43. If you have any questions or issues, please feel free to reach out to support (at) SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  25. Mark, Currently there is no plans on supporting capturing UEFI based VMs. You can capture a BIOS based VM, and then deploy to a BIOS or UEFI enabled machine. Thanks, SmartDeploy Support