SmartDeploySupport

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

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

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

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

When you say you want to image via PDQ deploy, what do you mean? SmartDeploy does not integrate with PDQ deploy. Thanks, SmartDeploy Support

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

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

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

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

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 @ smartdeploy.com Thanks, SmartDeploy Support

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

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

Can you run diskmgmt.msc in the VM this image was captured from and send us what it looks like? Thanks!

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

You could try right-clicking on that image and select refresh. If that doesn't work could you send the following to support @ smartdeploy.com and we'll take a look. c:\smartdeploy\logs\console.log c:\windows\system32\SmartDeploy.sdf Thanks, SmartDeploy Support

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) smartdeploy.com. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

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) smartdeploy.com. 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

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

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. https://www.smartdeploy.com/wp-content/uploads/SmartDeploy_WDS.pdf 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) smartdeploy.com and we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

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.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

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

Hello, We have seen this if the virtual machine was updating the Windows Store applications during the capture process. Try starting your virtual reference machine, running Windows Updates, then open the Windows Store and update all the applications there as well. You may have to restart a couple of times and keep updating until all updates are complete. Then capture/deploy and let us know your results. Thanks, SmartDeploy Support

We have not received any reports of this effecting deployment and the above way would be the supported way to customize your Windows 10 desktop when copying the default profile. Thanks, SmartDeploy Support

https://www.smartdeploy.com/download/smartdeploy/ Thanks, SmartDeploy Support

Hi Mike, A remote/web interface feature is not implemented into the product. Currently, there is nothing on the roadmap to change this. You can however install the SmartDeploy tools on as many machines as you would like without any licensing issues since licenses are based on deployments, not tool installations. So, essentially, you could install the tools on another machine and just give them access to that server if you don't want them accessing the WDS role. Thanks, SmartDeploy Support