Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 5332 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

Policy Behavior for clients in Unassigned group?

Lestat

I am running Sophos Enterprise Console 4.0.0.2362

If a client belongs to the "Unassigned" group in the Enterprise Console, which Policies are applied to it?  The "Default" policies?  Or something else?

What if I take a client from a Group that has policies defined and move it into the "Unassigned" group?  What settings will the client then have?  Does it keep the policy settings from it's original Group or does it "forget" them since it now belongs to the "Unassigned" group?

:2756


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

    Hi Letstat

    I can't comment on the Linux part of the query but with regards to your Windows machines, if left in the unassigned folder (after manual installation), they will assume the default policy, ie. as Sophos ships. so the policies as they exist upon your initial install of the SEC, will apply to the unassigned folder. Since the policies the SEC "ships" with isn't, imo, the most secure, it is highly advisable that you move your endpoints to the correct groups to apply the policies you have implemented.

    :2880
Reply
  • 0

    Hi Letstat

    I can't comment on the Linux part of the query but with regards to your Windows machines, if left in the unassigned folder (after manual installation), they will assume the default policy, ie. as Sophos ships. so the policies as they exist upon your initial install of the SEC, will apply to the unassigned folder. Since the policies the SEC "ships" with isn't, imo, the most secure, it is highly advisable that you move your endpoints to the correct groups to apply the policies you have implemented.

    :2880
Children
No Data
Unfiltered HTML