Inconsistent Collection information

[aidanbree]

Hi,

I am hoping someone may be able to offer me some information as I am totally at a loss.

I have 2 Sites running SMS 2003. When I go into a Collection in the parent site and look through the members I see the regular view of machines information. This is all correct for the parent site but does not show key fields for the child site. The missing information for child site machines are Client Type, Site Code, Obsolete, Active.

When I use the console to connect to the child site I see the same clients however they are ALL missing lots of information under the fields Client Type, Site Code, Obsolete, Active.

There is a firewall in between the sites but everything else seems to be operating correctly.

Can anyone offer any suggestions as to what is going on?

 

[tbrennans]

perhaps thye are trying to use the MP at the parent site?? Is one configured at the child? these are both primaries right?

 

[tbrennans]

eh....naw thats not it.

it would almost seem to be a db problem now that I think about it, where the client info isnt being cmpletely entered into the db.

 

[tbrennans]

one more after thought...perhaps you dont have hardware inventory or software inventory enabled?

 

[ncotton]

On the child site, do you have all the discovery methods running correctly?
Have you tried it with disabling the firewall (temp)?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[aidanbree]

Sorry I have just realised that my orginal post is incorrect.

At the child site, the clients report as being OK. It is only when I go to the Parent site that it doesn't report correctly.

Interestingly enough, I downloaded the SMS Console Client Tools from

http://www.myitforum.com

and using that I have managed to get partial success. When I use 'Initiate Discovery' the clients start 're-registering' with the Parent site. Any ideas why I need to do this to force the flow of information to the Parent site?

I have disabled the desktop firewall.

 

[ncotton]

You could try pushing out the client and using the "always install or repair option". That should get something, otherwise, see if just forcing the hardware inventory and machine policies action will speed it up

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant