SmartDeploySupport

Hi louis.haug, Have you successfully deployed this image via USB/Local Network? Can you email your response here You can refer to this thread in the ticket.

Hi Jay, We'll follow up by email to troubleshoot this further. Glenn SmartDeploy Support

Hi Rysamp, In order to see what is going on, we will need some logs to give us specifics. It sounds as though the PE drivers are not getting injected into the boot media. Once you have booted the Surface from your boot media into the SmartDeploy boot environment, click Collect Logs. Save the resulting zip and submit a support request here with them attached. If you could also send your C:\SmartDeploy\Logs\Media.log from the SmartDeploy host that would be helpful as well. Please refer to this thread in the ticket. Thanks, Devon

Hi Jay, How can you tell that the packs are corrupt? Is this an error message that appears during deployment? If that's the case, go ahead and browse to the Platform Packs directory and try opening them one at a time by double-clicking on them. It may just be a single Platform Pack that is corrupt, and this can be remedied by deleting and redownloading the pack. If the issue persists, go ahead and email us at support@smartdeploy.com (making sure to reference this thread), and we can assist further. Glenn SmartDeploy Support

Hi Chris, Aaron is correct - Windows Update management is not a feature of the product at this time. Note that you can use SmartDeploy to deploy a new image built from a VM using media with the latest version, and enable user data migration in your answer file. So if you want to reimage your endpoints with the latest version with minimal disruption, that is an option. I should mention - I understand that Windows 10 Version 1909 has started to become available on MSDN this week. We will begin testing with it as soon as we're able to get our hands on OS media for it, but please note that as of this writing, we can't confirm whether it is supported yet. If anyone else is reading this message later on, you can always check our Release Notes to see the list of currently supported operating systems. Glenn SmartDeploy Support

Hi Michael, I replied to your ticket and provided more guidance on mapping your drive. Thanks, Devon SmartDeploy Support

Hi Michael, On the target machine you will want to deploy to, you will want to perform a network boot from the network card. You should be able to see a network card or network boot option in the BIOS of the machine. Usually, it's F12 to PXE boot upon boot. What manufacture and model is the machine? I could probably find the correct key to PXE boot. Thanks, Devon SmartDeploy Support

Hi Sam, Let's take a look at your Application Logs from Event Viewer on the Windows 7 clients. Open Event Viewer and expand the Windows Logs - > Application and right click to save them. Please submit a ticket here and refer to this thread, and we can take a look at why the client is having issues with the Window 7 clients. Thanks, Devon SmartDeploy Support

Disable any anti-virus real-time scanning, and it will be much faster.

Hello, Usually this indicates the meta data for the image is incomplete and that's why it's not populating those fields. Please send us your C:\SmartDeploy\Logs\Capture.log and C:\SmartDeploy\Logs\Answer.log from the SmartDeploy host. Refer to this forum post and submit here. Thanks, Devon SmartDeploy Support

Hi Chris, SmartDeploy is licensed per deployed endpoint, so there is no licensing restriction that would prevent you from installing the SmartDeploy console on multiple computers. As for "pointing to the main server", that is not functionality that exists in the console. Each console exists independently, and will display whatever files are in the SmartDeploy directory (C:\SmartDeploy by default). You can copy files from one console computer to another, if for instance you wanted to have the same OS image (.wim) file on both consoles, or use the same answer file, that sort of thing. Any given SmartDeploy client (installed on an endpoint in your environment) can only be pointed at one specific console at a time. So whichever console you specified (using hostname or IP) at the time you installed the client, that is the one where it will appear, in the Computer Management view. If you need to switch a client so that it is pointing to a different console (by hostname or IP), we can provide a script that will allow you to make this change easily per-endpoint. If you have any questions, feel free to submit a support ticket here. Glenn SmartDeploy Support

Hi RPA, No specific size limit for Application Packs. Can we see the Application event log from the target computer? C:\Windows\System32\winevt\Logs\Application.evtx Go ahead and zip the file, then submit it via the Support Form here: https://support.smartdeploy.com/new And please be sure to reference this DeployCentral thread. Glenn SmartDeploy Support

Hi Jay, As my colleague noted on the other thread, Sure Start is a different feature, separate from Sure Recovery. You can disable HP Sure Recovery under Advanced | HP Sure Recovery. I'd like you to try disabling this feature, but I'd also like you to make sure that the boot mode is set to UEFI only, TPM is enabled, and Secure Boot is enabled. You may find it easiest to just reset the BIOS to its factory defaults, then check to confirm that Sure Recovery is disabled. Glenn SmartDeploy Support

Sure Start is a different thing. Sure Recover, if you wanted to disable it is under Advanced, "HP Sure Recover". But, you shouldn't need to disable it. Ensure your machine is in the factory default configuration of "Legacy Support Disable and Secure Boot Enable".

Turns out HP's Sure Recovery feature is looking for a valid Windows Recovery Environment. Not sure why, and not having it doesn't mean that the OS can't be found... as demonstrated by the fact you can press Esc and the OS will boot just fine. In this case the image had been captured with the "for use with WDS" option checked. This leaves off the system partition (where WinRE is by default) and only captures the boot partition since WDS only supports importing images with a single index. Note: You only need to import an image into WDS if you are going to use it for multicast. To work around the issue, you can either create a single partition VM and install Windows to that single partition. Or you can place a regularly captured image next to the image that was imported into WDS and the Deploy Wizard will look for and use WinRE out of that image. In a future release, we will look at making the Capture Wizard "for use with WDS" option handle this better by moving the Windows Recovery Environment from the system partition to the boot partition during capture.

Hi Jay, I think we'll need to see some logs and ask a few more questions on this - can you submit a support ticket here, and we can assist further? Be sure to reference this DeployCentral thread. Glenn SmartDeploy Support

Sent. Being able to ping both ways is encouraging, but there are specific port requirements that may not be met here (8733 is one of them, which is referenced in the error message above). We should be able to see what's going on in the event logs in any case; we'll be in touch. Glenn SmartDeploy Support

Hi Ted, Sounds like it may be a connectivity problem, but if we can take a look at the Application event log from the endpoint, we can see if if received the command and tried to follow it. Also possible there simply weren't any newer drivers available, as everything installs silently, and the device only reboots if a particular driver requires it. I'll send you an email shortly. Glenn SmartDeploy Support

Hello, We are glad you're happy with SmartDeploy! You were right in containing the security software as an application pack. Security software and anti-virus software can cause issues if installed on the image as it can break sysprep, capture issues, etc. You can also install it as a post image task. Most customers install applications on the image, or install the base applications all their users need, then deploy application packs for any unique machines that need a couple different applications. You could also make separate images for those users as well. It's really up to you. We recommend installing your applications on the image so you don't have to do any steps after the image is laid down. There is really no pro or con. I hope that answers your question! Thanks, SmartDeploy Support Devon

Hi Scott, Yes, you will need to recreate your deployment package and select the updated answer file during the process. Thanks, SmartDeploy Support Devon

Chris, Thanks for clarifying. You can install the SmartDeploy client on the Windows 7 machine. During the installation it will ask you for the SmartDeploy hostname or IP. Enter that and the machine will show up in Computer Management in the SmartDeploy console. You will then create a deployment package, which then can contain your answer file that migrates user data. You can find more information on page 57 in our user guide. Thanks, Devon SmartDeploy Support

Hi Chris, Aaron is correct. You will want to do this via the answer file. You do not have to migrate it with WDS, but you can always add a migration answer file to your WDS boot media if needed. In order to migrate from a Windows 7 machine to Windows 10, you will want to create a new virtual reference machine with the latest version of Windows 10 media (1903). You will want to create an answer file via the Answer File Wizard. To get to the Answer File Wizard, open the SmartDeploy console, Activities - > Reimage Devices - > Create Answer File. When creating the answer file you will have the option to migrate user data. You can find more information on page 107 in our user guide. Thanks, Devon SmartDeploy Support

We will need to look at the full log files to see what is going on. Also, did you run any 3rd party applications to customize the start menu or uninstall or remove any of the built in appx packages? Please send us log files from the instructions above. Thanks, Devon SmartDeploy Support

Hi phildown, Yep, SystemFamily and SystemSKUNumber are newer properties within Win32_ComputerSystem, only supported in Windows 10 and Windows Server 2016 or later. This means the current version of the script will fail in an older OS, but it will run just fine in our WindowsPE environment. So the easiest way to get a wmi.txt for a system that is currently running an older OS would be to boot to SmartDeploy media (best option would be a boot media USB stick with no answer file). When the SmartDeploy splash screen appears, click the Collect Logs option. Select a location to save the zip file. A log zip file will be generated in that location, and you can find the wmi.txt file in [zip root]\X\Windows\Temp, then submit a Platform Pack request via the Support Form (here). If you have any issues with this process, go ahead and submit a support ticket and we'll be happy to assist further. Glenn SmartDeploy Support

Hi wajtech, We'll need a few more details on this - I'll open up a support ticket and you'll hear from us shortly. Glenn SmartDeploy Support