EMLibrary Removal

HI,

If you create the key:

HKLM\Software\Sophos\Enterprise Manager

on the machine and re-open the console does it display correctly?

Regards,

Jak

Hi Jak,

Thank you for your speedy reply.

I re-created the key in the location you specified and opened the console again but the option is still greyed out.

Regards,

Tom

So if you go down the list of policies in the "Legacy updating" policy type and select: "View group using policy" they all return: "This policy is not assigned to any groups."?

In that case I'd go to the database to see what is in there. The following command should list all the group ids and policy names that are using the legacy policy type (at least if my calculations are correct).

select gpm.groupid, 
sp.pathandname as [SEC Path], 
p.name as [Policy Name] from grouppolicymapping as gpm
inner join policies as p on
p.id = gpm.policyid
inner join grouppathandnametable() as sp
on sp.groupid=gpm.groupid
where gpm.type = 1
and name not like '*%'
order by p.name 

I'd be interested to see the output.

Regards,

Jak

PS.  When you created the key: HKLM\Software\Sophos\Enterprise Manager, you did put a space between Enterprise and Manager and it was created in the correct path for os, i.e. wow3264node was considered?

Hi Jak,

No, that is not the case. When I look at my legacy policies and right click on it, the option you referred to is now also greyed out. I have removed all the old policies in the legacy hierarchy as I thought they were now not needed.  I can create policy and the rest is not an option. Also, the only policy present is "Default".

Regards,

Tom

Hello Tom,

I have checked add/remove in Appwiz.cpl and I can not find EM Library being installed either.

Is it possible that it was never installed on this system? Have you ever and can you still run it  (...\Sophos\Enterprise Console\EMConsole\Console\Bin\Sophos Enterprise Manager.msc)?

If not but you fear that it could cause troubles then you should probably call Support. If just the pop-up annoys you simply check the box and it will no longer show (you can always turn it on again using Tools->Confirmation dialogs ....

Christian

Hi OC,

If I remember correctly I started off with version 4.0 so it wasn't even an upgrade from the v3.x, but I did check the path you specified and I can only get as far as ..\Sophos\Enterprise Console\

The EMConsole directory doesn't exist. We did have some issues but the server not pulling updates from Sophos but this was resolved was I upgraded to v4.5 but was a little bit worried about the message perhaps causing issues in the future.

I can supress the message as long as having the legacy hierarchy in there not cause any confusion to the software.

Thank you for your help.

Tom

Hello Tom,

dunno if uninstalling EM Library will remove all traces. But - you don't get Legacy Updating with a fresh SEC4.x install (as far as I know). All I can imagine is that either EM Library was installed before SEC 4 and has been removed at some point with Add/Remove programs (can't say if this is possible) or a 3.x database has been imported and upgraded.

Anyway I'm not aware that the legacy hierarchy causes any troubles (I'm still dragging one along - perhaps nostalgia :smileyvery-happy:)

Christian

Hi,

If you save the above SQL in the post as a file, e.g. test.sql

then run:

sqlcmd -E -S .\SOPHOS -d sophos45 -i test.sql -o groupsandpol.txt

I'm assuming that you have a local SQL instace called SOPHOS and test.sql is in the same directory where the command is run from

Could you paste the contents of groupsandpol.txt here?

Regards,

Jak

re-creating the reg key (as below) worked for me.  I then had the option to remove EMLibrary :)  thanks Jak 

---

jak wrote:

HI,

If you create the key:

HKLM\Software\Sophos\Enterprise Manager

on the machine and re-open the console does it display correctly?

Regards,

Jak

---

Recreating this key worked for me aswell. It's also worth re-iterating that this must be done from the machine running the Enterprise Console. Running it from a workstation connected to the machine running the enterprise console will always be greyed out.