SMS clients are appearing as Obsolete
Let me say this upfront: I am real new to SMS and application deployment all together.
That being said please help.
All of a sudden SMS system resources are showing up as Obsolete. The client is still there. However, the systems are identified as obsolete. Then once the systems are flagged as obsolete they are dropping out of my collections.
I am grasping at any clues to research right now. Any input is appreciated.
That being said please help.
All of a sudden SMS system resources are showing up as Obsolete. The client is still there. However, the systems are identified as obsolete. Then once the systems are flagged as obsolete they are dropping out of my collections.
I am grasping at any clues to research right now. Any input is appreciated.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
dunnpy
18 years ago
I'm not all that up on SMS side of things (I deploy with SMS, but site management etc is dealt with in house by our client), but a couple of things occur to me.
Either the client is obsolete (machine rebuilt and SMS client installed which will give it a new GUID)
or
The Client Health Monitoring tool (for SMS 2003 SP1 only) is in use, which can be configured to set the unhealthy client's Active bit to 0.
Next time a DDR (Discovery Data Record) is received for this client the Active bit will be reset to 1
Hope this info at least points you in the right direction,
Thanks,
Dunnpy
Either the client is obsolete (machine rebuilt and SMS client installed which will give it a new GUID)
or
The Client Health Monitoring tool (for SMS 2003 SP1 only) is in use, which can be configured to set the unhealthy client's Active bit to 0.
Next time a DDR (Discovery Data Record) is received for this client the Active bit will be reset to 1
Hope this info at least points you in the right direction,
Thanks,
Dunnpy
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
