Hi All,
We have been experiencing this problem for a while but only just getting around to fixing it...Where to start...
We are using WDS with MDT to create the .wim files, WDS is running on Windows Server 2012 R2 and we are using a Linux DHCP. The issue we are facing is we are unable to boot into the environment, depending on settings we get a range of different errors.
Our DHCP has the following information set:
allow booting; allow bootp; next-server 10.16.0.60; option tftp-server-name "10.16.0.60"; option bootfile-name "boot\\x64\\Images\\wdsnbp.com";
Notes:
10.16.0.60 = WDS Server
WDS has the following config:
C:\Users\>wdsutil /get-server /show:config
Windows Deployment Services Management Utility [Version 6.2.9200.16384]
(C) 2012 Microsoft Corporation. All rights reserved.
SETUP INFORMATION FOR SERVER
[-----------------------------------------------------------------------------]
Server State:
OS version: 6.2
WDS operational mode: Native
Standalone configuration: No
Installation State:
RemoteInstall location: D:\RemoteInstall
RemoteInstall share up-to-date: Yes
Boot files installed:
x86 - Yes
x64 - Yes
ia64 - No
arm - Yes
x86uefi - Yes
x64uefi - Yes
[-----------------------------------------------------------------------------]
CONFIGURATION INFORMATION FOR SERVER
[-----------------------------------------------------------------------------]
Server Authorization:
Authorization state: Not 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=DSDB,DC=INT
DHCP Configuration:
DHCP service status: Not Installed
DHCP option 60 configured: <Not Applicable>
PXE Bind Policy:
Use DHCP ports: Yes
Rogue detection: Disabled
RPC port: 5040
Interface Bind Policy:
Policy: Exclude Registered
Registered interfaces:
Boot Program Policy:
Known client PXE prompt policy: OptIn
New client PXE prompt policy: OptIn
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 -
x64 -
ia64 -
arm -
x86uefi -
x64uefi -
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: 0
Variable window extension enabled: No
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
[-----------------------------------------------------------------------------]
The command completed successfully.Image may be NSFW.Clik here to view.
Image may be NSFW.
Clik here to view.
The errors we are getting are strange, depending on when we change around options:
Case 1:
The machine looks to boot from the NIC, then contacts DHCP for an IP etc.
We get an IP and it knows where the WDS server is (IP), it then downloads wdsnbp and runs it referral to DHCP, it then asks to press F12 to enter the environment. You press F12 and it just starts again with contacting WDS.
Case 2:
The machine looks to boot from the NIC, then contacts DHCP for an IP etc.
We get an IP and then all it says is:
TFTP.
Exiting Intel Boot Agent
Case 3:
We change the settings on WDS properties to "Continue the PXE boot unless the user presses the ESC Key"
When we set this, it continues the same as Case 1, and after about 5-6 refreshes of contacting the WDS Server it finally enters the environment. Problem with this is we have machines in our environment that will then boot from PXE every time they reboot automatically.
Anyone have any idea where we are going wrong? Would be really useful to use our MDT .wim files to install our machines instead and save us a lot of time.
If you need anymore information please outline what you require, and will get this for you.