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

Computers stuck in unmanaged section

Hello, I am new to Sophos and this is a new issue that has been happening for the last weeks, whenever I install Sophos on a new computer the installation completes successfully and does get the updates correctly, but when I check on the enterprise console they go to the unmanaged group (not unassigned), and I can't do nothing to them except delete them.

One more thing, the ones I am using as test are running under Windows 10, I don't know if that might be the issue



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

    whenever I install
    how do you install - locally (setup.exe from the CID or a package) or using Protect Computers?

    they go to the unmanaged group (not unassigned)
    there is no unmanaged group. If the endpoint "appears" in the console because it has contacted the management server it is managed, otherwise it(s name) has been imported by some means - at this point it is unmanaged and thus can't go to unmanaged. So - did you discover/import the endpoint(s) and if so, how?
    As the endpoint should register with the server after installation something's not right with RMS, Jak has already suggested what and where to check.

    Christian

  • QC said:

    whenever I install
    how do you install - locally (setup.exe from the CID or a package) or using Protect Computers?

     

    Yes, I install localy, with these unmanaged computers I can't use Protect Computers

    QC said:

    they go to the unmanaged group (not unassigned)
    there is no unmanaged group. If the endpoint "appears" in the console because it has contacted the management server it is managed, otherwise it(s name) has been imported by some means - at this point it is unmanaged and thus can't go to unmanaged. So - did you discover/import the endpoint(s) and if so, how?

     

     
    Yes they were imported via Active Directory, also I checked one of the computers which has Windows 10 doesn't let me instal RMS from its .exe
Reply
  • QC said:

    whenever I install
    how do you install - locally (setup.exe from the CID or a package) or using Protect Computers?

     

    Yes, I install localy, with these unmanaged computers I can't use Protect Computers

    QC said:

    they go to the unmanaged group (not unassigned)
    there is no unmanaged group. If the endpoint "appears" in the console because it has contacted the management server it is managed, otherwise it(s name) has been imported by some means - at this point it is unmanaged and thus can't go to unmanaged. So - did you discover/import the endpoint(s) and if so, how?

     

     
    Yes they were imported via Active Directory, also I checked one of the computers which has Windows 10 doesn't let me instal RMS from its .exe
Children
  • Hello Jonathan Ramirez,

    with these unmanaged computers I can't use Protect Computers
    there might be some misunderstanding of unmanaged. A computer object in SEC is unmanaged when its name and some optional attributes have been imported by some means but an endpoint with this name and attributes has not yet registered with the console. Unmanaged does not relate to any other management capabilities (AD, third-party) in your network. Normally Protect is used for these very unmanaged ones. That a computer is managed (i.e. Sophos is installed) does not facilitate the use of Protect.

    As said, in the case for which you've provided the log the Certification Manager rejects the certificate request, the mentioned log should have details.

    doesn't let me instal RMS from its .exe
    what is its .exe? Could you give the name of this .exe and also what doesn't let me is exactly? Do you run setup.exe interactively with the GUI or using command line switches?

    Christian

  • QC said:

    doesn't let me instal RMS from its .exe
    what is its .exe? Could you give the name of this .exe and also what doesn't let me is exactly? Do you run setup.exe interactively with the GUI or using command line switches?

    Hello Christian.

    The .exe is located on CIDs\S000\SAVSCFXP\rms, the name is Sophos Remote Management System and I tried installing it with the GUI

  • Hello Jonathan Ramirez,

    Sophos Remote Management System is an Installer package (.msi) - this [:@] Hide extensions for known file types - and it won't work if you double click it.
    If asked about setup.exe in ...\SAVSCFXP\ - this is the one and only one to use. It should take care of all the rest if the correct options are selected (actually it installs AutoUpdate telling it what to subsequently download and install).
    What did you configure in setup.exe's window prompt (perhaps you can show a screenshot), what was the result? Any why did you try to install RMS using the .msi?

    Christian

  • Hello Christian

    Here's the screenshot, when we install it we leave it like this, except the username and password

    Is it better if we add a group path or leave it blank?

    Also about the RMS, I tried installing it because one Windows 10 PC didn't show it on control panel and also thought a reinstall might help.


  • E Router::Start: Caught Certificate request refused by certification manager, undefined failure 

    ...seems to be the issue here and why the client can't become managed.  I have to say, I've not seen that error message before.  I would hope that the certification manager log file on the server has a more meaningful message at the same time.

    Are any clients working from the management server?

    Regards,

    Jak

  • Hello Jak

    I'll check the logs on the servers.

    And by Are any clients working from the management server? do you mean if there are computers that are being managed by the console?, if yes, the answer is YES, but these computers are the ones that had Sophos for some months now, we have installed Sophos on about 20 to 30 computers now and these are the ones not communicating properly with the server.

    Regards.