Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Posts

    904
  • Joined

  • Last visited

Posts posted by SmartDeploySupport

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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.

  9. 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

  10. 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

  11. 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

  12. 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

  13. 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

×
×
  • Create New...