none
offline deployment using windows 10 using usb RRS feed

  • Question

  • Hi,

    I have a captured a wim image file  from mdt .Now wants deploy  this image to a pc where there is no network 

    How can we use usb stick for offline deployment  

    Thanks

    Saturday, August 26, 2017 1:51 PM

Answers

  • In this case, may I recommend that you change your BIOS settings to boot from HDD first? Then, to initiate the installation, press your boot menu key during the POST phase. Doing this: e.g. boot from usb to WinPE, select task sequence which will layer down the image and initiate a reboot, will make your system boot from hDD and your installation will proceed. Do not remove your USB drive until the installation finishes.

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    • Marked as answer by supportsib Sunday, August 27, 2017 2:21 PM
    Sunday, August 27, 2017 1:57 PM
  • The thing about creating a special selection profile for WinPE is so that we keep the size of the boot image as small as possible. If you go to a vendor's website you will notice that they offer special Windows PE drivers packages. For example, for HP systems, you can go to this page and get your driver packages. For other vendors, google "%VENDORNAME% SCCM drivers".

    The bottom line is, you may get away with using "All drivers" selection profile for your boot images, but the general recommendation is as outlined in the article I linked previously.


    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    • Marked as answer by supportsib Monday, August 28, 2017 5:28 AM
    Sunday, August 27, 2017 9:11 PM

All replies

  • Basically, your next steps will be as follows:

    1. Import your captured WIM file into MDT
    2. Create a new task sequence and point it to your WIM image
    3. (optional) Create a selection profile. By creating a Selection Profile you control what’s included in the deployment media.
    4. Create an offline media.

    Here are two step-by-step guides that will walk you through the process:

    • http://www.vkernel.ro/blog/creating-an-offline-mdt-deployment-media
    • https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    Saturday, August 26, 2017 2:28 PM
  • Hi,

    Thanks for the reply .I went through the link .Its working fine .But once its rebooted still it is going to the mdt welcome screen

    Thanks

    Sunday, August 27, 2017 11:31 AM
  • Please verify that USB is not set to first boot device in BIOS. I have seen this setting confusing the heck out of people many times. Once your system goes back to WinPE do you see a message box stating that there is a dirty LTI environment present?

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    Sunday, August 27, 2017 12:21 PM
  • Hi

    Once your system goes back to WinPE do you see a message box stating that there is a dirty LTI environment present?

    Yes

    Sunday, August 27, 2017 1:43 PM
  • In this case, may I recommend that you change your BIOS settings to boot from HDD first? Then, to initiate the installation, press your boot menu key during the POST phase. Doing this: e.g. boot from usb to WinPE, select task sequence which will layer down the image and initiate a reboot, will make your system boot from hDD and your installation will proceed. Do not remove your USB drive until the installation finishes.

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    • Marked as answer by supportsib Sunday, August 27, 2017 2:21 PM
    Sunday, August 27, 2017 1:57 PM
  • Hi,

    You are great savior of life :)

    Thanks

    Sunday, August 27, 2017 2:28 PM
  • Hi,

    The below are excerpts from the link you  provided.

    1. In the General tab, configure the following:
      1. Clear the Generate x86 boot image check box.
      2. ISO file name: Windows 10 Offline Media.iso
    2. Still in the Windows PE tab, in the Platform drop-down list, select x64.
    3. In the General sub tab, configure the following settings:
      1. In the Lite Touch Boot Image Settings area:
        • Image description: MDT Production x64
      2. In the Windows PE Customizations area, set the Scratch space size to 128.
    4. In the Drivers and Patches sub tab, select the WinPE x64 selection profile and select the Include all drivers from the selection profile option.
    5. Click OK.

    Why do we have to customize  winpe 

    second thing  ,why do we have to do the below step ?

    Extract and import drivers for the x64 boot image

    Windows PE supports all the hardware models that we have, but here you learn to add boot image drivers to accommodate any new hardware that might require additional drivers. In this example, you add the latest Intel network drivers to the x64 boot image. In these steps, we assume you have downloaded PROWinx64.exe from Intel.com and saved it to a temporary folder.

    Thanks

    Sunday, August 27, 2017 3:57 PM
  • The thing about creating a special selection profile for WinPE is so that we keep the size of the boot image as small as possible. If you go to a vendor's website you will notice that they offer special Windows PE drivers packages. For example, for HP systems, you can go to this page and get your driver packages. For other vendors, google "%VENDORNAME% SCCM drivers".

    The bottom line is, you may get away with using "All drivers" selection profile for your boot images, but the general recommendation is as outlined in the article I linked previously.


    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    • Marked as answer by supportsib Monday, August 28, 2017 5:28 AM
    Sunday, August 27, 2017 9:11 PM
  • Hi,

    I have an issue  ,I don't its related with the deployment .Once I deployed   i am facing intermittent connectivity of network in these pc's 

    ?

    Please help 

    Thanks


    • Edited by supportsib Tuesday, August 29, 2017 1:39 PM edit
    Tuesday, August 29, 2017 2:56 AM
  • Hi Anton 

    Let's say I have  created a reference image with few applications . 

    Now I Deploy the Image on a physical pc and  installed remaining applications 

    Then capture the physical pc image  

    and deploy multiple pc's of same kind.

    Can you validate the process is right or wrong 

    Thanks

    Tuesday, August 29, 2017 1:39 PM
  • I would use Hyper-V Gen 1 (not Gen 2!) instrad: this approach is faster and safer in terms of drivers being installed on the system. You will end up with a cleaner image. Plus you can use Hyper-V on a dedicated Windows 10 box - no need for a server grade hardware.

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    Tuesday, August 29, 2017 1:58 PM
  • I would use Hyper-V Gen 1 (not Gen 2!) instrad: this approach is faster and safer in terms of drivers being installed on the system. You will end up with a cleaner image. Plus you can use Hyper-V on a dedicated Windows 10 box - no need for a server grade hardware.

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    Hi,

    The above one is for reference image ,correct ?

    Once you capture the reference image , what are the next steps

    Thanks

    Tuesday, August 29, 2017 2:15 PM
  • Correct.

    Once you have captured your WIM, you will need to import it into your deployment share and build a deploy task sequence around it.

    Note: You may want to use a different deployment share if you need to use different CustomSettings.ini file and / or do not want other users being able to see the build and capture task sequence or you can use task sequence specific CustomSettings.ini so that you can have a different set of rules.


    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    Tuesday, August 29, 2017 2:22 PM
  • Hi,

    I have an issue like my deployment become slow after reboot the server .Usually is there something need to be done on network side like mtu 

    Thanks

    Wednesday, August 30, 2017 5:25 AM
  • Correct.

    Once you have captured your WIM, you will need to import it into your deployment share and build a deploy task sequence around it.

    Note: You may want to use a different deployment share if you need to use different CustomSettings.ini file and / or do not want other users being able to see the build and capture task sequence or you can use task sequence specific CustomSettings.ini so that you can have a different set of rules.


    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    When you create reference image , it means a complete image ?

    For example all software included in reference image  antivirus

    Thanks 

    Wednesday, August 30, 2017 5:29 AM
  • Look at the MDT documentation - it answers pretty much all of your questions and walks you through the process: https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit. Regarding antovirus: probably no, check vendor‘s documentation on sysprep supportability.

    Blog - http://www.vacuumbreather.com / http://www.wcsaga.com

    Wednesday, August 30, 2017 6:40 AM
  • Hi,

    Once the deployment Completed what we do with the default 'Administrator account ' 

    How to disable it after in a task sequence 

    Thanks

    Monday, September 11, 2017 5:34 PM
  • Simply add net user Administrator /active:no as your last task sequence step. Do not reboot your system via task sequence afterwards. After you click Finish in the Final Summary and the system reboots, local admin account should be disabled. Alternatively, you could use Johan‘ Final Configuration script: https://deploymentresearch.com/Research/Post/427/Final-Configuration-for-MDT-2013-Lite-Touch-now-with-Autologon-support

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    • Proposed as answer by Anton Romanyuk Tuesday, September 12, 2017 5:45 AM
    Tuesday, September 12, 2017 5:45 AM