how to set Network boot program (NBP) on WDS server?
Please tell me how to set Network boot program (NBP) on WDS server if it is IP helper based environment?
Pls note that we have seperate server for DHCP and seperate server for WDS for your info.
Furthermore which is the correct path of NBP program and file that we have to map?
- Path should be Remoteinstallbootx64 (or) RemoteinstallSMSbootx64 ?
- File should be wdsmgfw.efi (or) wdsnbp ?
Answers ( 6 )
Thank you for the response. I will do that.
I don’t think I have any solution for this type of issue.
The forum troubleshooting can be very complicated in this kind of complex issues.
I would recommend opening a ticket with Microsoft to fix this issue if you like.
Yes exactly 🙂 i am facing specific issue.
While we try PXE boot, it says Downloading NBP file and then NBPfile download successfully but after thatno result means not loading boot files from DP.
The NBP downloads as from #MPCpathboot\bootHD
We are looking for UEFI NBP should downoad. So i am looking for the solution so i needed above points and your solution. Pls suggest
Unfortunately I don’t have these information.
But in normal scenarios you don’t need to worry about all these things …isn’t it
Is there any specific issue you are trying solve
Thank you for the response.
The above link was useful. But could you please help me to answer the below qsns also as it is not exactly available in link but this is important information for our organisation. Thank you
1.which is the correct path of NBP program and file that we have to map?
Path should be Remoteinstallbootx64 (or) RemoteinstallSMSbootx64 ?
File should be wdsmgfw.efi (or) wdsnbp ?
2. Will we need to manually map the above information or WDS will automaticall load the NBP files automatically depends on PC architecture?
I have not tested this … but this is well documented….
Is this what you are looking for
When you run WDSUTIL /Set-Device /Device:
/BootProgram: for a computer, the command sets the netbootMachineFilePath attribute of the prestaged computer (that is, the computer account that represents the client computer in AD DS). In the following netbootMachineFilePath attribute syntax, and are optional, and you can specify to indicate the PXE server referral.
ldap_search_s(ld, “DC=domain,DC=com”, 2, “(&(objectClass=*)(netbootMachineFilePath=*))”, attrList, 0, &msg)
Result <0>: (null)
Getting 1 entries:
>> Dn: CN=Prestage1,CN=Computers,DC=domain,DC=com
5> objectClass: top; person; organizationalPerson; user; computer;
1> cn: Prestage1;
1> distinguishedName: CN=Prestage1,CN=Computers,DC=domain,DC=com;
1> name: Prestage1;
1> netbootMachineFilePath: machine.domain.com\boot\x86\pxeboot.n12;
1> canonicalName: domain.com/Computers/Prestage1;