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

Customizing the SophosUser, SophosPowerUser, and SophosAdmin groups during a SAV agent install

ThomK

Looking for information on how to control/initiate the Sophos group setup during the installation of the agent on a workstation both in a domain or as a standalone (no domain) system. Here are the questions enquiring minds would love to know:

1. For a workstation not in a Domain, is there a way to customize which  users/groups get added to SophosUser,  SophosPowerUser, and SophosAdmin you install the SAV agent?

2. Is there also a way to do the same thing if you were part of a domain (reference domain global group accounts instead of defaulting to creating local groups)?

3. Can you change from a local group model to AD domain model? If so, how?

I realize I could run the "net user" commands or write a .VBS file to accomplish the local group customizations, but I am hoping there is something thats part of the Sophos product install to accommodate this directly. Any information on automating these changes is appreciated.

:5387


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

    Hi QC,

    I found them one day on a DC and realised it must have been due to the fact I installed using the standalone installer.

    I tested this further and found that they are only ever created if the SAV package is installed as a domain administrator, of course this only happens if you use the standalone installer as SAV is installed before AutoUpdate as the installing user.  From a CID install, i.e. setup.exe, SAV is installed by AutoUpdate as the system account and thus they are never created.

    Thanks,

    Jak

    :5404
Reply
  • 0

    Hi QC,

    I found them one day on a DC and realised it must have been due to the fact I installed using the standalone installer.

    I tested this further and found that they are only ever created if the SAV package is installed as a domain administrator, of course this only happens if you use the standalone installer as SAV is installed before AutoUpdate as the installing user.  From a CID install, i.e. setup.exe, SAV is installed by AutoUpdate as the system account and thus they are never created.

    Thanks,

    Jak

    :5404
Children
No Data
Unfiltered HTML