WinPE re-distribution image

My company makes a WinPE/BartPE plug-in for recovery purposes but does not create the WinPE ISO image for re-distribution and I'm curious if this is something we can do without needing to purchase licenses for each distribution.

Hi,
The Windows PE 3 EULA (License agreement) is included with WAIK and explains clearly the scope where/how Windows PE can be used.
Windows Pre-Installation Environment: You may install and use the Windows Pre-Installation Environment for purposes of installing and recovering Windows operating system software. For the avoidance of doubt, you may not use the Windows Pre-Installation Environment
for any other purpose not expressly permitted in this agreement, including without limitation as a general operating system, as a thin client or as a remote desktop client.
Windows Automated Installation Kit (AIK)
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=10333
Otherwise, you may need to buy the related licensing to extend the WinPE.
Thanks for your understanding.
Kate Li
TechNet Community Support

Similar Messages

  • Windows Image Deployment - WinPE - Execute Command After Server Image Deployment but Before WinPE Reboot

    Simplified version: Execute command in WinPE after server image deployment but before WinPE reboots.
    I have a custom ISO with a boot.wim and install.wim for deploying Windows Server to our environment. Our environment does not allow DHCP and we have no static IPs available at build time so this will all be done with no internet connection during all phases
    of deployment.
    We have a custom HTA form that generates an XML file based on user input and stores it on the RAMDisk during WinPE. How can we move this XML file from the RAMDisk to the deployed Windows Server image?
    Thanks in advance, Tim

    I believe you should be able to do this during the offlineServicing configuration pass.  You would just need to add into your answer file a command or script to copy from the XML file over to the newly created C:\ drive.  
    I don't have System Image Manager installed on the computer I'm using but if I recall there is a spot during the offlineServicing pass to execute custom commands. You would just add your script path there, the WinPE system drive letter is
    X:\ , and I think the target drive letter Windows is installed to might change depending on how many devices you have hooked up so do a test install and hit SHIFT-F10 , from there you can run diskpart > list volume to see where the new Windows
    install is located. 
    Another alternative could be using a USB drive as your install media, then you can run a script during offlineServicing to copy that XML over to the USB drive.

  • Can't add drivers to Server 2012 R2 boot image in WDS

    Hi all.
    I want to use my "old" Windows Server 2012 (not R2), WDS to deploy new R2 servers but i can't add driver package to the R2 boot image, it comes out with error code: 0xc0000135 no matter what drivers i use.
    Without network drivers i can't boot the image on my physical servers, i've tried on a virtual machine where it works just fine.
    I can't use the old boot image to install R2, then it comes with error: "Windows could not apply unattend settings during pass [offlineServicing]." when it tries to install it on both virtual and physical servers.
    My initial thought is that the WDS server has to be on a R2 server but i can't find anything that proofs that.
    Can someone confirm that non R2 WDS is not supported to R2 or does anyone have an idea to a solution?
    Thank you in advance.

    Okay maybe not a solution but i installed a new WDS server on R2 and then there was no problem adding driver package to to boot image.
    So i was able to confirm my theory that it's not supported to deploy R2 from a non-R2 WDS server. If anyone can make it work please let me know but until then i think this is the only way.
    If I understand your description of the issue, the problem is that you are trying to update a WinPE 5.0 WIM with a version of the ADK that services WinPE 4.0 images.  Installing the new Windows Server 2012 R2 server caused SCCM to use the version of the
    ADK that services WinPE 5.0 images.  You should be able to deploy them fine from the other server, but you can only service them from the new one.  You will not be able to service the older WinPE 4.0 images from the new server either.

  • WDS unattend.xml shutdown the system after installing the image instead of reboot.

    I have a large number of machines that I want to install Windows 7 by using WDS unattend.xml. 
    unattend.xml works absolutely fine but I want WINPE to shutdown the system at the end of image installation and before OOBE. 
    Could you please let me know, how can I automate this process, so Winpe shutdown instead of rebooting after image deployment and before oobe.
    Do I have to put this command x:\windows\system32\wpeutil.exe shutdown somewhere in unattend.xml or elsewhere else. 
    I would appreciate if you could please answer this question.
    Here my unattend.xml it works fine, but reboots the system instead of shutdown. 
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SetupUILanguage>
    <UILanguage>en-US</UILanguage>
    </SetupUILanguage>
    <InputLocale>0809:00000809</InputLocale>
    <SystemLocale>en-GB</SystemLocale>
    <UserLocale>en-GB</UserLocale>
    </component>
    <component name="Microsoft-Windows-Setup" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DiskConfiguration>
    <Disk wcm:action="add">
    <CreatePartitions>
    <CreatePartition wcm:action="add">
    <Order>1</Order>
    <Type>Primary</Type>
    <Extend>true</Extend>
    </CreatePartition>
    </CreatePartitions>
    <ModifyPartitions>
    <ModifyPartition wcm:action="add">
    <Order>1</Order>
    <Active>true</Active>
    <Extend>false</Extend>
    <Format>NTFS</Format>
    <Label>Windows</Label>
    <Letter>C</Letter>
    <PartitionID>1</PartitionID>
    </ModifyPartition>
    </ModifyPartitions>
    <DiskID>0</DiskID>
    <WillWipeDisk>true</WillWipeDisk>
    </Disk>
    </DiskConfiguration>
    <WindowsDeploymentServices>
    <ImageSelection>
    <InstallTo>
    <DiskID>0</DiskID>
    <PartitionID>1</PartitionID>
    </InstallTo>
    <InstallImage>
    <ImageGroup>xxxxxxxxxxx</ImageGroup>
    <ImageName>xxxxxxxxxxxx</ImageName>
    <Filename>xxxxxxxxxxxxx</Filename>
    </InstallImage>
    </ImageSelection>
    <Login>
    <Credentials>
    <Domain>xxxxxxx</Domain>
    <Password>xxxxxxx</Password>
    <Username>xxxxxx</Username>
    </Credentials>
    </Login>
    </WindowsDeploymentServices>
    <restart>Shutdown</restart>
    </component>
    </settings>
    <cpi:offlineImage cpi:source="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    I have also tried to use the command line like this, see below. 
    </WindowsDeploymentServices>
    <CommandLine>
    x:\windows\system32\wpeutil.exe shutdown
    </CommandLine>
    WinPE does not even start with above mentioend wpeutil.exe shutdown command, it throws an error and reboots. 
    I would really appreciate if someone can help me figure it out, how can I auto shutdown the system instead of reboot after WDS / WINPE installs the image.
    Thanks in advance

    1. When the error message appears, open up a command window with SHIFT + F11
    2. open the REGEDIT
    3. navigate to hklm\system\setup
    4. change CmdLine to blank (no value entered) (was oobe\windeploy.exe)
    5. change CreateNewQueueOnFirstBoot to 0 (was 1)
    6. change OOBEInProgress to 0 (was 1) (i am guessing that might be AUDITInProgress
    if that was your sysprep choice)
    7. change SetupPhase to 0 (was 4)
    8. change SetupShutdownRequired to 0 (was 1)
    9. change SetupType to 0 (was 2)
    10. change SystemSetupInProgress to 0 (was1)
    11. exit REGEDIT and reboot

  • Using MDT boot image in SCCM 2012

    Hi,
    I want to import MDT boot image in SCCM 2012. Please let me know if this is possible.
    I have integrated all the driver in it and want to use from SCCM.
    Any suggestion on this?
    Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

    These two blogs explain this process very very well.
    http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
    http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Upgrade to SCCM R2 have to recreate boot image and TS

    Wanna ask, I have upgraded from my SCCM from SP1 CU3 to R2. But i noticed that in boot image, the WinPE tab is missing thus i cannot include the network driver. Anyway that i can make the tab reappear again? Net says have to recreate the boot image and TS...
    http://www.deploymentresearch.com/Research/tabid/62/EntryId/117/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-and-MDT-2013.aspx

    This often happens after R2 upgrade. If your boot image does not have 6.3.9600 version then you will not be able to manipulate it using the R2 console. You don't need MDT to create a new one though (this new version).
    You can use dism. See here. It's very easy. I had to do it yesterday.
    http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
    http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Win7 capture failing at WinPE 0xc000000d

    Hello
    I currently have multiple Win7 x64 virtual machines that I use for capturing at the start of each year. I currently have an issue where no of them will capture, giving the same error.
    I run the litetouch.vbs on the virtual machine like I have always done. I complete the wizard, choose the Capture task sequence I've set up and used previously, fill in my credentials and name the .wim that will be created. The wizard then finishes and the
    lite touch process starts. It gets to the point where the system restarts and goes to boot into WinPE for the image to capture. It's a black screen with a white bar with a message above saying "Windows is loading files..."The issue appears once the
    system has completed the loading phase and is about to boot into the WinPE environment.
    The error that occurs is below:
    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
       1.Insert your windows installation disc and restart your computer.
       2.Choose you language settings, and then click "next"
       3. Click "Repair your computer."
    If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
       Status:0xc000000d
       Info: The boot selection failed because a required device is inaccessible.
    I can't recall any changes I've made on my server that could relate to this. I have made sure permissions are correct and that the share is configured correctly. This message comes up on all VM's I have so it is a server side issue and not a individual VM
    issue.
    If I select enter, I'm prompted to choose between 2 operating systems, a "Ramdisk Device Options" and a "Windows 7" option. The Ramdisk just loops me back to the white bar and loading of files and the Windows 7 option starts to boot back
    into the operating system.
    Any help would be appreciated as I'm out of ideas.
    Thanks
    Beau

    Thanks for the reply DiWuNewFolder
    I'm currently running my WDS setup from a Server 2012 R2 VM. I've increased the memory for the VM I'm trying to capture to 8GB but it still produces the same error.
    I've had a look at the LiteTouchPE_x64.iso file and it is "2.08 GB (2,243,663,872 bytes)". Once I have updated the boot image inside the WDS server, the expanded size is 7941MB. If this is an issue, how do I reduce the PE image size?
    I had been looking through this forum for a solution and in another thread someone mentioned mounting the LiteTouchPE_x64.iso directly to the VM from Hyper-V, which I did and I was able to complete the capture of the VM this way. After the VM sysprep'ed,
    it would restart and boot off the CD I mounted. It looked like it normally does so I'm not sure what this points to exactly.

  • Slow boot from WinPE 4.0

    Putting this in the Win8 forum, as there doesn't seem to be one for Server 2012 deployment.
    I am currently automating deployment of a Server 2012 customised image, but am getting very poor performance when booting off WinPE 4.0 on physical servers only.
    I have the following comparisions:
    1. Boot WinPE 3.0 on an HP DL380 Gen 8 using an ISO made with WAIK and mounted via iLo remote board - takes a couple of minutes max.
    2. Boot WinPE 3.0 or 4.0 on a VMware version 8 guest running on vCenter 5.0 using an ISO made with WAIK/WADK and mounted via vmware console - takes a minute.
    3. Boot WinPE 4.0 on the same HP DL380 Gen8 using an ISO made with WADK and mounted via iLo remote board - takes 15-20 minutes.
    Typically all of the above images only have drivers for NIC and storage controllers for the approriate WinPE version, however I have also tried putting all Server 2012 drivers from the HP Service Pack for Proliant into the WinPE 4.0 image, with no change.
    The wpeinit log shows no delays, so it would seem that any delay occurs before that log is started.
    Anyone have any further ideas for troubleshooting?

    Well, I finally got around to troubleshooting some more. Being convinced it was a driver issue I took out the drivers and booted in the same manner. Of course it bluescreened, but it took a while before it did so, so it looked like the same issue.
    So then I took Tripredacus' advice and used a USB stick with my original ISO image extracted on it, went across to the data centre and it only took a few minutes to boot WinPE 4.0 from USB.
    Thus it seems to be a problem with WinPE 4.0 booting over the HP iLo interface. I will open a case with HP, but it's odd that WinPE 3.1 does not have this problem.

  • Windows Deployment Services 2012 - Driver Group filter by Model value not working - Drivers are not installed!

    Hi,
    I'm using Windows Deployment Services 2012 to deploy Windows 7 Pro x64 driverless images to different hardware models (drivers are injected using WDS). I already have organized the drivers in driver groups per
    hardware model. I'm experiencing driver conflicts so I decided to start using driver group filters to make sure that the driver groups are available only available for the corresponding hardware model.
    To get the correct values for the filters i have used the following method: (as described in this article: http:// technet.microsoft.com/en-us/library/dd759191.aspx)
    so I checked msinfo32.exe
    (System Manufacturer: Dell Inc.     System Model: OptiPlex 790)
    and set these values in the driver group filter:
    Then fired up WDS using PXE booting on my OptiPlex but when finished: No drivers are installed! I investigated further and found on forums to use the following commands (which return the same values btw):
    wmic bios get manufacturer      
    (returns: Dell Inc.)
    wmic computersystem get manufacturer
    (returns: Dell Inc.)
    wmic computersystem get model
    (returns: OptiPlex 790)
    Values are the same so no problem there.
    Then I checked the output of the following commands: 
    wmic bios get model (returned: error, invalid query)
    wmic bios get /all (returned: all kind of information but no model value)
    When I remove the value "OptiPlex 790" from the filter list the drivers are installed correctly. So this has to be some problem with the Model value.
    Could someone please help me?
    As a workaround I now disable all the driver groups exept the one that I need for the hardware. But as more new hardware models are added this is a lot of work to do everytime.
    Extra info:
    I'm using a WINPE 4.0 image (windows 7 media boot.wim file). 6.1.7.601
    Windows Server version: Windows Server 2012 - version 6.2 (Build 9200) - All Windows updates are installed
    Windows Deployment Services version 6.2.9200.16384
    Having this problem on multiple systems
    Questions:
    - Does WDS/WinPE uses only the Bios values for determining system info? (then this problem could be with Dell in this example, because no model value is available)
    - Is this the correct way to set up driver group filters? (then this is a problem with MS. Does anyone have solution??)
    Thank you for your answers & help!

    Hi Microsoft,
    I still have no answer to my Questions.
    Thank you for your answers & help!

  • Oracle Linux 6.4 Bootable disk?

    Hello, I am about to download Oracle Linux 6.4 and install it on a 32 bit computer.
    How can I make a bootable disk so when I reboot this computer it goes straight into the install process?
    Do I download Oracle Linux Release 6 Update 4 for x86 (32 Bit) and then download Oracle Linux Release 6 Update 4 Boot iso image for x86 (32 bit)?
    Do i burn the content of the Oracle Linux Release 6 Update 4 Boot iso image for x86 (32 bit) on the same disk as the  Oracle Linux Release 6 Update 4 for x86 (32 Bit)?
    Can someone please tell me how to do this?

    Installing a 32-bit OS on reasonable and recent hardware does not make sense. It will only limit your addressable memory and disk space for no good reason.
    Anyway, you need to download the binary software distribution image, which is about 2 - 4 GB. You do not need the boot or source media.
    Before burning the DVD, make sure to verify the checksum of the downloaded ISO image. It is not unlikely that the download is corrupted and won't work properly.
    You can find the checksum value when clicking the View Digest button on the E-Delivery software download web page.
    Under Microsoft Windows, see the following knowledgebase article:
    http://support.microsoft.com/kb/841290
    Under Linux and Mac OS X, enter the following at the system command prompt (Terminal):
    openssl sha1 name.iso
    The checksum must match!
    To burn the iso image to DVD:
    http://windows.microsoft.com/en-US/windows7/Burn-a-CD-or-DVD-from-an-ISO-file
    For information using Apple Mac OS X and older versions of MS Windows:
    http://www.wikihow.com/Burn-ISO-Files-to-DVD
    And last not least, remember to set the media startup priorities of you computer BIOS accordingly: Floppy, DVD, Harddrive, Network.

  • Ewfmgr: Failed getting protected volume configuration with error 1

    Hello,
    I created a Windows 7-64 image for an Ivy-Bridge VME card. The image contains EWF with RAM-REG.
    The disk was divided into 2 partitions with the windows installer and the image was successfully installed.
    As I'm using RAM-REG, all
    the disk was allocated.  
    After the image was installed I tried to run "ewfmgr c:" and got the current status.
    Then I created a GHOST image and wrote the image on a new card with a clean disk.
    After Windows booted, running "ewfmgr c:" gave:
    Failed getting protected volume configuration with error 1
    I found few threads on this issue but failed to understand what is the right solution.
    Can you help ?
    Thanks,
    Zvika  

    The Problem is always Volumeid related (diskid)
    Explaination:
    Sysprep creates new bcd for the System. - Therefore it's recommended to use sysprep (and SID and so on..) but if you're lazy or don't have Domain Controller and so on or always use physical seperated (better not Internet connected) machines you would be
    totaly fine with non-syspreped Images. You only Need updated/new bcd.
    Captured wim has 'old' bcd (if there is no seperated MSR Partition) you can update this 3 entries within winpe and your Image will boot:
    bcdedit /store c:\boot\BCD /set {BOOTMGR} device boot
    bcdedit /store c:\boot\BCD /set {DEFAULT} device PARTITION=C:
    bcdedit /store c:\boot\BCD /set {DEFAULT} osdevice PARTITION=C:
    (boot could also be Partition=c: or all entries could be boot - and /store is not needed as in winpe bcdedit automatically Redirects the commands into the other/System (found) bcd. But i always recommand to specify the bcd store you want to edit, like in
    this lines)
    The definition of "C:" in this Parameter is 'translated' into volumeid/diskid. - So in the bcd is not "C:" it's some DiskID.
    Instead of the 3 entries you can just create a whole new bcd with updated volumeid/diskids. --> It would be enough to run bcdboot /s C:\ (or whatever the current boot (c:\) Partition is.
    EWF needs to be reconfigured as it also works with Volume/Diskids. So it needs additional command while running (online).
    ewfcfg /install-configuration for win7
    rundll32 ewfdll.dll,ConfigureEwf for win xpe/wes2009.
    Windows Embedded Developer and Scripting Guy //Germany (http://www.wesnext.com)

  • Drivers signing problem adding to WDS

    Hello
    I need to add NIC (Intel Ethernet Connection I218-V) drivers to my WDS boot image (Windows Server 2008 R2)
    I tried to add a driver to WDS drivers, but WDS refuses to add it saying the driver is not signed.
    I installed the same driver on my workstation and it appers in driver properties, it is signed by Microsoft Windows Hardware Compatibility Publisher.
    So why WDS refuses to install them?

    What is the Hardware ID of the NIC? Also provide what version WinPE your boot image is and architecture.
    I know there are some certificates that Server 2008 R2 does not recognize because they are too new. In this case, WDS (or even DISM) will throw an error about it not being (properly) signed, or the OS may think the certificate is expired. I ran into this
    with one driver and in my research I found there was no update you could get to fix it. I ended up having to inject the driver on a Server 2012 with the ADK installed.
    My scenario may not be the same as yours, but I figured I mention it. If you can provide the HwID, I (or others) may be able to locate another driver that will work.

  • SCCM 2012 with MDT: osd, apply wim captured with CM task sequence in MDT task sequence: "cannot find the file specified"

    Hi,
    Please see titlte. When I try to apply an CM captured WIM via an MDT task sequence, it starts, applies but stops after 15 minutes.
    Logfile says it "cannot find the file specified".
    Full error: "Installation of image 3 in package mypackage failed to complete. . The system cannot find the file specified. (Error: 80070002, Source: Windows).
    Though the image IS there, redistributed it (if it wouldn't be there the task sequence would not start).
    Please advise.
    J
    Update: could it be the fact I'm using an old (SCCM 2012) MDT wim? If I need to recreate the WIM boot image, where do I get the SCCM 2012 R2 boot wims?
    Jan Hoedt

    See how to manually re-create your boot images
    http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
    http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Cloning Toshiba Laptops with sysprep

    Hi,
    We have many different makes and models of laptops and have a sysprep image which we use for all of them and up till now have had no issues other that having to put drivers in after the laptop has been imaged.
    That is until we started purchasing Toshiba laptops!!
    After we have imaged the laptop it blue screens with either
    PAGE_FAULT_IN_NONPAGED_AREA
    Stop: 0x00000050 (0xF0000223, 0x00000000, 0x806BAF76, 0x00000002)
    or a
    Stop 0x0000007B
    Even after repairing the image it blue screens.
    Thus far we have had to build a new image for every model of Toshiba laptop and then image.
    Any ideas on how I can get my sysprep image to work?

    @crystalreef
    What do you wrap the sysprep image in? wim file? ghost file? clonezilla image?
    I have had 100% success with sysprep by using wim file method. First I prepare the image with newprep method and capture the image with imagex. When we deploy the image we use either bartPE or winPE 3.1 image from PE boot which uses imagex to install wim file from samba share. In the same PE session it then injects the hdc drivers using fix_hdc.cmd script from that samba share. This is responsible for fixing the 7B errors. Additionally there is a program which I wrote in autoit which detects the model of the machine and pulls the appropriate drivers off the network and puts them in c:\drivers. There is then another routine in mini setup to inject lan drivers and on intial boot another script which goes and installs the drivers from the c:\drivers etc..
    Anyway what sysprep method do you use? If you can I recommend to use the newprep method as it does not involve adding any mass storage driver entries to sysprep.inf and is very clean sysprep method. From then I am sure you will never have problems syspreping Toshiba laptops.

  • ConfigMgr version to upgrade XP- Win 7

    What ConfigMgr version to upgrade XP-> Win 7?
    ConfigMgr 2012 SP1 or ConfigMgr 2012 R2

    Earlier only SP1 support XP-Win7 Migration.
    Not sure where you're getting that from but 2012 has always supported XP to Win 7 migrations.
    With CU2, you should not have any explicit issues -- prior to CU2, there was an issue using WinPE 5 boot image on XP systems during refresh scenarios but this has been resolved.
    Jason | http://blog.configmgrftw.com | @jasonsandys

Maybe you are looking for