SmartDeploySupport

Looks like it could be because you didn't have networking, and your answer file was specifying a network based image. When you boot the Surface Pro 4, do you have a valid IP address in the lower right-hand corner? If not, then you'll need to re-create your boot media and include the Surface Pro 4 platform pack. An image on offline media was browsed to, so if you want to do that then delete or rename the SmartDeploy.xml on that media so that it's not trying to do all the network based things in that answer file.

Hello, Email support @ smartdeploy .com and refer to this thread. We can send you instructions on how to copy the default profile and customize your start menu for all users. Thanks, SmartDeploy Support

Hello Steve I have replied to this request via email. Please reply to the email with the requested info. Thank you SD Support

Once you receive the error, dismiss it and close out of the Deploy Wizard. Click the link to open a command prompt and browse to X:\Windows\Temp\Deploy.log. Save that to a USB/Network share and send it to support @ smartdeploy .com referencing this thread and we can take a look. Thanks, SmartDeploy Support

Try recreating your multicast transmission and redeploy. Thanks, SmartDeploy Support

Looks like hcmon.sys is the "VMware USB monitor", and perhaps comes from the vSphere Client install. If this is part of your image, uninstall it and re-capture. Thanks, SmartDeploy Support

Hello Bluerace We have a script that needs to be ran to resolve this issue. Please email us at "support (at) smartdeploy.com" and we will get you set up. Thank you. SmartDeploy Support

Hi JDK, Currently, the Computer Management section of the console is only designed to initiate and monitor unattended deployment packages. You can run scripts and tasks at deployment time, via the Tasks pane in the Deploy Wizard advanced options, but this can only occur in the context of a complete deployment operation. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Darrin, Sorry to hear that - the Conexant drivers generally plug-and-play without issue at deployment time (this is the case on other HP ProBook models), but we can modify the pack to run the full installer, which should hopefully resolve the issue for future deployments. It looks like there is a new version of the Audio driver available, so we can go ahead and update the pack. You'll just need to submit the Platform Pack Request Form, here: https://www.smartdeploy.com/support/platform-pack-request/ Be sure to note which OS version you're experiencing this issue with - it appears that HP has released an update for this device on Windows 10, but not on Windows 7. Feel free to email us at support (at) smartdeploy.com if you have any questions. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Steven, Yes, this is a common issue that can occur with system board replacements. The model identifier is set by the manufacturer, and cannot generally be changed by the end user - but it is something we can offer a workaround for. As a first step, go ahead and download our wmi.vbs script from Step 1 on the Platform Pack Request Form, and run it on the target device (you can do this via WindowsPE command prompt if the device doesn't currently have an OS on it). https://www.smartdeploy.com/support/platform-pack-request/ This will generate a file, wmi.txt, in the same folder where the script is located - send this file to support (at) smartdeploy.com (along with a link to this DeployCentral thread), and we will send further instructions. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Could you please email your c:\smartdeploy\logs\media.log to support @ smartdeploy.com. Thanks, SmartDeploy Support

Getting computer startup scripts to work reliably, especially in Windows 10, is difficult. We have a .msi solution, if you'd like to email us at support @ smartdeploy.com we can get that to you. Thanks, SmartDeploy Support

Hello, We do not have plans to implement Blu-ray support at this time. Our focus is currently on adding additional network-based deployment features, including (most recently) push deployments, initiated from the console. This method allows you to easily redeploy systems that currently have a working OS installed - you simply install a lightweight client and specify the hostname or IP address of your SmartDeploy workstation (this can be automated or done as a part of deployment as well). The computers with the client installed will appear in the Computer Management view of the console, and you can then initiate unattended deployments on one or more computers from the console, without any action required on the computers themselves. Additionally, we do support integration with Windows Deployment Services, which permits you to PXE boot target devices into an attended or unattended SmartDeploy PE environment, and proceed with deployment from there. We're working on several exciting new features in network-based deployment for future release. Please feel free to reach out if you have any questions or issues - you can reach us at support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Access denied, especially during the file processing phase, is often due to anti-virus software getting in the way. Try rebooting your machine, then disable any anti-virus software you have. Run the Capture Wizard again. If that doesn't do it, email your c:\smartdeploy\logs\capture.log to us at support @ smartdeploy.com Thanks, SmartDeploy Support Team

Hi Marc, Long story short, yes, there's a workaround for this. This all started back in November, when Microsoft decided to install the 1511 update (and, it appears, all future Windows 10 updates) as an in-place upgrade via Windows Update, which made it impossible to run Sysprep on the image at deployment time, since Sysprep will not run on an upgraded OS. Caused no shortage of deployment headaches. Once this issue became apparent, we added a check to Capture Wizard to prevent users from capturing images from upgraded operating systems, since – at the time – we knew that these images would not deploy properly. As of the 1607 update, however, Microsoft has fixed Sysprep and allowed it to run on an upgraded OS. We will be updating Capture Wizard again in our next release (coming soon) to permit capturing upgraded images as long as they have 1607 or later installed. In the meantime, we can offer a workaround. Since this issue will be moot in a couple of weeks, I'll not post the workaround here (don't want to cause any inadvertent registry problems), but I'll send it to you via email shortly. Anyone else who is running into this issue, please email us at support (at) smartdeploy.com, and we'll be happy to send you the workaround as well if needed. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

There is no UI option planned for this (as this feature has only been designed to allow user data to be backed up and restored from an existing PC) - however, USMT is installed and run on the target PC at deployment time, so it is conceivable that if you backed up the user data (.mig) file to a network location, then copied that file down to the target PC afterward, you could run a LoadState command manually to restore the user data at that time. LoadState lives in C:\Windows\Temp after deployment is complete (assuming you've enabled the USMT option in Deploy Wizard), so you can run this command: C:\Windows\Temp\LoadState.exe [path to .mig file] /c /l:C:\\Windows\\Temp\\LoadState.log /lac SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Certainly, you can view that here: https://www.smartdeploy.com/events/windows-10-migration-recording/ SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Once you receive that error, dismiss 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 and save it to a USB/Network share. Send support @ smartdeploy .com your deploy.log. Thanks, SmartDeploy Support

You have to select the CD/DVD option when creating WDS boot media. This will create both a boot .WIM and an ISO. These steps are on page 6 in our WDS documentation: https://www.smartdeploy.com/wp-content/uploads/SmartDeploy_WDS.pdf Thanks, SmartDeploy Support

Hello, You're correct - a BIOS-based VM can be captured and deployed onto a UEFI-based physical device without issue. Matching the boot method from the reference VM to the target device is neither necessary, nor supported. You don't need to manually create any partitions - Windows will automatically create any partitions that are needed at deployment time. The process is identical to how you've been creating images so far - create a new, blank VM, install Windows from OS media, install software, shut the VM down gracefully, and capture to a .wim file using Capture Wizard. You would then run Media Wizard to create SmartDeploy media (by default, all SmartDeploy media is UEFI-compatible unless you specifically select otherwise in Media Wizard), then select the captured image (.wim), which will be applied to your target device. The only thing you might want to watch out for is if you're deploying Windows 7 to UEFI-based target devices, you may need to modify the BIOS settings to ensure that the device will boot properly. If you have any issues after applying a Windows 7 image to a UEFI-based device, go ahead and shoot us an email at support (at) smartdeploy.com, making sure to note which make/model of device you're deploying to. We can then advise whether any BIOS settings changes may be needed. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, Ensure you're using the latest version of SmartDeploy as we fixed a bluescreen issue in the latest version. You can download the latest version here. You can install the newest version over the existing version. Once installed, recreate your boot media via the Media Wizard and redeploy. If you still have issues email us at support @ smartdeploy.com and we can provide you instructions on how to gather some logs for us. Thanks, SmartDeploy Support

Hello, That's a very cool service you provide for the military. I'm sure they appreciate it. Unfortunately, this isn't something SmartDeploy is designed to do. SmartDeploy does not have the ability to compare changes to a master image upon reboot and auto-update if necessary. I'm pretty familiar with Steam and the B.net services but haven't tested them on a SmartDeploy image. Here's what I imagine would be the best scenario for those gaming platforms and SmartDeploy. We have a free 15 day trial, so you may want to test. Build your virtual reference machine and apply Windows Updates and install Steam and Battle.net along with LoL and WoW and all games and fully update them via their platform. Capture/Deploy an image This should work out, although the Players will most likely have to change the video settings on the deployed machine upon first launch. Also, if the games update, they will only update on the deployed machine. You will have to update them on the virtual reference machine, then capture and deploy again if you want the master image updated. Hope that helps. Thanks, SmartDeploy Support

Hello, Just to confirm, is this the same issue from this thread? Please note that you can also reach us via email at support (at) smartdeploy.com, if you need to follow up on an existing thread. Just to clarify your question above, the image is not a "part" of the deployment package per se. A deployment package is essentially an unattended answer file - a set of instructions in an XML file for all of the settings that will be used at deployment time, including the location of the image. So while the image itself is not included in the package, a path for where the image is located is included, as well as a hashed set of user credentials which are used to access the network share that you've specified. If an IP address appears in the lower-right corner when you boot to the target device, but you're still being prompted to specify the image file, this suggests that the device does have network connectivity, but is still unable to reach the image. On the Select image page, try clicking Browse | Network, and entering the UNC path for the location where your image and Platform Packs are stored. Then, assuming you're able to view your image file in that location (switch to the default Z:\ in the Browse window, and select your image in that location). Complete the remainder of the Deploy Wizard settings as desired, and then - on the final Summary screen, click Export, and save your SmartDeploy.xml answer file to an external location (such as the network share that you mapped above). You will be prompted to reenter your credentials - make sure to enter them exactly as you did when you first connected to the share. You will also be asked whether this should be an unattended answer file - say Yes. After you've exported the answer file, click Finish to start deployment, and confirm that the deployment completes as expected. Then, back on your IT workstation, re-run Media Wizard to create a new deployment package, and specify the new answer file that you created above. It should retain all of the settings that you specified in Deploy Wizard, including the image location. If you have any issues with the steps above, or if this does not resolve the issue, please feel free to email us at support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, When the target machine boots to SmartDeploy's boot environment, does it have an IP address in the bottom right corner? The answer file is supposed to be part of the package, but usually when it can't access the image, there is a network/credential issue. You could try creating the answer file via the Deploy Wizard. i.e. Click Deploy an image, proceed to the summary page, then export your answer file there. This would ensure the mapping process is done correctly from the target machine. Thanks, SmartDeploy Support

We replied. You need to ensure the X1 pack is selected in the Media Wizard. Only a default.ppk was selected, and that didn't contain the X1 pack. Thanks, SmartDeploy Support