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

Manually Adding Clients to Console (no AD)

We've installed Sophos Enterprise Console 5.2.1 on a Windows 7 Pro pc .

There is not an active directory in the network, and our desktops were running Sophos as stand alone / unmanaged clients before .

We try to add the clients in the console, but we have two issues .

1/ When the console scans the network subnet, it finds about 60% of the clients that are online .(Maybe it's a firewall issue ? but Sophos Firewall was installed only on a couple of desktops..

Anyway this is not a big issue, as even if a client is discovered and joined manually in the console we can't actually click 'protect pc' as no matter what combination of username pass we use we can't proceed ..

2/ the big issue is that we try to manually add the clients, many clients seem to update and getting the auto update policy (with the correct primary and secondary location, the correct amount of minutes interval in schedule etc but it's not shown as managed in the console..

We try the manual install by running the setup.exe from the \\SERVERNAME\SophosUpdate\CIDs\S000\SAVSCFXP

we enter in the username credentials the username and password of the sophosupdate user we created on the pc running the console and in the group path

\servername\groupname

do we do something wrong ?

:41335


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

    finds about 60% ... no matter what combination of username pass we use

    I'd not bother with Discover unless you really need it. Which error do you get when using Protect? Please see step 1.1. in How does the 'Protect computers wizard' perform an installation?, in short the account must have administrative rights on the endpoint and be able to log on to the management server (and access to SophosUpdate share). In a workgroup this means a local accounts with the same name and password must exist on the target client and the server.    

    The new Sophos endpoint deployment guide mini-site has some additional material.

    many clients ... getting the auto update policy ... not shown as managed in the console

    The account is likely correct (otherwise the clients would not update), and even if you mistype the Group Path (case sensitive) the clients should appear in the Unassigned group. As RMS is installed you should be able to open the Sophos Network Communications Report. If your clients did receive a policy then they are managed - could you provide a small screenshot of the Console where these clients can be seen? 

    Christian

    :41343
Reply
  • Hello dcstech,

    finds about 60% ... no matter what combination of username pass we use

    I'd not bother with Discover unless you really need it. Which error do you get when using Protect? Please see step 1.1. in How does the 'Protect computers wizard' perform an installation?, in short the account must have administrative rights on the endpoint and be able to log on to the management server (and access to SophosUpdate share). In a workgroup this means a local accounts with the same name and password must exist on the target client and the server.    

    The new Sophos endpoint deployment guide mini-site has some additional material.

    many clients ... getting the auto update policy ... not shown as managed in the console

    The account is likely correct (otherwise the clients would not update), and even if you mistype the Group Path (case sensitive) the clients should appear in the Unassigned group. As RMS is installed you should be able to open the Sophos Network Communications Report. If your clients did receive a policy then they are managed - could you provide a small screenshot of the Console where these clients can be seen? 

    Christian

    :41343
Children
No Data