SmartDeploySupport

Administrators
  • Content count

    404
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

6,283 profile views
  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) smartdeploy.com 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) smartdeploy.com Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  6. 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
  7. 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
  8. When you say you want to image via PDQ deploy, what do you mean? SmartDeploy does not integrate with PDQ deploy. Thanks, SmartDeploy Support
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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