Skip to main content

Posts

Showing posts with the label Deployment

Add and Remove Drivers to an offline Windows Image or WinPE

Add and Remove Drivers to an offline Windows Image Link  https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image You can use DISM to install or remove driver (.inf) files in an offline Windows or WinPE image. You can either add or remove the drivers directly by using the command prompt, or apply an unattended answer file to a mounted .wim, .ffu, .vhd, or .vhdx file. When you use DISM to install a device driver to an offline image, the device driver is added to the driver store in the offline image. When the image is booted, Plug and Play (PnP) runs and associates the drivers in the store to the corresponding devices on the computer.   Note To add drivers to a Windows 10 image offline, you must use a technician computer running Windows 10, Windows Server 2016, or Windows Preinstallation Environment (WinPE) for Windows 10. Driver signature verification may fail when you add a driver to a Windows 10 im...

Create Bootable WinPE 10 Media

Create bootable WinPE media (Information from https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive ) The Windows Assessment and Deployment Kit (ADK) includes the CopyPE and MakeWinPEMedia command line utilities. When run from the Deployment and Imaging Tools Environment, CopyPE creates a working set of WinPE files, that MakeWinPEMedia can use to create bootable WinPE media. MakeWinPEMedia can create bootable WinPE USB drives, virtual hard disks, or ISOs that allow you to boot a VHD or burn to a DVD or CD. CopyPE and MakeWinPEMedia are installed when you choose the Deployment tools and Windows Preinstallation Environment options when installing the ADK. If you're using the ADK for Windows 10, version 1809, Windows PE is a separate add-on that you download and install after you install the ADK. You can download the WinPE add-on from the Download Center. Step 1: Create working files No matter what type of media you're go...

mapshare.cmd

rem == mapshare.cmd == rem == This command will map a shared network folder rem    or NAS drive to be used in capturing and deploying rem    the system image. rem    Winpe won't work with smb1 shares rem    Share needs a username and password rem    from what I've seen so far. net use y: \\ServerName\FolderName /user:image image

capture.cmd

rem == capture.cmd == rem == These commands capture a specified Windows rem    image file to the specified share, and save it to a rem    .wim image file Dism /Capture-Image /ImageFile:"y:\w10.wim" /CaptureDir:C:\ /Name:w10x64

ApplyImage.bat

rem == ApplyImage.bat == rem == These commands deploy a specified Windows rem    image file to the Windows partition, and configure rem    the system partition. rem    Usage:   ApplyImage WimFileName rem    Example: ApplyImage E:\Images\ThinImage.wim == rem == Set high-performance power scheme to speed deployment == call powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c rem == Apply the image to the Windows partition == dism /Apply-Image /ImageFile:%1 /Index:1 /ApplyDir:W:\ rem == Copy boot files to the System partition == W:\Windows\System32\bcdboot W:\Windows /s S: :rem == Copy the Windows RE image to the :rem    Windows RE Tools partition == md R:\Recovery\WindowsRE xcopy /h W:\Windows\System32\Recovery\Winre.wim R:\Recovery\WindowsRE\ :rem == Register the location of the recovery tools == W:\Windows\System32\Reagentc /Setreimage /Path R:\Recovery\WindowsRE /Target W:\Windows :rem == Verify the confi...

Win10 Deployment help

Windows 10 Deployment Help Notes from Author This is posted on other pages I'm just using this to help gather information for myself and others for it to be easily accessible. If you find any errors or you know of a better faster way to deploy win10 please feel free to let me know. I'll be making separate posts if you want the contents of the txt/cmd files Capturing the Image Verify that the windows partition is listed currently as C: or you will need to adjust my scripts capture.cmd Prepping the hard drive for Image Deployment For newer PCs diskpart /s CreatePartitions-UEFI.txt For Legacy PCs diskpart /s CreatePartitions-BIOS.txt Deploying image to newly cleaned hard drive Applying the Image ApplyImage.bat imagename.wim