SmartDeploySupport

Administrators
  • Content count

    416
  • Joined

  • Last visited

Everything posted by SmartDeploySupport

  1. Hello, You'll want to check to make sure that you have a valid Multicast Transmission created on this WDS server. Right click on your install image and select Create Multicast Transmission, or delete the current one associated to your install image and recreate with the same steps. If you still encounter the same error, we have seen this if the .RWM is corrupted or associated to the wrong image somehow. - Delete your ImageGroup via the WDS interface - Create a new ImageGroup via the WDS interface - Import your Install image into the Imagegroup - Right click on your image and select "Create multi-cast transmission" - Attempt to re-deploy and say "Yes" when asked if it's a multicast transmission If the error code recurs, switch back to the SmartDeploy splash screen, click the Collect logs option, save the resulting zip file to an external location, and email it to us at support (at) smartdeploy.com - and be sure to reference this thread. Note that some organizations restrict sending zip files over email, so you may want to check with your IT department to make sure the email made it out with the attachment. Alternately, you can fill out our Support form, which includes a file upload option. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  2. Hi Chris, By design, the SmartDeploy console libraries must be in a [Drive]:\SmartDeploy folder on a local hard drive. That said, there's no requirement that you use the console libraries at all - when you download your Platform Packs, they will go to the default folder in the SmartDeploy directory (\Platform Packs), but you can certainly move them to a network share after that. When you use Media Wizard to create SmartDeploy media, and you're prompted to specify Platform Packs, you would just need to browse to the location where your Platform Packs are stored. Ditto your images, if you plan to store those on a network share as well. You'll need to test and make sure that you get reliable performance running through the usual SmartDeploy wizards with your files on a network share - we generally recommend keeping the files on a local hard drive when you're working with them (to avoid connectivity or authentication issues interfering with the process), but you may find that it works just fine in your network environment. Feel free to reach out if you have any questions or issues - support (at) smartdeploy.com. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  3. When you create the WDS boot wim, you are asked to provide answer file. If you need to made a change to the answer file, you will indeed need to create a new WDS boot wim with the new answer file, and re-import it to your WDS server.
  4. Hello, There's no limit that I'm aware of. It's possible there's a syntax error that's preventing the field from populating properly, or this could just be a limitation we haven't yet seen in testing. Go ahead and email us your answer file to support (at) smartdeploy.com, and we can take a look. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  5. Hi there, Thanks for reaching out. This behavior is definitely not expected - assuming you've supplied a valid UNC path and set of credentials, the image path and name (and description, if present) should be populated in those fields, and - since this is a multi-image WIM file, you would then have the option of selecting one of the other images from the dropdown. Assuming that - when this occurs - you are able to manually map the network drive and continue with the deployment, this most likely indicates that you simply made a typo when saving the credentials in the Answer File Wizard. Credentials are hashed and salted in the Answer File exactly as entered (they are not validated at that time), so any typos at this stage will result in the behavior that you describe - a failure to automatically map the network drive and select the image, but no issues with network connectivity otherwise, and you are able to proceed with mapping the drive and selecting the image manually. To resolve the issue, right-click the answer file in the Answer File Library, and click Edit. Then re-save the answer file, either overwriting the answer file or saving a new one (safer option), carefully re-entering the credentials when prompted. Note that you will need to edit the newly saved answer file in Notepad and set the Skip values to "1" (for each page that you wish to skip) as you did before. Then recreate your media and retry deployment. Feel free to reach out by email if the issue persists - you can reach us at support (at) smartdeploy.com, and be sure to reference this thread. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  6. Hi Dave, This is a known but in 2.0.2080 and is fixed in an internal build we are testing. The next release should be out in the next week. Sorry for the inconvenience, SmartDeploy Support
  7. Hi Sigmaphi, You will want to refer back to the virtual reference machine that the image is created based on, then make your edits, then recapture/deploy the updated image. That is the supported way to edit your image. Thanks, SmartDeploy Support
  8. Thanks for the feedback. I will forward this thread to the dev team. I know we have a lot on the road map, but we can see what we can do. Thanks, SmartDeploy Support
  9. Hi all, Quick update on this - we have confirmed that Disk Cleanup removes the C:\Windows\Panther folder, which (in the current SmartDeploy version, 2.0.2080) causes Deploy Wizard to fail to create the Windows Unattend.xml file in that location, which causes Sysprep and deployment to fail. The key indicator that you've experienced this issue is - if you use the Collect Logs function in SmartDeploy PE, there is no [OS-drive]:\Windows\Panther directory included. Apologies for the inconvenience; this will be fixed in the next SmartDeploy version (release date TBA, but it should be soon). In the meantime, the easiest workaround for this would be to power on your reference VM, browse to the C:\Windows directory, and create a new folder called Panther. Then recapture and redeploy. If you'd prefer not to recapture your image, you can use our smartwim command line tool to mount your existing image file offline and add this folder - email us at support (at) smartdeploy.com if you'd prefer to go that route, and we can send you instructions. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  10. Hello all, We've received several reports about this issue, and are currently investigating it internally. The common thread so far seems to be that users have upgraded their reference VMs from a previous Windows 10 version to 1703, then run Disk Cleanup. We're testing to reproduce the issue internally, and should hopefully have a fix available soon. In the meantime, if anyone runs into this issue, please email us at support (at) smartdeploy.com, and reference this thread. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  11. Hello, We will need some logs to investigate further. Restart the machine back into the SmartDeploy boot environment and click Collect Logs. Save that zip file to a USB/Network share and send it to support @ smartdeploy .com and reference this thread. Thanks, SmartDeploy Support
  12. Hello, Setting a static IP is a standard option in Deploy Wizard (and can be automated with the use of an answer file, although it is typically a manual step, as the static IP address would typically vary between target devices). No advance preparation needs to be done to the VM prior to capture, as this is a setting that is applied per target device. However, if you're performing a network-based deployment, you would also need to set a static IP address in the SmartDeploy WindowsPE environment, which can be done via the Settings option on the SmartDeploy splash screen. If you have any further questions on this setup, please feel free to email us at support (at) smartdeploy.com, and be sure to reference this thread. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  13. 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
  14. 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
  15. 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
  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. 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
  18. 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 licensing@smartdeploy.com. 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.
  19. 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
  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. When you say you want to image via PDQ deploy, what do you mean? SmartDeploy does not integrate with PDQ deploy. Thanks, SmartDeploy Support
  22. 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
  23. 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
  24. 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
  25. 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