We help IT Professionals succeed at work.
Get Started

WDS problems after boot.wim load server 2012r2

Steve Nicholson
on
1,675 Views
Last Modified: 2015-04-28
Hello all. I am working with a ~100 machine environment and setting up WDS to handle imaging. I am running into the error displayed in the below screenshot. The error happens after PXE boot, after boot.wim gets loaded, and about 20-30 seconds into 'setup is starting'.

I have done everything possible over the last 6 days to rectify this, any help is greatly appreciated.

Error: Screen grab of error. This is after pxe boot, after boot.wim loads, after "setup is starting"
The Setup: DHCP and WDS on same server 2012r2 VM. Normal dhcp scope options enabled (60,66,67).

I've tried the obscure fixes such as the RPC group policy as well. At my wit's end.

WDSUTIl Config dump:
Server Authorization:
     Authorization state: Authorized

Answer Policy:
     Answer clients: Yes
     Answer only known clients: No
     Response delay: 0 seconds

Active Directory Use Policy:
     Preferred DC:
     Preferred GC:
     Prestage devices using MAC: No
     New computer naming policy: %61Username%#
     Domain search order: Global Catalog Only
     New computers join domain: Yes

New Computer OU:
     OU type: Server Domain
     OU: CN=Computers,DC=csdept,DC=local

DHCP Configuration:
     DHCP service status: Running
     DHCP option 60 configured: Yes

PXE Bind Policy:
     Use DHCP ports: No
     Rogue detection: Disabled
     RPC port: 5040

Interface Bind Policy:
     Policy: Exclude Registered
     Registered interfaces:

Boot Program Policy:
     Known client PXE prompt policy: OptOut
     New client PXE prompt policy: OptOut
     Allow N12 for new clients: <Not Applicable>
     Reset boot program: Disabled
     Default boot programs:
         x86     - boot\x86\pxeboot.com
         x64     - boot\x64\pxeboot.com
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - Boot\x86\bootmgfw.efi
         x64uefi  - Boot\x64\bootmgfw.efi
     Default N12 boot programs:
         x86     - boot\x86\pxeboot.n12
         x64     - boot\x64\pxeboot.n12
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - Boot\x86\bootmgfw.efi
         x64uefi  - Boot\x64\bootmgfw.efi

Banned GUIDs list:

Boot Image Policy:
     Default image type for x64 clients: Both
     Default boot images:
         x86     - Boot\x86\Images\boot.wim
         x64     - Boot\x64\Images\boot.wim
         ia64    -
         arm     -
         x86uefi - Boot\x86\Images\boot.wim
         x64uefi  - Boot\x64\Images\boot.wim

Driver Policy:
     Avoid duplicate driver packages: Yes

WDS Client Policy:
     Logging policy:
         Enabled: No
         Logging level: Info

     Unattend policy:
         Enabled: No
         Command-line precedence: No
         WDS unattend files:
             x86     -
             x64     -
             ia64    -
             arm     -
             x86uefi -
             x64uefi  -

Server Automatic Refresh Policy:
     Refresh period: 900 seconds

BCD Refresh Policy:
     Enabled: No
     Refresh period: 60 minutes

Pending Device Policy:
     Policy: Disabled
     Poll interval: 10 seconds
     Max retry count: 2160 times
     Message to pending clients:
     Retention period:
         Approved devices: 30 days
         Other devices: 1 days
     Defaults for x86:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for ia64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for arm:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x86uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes
     Defaults for x64uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes

WDS PXE Providers:
     Name: WDSDCPXE
     Path: C:\Windows\system32\wdsdcpxe.dll
     Order: 1
     Critical: No

WDS Device Controllers:
     Name: WDSADDC
     CLSID: {1F05CFEA-D4E4-4049-9C76-7B4F0013ECC9}
     Priority: 32768
     Enabled: Yes

     Name: WDSSDC
     CLSID: {17FD4B68-06B7-48EB-97B7-1575A171AED9}
     Priority: 32768
     Enabled: No

WDS Transport Server Policy:
     IPv4 source: Range
         Start address: 239.192.0.2
         End address: 239.192.0.254
     IPv6 source: Range
         Start address: FF15::1:1
         End address: FF15::1:FF
     UDP Port Policy: Dynamic
         Start port: <Not Applicable>
         End port: <Not Applicable>
     Network profile: <Not Applicable>
     TFTP Properties:
         Maximum block size: 8192
         Variable window extension enabled: Yes
     Multicast session policy:
         Slow client handling policy: None
         AutoDisconnect threshold: 256 KBps
         Multistream stream count: 2
         Slow client fallback: Yes
     Multicast Content Providers:
         Name: WDS
         Description: Default Content Provider
         File path: C:\Windows\system32\wdscp.dll
         Initialization routine: WdsTransportProviderInit

Open in new window

Comment
Watch Question
CERTIFIED EXPERT
Distinguished Expert 2018
Commented:
This problem has been solved!
Unlock 1 Answer and 17 Comments.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE