Windows Deployment Service corrupts \systemroot\system32\config\software in images.

Hello,
Recently we have upgraded to Server 2012 R2 to handle our WDS services but some images are not deploying correctly. 
When checking the event log on the machines that do not deploy correctly, the following error message is discovered: "\systemroot\system32\config\software was corrupted and it has been recovered'
We can restore the SOFTWARE registry backup from the regback folder and this corrects the problem, but this has to be done after the image is deployed and takes a lot of time.
The WIM files all deploy fine in all instances of deployment on Server 2008 R2, using DISM directly and ImageX.
For one image, this only occurs on certain machines.  It has been tested on 3 Z200 with the same hardware setup and the error occurs on 2 consistently and does not occur on the 3rd.
On another one of the images, this error occurs every time it is deployed using Server 2012 R2 but never when deployed using WDS on Server 2008 R2, DISM or ImageX.
This occurs whether the deployment is set attended or unattended. The majority of deployments have been tested without using an unattended file to eleminate variables.
Does anyone have any suggestions? Any ideas would be appreciated.
Edit:
We have also exported the WIM file of the image that always "breaks" from WDS 2012 R2 and successfully deployed it every time using 2008R2 WDS DISM and ImageX. 
We have created separate folders for these problem WIM files so that the RES file only contains the information from the specific WIM that is having problems; this does not fix the problem. 
Edit 2:
There is an error in setupact.log but it onlys says that the mentioned registry setting is malformed or corrupt. I tried a web search on this and had results but the majority of the answers were related to errors sysprepping. 
Starting WDS GUI
2014-02-12 16:47:07, Warning    [0x0a0180] UI     Failed to change the UI language to en-US.
2014-02-12 16:47:22, Error      [0x0a0052] UI     Failed to read image data from blackboard[gle=0x00000002]
2014-02-12 16:47:29, Warning    [0x07008d] DIAG   Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106
2014-02-12 16:47:31, Warning    [0x070026] DIAG   Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0
Setting up disk
2014-02-12 16:47:51, Warning    [0x0606cc] IBS    DeleteFileEx: Unable to clear out attributes on [D:\$WINDOWS.~BT\Sources\Rollback\bootsec.dat]; GLE = 0x2
2014-02-12 16:47:51, Warning               WDS    CallBack_WdsClient_MulticastCopyFiles: Error transferring files. Falling back to unicast. Error [0x80070002]
2014-02-12 16:47:51, Warning    [0x0b0095] WDS    CallBack_WdsClient_MulticastCopyFiles: Multicast transfer failed. Error code [0x80070002].
Active Dir Setup
2014-02-12 17:11:21, Info       [0x0b0083] WDS    MgLibpOpenLdapConnectionFromDN: DN=
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b007e] WDS    ProcessDomainJoinInformation: MachineName = [(null)], MachineDomain = [(null)]
2014-02-12 17:11:21, Warning    [0x0b0093] WDS    ProcessDomainJoinInformation: Error resetting machine account. Error [0x80070057].
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
Set up IBSLIB
2014-02-12 17:12:39, Info                  IBSLIB Copying files from D:\Windows\Boot\PCAT\en-US to \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US...
2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\bootmgr.exe.mui for read because the file or path does
not exist
2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\memtest.exe.mui for read because the file or
2014-02-12 17:12:39, Warning               IBSLIB Resource files missing from D:\Windows\Boot\Resources. These files are required for some editions of Windows. If you are servicing older
versions of Windows, you can ignore this message.
Sysprep Plug N Play
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Removing the devices that are using service mpio ...
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: The device Root\LEGACY_MPIO\0000 is using the service mpio.
2014-02-12 17:14:54, Warning               SYSPRP SPPNP: Error 0xE000020B occurred while adding device Root\LEGACY_MPIO\0000 to the device info set.
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Finished removing the devices that are using service mpio.
Sysprep specalize
2014-02-12 17:18:11, Info       [0x0f008a] SYSPRP RunRegistryDlls:Retrieved section name for this phase as Specialize
2014-02-12 17:18:11, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
2014-02-12 17:18:11, Info                  IBS    Callback_Specialize: External Providers Specialized Succeeded
Modify boot entries (Non UFI)
2014-02-12 17:18:15, Info       [0x0606cc] IBS    Flushing registry to disk...
2014-02-12 17:18:17, Info       [0x0606cc] IBS    Flush took 1201 ms.
2014-02-12 17:18:17, Info       [0x06036b] IBS    Callback_SystemRestore: Successfully set System Restore state.
2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: There was an error getting the path to the boot.ini or ntldr. dwRetCode=[0x1F]
2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: We did not successfully complete ModifyBootEntriesLegacy.  This is non-fatal, continuing setup. dwRetCode[0x1F]
Error in system log:
Log Name:      System
Source:        Microsoft-Windows-Kernel-General
Date:          2/12/2014 5:14:28 PM
Event ID:      5
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:     
Description:
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-General" Guid="{}" />
    <EventID>5</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-13T01:14:28.620907400Z" />
    <EventRecordID>12326</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="364" />
    <Channel>System</Channel>
    <Computer>COMPUTERNAME</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="FinalStatus">0x8000002a</Data>
    <Data Name="ExtraStringLength">36</Data>
    <Data Name="ExtraString">\SystemRoot\System32\Config\SOFTWARE</Data>
  </EventData>
</Event>
Sysprep Panther Log:
2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Cleanup
2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Generalize
2014-02-12 14:40:10, Warning                      TapiSysPrep.dll:RetainTapiLocations:RegQueryValueEx() returned 2
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vhdmp was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service VMBusHID was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service Brserid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbcir was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbccgp was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbhub was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service USBSTOR was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service sffdisk was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vpcbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service umbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service swenum was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service rdpbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service iScsiPrt was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service CompositeBus was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service circlass was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service ebdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service b06bdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service s3cap was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service 1394ohci was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbehci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbohci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbuhci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ohci1394 was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HDAudBus was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrUsbMdm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrSerWdm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service MTConfig was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service mouhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service kbdhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sfloppy was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbprint was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidUsb was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service UmPass was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidIr was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBth was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BTHMODEM was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service hcw85cir was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WacomPen was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Processor was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service IPMIDRV was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service intelppm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdK8 was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdPPM was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AcpiPmi was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service CmBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sermouse was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ErrDev was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WmiAcpi was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service flpydisk was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service fdc was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Parport was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service pcmcia was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service i8042prt was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.

We have discovered that this is only happening to target computers with installed
RAM greater than 4gb. If the machine has greater than 4gb of RAM, the mentioned corruption occurs. If the machine has
4gb or less, the corruption does not occur. We still have not found a fix for this, (besides removing the excess RAM during imaging and reinstalling after.)  Any ideas/thoughts would be helpful! Thank you in advance.

Similar Messages

  • Windows Deployment Services "the specified image file is either invalid or corrupted"

    I'm trying to add images to a virtual server running WS08 R2 but the only type of images that get accepted are the vista x86, nothing else works,
    I tried the following image files:
    windows server 2008 R2
    windows server 2008 x64
    windows 7 x64
    windows 7 x86
    windows vista x64
    and always the same error: "the specified image file is either invalid or corrupted"
    the machine configuration is as follows:
    Virtual machine on Hyper-V 2 (host is WS08 R2 Enterprise)
    2048 MB RAM
    25 GB free diskspace
    running these roles:
    AD
    DNS
    DHCP
    WDS
    hope someone can help

    Was a solution for this ever found?  I am experiencing the same issue with the following setup:
    I am having an issue with a virtualized Windows Server 2008 R2 Enterprise blue-screening any time I try and add an install image through the Windows Deployment Services mode.
    Server:
    Lenovo TD200x – 3822-43U
    Dual Intel Xeon E5530 CPU’s                                                                                                                                                                                               
    Installed Memory: 28.0 GB
    Two raid arrays.
                    Array 1 – 500 GB Mirror – hosting Windows 2008
    R2 Enterprise running Hyper-V
                    Array 2 – 1 TB RAID 10 – hosting Virtual Machines
    and Virtual Hard Disks
    We have the latest firmware update installed on this physical machine
    Our physical server is the Lenovo TD200x machine.  On it, we are running Windows Server 2008 R2 Enterprise
    Within Hyper-V, I am running a Windows Server 2008 R2 Enterprise domain.
    Virtual Server 1 is a domain controller running Windows Server 2008 R2.  It is configured with roles of: Active Directory Domain Services, DNS,
    and DHCP.
    Virtual Server 2 is a member server running Windows Server 2008 R2.  It is configured with the role of: Windows Deployment Services.
    The error is occurring on Virtual Server 2.  After everything is installed on this server, and it is setup as a domain member and has the Windows
    Deployment services role added, I go through and ad a Windows 7 boot image within Windows Deployment Services with no problem.  When I go through and try to add a Windows 7 install image, however, during the creation of that install image, the Virtual
    Server 2 pops up an error that reads:
    Error occurred while trying to execute command.
    Error Code: 0x80070002
    After this, the system will immediately blue-screen and reboot with a STOP 0x000000F4 Error
    I have tried using various Windows 7 DVD’s and even using the Windows 7 ISO file, mounting it as a drive.  All with the same results. 
    I have erased the virtual server and recreated it with the same results.  I have removed the entire domain and recreated both servers with the same results.
    I have setup the physical box as a Windows Server 2008 R2 domain controller and added the Windows Deployment Services role and did NOT have any problems
    going about it in that manner.  Therefore, the issue lies within running this in a Virtualized server within Hyper-V.

  • An error occurred while trying to start the Windows Deployment Services server

    After rebooting the server, I cannot start the Windows Deployment Services anymore.
    It worked perfectly before the reboot. When starting it manually these errors appear in the event log:
    The Windows Deployment Services Server service terminated with service-specific error 1460 (0x5B4).
    An error occurred while trying to initialize multicast manager. Windows Deployment Services server will be shutdown.
    Error Information: 0x5B4
    An error occurred while trying to start the Windows Deployment Services server.
    Error Information: 0x5B4
    This is on server standard beta 3.

    I have removed the server from the WDS, then I have uninstalled the role, rebooted, reinstalled the role.
    When I started the WDS the server was back in there, but when I wanted to start the service I got the message "the windows deployment services configuration is corrupt". I have triggered these commands to reset this:
    Code Snippet
    wdsutil /Verbose /Progress /Uninitialize-Server
    Windows Deployment Services Management Utility [Version 6.0.6001.16510]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Tearing down server...
    == Original server operational mode: Native ==
    -> Resetting setup state
    -> Disabling and resetting Windows Deployment Services services
    -> Removing server BINL SCP
    -> Removing Windows Deployment Services share at \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST
    == Final server operational mode: Not Configured ==
    The command completed successfully.
    Then i did this command, but again it failed to start at the end.
    Code Snippet
    C:\Windows\system32>wdsutil /Verbose /Progress /Initialize-Server /REMINST:"c:\R
    emoteInstall"
    Windows Deployment Services Management Utility [Version 6.0.6001.16510]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Setting up server...
    -> Creating Windows Deployment Services installation tree
    ---> Creating Windows Deployment Services installation root at \\LH-AJGG6OZWH9Z4
    .longhorn.office\c$\RemoteInstall
    ---> Creating Windows Deployment Services share at \\LH-AJGG6OZWH9Z4.longhorn.of
    fice\REMINST
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\x86\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\ia64\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\x64\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\Fonts
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Tmp
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Mgmt
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\WdsClientUnattend
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Templates
    -> Installing Windows Deployment Services files
    ---> Installing system files
    ---> Installing boot files for x86
    ---> Installing boot files for ia64
    ---> Installing boot files for x64
    -> Updating registry
    -> Configuring the TFTPD service
    -> Configuring BINL SCP
    Enabling Windows Deployment Services services...
    Starting Windows Deployment Services services...
    An error occurred while trying to execute the command.
    Error Code: 0x41D
    Error Description: The service did not respond to the start or control request in a timely fashion.
    Anyone have an idea what could be the cause? I found this additional error in the event log, but distributed file system hasn't been installed since the beginning.
    DFS could not access its private data from the Active Directory. Please manually check network connectivity, security access, and/or consistency of DFS information in the Active Directory. This error occurred on root REMINST.

  • Windows Deployment Services - Windows 8.1 Deployment Failure (Required Driver could not be Installed)

    Hello everyone,
    Give you a little background on the hardware/software which we are running to do a Windows 8.1 Deployment, we have an VM of Windows Server 2008 R2 with Windows Deployment Services installed and configured correctly. For the boot image it's a Windows 8.1
    WIM and as for the Install Image we have a base image of Win 8.1 with all drivers installed for an HP EliteBook 8540w , we Syspreped and then capture the image using the W2K capture on PXE to capture and upload the image to the server. This is where we first
    ran into the problem of connecting to the server and had to inject the lan drivers to have network connectivity. After the image was uploaded to the server, we thought to try and run a deployment of that image on an identical laptop. PXE boot into that Image,
    it asks for domain credentials which are accepted it begins the installation process and fails at "Windows installation cannot continue because a required driver could not be installed"?
    We just set up client logging on the server and it is useless it just says that the driver is missing, but what driver is missing? There are thousands, which one?
    Another forum has this issue:  http://social.technet.microsoft.com/Forums/windows/en-US/4cf0b378-09d0-4e0b-bc6e-3d898b668f98/during-deployment-windows-installation-cannot-continue-because-a-required-driver-could-not-be?forum=w8itproinstall

    Hi,
    Please first check the solution here:
    Error: Windows installation cannot continue because a required driver could not be installed
    http://support.brainwaregroup.com/kb/article/AA-00702/0/Error%3A-Windows-installation-cannot-continue-because-a-required-driver-could-not-be-installed.html
    Also, please try to find out Setup logs from the client computer, and we can see the details in the Setup log:
    If the failure occurs in Windows PE before the disk configuration page of the WDS client is completed, you can find the logs at the
    X:\Windows\Panther folder. Use Shift+F10 to open a command prompt, and then change the directory to the location.
    If the failure occurs in Windows PE after the disk configuration page of the WDS client is completed, you can find the logs on the local disk volume at the
    $Windows.~BT\Sources\Panther folder. The local disk volume is usually the drive
    C. Use Shift+F10 to open a command prompt, and then change the directory to the location.
    Kate Li
    TechNet Community Support

  • Windows Deployment Services and Mikrotik

    I Have an active Directory setup within my office, and I wish to take advantage of Windows Deployment Services to deploy office workstations for our employees.
    I have 1 requirement.
    The DHCP server is an Mikrotik RouterBoard.
    I need to know what options I need to set to allow our clients to PXE boot into WDS.
    No one really seems to know what needs to be done.
    Since there are options for using a 3rd party DHCP server software, I cant see why this will not work.

    check here: http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server
    you will probably need to use these:
    Sub-menu: /ip dhcp-server network
    next-server (this may need to be set to the ip address of your WDS, so that your RouterBoard performs a referral to your WDS)
    [this may be the only thing you need, if all your computers are on the same subnetwork]
    otherwise you might need to explore these:
    boot-file-name (not sure about this one)
    dhcp-option (the usual options needed are option 66 and option 67)
    EDIT: this may help you:
    http://forum.mikrotik.com/viewtopic.php?f=2&t=18203
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Can't start "Windows Deployment Services" Service

    I have a Windows 2003 Server that has WDS SP1 installed.  The Windows
    Deployment Services Server Service isn't started and when I try to
    start it I get a message that says:
    Windows could not start the Widows Deployment Services Server on Local
    Computer.  For more information, review the System Event Log.  If this
    is a non-Microsoft service, contact the service vendor, and refer to
    server-specific error code 2310.
    Event viewer lists Event ID 257 and this:
    An error occurred while trying to start the Windows Deployment Services
    server.
     Error Information: 0x906
      When I go to the actual WDS application, my server isn't listed.  If
    I try and add it, I get a message that says "The Windows Deployment
    Services configuration is corrupt.  Would you like to add it anyway?"
    If I say yes, the server is added, but it has a red x through it.
    I thought about removing WDS and then re-installing it, but it listed a
    number of programs that might fail if I did that.
    What should I do?

    Thanks, my problem was exactly that:
    ..................The error you are receiving generally indicates that you have a networking configuration problem on your server that
    is causing the domain to be unreachable...............
    They exchanged the Firewall and forgot to unlock the doors. After review and release back to work.
    Thank you.________________
    Moura

  • Windows Deployment Service Failed to Start

    Hi,
    I am trying to test the deplyment of Windows Vista RC1 using Windows Deployment Services (WDS). I have Installed WDS using WAIK on Windows Server 2003 Sp1. Installation completed Successfully, however i am not able to start the service of WDS. Following errors are logged in event logs:
    Event ID: 257 Source: WDSServer
    Description: An error occurred while trying to start the Windows Deployment Services server. Error Information: 0x54B
    Event ID: 513 Source: WDSServer
    Description: An error occurred while trying to initialize provider BINLSVC from C:\WINDOWS\system32\binlsvc.dll. Windows Deployment Services server will be shutdown.Error Information: 0x54B
    Any help would be greatly appreciated.
    Thanks in advance....
    Vineet Arora

    I am having a similar issue with WDS.  Here is how my server is configured:
    1. The server was initially a RIS Server, it was confiured with Windows Server 2003 SP1.
    2. RIS was then removed, and Server 2003 SP2 was installed.
    3. I then installed WDS (Obviously native mode now)
    4. Configured the WDS Settings for PXE etc.
    5. The WDS Server Service however just refuses to start, these are the messages in the Event viewer:
    Application:
    Source:WDSServer
    Category: WDSServer
    Type: Error
    Event ID:257
    An error occurred while trying to start the Windows Deployment Services server.
    Error Information: 0x32
    System:
    Source: Service Control Manager
    Category: None
    Type: Error
    Event ID:7024
    The Windows Deployment Services (WDS) Server service terminated with service-specific error 50 (0x32).
    Any ideas?
    Laila*

  • Windows deployment services configuration

    Hi,
    Can any one tell me how to deploy .EXE file in windows deployment services. It`s accepting .MSI file types only.
    Regards 
    Sakthi

    Hi Sakthi,
    >>Can any one tell me how to deploy .EXE file in windows deployment services. It`s accepting .MSI file types only
    By default, in Active Directory, group policy can be used to deploy .msi software package. If we want to deploy a .exe file with group policy, we can convert the .exe file into .msi package or we can use a script to install the file and use
    group policy to deploy the script to clients.
    Windows Deployment Services is used to deploy Windows operating systems over the network. To push .exe to the operating systems, SCCM is a great option.
    Regarding SCCM, the following article can be referred to for more information.
    Configuration Manager
    https://technet.microsoft.com/en-us/library/gg682129.aspx
    Regarding deploying .exe files, the following thread can be referred to for more information.
    What is the best way to push deployment of  a  exe file
    https://social.technet.microsoft.com/Forums/en-US/a79b3406-6bc1-4af1-b826-522b1d4fa827/what-is-the-best-way-to-push-deployment-of-a-exe-file?forum=winserverDS
    In addition, if we have questions regarding SCCM, we can ask for suggestions in the following forum.
    Configure Manager 2012
    https://social.technet.microsoft.com/Forums/en-us/home?category=systemcenter2012configurationmanager
    Best regards,
    Frank Shen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Windows Deployment Services - Capturing Image

    To Microsoft Technet,
    I am currently a student and I have setup a fully functioning Windows Server. This Windows Server has AD, DHCP, WDS and MDT installed on to it. This server was setup so that we can re-deploy Windows to any of our computer labs and it will just be a fresh
    install. My problem is that the students also need to upload (capture) an image of the OS to the server every now and then as part of the coursework. When uploading an image they are presented with this option:
    Obviously when you click connect it asks for a username and password so that it can write to the folder. The students are not allowed to know the username and password because if they do then they break the server. They do this because they log on and mess
    around with it. I am currently asking if there is a solution so they can connect to the server and it will automatically log them on as the admin.
    These are solutions however I feel they would be inappropiate:
    - Give them a username that has read / write access but block the logon.
    - Allow "Everyone" to read / write thus no logon screen.
    However I feel that both are a security risk as students can just join the folder from the network and delete other students work.
    Instead I would like the windows server to automatically allow the connection by implementing the logon details. Is there a possible way to do this?
    Thanks,
    Thomas.
    The image is off the internet (I did not make it).

    Hi thomasjcf21,
    Another possible is you can create shared folders for each student and give each student account full control permission, after they finish the OOBE they can upload their
    image to WDS server.
    The related third party article:
    Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I
    http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-using-windows-deployment-services-wds-step-by-step-part-i/
    I’m glad to be of help to you!
    *** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
    sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
    of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows could not start the windows deployment services server Error 1067: The Process terminated unexpectedly - Please help

    Hello All
    I am trying to set up a PXE service point on my DP in SCCM 2012 R2
    1) I have enabled the role on the DP
    2) rebooted and verified WDS installed as a role.( I let SCCM enable this role as instructed)
    3) When I tried to start the role from services I get the error below:
    Note: I also followed the troubleshooting steps in this technet article but still it stops at the half way point
    http://support.microsoft.com/kb/2009647/en-us
    Phil Balderos

    Hi,
    Here is a similar post for your reference.
    Windows Deployment Service
    http://www.windows-noob.com/forums/index.php?/topic/3938-windows-deployment-service/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Deployment Services will not start

    After advertising a image to my remote client computer I receive this error:
    PXE-T01: the specified file was not found
    PXE-E3B: TFTP error - file not found
    PXE-M0F: Exiting Broadcom PXE ROM
    I logged into the server and noticed the "windows deployment service" is not running. I tried to start the service and it failed to start. I then checked the "Site System Status" log and noticed there was a "Critical" message for the PXE service point role,
    and a "warning" message for the management point role.
    On 8/16/10 for the PXE service point role I see this critical error: PXE Control Manager detected PXE service point is not responding to pxe requests. The error is 16389. Possible cause: pxe service point is not started or not responding.
    I would greatly appreciate any assistance.
    Thank you

    Thank you everyone for your patience and assistance. I have resolved the issue after double, and tripple checking everything. The problem was that the boot images (x64, and x86) were not pointed to SMSPXEIMAGES$ distribution which is the server share. I
    pointed it to the Server only. After pointing to both the share, and the server all works fine.
    So the initial issue with the deployment service not starting was to uninstall WDS, and the PXE option in SCCM. During the troubleshooting I accidently deleted the SMSPXEIMAGES$ distribution point from the boot image which caused another issue after resolving
    the windows deployment problem.
    Hope this helps the next person that has this issue.
    The solution exists already in the link that I gave you, see the point N°5 :)
    http://blogs.technet.com/b/smsandmom/archive/2008/09/17/configmgr-2007-troubleshooting-pxe-service-point-issues-and-wds-service-not-starting.aspx

  • Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

    Hi
    I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
    Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
    The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
    I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
    I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
    I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
    Cheers   

    Hi Joel,
    This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
    The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
    should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
    The related KB:
    PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
    http://support.microsoft.com/kb/259670
    The similar thread:
    PXE-E53: No boot filename received
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
    WDSServer (Windows Deployment Server) Fails to Start
    http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • 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!

  • Windows Deployment Services Issues

    i have a Windows deployment Services server running , and at the same server i am running dhcp as well as dns server. the network series is 10.241.0.1 to 10.241.0.105 , questions:
    Q: if i want the dhcp server to offer ip address in the network of 10.241.1.1 is it possible or i need to take the dhcp server in the network series of 1. 
    Q: sometimes there is a problem in wds , the client pc says no dhcp proxies were offered, how do i resolve that ?
    Q:While entering the scope in the dhcp server, the dhcp server says the IP is overlapped or invalid ip address, any solutions ?
    Q: i have multiple operating systems to deploys via network, so how is that possible , should i create a new image group or can i add the images in the same images and will it ask during the startup ? i tried by adding the other os to the group , the first
    os gets booted and installed but when i select the second operating system says, wdsclient error, no dhcp offered , , , , and so.

    Hi,
    According to your description, I list your questions and the suggestions for each question as bellow:
    Q: if i want the dhcp server to offer ip address in the network of 10.241.1.1 is it possible or i need to take the dhcp server in the network series of 1.
    If there are 2 network, 10.241.0.1/24 and 10.241.1.1/24, and you want the DHCP server (which is belong to network 10.241.0.1/24 ) to provide DHCP service to clients on network 10.241.1.1/24. You may configure a DHCP relay agent on network 10.241.1.1/24, in
    order to forwarder DHCP messages between clients (which are on network 10.241.1.1/24) and DHCP server. Detailed information about how to configure DHCP relay agent you may reference the link:
    http://technet.microsoft.com/en-us/library/dd469685.aspx
    Q: sometimes there is a problem in wds , the client pc says no dhcp proxies were offered, how do i resolve that ?
    On the client which says no DHCP proxies were offered, open CMD, type “ipconfig /all” and hit Enter, check to see if it obtains the correct parameters. If not, type “ipconfig /release“ and “ipconfig /renew” to renew IP address.
    Q:While entering the scope in the dhcp server, the dhcp server says the IP is overlapped or invalid ip address, any solutions ?
    On a DHCP server, you can create only on scope for a subnet. If you have created a scope from 10.241.0.1 to 10.241.0.105, with subnet mask 255.255.255.0, then a scope with network ID 10.241.0.0 can’t be created. You may use
    Exclusions to resolve this problem. If the problem still exit, please provide the scope and relate parameters you want to add, and the exiting scope you have already added on the DHCP server.
    Q: i have multiple operating systems to deploys via network, so how is that possible , should i create a new image group or can i add the images in the same images and will it ask during the startup ? i tried by adding the other os to the group ,
    the first os gets booted and installed but when i select the second operating system says, wdsclient error, no dhcp offered , , , , and so.
    You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing. Make sure that your DHCP implement is working and let us resolve the above 3 problems first. Besides,
    you may reference the link for detailed information about Windows Deployment Services Getting Started Guide:
    http://technet.microsoft.com/en-us/library/cc771670(v=WS.10).aspx
    Best Regards,           
    Eve Wang 

  • Windows Deployment Service. Network Profile Radio Buttons greyed out with R2

    Hi All
    I have downloaded and setup Server 2008 R2 (not yet activated). I have added the following roles "DHCP Server", "DNS Server", "Active Directory Domain Services" and "Windows Deployment Services". I can PXE boot a test client machine and (using the boot.win from windows 7 dvd) multicast a XP Image to it. This setup is connected via a 100 Mb switch and is an isolated network. 
    Under windows deployment services - if I right click my server - select properties - network tab "Network Profile is greyed out". I have tried running wdsutil /Set-TransportServer /Server:big /Profile:100Mbps but get the following error message: "Windows Deployment Services Management Utility Version 6.1.7600.16385. Error code 0xC110011F This WDS transport server does not support network profiles.
    I have tried this on two hardware setups:
    An Intel D915GUX 3GHz 2GB RAM and Marvel Yukon 88E8050 ethernet controller.
    An Intel D965 Core2Duo 1.86GHz 2GB RAM and  Intel 82566DM Network controller.
    Incidently I have done the same setup with Server 2008 (not R2) on the D965 and the Network Profile radio buttons are not greyed out. If I upgrade the same test machine to server 2008 R2 the Network Profile radio buttons are greyed out. Is this a design change, does Server 2008 R2 no longer support network profiles as I am now unable to select 10 100 or 1000 Mbs ?
    If more information is required or if anything needs further detail please let me know.
    Thanks for any help.
    Liam.D

    Is there any way at all to manually set or control the network profile? In my environment, a SCCM\WDS multicast stream is bottoming out on speed and network utilization when the stream crosses a Nexus 7009 router. Speeds go from 200 Mbps to 20 mbps. I have
    a theory that this "new" automatic configuration is placing the clients in a slow network profile that are on the opposite side of the router and I have been unable to find a way to speed of the transmission. I have also ruled out the "master
    client" slowing down the stream buy using different clients only connecting to a stream 1 at a time. I have also ruled out the router as the source of the problem by having a VLC client listen to the multicast stream on the same side of the router as
    the slow clients. The VLC client (unknown to SCCM\WDS) was able to receive the transmissions at 20 % utilization / 200 Mbps.
    -Tony

Maybe you are looking for

  • "ERROR: Could not read block 64439 of relation 1663/16385/16658: Result too large"

    Hi, I've already archived a lot of assets in my final cut server but since one week there is a message appearing when I click on an asset and choose "Archive". The pop-up says: "ERROR: Could not read block 64439 of relation 1663/16385/16658: Result t

  • WIFI signal reciever?

    can i use an airport express to recieve a wireless signal if i hooked it up via ethernet to my mac? i do not have an airport card in my mac. i am basically finding alternate routes to installing an airport card into my mac and this would serve as a d

  • Case order of EVENT structure

    LV 8.2.1 - Regarding the order of cases in an EVENT structure: 1... Is there any performance (speed) advantage to having the most-commonly used events near the top of the list?  Does it have to search through a list to find which case to execute, or

  • Performance Appraisal - Add PA, PSA, EG and ESG to PHAP_ADMIN_PA

    Hello There is a requirement to add Personnel Area, Personnel Subarea, Employee Group, Employee subgroup to the output of the report generated by  PHAP_ADMIN_PA. What steps we need to take in order to meet the business need? Also, it would be great i

  • Extra Finder icon in Dock

    This seems odd...I now have an extra Finder icon in my dock. It's white and appears to have a mini applications folder logo at the bottom of the icon. When I hover the mouse over it, though, it shows up as Finder, and I see the original Finder icon,