SmartDeploySupport

Very interesting. We'll test, and if that is the case, we can certainly include those files. Thanks!

Many of these update programs verify the installed version by looking for application or registry entries left by running the install packages. For the most part with SmartDeploy we install device drivers via Plug-n-Play. Lenovo's System Update tool for example used to have this same issue, buy they have updated it to actually check the installed driver versions, so it works fine now. No real way to fix HP's tool, unless they change it to query actual driver versions. Thanks, SmartDeploy Support Team

Hi Stephen, Have you successfully performed any console-initiated deployments? If so - was this on clients that are on the same network and subnet as the ones that are currently failing? Are all of the clients running the same version of the SmartDeploy client as the console version that you have installed? You can check the client version in the Computer Management view, or in Programs and Features on the target device. You can check the console version in the Tools view of the console. If any devices are running outdated version of the client, they will need to be updated. That should occur automatically, but you can uninstall and reinstall the client manually if needed. See P. 40 of the User's Guide for details on how to locate and install the client. As for the USB device failing to boot, that may indicate a hardware problem with the target device, or with your USB media - or a problem with the boot settings in the BIOS of the target device. Try changing the variables a bit: different USB stick, different port, different device - determine whether it's a persistent problem on all devices, or confined to a single unit. Depending on those answers, we can advise further. If you're unable to resolve the connectivity problem with your console-initiated deployments, go ahead and email us at support (at) smartdeploy.com (and be sure to reference this thread), and we can help troubleshoot this further. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Try capturing the VM while it’s powered on. You will mount the SmartDeploy_x64.iso to the VM, boot to it and select the capture option. This process is documented on page 76 in our User Guide Thanks, SmartDeploy Support

Hi Kirk, We did change the way databases are stored to localdb, which may take a bit to re-populate. Did they eventually show up? If not, open an administrative command prompt and type: net stop sdeconsoleservice Go to C:\Windows\System32\ and send us the following files: SmartDeploy.mdf SmartDeploy.sdf SmartDeploy_log.ldf Send to support @ smartDeploy .com Thanks, SmartDeploy Support

Hi there, We added this check and warning for the Windows ADK installation to the latest version of SmartDeploy, to prevent users from running Media Wizard without the ADK installed, as this will lead to a common failure. At present, it only checks for the ADK in the default install location. However, we have received feedback like this from other users who have it installed on a secondary hard drive, so we will be widening this check to look for the ADK in any valid install location (as recorded in the registry) in a future version. In the meantime, the workaround would be to uninstall the ADK and reinstall it in the default location on C:\. The three required components would be Deployment Tools, WindowsPE, and the User State Migration Tools. You can run the installer from here (1703 is fine at this time): https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit Sorry for any inconvenience, and please let us know if you have any questions or issues - you can reach us at support (at) smartdeploy.com. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Hi Stephen, Thanks for reaching out. You're correct about how the hash signs work - they are essentially random, and if you're only using two digits, there's a good chance you will get some repeats. It's possible this will change in the future, but at this time, each deployment is a discrete event that is unaware of the others, and there is no mechanism that would allow for sequential computer naming other than manually entering the computer name for each deployment. Many of our users have found this to be a practical workaround, however - rather than using an unattended answer file, you can use an attended answer file and skip every Deploy Wizard page besides the one that you need to modify per-deployment (Network Identification in this case). You can find guidance for how to update your answer file to skip Deploy Wizard pages at the very end of the User's Guide. Go ahead and email us at support (at) smartdeploy.com if you have any questions or issues. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Hi Baz, We'll need to see a log set from the deployed device to be sure what's happening here. Boot to SmartDeploy media on the affected device, click the Collect logs option, save the resulting zip file to an external location, and send with your reply. 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

Hello, Please update to SmartDeploy v2.0.2090 and try your deployment again.

Yes, you will need to create new boot media each time you update SmartDeploy.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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