SmartDeploySupport

Please email the c:\smartdeploy\logs\media.log to support @ smartdeploy.com and we'll take a look. Thanks, SmartDeploy Support

No. Just need to ensure you create boot media from that pack so the drivers can get added to the boot environment. Thanks, SmartDeploy Support

We've just updated and combined the X1 Carbon 4th and Yoga 1st packs. Delete the X1 packs you have, then download the latest. Re-create your boot media using this latest pack. Thanks, SmartDeploy Support

***Update 11/23/2016*** Hello all, We've identified the cause of this issue on the Precision 5510 and certain other new Dell models. It appears to be an issue with a specific version of bootmgr (present in SmartDeploy v2.0.2020 and earlier). Now that we've identified this issue, we'll be fixing this in our next service release of SmartDeploy. In the meantime, if anyone runs into this issue: 1. Check for SmartDeploy updates, as it's possible we've released a new version since this thread was updated. Download and install the latest version, then recreate your SmartDeploy media and retry deployment. https://www.smartdeploy.com/download/smartdeploy 2. If you're on the latest version and the issue persists, please email us at support (at) smartdeploy.com and reference this thread. SmartDeploy Support

Correct on all counts. If you set up multiple SmartDeploy workstations (at different locations, or even at the same location) with the same license key, any devices that you deploy using SmartDeploy media created on either of those workstations would count toward your license total. What you're describing is the recommended setup, yes. When you install the SmartDeploy push client (which is an option in the Deploy Wizard advanced options), you would specify a hostname or IP address for the SmartDeploy console that those devices will communicate with. Depending on your network architecture, it's conceivable that you could point all of your devices to the same SmartDeploy console and initiate deployments from them (you would need to test this setup to be sure), but we would recommend pushing separate deployment packages to each office's devices, which point to a network location that's actually at the office where the device will be deployed. Computer Management does allow you to arrange computers in groups. So if your testing determines that you can initiate deployment commands from one location at another, you could select (or multiselect) all of the Brazil devices and initiate deployment of the "Windows 7 - Brazil" deployment package (pointing to a .wim file located on \\BrazilServer), then select all of the US devices and initiate deployment of "Windows 7 - USA" (located on \\USAServer), etc. May be easier to just set up separate SmartDeploy workstations at each office - but that just depends on your preferences and infrastructure. Please let us know if we can assist with anything else. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, SmartDeploy only supports changing the SmartDeploy to local physical drives. We do this because capturing VMs across the network doesn't always work out due to latency, network configurations, etc. That being said, you do not have to use the SmartDeploy folder structure. We just provide it for organizational purposes. You can store you files anywhere, but again, we don't recommend capturing from other locations other than physical drives. Thanks, SmartDeploy Support

Hi Roger, Staging the image on a local network share is definitely a recommended option. SmartDeploy is licensed per target device, so if it makes practical sense to actually create the images at each local office on their own SmartDeploy setup, you could do that without consuming an additional license for each SmartDeploy workstation (just for any client devices deployed using media created from those workstations). Conversely, if it's more practical to create the image(s) at a central office, you would need to get the image to each of your branch offices, which would involve the transfer of a 5-8GB .wim file initially. But when it comes time to update the image, you could use differencing WIMs. This is an option in Capture Wizard, and is intended for when you make changes to the same virtual machine from which you captured the original WIM. You would select "Differencing WIM", and point to the original WIM that you captured earlier. Then Capture Wizard will create a smaller (.DWM) file, which only contains any files which have changed since the original WIM was captured. This way, you would only have to distribute the smaller file for each update. At deployment time, you would only need the original WIM, and the most recent DWM (there's no requirement to hold onto the others). The .DWMs would obviously get bigger over time as the virtual machine diverges further from the original WIM, so you would probably eventually want to capture and transfer an entirely new WIM to each office - but this method would allow you to decrease the frequency of such large-file transfers. If you have any questions, please feel free to reach out - support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Vincent, Sorry you're still encountering issues. It sounds as though something on your network is still causing issues. Does your network have a firewall? Not just the SmartDeploy host? Email us at Support @ SmartDeploy .com and we can troubleshoot further. Thanks, SmartDeploy Support

Looks like you have a Hynix SSD, and Dell has a firmware update for it here. Probably should also try updating to the latest BIOS, which is A18 here. If those 2 things don't fix it, then once the error happens close Deploy Wizard, open a command window and grab the X:\windows\temp\diskpart.scr file. Copy that to USB or Network, rename it to diskpart.txt and either post it or email it to us at support @ smartdeploy.com Thanks, SmartDeploy Support

Hello, Are you running a OOBE script we provided you, or a custom answer file as OOBE is not a regular behavior when deploying with SmartDeploy. Thanks, SmartDeploy Support

Hi Dita, Right-clicking a Platform Pack and clicking Refresh will cause the console to refresh the information for that file (located in the \Platform Packs folder in your SmartDeploy working directory, which is C:\SmartDeploy\Platform Packs by default). So if you were to replace the pack with an updated version, and/remove items from it, etc., this would ensure that the latest information about that file is displaying properly in the console. This functionality does not submit an update request or download a newer version of the pack (if available) - that is still a manual operation at this time. You can submit a request to update any Platform Pack here: https://www.smartdeploy.com/support/platform-pack-request/ SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

The service is used for a few things, and forcibly disabling it may result in an incomplete deployment. The service is used to run post image tasks, specified from the Deploy Wizard or from a platform pack. It's also used for various clean up tasks. When complete, the service will disable itself. Thanks, SmartDeploy Support

Hello, Try unblocking Silverlight as well as the SDEConsoleservice. Thanks, SmartDeploy Support

Thank you for your feedback and we certainly don’t want this change to create additional work for you. Can you explain what you mean when you say that you will have to redo your current platform if you upgrade to SmartDeploy 2.0? Also, is there a reason that your organization wants to use an older version of the product? We chose to make this change based on a number of reasons. Downloading Platform Packs within the product is faster because you save a trip to the website, and fewer than 20% of Platform Pack downloads were taking place on the website. This was a strategic decision that will allow our team to focus on product improvements and provide excellent support to our valued customers like you. We sent an initial announcement on July 27th to the primary contact of each account, we apologize if you did not receive this. Would you like to be the primary contact for your account? We always recommend that customers use the latest version of SmartDeploy. Each new release of SmartDeploy includes bug fixes and product improvements. Running older versions of SmartDeploy can put you at risk of experiencing issues that have already been resolved in newer builds. Additionally, if you were to run into an issue, we would ask you to upgrade to see if that fixed the issue you were experiencing. We’ve also released new features, including zero-touch remote computer imaging and the answer file wizard which makes using SmartDeploy even faster and easier; using an older version may actually be taking more time. Best regards, SmartDeploy Support

Hi Nathan, Platform Packs only work for a device if that device is an exact match for the expected model identifier in the system firmware. There is no logic for "minimal hardware differences" - we will only use the pack if it is the exact model that we expect. This is by design, to ensure that only the correct pack will be used for a particular device. Sometimes there is some variability between model identifiers within a single model series, and sometimes a single driver set can support multiple models where the only difference is the screen size, for example. If you have a device that you aren't sure is served by an existing Platform Pack, you can go ahead and submit the Platform Pack Request Form (here), and we will advise whether an existing pack can be updated, or whether this will require a new pack to be created. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, Send us your C:\SmartDeploy\Logs\Console.log from the SmartDeploy host and we can see what may be going on. support @ smartdeploy .com Thanks, SmartDeploy Support

Hello, Attached is a VBScript that will update the Windows Unattend.xml that will get used. Run this as a post image task. I.e. open Deploy Wizard, Advanced, Tasks, add “after image is applied” task… Wscript.exe C:\scripts\autoadmin.vbs (This assumes the .vbs is sitting in this path on your image). Edit the script for the correct user name and password. (Replace “demo” and “pass@word1”.). Create another task at first logon with the following command: cmd.exe /c shutdown.exe /r Thanks, SmartDeploy Support autoadmin.txt

Hello, If you have any anti-virus on the SmartDeploy host, disable it and then attempt to recreate the media. If you still have issues, send us your C:\SmartDeploy\Logs\Media.log to support @ smartdeploy .com and we can see which driver is having issues injecting into the media. Please refer this thread. Thanks, SmartDeploy Support

Hi Allen, No, this should not be an issue. We've sent a reply to your email as well - please let us know a few more details (whether the same media has suddenly stopped working, or whether you're completely able to create media that works for the Surface Pro 4, whether this affects multiple USB sticks and Surface Pro 4 units, etc.) and we can assist further with troubleshooting. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, Once you receive the "Please insert disc 0" message close it and close out of the Deploy Wizard so you're returned to the splash screen. Click the link to open a command prompt and browse to X:\Windows\Temp\Deploy.log. Save that to USB/Network share and send it to support @ smartdeploy .com. Refer to this thread if you could. Thanks, SmartDeploy Support

Hello, We use the default proxy that is set in Internet Explorer for our Silverlight tools. Make sure those are set to default, no anti-virus is running on the SmartDeploy host and the following ports are enabled if you have a firewall: 80 and 443. Thanks, SmartDeploy Support

Hello, Can you ping the SmartDeploy console host from the client machine? Try disabling your firewall if you have a firewall and let us know your results. Thanks, SmartDeploy Support

Hi there, For Question 1, the answer is - essentially yes, but there are some additional details about how it compares to SmartDeploy push deployment that you'll want to take a look at. Here is a blogpost that explains this in detail: https://www.smartdeploy.com/blog/need-windows-deployment-services/ For Question 2: Yes, you can absolutely use SmartDeploy with WDS in this manner. If you select your OS image by browsing to the network share and selecting the image, it would copy across the network just like any other file. This is a fine scenario as long as you're deploying less than 25 computers at a time. If you're deploying more than 25, you'll definitely want to add the image to WDS and enable multicast, as this will result in greater deployment speed with this number of clients. If you have any questions, feel free to reach out at support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

If you send us C:\Windows\Debug\Deploy.log from the affected device, we can take a look at what's going on. support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Anthony, This likely indicates that your current WDS boot image has an Answer File that points to your old OS image - which must still exist in some location on your network that you specified previously. You'll need to create a new Answer File that specifies your new OS image, then re-run Media Wizard to create new boot media using this Answer File. Be sure to check the box that says "For use with WDS", and save as an ISO file. This will create a .wim version of the boot image in whichever save location you specify. Copy the WIM file to your WDS server, and replace the existing boot image with the new one. If the issue persists, shoot us an email at support (at) smartdeploy.com, and we can help troubleshoot further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL