SCCM 2007 OS PXE Configuration
- I want to deploy winxp sp3 Build capture via pxe on a local workstation that is set to boot on pxe and I get PXE-T01 -file not found; PXE -E3B -TFTP Error file not found
I have a windows 2003 R2 SP2 running DNS, DHCP, and WDS (WDS is configured, not sure if it should be) (RIS is not install, not sure if required). DHCP Optionas as follows"
1. #602. #67 -- \boot\x86\pxeboot.com3. #66 -- FQDN for SCCM server
Second, I have a SCCM 2007 (no service packs installed), running on Windows 2003 R2 SP2, and SQL 2005(no service packs). The SCCM 2007 manages all site roles to include ConfigMgr PXE Service Point.
These questions may have been asked before but I cannot find what applies to my environment so please bare with me.
If RIS is required to be installed is there a way to do this with out having to restart the server?
Second, can I deploy to a machine that already has the client installed with out having to boot to pxe? I have tried this according to this link using computer association but nothing happens.
http://www.windows-noob.com/forums/index.php?/topic/569-how-can-i-deploy-windows-xp-sp3-using-sccm-2007-sp1-part-1/
http://www.windows-noob.com/forums/index.php?/topic/570-how-can-i-deploy-windows-xp-sp3-using-sccm-2007-sp1-part-2/
Answers
Please correct the second point:
"2. If WDS resides on a seperate server form DHCP, only dhcp option 66 is required"
No need to set any DHCP option if DHCP and WDS are on different server.
Rest looks good to me.
Best of luck!
Regards,
Harpreet Rana
Harpreet Rana- Marked As Answer byJoe1099 Wednesday, November 25, 2009 5:47 PM
All Replies
- Is the PXE role installed on your server through the configmgr console? This is a must. Do you have the boot images added to that distribution point and updated through the console? Also note-you need to have both the x64 and 32 bit boot images added to this DP even if you are deploying a 32bit image. Found that out the hard way!
On that server, you can view the smspxe.log file, which is in a folder called sms_ccm normally on the C:\ Drive. View it with a tool called SMS trace which will make it easy to read and follow. Look for specific messages.
Through configmgr, the main ways to allow a computer to boot from PXE:
-Unknown computer support, if enabled advertise a task sequence to this collectiion (NOT MANDATORY), any computer without a record in the configmgr console will be given permission to boot.
-If the computer has a record already, put it in a collection and advertise a task sequence to it
- if there is no record, under OSD, choose import computer information and make a record from the mac address and add it to a collection.
If all else fails, remove the PXE point, uninstall those DHCP options and then add the PXE Point again. That should reset everything.
Hope this helps! - I have seen problems if WDS is configured on the server. You shouldnt run the WDS configuration wizard after installing WDS.
Mayur Rybal, thanks for the response to my question. You mention PXE Role and Configmgr are you referring to SCCM and PXE service point or are you referring to WDS configuration?
I currently have PXE service point installed on my SCCM server and I have DHCP and WDS co-hosted on my DNS/AD server. I have configured DHCP options 60,66 and 67.
When I configured WDS I selected options 66, and 67.
Now I notice after setting up WDS I now have a folder called RemoteInstall that store my images on my root directory. I also notice when I installed PXE service role on SCCM I have a new DP called SMSPXEIMAGES$. Something is not right, shouldn't these services share common folders for images?
Another thing I have been reading from the link below and it gives me the conclusion that WDS and DHCP have a conflict with option 67 when co-hosted. I am thinking of moving WDS to the PXE service point server which is my SCCM. Can I move PXE service point and WDS to a server all their own and if so is there a recommend configuration make these serices talk to one another?
The sites I recently reference is below. Please share your thoughts on the written process as whether accurate or not. Thank you again for your help.
http://social.technet.microsoft.com/forums/en-US/configmgrosd/thread/0a9ae3b5-ffe9-45e8-a2d4-967325de9e37/
One more thing, do I need RIS installed before I install WDS?Let's start with that when you are going to install a ConfigMgr PXE Service Point you do NOT need to configure WDS (ConfigMgr will do that for you)!
Install WDS on the same server as where you are going to install the PXE Service Point. After the installation of WDS cancel the wizard of the configuration. Now install you PXE Service Point on the same server and everything will be configured for you.
Note: If you are using Windows Server 2003 you must install the Remote Installation Services (RIS) and the Windows Automated Installation Kit (Windows AIK). If you are using Windows Server 2003, Service Pack 2 you must install the Windows Deployment Services using Add or Remove Programs.
My Blog: http://www.petervanderwoude.nl/- I am talking about removing the custom setting you set manually in WDS and removing the PXE service point role from configmgr, and letting it install it again. As Peter wrote, configmgr takes care of all of the WDS Settings automatically.
If you want to watch the configmgr logs during this, you can bring up distmgr.log on your management point. View it in SMStrace32 to make things easier.
That is proper to have the smspxeimages$ share. Basically. when you PXE boot a machine it is "imaging" the ram with your boot image. To add these from the configmgr console, you choose the boot image, then add it to the SMSPXEIMAGES$ Share. It is a separate share for PXE images. - Rybal, from what you and Peter explained its beginning to make since now. So as I understand I push my boot image both x86 and x64 to SMSPXEIMAGES$ DP. What about my Windows XP package do I send it to my standard DP or do I use the SMSPXEIMAGES$ DP. I what i am asking is the SMSPXEIMAGES$ DP only for the boot image?
- Peter thanks for the clarification.
I have one more question, you said if I am using Windows Server 2003, Service Pack 2 of which I am, I need to install WDS using Add or Remove Programs.
My question is am I required to install RIS before adding WDS or is that just if you are not at service pack 2? I want to thank you Peter and Rybal for your assistance. you guys are are the best. - Hi Joe,
RIS is not at all required for PXE configuration. It only requires WDS and PXE service Role on the same box (this could be separate from SCCM Server). Moreover we could install WDS as a component from the server or can download, preferred way is to install via Add/Remove component if Windows Server 2003 SP2 is installed.
Adding Boot images to Distribution Points:
As per my experience I suggest you update both the boot images (x86 and x64) to Standard DP as well as SMSPXEIMAGES$.
Adding Operating System Image to DP:
OS Image is not required to be updated on SMSPXEIMAGES$ DP. It only required to be updated on Standard DP.
Hence SMSPXEIMAGES$ DP is only for the boot images.
Now from your environment it appears that you have DHCP and WDS on Same box. Generally WDS and DHCP both listens at port 67 therefore having both of them would make life difficult on the said UDP port 67. So in addition to configuring the server to not to listen on port 67, you will need to use your DHCP tools to add Option 60 to their DHCP scopes, which you already have. Actually it allows the PXE client to know about theWDS PXE server from the DHCP response generated by the DHCP server. Setting DHCP option 60 has one side effect: clients booting from the network are always notified that the Windows Deployment Services PXE server is available, even if the server is not operational or has stopped.
Moreover we need to sure if DHCP is authorized or not.
Hope this answeres your question!
Regards,
Harpreet Rana
Technikala
Harpreet Rana Harpreet, thank you for clearin g all of that up for me. I am going to uninstall WDS from my DHCP server and uninstall PXE service point role from my SCCM server. I will co-host both WDS and PXE service point role on the SCCM server seperate from my DHCP server. When I install WDS from Add or Remove Programs I will not configure it. At this point I only need to install PXE service point role and I should be able to add my X86 and x64 boot image to SMSPXEIMAGES$ DP. As for my DHCP options I only need to set option 66, option 60 and 67 can be removed no that my WDS resides on a seperate server.
So as I understand it:
1. No need for RIS if running Windows 2003 R2 SP2
2. If WDS resides on a seperate server form DHCP, only dhcp option 66 is required
3. No need to configure or start WDS once installed, PXE service point role will do the configurations for WDS and start the service.
4. load both x86 and x64 to SMSPXEIMAGES$ DP.
So if this is correct Harpreet then all I have to do is decide how I will advertise to known and unknown computers.
Thank you Harpreet if you agree with these steps then this should get me up and running. Thank you again.Please correct the second point:
"2. If WDS resides on a seperate server form DHCP, only dhcp option 66 is required"
No need to set any DHCP option if DHCP and WDS are on different server.
Rest looks good to me.
Best of luck!
Regards,
Harpreet Rana
Harpreet Rana- Marked As Answer byJoe1099 Wednesday, November 25, 2009 5:47 PM
- Hello Harpreet, I removed option 66 from DHCP server as you mention in your last note. I am recieving PXE-E53: No Boot filename received; PXE-MOF: Exiting Intel Boot Agent.
I have verified that RemoteInstallSMSBoot\x86 is populates with these files:
abortpxe.com
bootmgr.exe
pxeboot.com
pxeboot.n12
wdsnbp.com
RemoteInstall\SMSIMAGES\SMSPKG\DIR00001\boot.DIR00001.wim 144,861KB
RemoteInstall\SMSIMAGES\SMSPKG\DIR00002\boot.DIR00002.wim 144,252 KB
WDS service is running
I have updates SMSIMAGES$ DP with boot image x86 and x64
DHCP server, and co-hosted SCCM and WDS server are on the same subnet.
Additionally I imported the MAC and GUID into computer association.
What am I missing? Please help.- Edited byJoe1099 Tuesday, November 03, 2009 9:49 PM
- Did you import the computer in a collection or are you using Unknown Computers?
My Blog: http://www.petervanderwoude.nl/ - I imported the computer into the collection.
Should I have used unknown computers and what are the steps for this. I greatly appreciate your help here as I have been working on this for days and I am receiving much pressure from management. Thank you lots. - I would:
1) start and stop Windows Deployment service
2) Use Trace32.exe (Part of sms toolkit) and view the log files in the c:\sms_ccm folder. One should be called smspxe.log. This will give more detailed information. Watch for errors when the service is starting especially.
Please post any errors you see in this log file. Trace32 makes it a ton easier to read and highlights errors and warnings. I use this tool almost every day.
Also, you should only need to import the MAC address or GUID. I would recommend just importing the MAC address. Are you positive you have a task sequence advertised to the collection you are importing into? Check your task sequence properties (right click-> properties) to verify it has the correct boot image selected.
Lastly- if you have reporting enabled- run a report of that machines MAC address and make sure that MAC address does not have a duplicate record that resides in another collection. I would recommend not using unknown computer support until you have it working with importing the computers information, sometimes getting unknown PC support to work can be tricky. You could try it though as a troubleshooting step though.
Edit: I noticed you are running no service packs, do you have the R2 feature pack installed? - I agree with the steps suggested by Rybal, I would suggest you too to look at SMS_CCM\Logs\smspxe.log or paste the results here when you boot the Pxe Client.
Apart from verifying if the task sequence is advertised to the collection to which we have imported the Client. [ Try Creating computer associations using MAC and advertise the task sequence again to the collection again] Monitor the smspxe.log or paste the results here.
Further verify that WDS is authorized in DHCP.
Regards,
TeckniKala
Harpreet Rana TeckniKala and Rybal, I thank you both for your assistance as I am beginning to lose hope here.
I am still receiving PXE-E53 No Boot filename Recieved.
WDS is authorized in DHCP.
Rybal I am using Sccm 2007 SP1; Task sequence properties I am showing X86 bootimage3
As far as a duplicate. when I ran a report for duplicate MAC I had a duplicate for MAC 00:24:E8:93:03:8C which is the MAC I am using.
This is not a new machine to SCCM it has a CM client installed. The report show the duplicate applied to netbios name.
since your last words I have removed my task sequence; remove my collection; uninstalled PSP; uninstalled wds and rebooted.
I then reinstalled WDS and restarted; installed PSP; Ran PXE.msi; verified my logs which are below. I recreated my DP and DP smspxsimages$ and updated with boot x86 and x64; I made a empty collect; configured a task sequence for PXE boot; imported computer mac and attact it to my collection; configured an avert and attacted it to the collection.
The SMSPXE.log never list my MAC 00:24:E8:93:03:8C at boot up and on the machine I continue to receive PXE-E53 No Boot filename Recieved.
Any Ideas?=========================================================================================================
SMSPXE.log
Executing LookupDevice(41180CB7-BE87-0133-85CB-575DED0CD68F, 00:1A:64:11:5D:78) smspxe 11/4/2009 2:20:00 PM 276 (0x0114)
CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 11/4/2009 2:20:00 PM 276 (0x0114)
MAC=00:1A:64:11:5D:78 SMBIOS GUID=41180CB7-BE87-0133-85CB-575DED0CD68F > Device not found in the database. smspxe 11/4/2009 2:20:00 PM 276 (0x0114)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 2237c6c smspxe 11/4/2009 2:20:02 PM 5664 (0x1620)
Policy Provider settings flushed due to registry change
smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Reloading PXE Provider Settings. cached=0 smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\Identification:
SMS Site Settings:
Server: DIR-R02
SiteCode: DIR
Parent SiteCode: <empty>
smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Cannot read the registry value of MACIgnoreListFile (80070002) smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
PXE Settings:
IsActive: Yes
SupportUnknownMachines: No
MACIgnoreListFile: <empty>
ResponseDelay: 0
CacheExpire: 3600
HTTP Port: 80
HTTPS Port: 443
IISSSLState: 0x0
BindPolicy: Exclude <empty>
TRK: <non empty>
SiteSignCert: <empty>
Root CA Certs: <empty>
PXE GUID: 406b29ed-c5e7-4c6d-97fa-38f4ce3dc28d
PXEPassword: <non empty>
smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Loaded TFTP settings from reg key HKLM\SYSTEM\CurrentControlSet\Services\TFTPD\Parameters:
TFTP Settings:
Directory: D:\RemoteInstall
smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
MAC Ignore List Filename in registry is empty smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Loaded Database settings from reg key HKLM\Software\Microsoft\SMS\PXE:
Database Settings:
Server: DIR-R02
Database: SMS_DIR
User: <empty>
Password: <empty>
Use Integrated Security: No
Impersonation Required: No
smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
PXE Provider Settings Changed smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Querying Database for Cert with GUID: 406b29ed-c5e7-4c6d-97fa-38f4ce3dc28d smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
inside GetPxeCert SmsPXE 11/4/2009 2:20:13 PM 5088 (0x13E0)
Executing PxeGetCert(406b29ed-c5e7-4c6d-97fa-38f4ce3dc28d) SmsPXE 11/4/2009 2:20:13 PM 5088 (0x13E0)
CDatabaseProxy :: GetPxeCert succeeded: 406b29ed-c5e7-4c6d-97fa-38f4ce3dc28d \\DIR-R02 <non empty> SmsPXE 11/4/2009 2:20:13 PM 5088 (0x13E0)
Loaded PXE settings from DB: PXE Cert: <non empty>
smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Site Code: (null), Parent Site Code: DIR smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Executing PXE_GetSiteTypeAndDefaultMP(DIR) smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
GetSiteTypeAndDefaultMP: SiteType=2 DefaultMP=DIR-R02.ADS.TXDIR.GOV smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Site Type: 2 smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
GetUnknownMachineResource (DIR,x86): smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Unknown machine resource not found smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
GetUnknownMachineResource (DIR,x64): smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Unknown machine resource not found smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
Loaded PXE settings from DB: Unknown machine GUIDs: (x86) , (x64) smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
No need to check cert smspxe 11/4/2009 2:20:13 PM 5088 (0x13E0)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 2252f1c smspxe 11/4/2009 2:20:32 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22582b4 smspxe 11/4/2009 2:20:39 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 225d64c smspxe 11/4/2009 2:20:43 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 2263a9c smspxe 11/4/2009 2:20:51 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 226f284 smspxe 11/4/2009 2:21:07 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 227aa6c smspxe 11/4/2009 2:21:14 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 227ed4c smspxe 11/4/2009 2:21:18 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 228a534 smspxe 11/4/2009 2:21:26 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 228d75c smspxe 11/4/2009 2:21:39 PM 5664 (0x1620)
Executing LookupDevice(113FE767-6CD0-CA32-8469-68688DCF16BA, 00:1A:64:07:7F:F4) smspxe 11/4/2009 2:21:39 PM 276 (0x0114)
CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 11/4/2009 2:21:39 PM 276 (0x0114)
MAC=00:1A:64:07:7F:F4 SMBIOS GUID=113FE767-6CD0-CA32-8469-68688DCF16BA > Device not found in the database. smspxe 11/4/2009 2:21:39 PM 276 (0x0114)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 2293bac smspxe 11/4/2009 2:21:42 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22a57e4 smspxe 11/4/2009 2:22:15 PM 5664 (0x1620)
Executing LookupDevice(41180CB7-BE87-0133-85CB-575DED0CD68F, 00:1A:64:11:5D:78) smspxe 11/4/2009 2:22:15 PM 276 (0x0114)
CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 11/4/2009 2:22:15 PM 276 (0x0114)
MAC=00:1A:64:11:5D:78 SMBIOS GUID=41180CB7-BE87-0133-85CB-575DED0CD68F > Device not found in the database. smspxe 11/4/2009 2:22:15 PM 276 (0x0114)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22a689c smspxe 11/4/2009 2:22:16 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22aee5c smspxe 11/4/2009 2:22:20 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22ba644 smspxe 11/4/2009 2:22:28 PM 5664 (0x1620)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22bf9dc smspxe 11/4/2009 2:22:44 PM 5664 (0x1620)
[169.254.144.174:4011] Recv From:[169.254.144.174:9000] Len:274 283d32c smspxe 11/4/2009 2:22:56 PM 5664 (0x1620)
Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF) smspxe 11/4/2009 2:22:56 PM 276 (0x0114)
CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0 smspxe 11/4/2009 2:22:56 PM 276 (0x0114)
MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database. smspxe 11/4/2009 2:22:56 PM 276 (0x0114)
[169.254.100.002:67] Recv From:[000.000.000.000:68] Len:548 22c7f9c smspxe 11/4/2009 2:22:57 PM 5664 (0x1620)
=======================================================================================================PXESetup.log
<11-04-2009 13:31:01> SMSPXE Setup Started....
<11-04-2009 13:31:01> Parameters: D:\CONFIG~1\bin\i386\ROLESE~1.EXE /install /siteserver:DIR-R02 SMSPXE
<11-04-2009 13:31:01> Installing Pre Reqs for SMSPXE
<11-04-2009 13:31:01> ======== Installing Pre Reqs for Role SMSPXE ========
<11-04-2009 13:31:01> Found 2 Pre Reqs for Role SMSPXE
<11-04-2009 13:31:01> Pre Req MSXML60 found.
<11-04-2009 13:31:01> MSXML60 already installed (Product Code: {1A528690-6A2D-4BC5-B143-8C4AE8D19D96}). Would not install again.
<11-04-2009 13:31:01> Pre Req MSXML60 is already installed. Skipping it.
<11-04-2009 13:31:01> Pre Req Wimgapi found.
<11-04-2009 13:31:01> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<11-04-2009 13:31:01> Pre Req Wimgapi is already installed. Skipping it.
<11-04-2009 13:31:01> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<11-04-2009 13:31:01> Installing the SMSPXE
<11-04-2009 13:31:01> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<11-04-2009 13:31:01> WDS Service is installed.
<11-04-2009 13:31:01> SMSPXE already installed (Product Code: {641BA145-0B62-44C3-BD4D-0135E3A989A1}). Upgrading/Reinstalling SMSPXE
<11-04-2009 13:31:01> New SMSPXE is the same product code. This is a minor upgrade.
<11-04-2009 13:31:01> Enabling MSI logging. pxe.msi will log to D:\ConfigMgr\logs\pxeMSI.log
<11-04-2009 13:31:01> Installing D:\ConfigMgr\bin\i386\pxe.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
<11-04-2009 13:31:08> pxe.msi exited with return code: 0- Joe, can you look under Component Status and then look for SMS_PXE_SERVICE_POINT component and populate the logs? When the client tries to boot, and if it can contact the SMS server, a log entry is generated. See if you find "An unknown computer with MAC address xx xx xx xx xx xx was encountered" or "A device was instructed to boot from boot image xxxxx". Try to find these entries during the time your client tried to PXE boot.
Mayur - Mayur, I find this very odd, the SMS_PXE_SERVICE_POINT does show a unknown computer with MAC address xx xx xx xx xx xx was encountered, but its not the MAC address I imported. Infact I never see the client mac I imported when I boot the client in the smspxe.log either, but this unknown mac address appears to be flooding my sccm server and shows up in both logs.
- At this point would anyone know why I would the imported mac address would not show up in smspxe.log or SMS_PXE_SERVICE_POINT logs?
I am out of options here please help. - The other unknown MAC address that you said is flooding the server; does it happen exactly the same time your known client is trying to boot?
It might be a completely isolated incident. Some clients have network boot as the only boot option and they will constantly try to PXE boot if you have not provisioned them.
If you do not see the known computers MAC address entry in the SMS_PXE_SERVICE_POINT log when it tries to boot that will mean there is a connection issue.
Mayur - Mayur, that last statement you made about having a connection issue if I dont see the imported mac address entry in the SMS_PXE_SERVICE_POINT log i believe to be the clue.
My DHCP server has a class c static ip, but my dhcp scope is a class A and my SCCM co-hosted WDS and PSP have a class C static ip in the same subnet as the DHCP static ip.
If this is the issue what would be the proposed resolution?
I cannot change the ip scheme on the production servers so how do I get DHCP Bootp on a class A subnet to talk to PSP on a Class C subnet? Any ideas? - I dont see your IP configuration being an issue. The DHCP request from the client is heard from both the DHCP server and the WDS server. The DHCP server will provide an IP address whereas the WDS server will send the WDS server IP address and the boot file. As long as both servers can listen to the DHCP broadcast from the client it should be fine.
Your DHCP and WDS servers are not co-hosted and hence you do not need to play with the DHCP options. Also as I said, your should not configure WDS at all after you have installed it.
I will recommend removing all the DHCP option changes that you have made, uninstalling WDS role, uninstalling WDS, and then start over. Do not configure DHCP options after this and do not attempt to run the WDS setup wizard after WDS is installed.
As always, since every change you make within SMS sets a chain of processes to occur in the background, make sure you wait for some time for it finish applying the changes before attempting further changes.
Mayur - Muyar, what led me to believe subnets are the issue is that I dis a wire share capture and I see the client machine (00:24:e8:93:03:8c), but this mac is never seen by smspxe.log or SMS_PXE_SERVICE_POINT.
My SMS_PXE_SERVICE_POINT looks health and no errors are indicated.
As mention above there are no DHCP option set, and I will uninstall PSP and WDS and reinstall once again as I did yesterday but I am out of options and I dont know what further to do.
Bootp flags: 0x8000 (Broadcast)
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Relay agent IP address: 10.10.1.1 (10.10.1.1)
Client MAC address: Dell_93:03:8c (00:24:e8:93:03:8c)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: (OK) - Are there more than one NICs installed? Again, does the unknown MAC address you are seeing in the smspxe.log file appear exactly at the same time you boot your known computer? (Keep the smspse.log open in SMS Trace while you boot the PC and you will see entries added to the log exactly at the same time your computer tries to boot)
Have you tried importing another computer and trying to PXE boot it?
Mayur - Mayur, thanks again for your response, that unkown mac address keep reappearing every minute as we speak so I be leave it to be an isolated machine as you mention before.
As for the mac address I did import we think that we need to configure ip helper on the router to direct bootp traffic to the PSP server since clients are on a different subnet than my PSP.
When I did a wire shark capture from the PSP server Bootp messages rarely come up and onely for the spare nic on that server and I assume it because its connected.
I wonder if I configured the spare nic on the psp server with a static ip on the same subnet as the client pc will resolve the issue with bootp communication?
I was thinking another option could be to move the WDS and SMS on to the DHCP server, I just don't know what the steps are to place the PSP role on a another server are. does any one know?
