ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 12 Operating System Deployment - DHCP/IP Helper and Computer Name
Back to main menu
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
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
No comments:
Post a Comment