I found what I consider a bug in the Enterprise Console when "Protecting" computers. I am running Enterprise Console 4.0.0.2362.
Steps to reproduce the problem:
In the Sophos Enterprise Console, use the "Find new computers" button to locate the TEST machine. TEST shows up in UNASSIGNED group.
Delete TEST from the Unassigned group (because you realized that you want to utilize the "Synchronize with Active Directory" feature instead.)
Synchronize with Active Directory -- TEST shows up under the proper Group (for example, DESKTOPS) as a greyed out name (because SophosAV is not installed).
Right-click on TEST and select "Protect Computers" option.
Expected Behavior:
After SophosAV installation, TEST should remain in the DESKTOPS Group.
Observed Behavior:
After SophosAV installation, TEST shows up in the UNASSIGNED Group until the next time an AD Synchronization is performed.
Depending on the interval between Synchronizations, TEST may not have the correct Policies applied for some time.
Notes
Where this bites me is that I used the Find New Computers wizard against my entire Domain when I first installed my Enterprise Console, and then I deleted all computers from the Unassigned Group. Now I am ready to start pushing out Sophos and found out that newly installed computers will not start to use my defined policies until after an AD sync. I am currently syncing every 60 minutes.
I guess I can bump my AD Sync interval way down (5 minutes?), but this was unexpected behavior to me.
This thread was automatically locked due to age.
