SCCM PXE SETUP Questions
I have a SCCM 2007 Single Server, One site Architecture. I am setting up the PXE Role in SCCM. I installed SCCM on a Fresh Install of Windows Server 2008 with All the Required roles, Including SQL, before Installation of SCCM. I even extended the schema
& Created a service account for it. I didn't configure any of the roles except maybe SQL, only the necessary Settings to get it installed. Now when setting up the PXE Role I have added the role as instructed in the documentation.
PXE installed okay. I then went into WDS to look at it's status & I received a message that It wasn't configured. After some research it seems that the next thing I should do is publish both of the boot files to both a Standard DP & the PXE DP. Then
the install of the SCCM PXE role should be complete. Is this true? Did I miss anything? Also the RemoteInstall Directory is present with the correct folders & files indicated that be in there. Furthermore, I seem to be getting the message that the WDS
status can be ignored & SCCM auto configures it even though it says it isn't configured. Also can you guide me on the server-side firewall settings for SCCM on a server with all SCCM roles installed?
August 7th, 2012 11:07pm
In Server manager right click the server > Configure > Check configure dhcp option 60 and (If the DCHP is on the same server and the PXE select do not listen on port 67). In PXE responces choose support unknown computers if needed. Then you can instlal
the PXE server role the boot images are added from SCCM not WDS.
Justin | http://patchmypc.net
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2012 12:01am
Hi
"After some research it seems that the next thing I should do is publish both of the boot files to both a Standard DP & the PXE DP. Then the install of the SCCM PXE role should be complete. Is this true?"
Yes, it's true. No need to manually configure WDS. PXE role will do the needful for you! Another important thing is that your PXE DP should have boot images only. Do not publish any other package/OS Images on PXE DP.
"can you guide me on the server-side firewall settings for SCCM on a server with all SCCM roles installed?"
refer below MS article on all ports which are being used in SCCM environment.
http://technet.microsoft.com/en-us/library/bb632618.aspx
Few basic ports are as below
Client to MP: 80 mixed mode, 443 for native mode
Client to SUP: 80/8530 or 443/8531
Client to DP: 80/443 and 445 (SMB)
Client to SLP: 80
If firewall is enabled then you can customize the same be defining port exceptions or it can also be done through GPO.
Cheers | Navdeep Sidhu
August 8th, 2012 5:03am
Hi
"After some research it seems that the next thing I should do is publish both of the boot files to both a Standard DP & the PXE DP. Then the install of the SCCM PXE role should be complete. Is this true?"
Yes, it's true. No need to manually configure WDS. PXE role will do the needful for you! Another important thing is that your PXE DP should have boot images only. Do not publish any other package/OS Images on PXE DP.
"can you guide me on the server-side firewall settings for SCCM on a server with all SCCM roles installed?"
refer below MS article on all ports which are being used in SCCM environment.
http://technet.microsoft.com/en-us/library/bb632618.aspx
Few basic ports are as below
Client to MP: 80 mixed mode, 443 for native mode
Client to SUP: 80/8530 or 443/8531
Client to DP: 80/443 and 445 (SMB)
Client to SLP: 80
If firewall is enabled then you can customize the same be defining port exceptions or it can also be done through GPO.
Cheers | Navdeep Sidhu
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2012 5:03am
You need to initialize the WDS server to get rid of the "not configured" problem. WDS won't work until it has been initialized.
First, have a look in the C:\Program Files (x86)\SMS_CCM\Logs\smspxe.log to make sure that your boot image has been properly loaded by the PXE Service Point Role.
You should see something like
Opening image file "D:\RemoteInstall\SMSImages\SMSPKG\C0100002\boot.C0100002.wim
Applying image 1 to volume C:\Windows\TEMP\PXEBootFiles
Closing image file D:\RemoteInstall\SMSImages\SMSPKG\C0100002\boot.C0100002.wim
After you've checked this enter this command:
WDSUTIL /Initialize-Server /RemInst:"D:\RemoteInstall"
When adding the PXE Service Point Role, it will create the RemoteInstall directory on the drive with the most space. If you don't want it on a specific drive
don't forget to add the NO_SMS_ON_DRIVE.SMS in the root of that drive. The above command is if RemoteInstall is on D:
If the DHCP command is located on the same server run these commands:
WDSUTIL /set-server /DHCPoption60:yes
WDSUTIL /set-server /usedhcpports:no
If you don't do this the client won't receive the boot image from the WDS service.
Hope this helped you out :)
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson
August 8th, 2012 7:36am
You need to initialize the WDS server to get rid of the "not configured" problem. WDS won't work until it has been initialized.
First, have a look in the C:\Program Files (x86)\SMS_CCM\Logs\smspxe.log to make sure that your boot image has been properly loaded by the PXE Service Point Role.
You should see something like
Opening image file "D:\RemoteInstall\SMSImages\SMSPKG\C0100002\boot.C0100002.wim
Applying image 1 to volume C:\Windows\TEMP\PXEBootFiles
Closing image file D:\RemoteInstall\SMSImages\SMSPKG\C0100002\boot.C0100002.wim
After you've checked this enter this command:
WDSUTIL /Initialize-Server /RemInst:"D:\RemoteInstall"
When adding the PXE Service Point Role, it will create the RemoteInstall directory on the drive with the most space. If you don't want it on a specific drive
don't forget to add the NO_SMS_ON_DRIVE.SMS in the root of that drive. The above command is if RemoteInstall is on D:
If the DHCP command is located on the same server run these commands:
WDSUTIL /set-server /DHCPoption60:yes
WDSUTIL /set-server /usedhcpports:no
If you don't do this the client won't receive the boot image from the WDS service.
Hope this helped you out :)
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2012 7:36am
Initializing wds comes after setup of the PXE role right? Meaning I will do what you described after I publish the boot images to the PXE DP. Also I believe option 60 is already set. Did I cover all my bases?
August 8th, 2012 3:02pm
Initializing wds comes after setup of the PXE role right? Meaning I will do what you described after I publish the boot images to the PXE DP. Also I believe option 60 is already set. Did I cover all my bases?
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2012 3:02pm