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

    It appears that a Windows client will continue to try and update itself  from the setup install location if it is "installed" into the "Unassigned" group in the Enterprise Console (by running the setup.exe program directly from the CID share).

    A linux client appears to "forget" its configured update location once it finds itself in the "Unassigned" group and therefore stops updating until the linux client is moved to another Group in the Enterprise Console.    (even though the customized savinstpkg.tgz file has the "--update-source-path" parameter defined in the 'sophos-av/sav-linux/installOptions' file. )

    So it would seem to appear that for linux clients, I need to either:

    1.  Figure out if there is a command line parameter I can pass to the installer that will put the client into a specified Group that has a Update policy defined.

    2.  Make sure to immediately move any installed linux clients out of the "Unassigned" group.  (need to coordinate with my linux admins).

    Does the above analysis seem sound?

    :2761
Reply
  • 0

    It appears that a Windows client will continue to try and update itself  from the setup install location if it is "installed" into the "Unassigned" group in the Enterprise Console (by running the setup.exe program directly from the CID share).

    A linux client appears to "forget" its configured update location once it finds itself in the "Unassigned" group and therefore stops updating until the linux client is moved to another Group in the Enterprise Console.    (even though the customized savinstpkg.tgz file has the "--update-source-path" parameter defined in the 'sophos-av/sav-linux/installOptions' file. )

    So it would seem to appear that for linux clients, I need to either:

    1.  Figure out if there is a command line parameter I can pass to the installer that will put the client into a specified Group that has a Update policy defined.

    2.  Make sure to immediately move any installed linux clients out of the "Unassigned" group.  (need to coordinate with my linux admins).

    Does the above analysis seem sound?

    :2761
Children
No Data
Unfiltered HTML