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

Role Base Administration

Hi,

I have a Central SEC with a domain Controller. I install a remote console with a same domain in other server. I configure remote console into a role or sub-estate, the user that i used member of:

 the Sophos Console Administrators group

the Distributed COM Users group

Be assigned to at least one Enterprise Console role.

Be assigned to at least one Enterprise Console sub-estate.

the Sophos DB Admins

when i run a remote Management Console into sub-estate that i configure on the Central SEC they will failed.

Link below is the sreenshot of remote console.

http://www.ge.tt/#!/2M460eJ/v/0

Can anyone help?

Thanks,

Teddy

:26281


This thread was automatically locked due to age.
Parents
  • Hi,

    One option would be to enable trace logging in the Sophos Management service with repect to RBA. To do so:

    1. Close all Enterprise Consoles that are open.

    2. Stop the "Sophos Management Service" service.

    3. Add the following registry keys to the management server:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Trace\{48502EEA-4629-4dd6-9D67-CBB1A80C29A4}]
    @="TraceRBA"
    "ErrorLevel"=dword:00000003

    Please adjust accordingly for a 64-bit OS.

    4. Start the "Sophos Management Service"

    5. Download and start DebugView (on the management service machine), available from: http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
    Remember to "run as administrator" as required.
    Under the "Capture" menu choose: "Capture Global Win32" and "Capture Win32" if they exist

    6. Launch Enterprise Console as the user, for who it fails when setup as you would expect it to work

    DebugView should populate with verbose logging of the significant components which can be saved as a log file and should help to determine the problem. Maybe paste, or link to the log here.

    If that doesn't help, we might need trace logging from the "Console" component as well. So in the case of a remote cosole, the same steps as above but the key would be:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\TraceOFF\{9D624120-2E7B-47a2-BD4D-BDEB7E5388D3}]
    @="TraceConsole"
    "ErrorLevel"=dword:00000003

    I hope it helps gets some logs that are useful.

    Regards,
    Jak

    :26431
Reply
  • Hi,

    One option would be to enable trace logging in the Sophos Management service with repect to RBA. To do so:

    1. Close all Enterprise Consoles that are open.

    2. Stop the "Sophos Management Service" service.

    3. Add the following registry keys to the management server:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Trace\{48502EEA-4629-4dd6-9D67-CBB1A80C29A4}]
    @="TraceRBA"
    "ErrorLevel"=dword:00000003

    Please adjust accordingly for a 64-bit OS.

    4. Start the "Sophos Management Service"

    5. Download and start DebugView (on the management service machine), available from: http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
    Remember to "run as administrator" as required.
    Under the "Capture" menu choose: "Capture Global Win32" and "Capture Win32" if they exist

    6. Launch Enterprise Console as the user, for who it fails when setup as you would expect it to work

    DebugView should populate with verbose logging of the significant components which can be saved as a log file and should help to determine the problem. Maybe paste, or link to the log here.

    If that doesn't help, we might need trace logging from the "Console" component as well. So in the case of a remote cosole, the same steps as above but the key would be:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\TraceOFF\{9D624120-2E7B-47a2-BD4D-BDEB7E5388D3}]
    @="TraceConsole"
    "ErrorLevel"=dword:00000003

    I hope it helps gets some logs that are useful.

    Regards,
    Jak

    :26431
Children
No Data