none
Single image deploy different brand PCs RRS feed

  • Question

  • Anyone suggest that Deploy different brand PCs with just one single image.

    For example:

    I use HP pc to capture a HP image.And I deploy it to a Lenovo PC.

    I konw this can work,but is it the better way for deployment?and if it's not recommended,is there any officical statement about this?





    • Edited by longgegeno1 Monday, September 7, 2015 8:10 AM 21
    Monday, September 7, 2015 8:06 AM

Answers

  • Additionally, this is covered in the FAQ:

    What are Fat Images? What are Thin Images? Hybrid?

    MDT can be used in two different scenarios, Imaging and Deployment.

    • Imaging is the process of creating a new *.wim file that contains common Applications, Settings (and sometimes common Drivers). MDT can install the OS, Applications, Registry Settings, Patch using Windows Update, Sysprep, and save the contents to a single *.wim file in a single automated process.
    • Deployment is where MDT or SCCM can install a retail *.wim file or use a captured *.wim file to install on the end user’s machine. MDT can also install additional Applications, Configuration Settings, Migrate User Files and Settings, Drivers and more.

    Should an Application be installed into the core image, or be installed at deployment? Examples:

    • Fat - If you have an environment where all the machines are identical (hardware, applications and setting), then a Fat Image could be optimal. Very little (or nothing) is done at deploy time.
    • Thin - If you have an environment where the machines are all different (hardware, applications, and settings), then it would be best to keep the core image as small (or thin) as possible, and perform an intelligent job of installing the required applications, settings and drivers per machine. A very thin image could be one that only contains Microsoft Hotfix patches.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Marked as answer by longgegeno1 Tuesday, December 1, 2015 12:47 AM
    Monday, September 14, 2015 5:28 PM
    Moderator

All replies

  • First: Hi

    Second: if you want to deploy the same Image to several pc-models you should not work with with an Image with Drivers.

    When you capture an Image with Microsoft Tools (so you get a wim-file) you will get a hardware independent Image. You can deploy this Image to different types or manufactures of PCs / Notebooks and it will work. The only thing you have to consider is, that you need the correct drivers for the Hardware!!!

    So one way could be:

    1. Configure your Client
    2. create wim-Image
    3. install wds role on a server
    4. Import Drivers to wds
    5. deploy wim with WDS

    Have a look here:

    https://technet.microsoft.com/en-us/library/hh831764.aspx

    Regards

    Eric


    Microsoft Partner Technical Solutions Professional (P-TSP)
    --
    www.ericberg.de
    @ericberg_de
    --
    MCSE: Private Cloud | MCSE: Server Infrastructure | MCSE: Desktop Infrastructure

    Monday, September 7, 2015 8:27 AM
  • You can deploy the image to different vendor specific model. But you have to work on driver i.e. need to install the proper driver.

    When you capture the image with HP model , it will work fine with HP as it will find the drivers from system32\driver but in case of other it will reject those driver and those drivers will not get installed automatically. Hence need to install manually.



    Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

    Friday, September 11, 2015 1:13 PM
  • thats absolutely the recommended way. One image, any hardware, is what MDT, and by extension SCCM is desgined to do. 

    Ideally, you should build your images on a VM, Hyper-V, VMWare, whatever, as its cleaner, has no proprietary vendor drivers to get left behind. But sysprepping a PC will always remove the drivers, unless you specifically tell it other wise.

    Using MDT you create a repository of drivers, that can be searched via plug and play, or you can set up logical groups of drivers per model that will be installed at deploy time via WMI query.

    Refer to here for an example driver management process:

    http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management

    Be sure to mark this answered if it helps you.  Good luck!


    Friday, September 11, 2015 6:32 PM
  • Additionally, this is covered in the FAQ:

    What are Fat Images? What are Thin Images? Hybrid?

    MDT can be used in two different scenarios, Imaging and Deployment.

    • Imaging is the process of creating a new *.wim file that contains common Applications, Settings (and sometimes common Drivers). MDT can install the OS, Applications, Registry Settings, Patch using Windows Update, Sysprep, and save the contents to a single *.wim file in a single automated process.
    • Deployment is where MDT or SCCM can install a retail *.wim file or use a captured *.wim file to install on the end user’s machine. MDT can also install additional Applications, Configuration Settings, Migrate User Files and Settings, Drivers and more.

    Should an Application be installed into the core image, or be installed at deployment? Examples:

    • Fat - If you have an environment where all the machines are identical (hardware, applications and setting), then a Fat Image could be optimal. Very little (or nothing) is done at deploy time.
    • Thin - If you have an environment where the machines are all different (hardware, applications, and settings), then it would be best to keep the core image as small (or thin) as possible, and perform an intelligent job of installing the required applications, settings and drivers per machine. A very thin image could be one that only contains Microsoft Hotfix patches.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Marked as answer by longgegeno1 Tuesday, December 1, 2015 12:47 AM
    Monday, September 14, 2015 5:28 PM
    Moderator
  • I don't know what kind of computers you've got home or pro ? 

    But you should do your image inside an hypervisor like Hyper-V, VMware or VirtualBox. That way you've got a clean image. 

    Then, for Lenovo or Hp if using Pro computers. 

    You can you use their tools:

     -SDM and SSM for HP. SDM to retrieve the drivers and SSM as an application while deploying.

    Something like: \\MyShare\SSM\ssm.exe \\MyShare\SSM\ /install /accept

    You can update the bios while deploying but I wouldn't recommend it. 

     - Lenovo Update Retriever (to get the drivers) and line command for installation. Seek on LENOVO website they've got a pdf "deployment". It's a command line to add before state restore. I don't know all the switches. 

    Or again with Lenovo Update Retriever but playing with "start.reg". Again look it up on LENOVO website.

    But both use a share. And it's very easy to maintain. LENOVO update retriever can be manage from third computer and can be set as a scheduled task. 

    There is another option with "make" but it's not so easy with Lenovo, you need a aliasExit script to manage LENOVO naming convention.

    Wednesday, September 16, 2015 10:59 AM
  • Working with a VM to create an image has its limits.  For example, if you are installing software that requires peripherals be connected for the software to be installed, you cannot use a VM, at least in my experience with Hyper-V because there is no USB support.  In this case, you would need a physical system to create your image.
    Sunday, February 16, 2020 6:57 PM