SCCM server not properly recognised

[Antda]

Hi,

 

I have a (big) issue with SCCM

Due to an physical issue with the SCCM Server, I did recreate completly the SCCM infrastructure on my company (1 SCCM Server only, 250 clients)

So I did reinstall a new box with 2007 R3, created a new site, new collections, reinstall all CCM clients software, everything was fine

 

We did recently shutdown the old server thinking that everything was working smoothly, but since then I have an issue : all advertissements are staying in "waiting for content"

 

I read a lot of forum to investigate and found some info, but I can't succeed to solve it

 

In http://technet.microsoft.com/en-us/library/bb693614.aspx it's written that I'm supposed to have 4 info in AD System Management container.

SMS-Site-<site code>

SMS-MP-<site code>-<site system server name>

SMS-SLP-<site code>-<site system server name>

SMS-<site code>-<Active Directory site name or subnet>

 

I just have the 3 firsts, the last one (SMS-<site code>-<Active Directory site name or subnet>) isn't there, is it normal ?

 

Then, it's looks like my site is recognised as "slow or unreliable", as it's trying to download instead of "run from DP" (Usualy my adv. are distributed as "run from DP" for FAST boundary and "download" for unreliable network)

 

Any advise ? I read that I need to clean AD manualy, but what to clean (appart the 3 olds:

SMS-Site-<site code>

SMS-MP-<site code>-<site system server name>

SMS-SLP-<site code>-<site system server name>) ? any idea how to make it running normaly ?

 

Thanks

 

Antoine

[Peter van der Woude]

Did you use a new Site Code? Did you create Boundaries? Is the new Site allowed to write in the AD?

[Antda]

Did you use a new Site Code? Did you create Boundaries? Is the new Site allowed to write in the AD?

Yes, I did recreate everything from scratch : install a new SCCM Server 2007 R3 on Win2k8R3, create a new database, a new site code, new boundary (1 only based on AD Site, only 1 site on AD) new collections, new packages, new advertissements ... everything new, then reinstall SCCM Client on desktop using push from the new SCCM server.