Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 9641 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SEC Dropping Managed Computers

CeeFcee

Enterprise Console dropped 73 computers over the weekend. They became unmanaged again.

Is there a config that could cause this ?

:45599


This thread was automatically locked due to age.
Parents
  • 0

    Hello CeeFcee,

    what do you mean by became unmanaged again? Once a computer is known and managed its status is stored in the database. SEC updates (or removes) these attributes only upon notification by the client. Thus to become unmanaged the client's RMS would have to notify SEC that it's about to get uninstalled - not very likely for 70+ clients. Or do you mean they "moved" to the Unassigned group? This happens e.g. when the group they are in is manually deleted or if they are in a synchronized (sub-)group and they are moved to a container in AD which is outside the sync scope.

    Christian

    :45603
Reply
  • 0

    Hello CeeFcee,

    what do you mean by became unmanaged again? Once a computer is known and managed its status is stored in the database. SEC updates (or removes) these attributes only upon notification by the client. Thus to become unmanaged the client's RMS would have to notify SEC that it's about to get uninstalled - not very likely for 70+ clients. Or do you mean they "moved" to the Unassigned group? This happens e.g. when the group they are in is manually deleted or if they are in a synchronized (sub-)group and they are moved to a container in AD which is outside the sync scope.

    Christian

    :45603
Children
No Data