Found 0 DPs in subnet, 0 DPs in local site, 0 Dps in remote location

[mjbraun]

Greetings! I am amazed by the quality of the tutorials and discussion here, and I am thankful to have such a great resource to learn from as I get to working with SCCM. I've been working through the tutorial for deploying XP SP3 and I've run into a roadblock which I suspect comes from improperly setting up SCCM 2007, and I would appreciate any guidance or suggestions.

 

I have a test setup consisting of 3 servers (only 2 are relevant for this discussion) and a desktop. They are set up as follows:

 

DEV2950: x64 system, Windows Server 2008 R2, AD DC, DHCP, DNS, SQL Server 2008 R2, Exchange, SCOM 2007 R2, ConfigMgr component server, ConfigMgr site system, ConfigMgr site database server

 

DEV2650: x32 system, Windows Server 2008: SCCM 2007 Configuration Console, ConfigMgr component server, ConfigMgr device management point, ConfigMgr management point, ConfigMgr PXE service point, ConfigMgr reporting point, ConfigMgr server locator point, ConfigMgr site server, ConfigMgr site system, ConfigMgr software update point, ConfigMgr state migration point.

 

I am attempting to deploy an XP image (x64) to the desktop and the system properly PXE boots but grinds for a bit, and then just reboots. Checking smsts.log I see the following error:

 

"Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs"

 

I have set up my site per the SCCM installation guides (named "Wheeling") and configured the desktop for receiving the XP image by importing the computer information (with both the MAC and GUID included) into a "Build and Capture XP x64" collection and then advertised the "Build and Capture XP x64" Task Sequence to the collection.

 

I've updated the DPs with the packages for the OS/ConfigMgr/Sysprep, but I can't figure out why it's not being seen by the client. What could I be missing, or where should I be looking?

 

The smsts.log file is attached, and I would be grateful for any guidance or assistance.

smsts.log

[wmmayms]

Greetings! I am amazed by the quality of the tutorials and discussion here, and I am thankful to have such a great resource to learn from as I get to working with SCCM. I've been working through the tutorial for deploying XP SP3 and I've run into a roadblock which I suspect comes from improperly setting up SCCM 2007, and I would appreciate any guidance or suggestions.

 

I have a test setup consisting of 3 servers (only 2 are relevant for this discussion) and a desktop. They are set up as follows:

 

DEV2950: x64 system, Windows Server 2008 R2, AD DC, DHCP, DNS, SQL Server 2008 R2, Exchange, SCOM 2007 R2, ConfigMgr component server, ConfigMgr site system, ConfigMgr site database server

 

DEV2650: x32 system, Windows Server 2008: SCCM 2007 Configuration Console, ConfigMgr component server, ConfigMgr device management point, ConfigMgr management point, ConfigMgr PXE service point, ConfigMgr reporting point, ConfigMgr server locator point, ConfigMgr site server, ConfigMgr site system, ConfigMgr software update point, ConfigMgr state migration point.

 

I am attempting to deploy an XP image (x64) to the desktop and the system properly PXE boots but grinds for a bit, and then just reboots. Checking smsts.log I see the following error:

 

"Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs"

 

I have set up my site per the SCCM installation guides (named "Wheeling") and configured the desktop for receiving the XP image by importing the computer information (with both the MAC and GUID included) into a "Build and Capture XP x64" collection and then advertised the "Build and Capture XP x64" Task Sequence to the collection.

 

I've updated the DPs with the packages for the OS/ConfigMgr/Sysprep, but I can't figure out why it's not being seen by the client. What could I be missing, or where should I be looking?

 

The smsts.log file is attached, and I would be grateful for any guidance or assistance.

 

 

I would check the package/packages that is being refered to this: "Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs"

 

Try to remove them from the DP and then redistrubute them..make sure that the status says installed in the console

[mjbraun]

I would check the package/packages that is being refered to this: "Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs"

 

Try to remove them from the DP and then redistrubute them..make sure that the status says installed in the console

 

wmmayms,

 

Thank you very much for your response! I deleted the distribution point from within OS Deployment --> OS Install Packages --> Windows XP 64 bit --> Distribution Points and then recreated it. I then checked under OS Deployment --> OS Install Packages --> Windows XP 64 bit --> Package Status --> Wheeling and the DP \\DEV2650 is present and the state was "Installation Pending" for longer than I thought was appropriate. I went into Site Management --> Wheeling --> Site Settings --> Senders, deleted the Standard Sender, and recreated it and now the Package Status is "Installed". I cleared the last PXE advertisement from the desktop and reattempted the installation, but with no change in results (the 0 DP message remains). Not sure what I should be checking at this point. I've attached the newer log file if that helps.

 

One thing I've noticed, however, and I'm not sure if this applies (or even what it means) is that there is a little hard-to-see (I just noticed it) red hourglass on the Build and Capture XP x64 collection icon. Updating the collection members doesn't seem to change it. Could that be relevant? Also, under Site System Status, I have a warning for the \\DEV2650 ConfigMgr distribution point for the storage object \\DEV2650\D$ (note that the storage object \\DEV2650\C$ is ok). "D$" is actually the System Reserved partition on DEV2650, so why it's being shared and/or assigned as a storage object is a mystery to me. Component Status, on the other hand, is all green across the board.

 

Again, I appreciate any guidance or suggestions!

smsts.log

[wmmayms]

wmmayms,

 

Thank you very much for your response! I deleted the distribution point from within OS Deployment --> OS Install Packages --> Windows XP 64 bit --> Distribution Points and then recreated it. I then checked under OS Deployment --> OS Install Packages --> Windows XP 64 bit --> Package Status --> Wheeling and the DP \\DEV2650 is present and the state was "Installation Pending" for longer than I thought was appropriate. I went into Site Management --> Wheeling --> Site Settings --> Senders, deleted the Standard Sender, and recreated it and now the Package Status is "Installed". I cleared the last PXE advertisement from the desktop and reattempted the installation, but with no change in results (the 0 DP message remains). Not sure what I should be checking at this point. I've attached the newer log file if that helps.

 

One thing I've noticed, however, and I'm not sure if this applies (or even what it means) is that there is a little hard-to-see (I just noticed it) red hourglass on the Build and Capture XP x64 collection icon. Updating the collection members doesn't seem to change it. Could that be relevant? Also, under Site System Status, I have a warning for the \\DEV2650 ConfigMgr distribution point for the storage object \\DEV2650\D$ (note that the storage object \\DEV2650\C$ is ok). "D$" is actually the System Reserved partition on DEV2650, so why it's being shared and/or assigned as a storage object is a mystery to me. Component Status, on the other hand, is all green across the board.

 

Again, I appreciate any guidance or suggestions!

 

I would check post #3 in this thread

http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/page__p__777entry777

 

And read through this post

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/781aac83-2ac1-4442-802b-c00837feb1e6

 

Cheers