Part 12 describes the final configuration to be carried out to our OSD solution.
1. DHCP options/IP Helper
2. Computer Name variable
1. DHCP Options/IP Helper
If you are network booting computers that are not in the same subnet as the PXE enabled DP, you have some additional configuration to carry out in order that these clients can locate the boot images.
The Microsoft best practice way to do this is by configuring IP Helpers on your switches and routers. This works well and is the only Microsoft supported way to do this. However it is not always possible. Another way to do this is by configuring DHCP Scope Options. Note that this is not the Microsoft supported way but it can work and get you out of trouble.
IP Helpers
Microsoft Best Practice - you will find more information here
Here is an example from a Cisco switch:
interface Vlan10
ip address 172.16.112.254 255.255.255.0
ip helper-address 172.16.1.1
End
This allows clients booting in 172.16.112.0/24 subnet to find the ConfigMgr or MDT server (172.16.1.1).
DHCP Options
Options 66 and 67 are configured so that a PXE client can locate the PXE point and boot into Windows PE using our boot images
These options can be configued at the server or individual scope level
Option 66 is the PXE server name (local PXE enabled DP) or IP address
Option 67 is the file name required and is always
SMSBoot\x64\wdsnbp.com
2. Computer Name
We use a collection variable so that the Administrator is prompted to enter a computer name and the beginning of the deployment process.
Right Click "Unknown Computers" and choose Properties. Open Collection Variables tab.
Click on the yellow star to add a new variable.
Type OSDComputerName
Hello,
ReplyDeleteFor PXE Server (WDS), the DHCP Options may be optional, if everything is on the same subnet. This can be used in cases where the IPHelper is not enabled through a router (usually)
Great job,
Best Regards
Mitch
Thanks Mitch. You're quite right. You don't need to do anything if you are dealing with one subnet only. However it's easier to configure DHCP Options at the server level instead of worrying about configuring your routers.
ReplyDeleteGerry
GREAT WORK, this cured my headache with the no boot file recieved
ReplyDeleteThanks Martin. Glad I was able to help
ReplyDeleteGerry
After adding the DHCP options 66 and 67, it comes up to TFTP and eventually times out. And looking in the RemoteInstall\SMSBoot\x64 directory, there are no files located there. Did I miss something?
ReplyDeleteYou'll have to fix that. Try disabling PXE on the DP, wait until WDS uninstalls. Then re-enable PXE, wait until WDS re-installs.
ReplyDeleteDon't forget to reboot after each step
ReplyDeleteHello Gerry
ReplyDeleteIts very nice that you spend a time and publish all of your experience.
Thank you for your great work.
My question is about multicast of PXE.
It seem when I use it, the image download of DP is at least three times slower then if its not used even if setting points to client transfer rate 1GB (its when the deploy is to only on PC).
From your screenshots in the next chapter I can see that you do not use it. Can you give me a brief explanation and is it possible to configure the network setting some how?
Thanks for your reply !
It can sometimes be very difficult to successfully implement OSD via Multicast. Much of the infrastructure can be outside your control. Pay attention to the switching environment. It must support and be configured to allow multicast.
ReplyDeleteHello,
ReplyDeleteCaution! For a migration phase to SCCM 2012, having added DHCP options can make it difficult transition. Normally, if IPHELPERs options are configured on the router (WAN / MAN), it is unnecessary to put! I suggest you test it before without any options. Do them if necessary!
Note: Without DHCP options, with two structures SCCM 2007 and 2012, during a transition migration, those are the site boundaries (limits / Groups limits for SCCM 2012) that will make the appropriate referrals PXE requests. It can therefore be "virtually" maintain two strucutures SCCM with the same level of services, including the PXE / WDS. But this is only possible with the lack of options in the DHCP service.
Same concept on the same VLAN, Range Scopes / IP subnet without crossing a router ...
Mitch
hi Gerry,
ReplyDeleteI am facing issue " no entry found in database for device"
Please describe what you have done. I may be able to help you then.
ReplyDeleteI have done mentioned tasks.
ReplyDeletein DHCP, Scope Options, Configured option 66 and 67 as suggested by you.
after that Enable PXE boot in DP Role, Cross check the WDS for know and unknown computers.
Distributed the boot images ( x86 and x64) to Distribution Point.
I have created Windows 2012 Operating System Image in SCCM Library with the help of UNC path of install.wim file and Distributed it to DP.
Created Task Sequence for windows 2012 OS Image.
Created One test Collection without any query method.
Imported Computer information in devices section of Assets and Intelligence with MAC address of Hyper-V VM Machine, Added this computer to test collection.
Deployed Task Sequence on test Collection
Reset the VM Machine, Now it is picking IP Address from DHCP, but not going to WDS Server installed on SCCM
Note: DHCP is configured on Domain Controller and WDS on SCCM VM Machine
"no entry found in database for device"
Any registry key need to be enter in SCCM VM Machine ?
Hi Kirpal,
DeleteI have tested above mention steps and worked fine in my lab.
Here is some different setup i have configured in sccm lab.
without DHCP server how to deploy image using SCCM.
Have a look in the SMSPXE.log file Kirpal. Do you see the MAC address you are expecting? Note that, by default, Hyper V uses dynamic MAC addresses. Is this your problem?
ReplyDeleteYou could configure your VM to use static MAC
OR
why don't you just use "Unknown Computers". It's much easier.
Gerry
VM is set to Static MAC address and task sequence is already deployed to unknown computers collection as well as manually created device collection, I think I have to log incident in Microsoft for same.
ReplyDeleteHi Kirpal,
ReplyDeleteI saw your question in the Technet Forum and read the SMSTS.log file. It's very strange that you are getting "no entry found in the database for the device" when the log file says the opposite.
I saw the response about the SSL certificate on the MP but not on the DP. That does cause issues but the symptoms are usually different - you get the dreaded "PC cannot be repaired" error.
It would be a good idea to log a support incident. Please let me know how you get on.
Gerry
I have followed your wonderful guide to set up SCCM 2012 but when I try and boot by pressing F12 I get the following error.
ReplyDeleteRecovery
Your PC needs to be repaired
The windows boot configuration Data (BCD) file from the PCE server does not contain a valid operating system entry. Ensure hat the server has boot images installed for this architecture.
If I look inside reminst\smsboot\x64 it is not empty but it certainly doesnt have a boot.wim inside.
I have tried to disable PXW in the DP and then Re enable several times to no avail.
Any help would be much apreciated
Hi Gareth,
DeleteRemove your boot images from the DP
Disable PXE on the DP. Confirm that you want to remove WDS (on occasions I've had to remove WDS manually in advance)
Manually delete the Remoteinstall folder
Wait 10 mins or so
Try to Add a role in Server Manager - you will see that a reboot is pending
Reboot
Enable PXE point on the DP again.
Check the distrmgr.log for issues.
Ensure that the Remoteinstall folder is recreated and that it is not empty
Re-distribute the boot images.
Note that you won't find the boot files in that location. Look in \RemoteInstall\SMSImages. You will find the boot images in their respective folders.
Also, remember that you have to distribute BOTH boot images (x86 and x64), even if you think you don't need them.
Hope this helps,
Gerry
Thank you for the help, I noticed that my MP was critical in Site Status. Fixed this by changing IIS to network instead of local and setting correct permissions. Still can't get it to boot I get the same error message, will it boot even if I have no task sequences or images (just from the boot wim)
ReplyDeleteNo Gareth. It will only boot if there is a task sequence deployed to the device (either directly or as Unknown Computer).
ReplyDeleteCheck the SMSPXE.log file.
The log file shows these errors when I try to PXE boot
ReplyDeletereply has no message header marker SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
reply has no message header marker SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
Failed to send status message (80004005) SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
Failed to send the status message SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
00:50:56:A8:14:3B, F19F2842-E02C-41BC-C663-5F37CA7ADE5C: Not serviced. SMSPXE 10/12/2013 14:20:04 2452 (0x0994)
Thank you ever so much for your help
meaning, you have ssl authentication broken... between (PXE level)client and server. make sure you have valid client cert published in DP and installed web server certificates in MP as well as DP. good luck...
DeleteI've answered this in the TechNet forum Gareth:
ReplyDeleteNo response from Windows Deployment Services server.
Launching pxeboot.com
This part is not normal Gareth.
Is the client in the same subnet as the PXE enabled DP? If not what additional configuration have you done - IP Helper or DCHP Scope Option?
Please describe in detail what you have configured.
Hi, can SCCM 2007 R2 support ?
Deletewhat should i perform so that i can use the manual key in Hostname and select the TS that i want after Bootdisk?
I'm sorry. I don't really understand the question.
DeleteHello Gerry,
ReplyDeleteI am facing a very strange problem. My VM starts, picks up a DHCP IP from the DHCP server, where scopes are configured. then it starts the SCCM sequence, contacts a network share to pick up the OS image and then starts OS installation, once it completes that , it has to again access the same share to pick up IPAK image, but it fails here. I have noticed that after OS installation the VM drops the DHCP IP and gets an APIPA IP. Can you suggest something here?
What happens if you do not deploy this IPAK image? Does the TS finish successfully (with a configured NIC in the OS)?
DeleteThe strange thing is that this works fine for vlan200 and doesnt works when I put the VM in different Vlan. The catch is that SCCM server and DHCP server are in Vlan200. My VM in Vlan45 fails. All the rules are in place to allow intervlan communication. When I do a IPconfig/renew before connecting to the share network folder second time, it works.
DeleteHi Gerry,
ReplyDeletewe do have an issue with DHCP and PXE. We have our environment with novell DHCP and now we are have the PXE running from SCCM server with options 66 and 67 configured. I'm not sure what we are missing but i'm unable to PXE boot. I can enable the scope on SCCM server to test and seems working and created a sccm boot cd which works as well.In our switches we have configured DHCP and SCCM server ip addresses as the helper ip address.
Hope you can share some of your experience for this matter...
Thanks
Hi Gerry,
ReplyDeleteI have tried that but still unable to get to PXE. After adding the DHCP options i have got to TFTP........ in the client pc ant wont go any further.
Any Ideas?.
Thanks
Hello Gerry,
ReplyDeleteThis is Ramneesh again. I spoke to you in another post while i had issues installing SCCM, SQL 2012,
And its working now, thanks to you.
The issue i am facing is while booting over PXE, i am able to connect tO DHCP and get an IP for baremetal installation,
after it asks for "Press F12 to boot over the network"
and it starts loading the boot file from configuation manger as well,
But after that it just shows the screen with SCCM 2012 logo, but
doesn't show any image to deploy.
i created collection, then i assigned the computer account to the collection,
then i create task sequence and deployed it.
I don't know where i might be doing wrong, as i am successfully able to boot over the network to my task sequence created in SCCM,
BUT can't actually load the insallation (.wim) file from the task sequence, may be some thing wrong with the task sequence setting,
thanks in advance for reply,
Ramneesh
Hi Ramneesh,
DeleteI find that the easiest way to do this is to use "Unknown Computers". Deploy your task sequence to Unknown Computers and it will be available when you PXE boot a new machine.
Note that if the machine is already known to ConfigMgr you must delete it first for this to work. I see that you have added the computer account to a collection. That would suggest it is already known.
Also be careful when you are actually deploying the task sequence. On the Deployment settings screen you must choose to make it available to PXE - it's not the default.
So if I understand this properly, "IP Helpers" are the same as ipbootprelay - it just forwards the DHCP requests across a router to your DHCP server. Which would be set up anyway on your network and wouldn't be something you'd just configure for SCCM. So if it is really just sending you to the DHCP server to get the 66/67 parameters (which is not supported) how can it also be the best practice at the same time? Can you clarify this?
ReplyDeleteIn our case, PXE is already in use on some subnets, so if these broadcasts are already happening and responding to PXE requests on a subnet, which would your device use - the local PXE or the response back from your IP Helper address?
Thanx...
Gerry, thanks for your work.
ReplyDeletei have added the dhcp options 66 and 67. but im getting an error when booting my machine, it says: "TFTP Download: smsboot\x664\abortpxe.com"
...
"Operating system not found"
while on the SCCM Server SMSPXE.log i get:
no advertisement found no boot action.Aborted and Not serviced
That means that the infrastructure is working but there is nothing deployed to that particular computer. If you are using Unknown computers that means that the MAC address is known to ConfigMgr.
DeleteA couple of things you can do:
1. Run the ConfigMgr report - Computer for a specific MAC address. This will tell you if your MAC address exists in the database and the name of the computer. Just delete it from ConfigMgr. Now it is Unknown.
2. ConfigMgr often knows the MAC address of a computer after a failed imaging attempt. Have a look in All Systems for Unknown. Delete them all (be careful not to delete the "Unknown Computers" collections).
Dear Gerry,
ReplyDeleteI have all in same subnet but I am getting same issue like boot file not received please give me solution on that
Dear Gerry,
ReplyDeleteI am Mathan T and I have tweeted some screen shot my errors kindly look in to that
If you are having issues with clients in the same subnet it looks like you have problems with WDS. Is the WDS service running? Look at your DP drive. Is there a RemoteInstall folder - is it populated with folders/files?
DeleteHi Gerry,
DeleteThanks for your information, I checked the WDS service but it is on started mode only and the remote install folder has shared with access, for the account where we configured for Net Access Account
Thankssssss for your great work
Hello Gerry
ReplyDeleteI have the same issue my DHCP have 2 Subnets
on Scope Option 067 Boot file name is SMSBoot\x64\wdsnbp.com
but I cannot locate this folder (SMSboot\x64) in my SCCM Server
so what can i do?
please help me
It should be in the RemoteInstall folder on your PXE-enabled Distribution Point. If it isn't there WDS is not installed correctly.
Deleteso i must Remove WDS Role and Add again, or i must do that and reconfigure Distribution point with PXE again
DeleteIf you remove PXE support from the DP WDS should automatically be uninstalled (you will need to reboot). Check and do this manually if it doesn't happen automatically.
DeleteThanks, and -->
DeleteWhat about this Issue in SMSPXE.log
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 6/4/2014 3:40:02 PM 10920 (0x2AA8)
Hi Gerry, I'm new to IP Helper and was wondering, while reading your article, what address I need to add to the IP Helper. You write "the ConfigMgr/MDT Server" - do you mean the DP or the actual Primary Site?
ReplyDeleteSpecifically I'm talking about a PXE-enabled Distribution Point.
DeleteThanks a lot for the exellant guide. I have a query regarding Office activation. The command would activate Office, but where does one enter the activation key for MAK activation.
ReplyDeleteNitin
It's in one of the steps of the Task Sequence Wizard - "Install Windows".
Deletei have successfully configured pxe on sccm 2012 sp1 but when i press f8 i couldn't get ip address. i did add the NIC driver on the boot image but still no luck. any help would be appreciated.
ReplyDeleteThen it looks like you are not using the correct NIC driver for your PE version Nilay.
DeleteSCCM 2012 RTM - Windows AIK for Windows 7 - Windows PE3
SCCM 2012 SP1 - Windows ADK for Windows 8 - Windows PE4
SCCM 2012 R2 - Windows ADK for Windows 8.1 - Windows PE5
You can find this information here
http://technet.microsoft.com/en-us/library/dn387582.aspx
The driver version you need should match the PE version, regardless of the OS you are deploying. Therefore, in your case, you need Windows 8 NIC drivers.
Test using drvload in the command prompt to get the correct driver.
Thank you Sir...
ReplyDeleteYou're welcome. Glad to help.
DeleteHi Gerry,
ReplyDeleteWe would like to prompt admins to manually type domain join account and password during the TS execution like using the OSDComputerName collection variables. Can we remove the join domain step in the build-in TS and use the OSDJoinAccount & OSDJoinPassword as collection variables? Thanks in advance.
I'm not sure why you would add a manual step like that. I've never tried. Test it and see.
DeleteScenario 1
ReplyDeleteDHCP Server Subnet A
SCCM DP Subnet A
Client Subnet A
Error No Boot File E53
In this Scenario this should not even need helpers. If I turn on DHCP Option 66/67 Client will work
Scenario 2
DHCP Server Subnet A
SCCM DP Subnet A
Client Subnet B
Error No Boot File E53
IP Helpers in Place to DHCP Server & SCCM DP. If I turn on DHCP Option 66/67 Client will work
Hello
ReplyDeleteI have the following issue :
I 'm testing a zti installation
all is ok but when I clear requirement pxe deployxement
when i boot my windows machine each time he try ro tun
the n12 file. but he keep asking me to press on f12 ...
( i have renamed the file in the boot /x64 folder
my pc are x64 and i change the dhcp option to point to x64 folder
tks
tks for your help
Why don't you change the boot sequence to boot from hard drive first? Choose One Time Boot if you want to boot from the NIC.
Deletebecause if I ask to boot fron the hard disk first he will never run pexe and run the os directly ???
ReplyDeleteIt will if you ask it to. Select One Time Boot (method varies between makes and models) and choose Network Boot.
DeleteThe fact is that I need to do a zero touch install, Nobody will be onsite ? all must be automatic
ReplyDeletetks Gerry
If you are trying to rebuild a computer at a remote site with no user intervention then you should not use the PXE method at all. You should deploy the TS to a collection containing that device and the computer will automatically restart and deploy the TS.
DeleteHi Gary,
ReplyDeletethanks for all your efforts that have been so helpful and are much appreciated. Quick question about Option 67:
If I have an x64 boot Image and use the x86 file name in the option 67 would that cause any issues?
Kind regards
Amir
Only if you using UEFI. In that case you must use the correct architecture.
DeleteHow do i add Computer name as computer serial number?
ReplyDeleteThe easiest way to do this is by integrating ConfigMgr and MDT and then using MDT task sequence variables.
DeleteYour guide has been invaluable in setting up my SCCM server!
ReplyDeleteI am trying to set up automated computer naming during the imaging task sequence so that it detects if the machine is a laptop, desktop, or vm. I think I am close to getting it right but so far it fails.
SCCM has MDT integration
What I've tried to do:
Directly under the Apply Operating System task, I've created a folder called TS Variables.
1. Use Toolkit Package which points to MDT Tools, which is just the 4 MDT folders from the MDT share (Control, Scripts, Servicing, Tools)
2. Gather (gather only local data (do not process rules)
3. Set Task Sequence Variable: OSDComputerName, Value: XX-LT-#Right("%SerialNumber%",6)# and then under options Condition: IsLaptop equals "TRUE"
and then 2 more that are similar for IsDesktop, and VMPlatform equals "Hyper-V"
Hi Gerry,
ReplyDeleteHope you are doing good. My question is that when you configure IP Helpers, then configuring DHCP options as well is possible? Does it conflict?
It's not a great idea. Please just use IP Helpers.
ReplyDelete