Clients not updating site codes

[dmacl74]

I have an SMS 2k3 primary site server which handled 2000+ client installs over the LAN and WAN. For future software deployment, we implemented (after the fact) 3 secondary site servers and enabled them as SLPs. I have configured the site boundaries in the SMS console for each secondary site server, however, all of the clients still point to my primary site server. Which means, all software distributions are still coming from the single server...

Even connected to a machine that resides in the secondary sites boundaries, trying to do a automatic site discovery, it will default back to the primary site. I set it static, and it just does not show up in the SMS admin console. I've hit a wall.

Any help or suggestions would be great. The secondary sites have been up for over a month, and heartbeat discovery is enabled evrey week...

 

[tbrennans]

ya only want one slp, so you might want to remove those new ones, advanced clients are only going to be a client of a primary site, never a secondary, but if a client is in the boundary of a secondary site you would make the secondary a proxy management point (pmp) and a possibly a protected distribution point (pdp) this would cause the clients to send inventory via the secondary site to the primary site, via the proxy mp, and the pdp will only let the cients in the secondaries boundary (actually in the set pdp boundary) recieve packages from that location

 

[dmacl74]

Thanks. Ok - Removed SLP, but I am still confused about the client assignment. I mean, even w/ a pmp in place, shouldn't the client get the secondary site code?

Also, quick one for ya... in configuring the pmp, should I be in the properties of the secondary site, under the primary's site system? Or should I be configuring the secondary in the site systems of the site settings of the secondary site?

Confuse ya? sorry..

 

[mib147]

Advanced clients will never belong to a secondary site. That is just how it is. However, they are smart enough to detect when they are in the boundaries of a secondary site and use it as a DP or PMP if you have enabled that.

Enabling a secondary site to be a PMP should be done in the site system properties of the secondary site. Is your secondary site listed as a site system for your primary site?

 

[dmacl74]

Yes - all secondary sites are listed as site systems in the primary site...

 

[tbrennans]

Its just one of those SMS things, advanced clients only belong to a primary site, advanced clients will use the secondary IF there is a proxy mp, for throttling the inventory and some policies (although I don't beleive it throttles any policies) it will also compress the SMS packages through the secondary to the local secondary DP.

So if your not going to throttle I dont even use secondaries as I feel they are somewhat of a waste of time in the things I engineer, which I base off of MS's capacity planning tool showing very little bandwidth difference between a secondary and a PDP, just use pdp's. (another subject)

You configure the pmp at the secondary

 

[dmacl74]

K - Got my secondary sites configured as an MP and PDPs. I have serious bandwidth considerations and need the PDPs to deploy the packages on the LAN...

I built a test package, added the distribution points, set the advertisement, and ran it. I go to System Status/Advertisement status, and I see my test advertisement. When i click on it in the left pane, I see in the right pane, that the programs all came from the primary site server. The secondary site servers do not appear at all...

I am unable to find any particular/special errors/logs and that is what I am serching on now...

Thoughts?

Thanks guys.

 

[tbrennans]

make sure you dont have a primary site with the same boundary as the secondary. If you just changed the setting then you will have to wait until the clients get the policy update from the primary before they will use the new pdp

 

[mib147]

Did you manually add all your secondary sites as a site system for the primary site?

 

[dmacl74]

Got all my boundaries seperated... Guess I'll have to wait out the policy update... Is there a way to force it?

mib147 - No, I didn't add them manually - Can't get rid of them either :-/ Should they not be there? How do I clear them out of there?

 

[mib147]

I must be misunderstanding something. If no one added them, you can leave them there.

 

[dmacl74]

Looks like this...

Site Database (ABC)
-Site Hierarchy
-ABC
-Site Settings
|T
|R
|E
|E
-Site Systems (Clicking on this shows all servers that are the secondary site servers (Say DEF, GHI, JKL) as well as the primary (ABC))
-DEF
|T
|R
|E
|E
-Site Systems - Shows the server for DEF - That's it
-GHI
|T
|R
|E
|E
-Site Systems - Shows the server for GHI - That's it

Etc...

 

[mib147]

Mine isn't like that at all. My secondaries are not listed as site systems for the primaries. What are their roles as a site system for the primary?

tbrennans, does this make any sense to you?

 

[dmacl74]

All the secondary site systems roles are listed as SMS Component Servers. Except one...
-Site Database (ABC)
-Site Hierarchy
-ABC
-Site Settings
|T
|R
|E
|E
-Site Systems
- DEF (type - server/Role - SMS Component Server)
- GHI (type - server/Role - SMS Component Server)
- JKL (type - server/Role - <Blank>)

 

[dmacl74]

Have some security issues I'm working on now... I started a new post - I think it is a big part of the problem. some of the Secondary site servers are in NT 4.0 domains, and the SMS is in an AD domain... Having issues accessing the registry on secondary site servers...