Collection changes not replicating up (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003



Message

jscott607 -> Collection changes not replicating up (10/3/2008 9:34:48 AM)

Hello. I have a central server with three primary servers attached. Each of these primaries have child secondaries. On one of the primary servers, I am having issues with changes made to it's collections not replicating up to the central server. For example, we are trying to remove a piece from machines so I created a collection on the central server that looks for machines with the software. As the software is removed, they drop out of the collection. On the problem primary, all of the machines have been cleaned several weeks ago and the collection is empty. However, when I look on central server the collection still has a lot of the machines from that primary server.

I have looked at all of the status messages, logs and inboxes that I can think of that would be the cause but have not located anything. Any ideas. Thank you for any assistance.



skissinger -> RE: Collection changes not replicating up (10/3/2008 10:24:14 AM)

Stupid question, but I have to ask it:  what's the update schedule on that collection?  Have you updated it manually?

What's the collection query based on? A file existing, or an entry in Add/Remove Programs?  Something else?  Depending upon what it is, it could be inventory data not replicating up the hierarchy.



jscott607 -> RE: Collection changes not replicating up (10/3/2008 11:06:00 AM)

Thank you for the response.

The update schedule is daily and I did an update myself. I watch colleval and could see it processing it successfully.

The collection is based on a key we place in the registry on each package. The machines that are still showing up on the central server are old machines that are no longer in use. Both the central and child have maintenance tasks set the same.






skissinger -> RE: Collection changes not replicating up (10/3/2008 11:17:32 AM)

Ok; who/what/where are your discovery?  Perhaps the Central is re-discovering those clients in AD and keeping them as not yet obsolete, because those boxes are still discoverable in AD?  You might need to clean up AD, or move the computer objects into an OU that you don't discover.  Or possibly buy ESD from systemcentertools.com



jscott607 -> RE: Collection changes not replicating up (10/3/2008 12:36:54 PM)

We use a GPO to install clients and check the health. We do not use AD System discovery. We do have AD System Group Discovery, AD Security Group and heartbeart turned on at central and the primaries.



skissinger -> RE: Collection changes not replicating up (10/3/2008 2:41:46 PM)

If you pick one of those machines, right-click properties, you can see AgentName[some number] and below Agent Time [some number]  By seeing what Agent Time happened lately, you should be able to trace back to the Agent Name, and figure out what is discovering the box.  i.e., if Heartbeat Disc, it's still out there, sending up a Heartbeat.



jscott607 -> RE: Collection changes not replicating up (10/3/2008 2:57:30 PM)

I actually checked that earlier. When I looked at one of the systems, I see AD System Group Discovery with heartbeat below. My understanding of System Group discovery was that it was an enhancement giving addititional information such as OU, etc. and could not be a primary discovery method. Also when I look in the adsysgrp those systems are not in there.




skissinger -> RE: Collection changes not replicating up (10/3/2008 4:01:46 PM)

Is AD System Group Discovery indicating a recent found date?  And Heartbeat not?  Are those computer accounts in AD?  Have you considered cleaning up AD (i.e., oldcmp from joeware.net)?



jscott607 -> RE: Collection changes not replicating up (10/6/2008 10:56:41 AM)

The central server is set to discovery the root domain. There are only 4 machines in that domain. A couple of domain controllers and the central SMS server. The problem machines and primary are in a child domain. Neither domain has the problem machines in it.

If I look at the properties on one of the machines, I see Agent Name(0) - AD_System_Group_Discovery and several lines below Agent Time(0) - 09/01/2008 - 12:00:01 AM.

I did not originally setup discovery. Is there any reason to have AD System Group Discovery setup if it is only going to the root domain with only 4 servers in it?



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.265625