Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 3365 views
  • Users 0 members are here
Options
Suggested
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

EndPoints - how to update the Updating after Enterprise Console Reinstall

BloodBaz

Hello,

I have just reinstalled Enterprise Console (now using 5.2.1) after I have had my license upgraded from Sophos Security Suite SBE to Sophos Endpoint Protection - Business.  I am running Windows Server 2012 VMs and a mix of Windows 7 and 8 clients.

As I recreated user accounts along recommended practises, my "Update Manager Account"  is now <mydomain>\SophosUpdateMgr.   However, my clients are still running Sophos AV with Updating details of the old (now deleted) account.  

As a result they cannot update themselves, nor can I correct the credentails manually on the clients as the Configuration > Updating dialog box (Primary location) has the settings "greyed out".  Chicken and egg!

Q1) How should I get my Winodws Clients to use the new Username/Password?

Q2) Should I just rerun the AV from \\myserver\SophosUpdate\CIDs\S000\SAVSCFXP\setup.exe ?

Q3) If so, will this include the new updating policy?

Thanks,

Chris

:42135


This thread was automatically locked due to age.
Parents
  • 0

    Are the clients showing up as connected/online and being managed through this new enterprise console?  If not, I'd assume either the Enterprise Console server is new, or the certificate changed, which is causing the clients to not check in.

    Path of least resistance may be to do a discovery of the machines, and then "protect" from the enterprise console itself.  This should basically do a re-install of all necessary components, including RMS, and have the machines appear in the new console.  After which, you can drag them to groups that have policies associated - if you don't install to these groups directly.

    :42167
Reply
  • 0

    Are the clients showing up as connected/online and being managed through this new enterprise console?  If not, I'd assume either the Enterprise Console server is new, or the certificate changed, which is causing the clients to not check in.

    Path of least resistance may be to do a discovery of the machines, and then "protect" from the enterprise console itself.  This should basically do a re-install of all necessary components, including RMS, and have the machines appear in the new console.  After which, you can drag them to groups that have policies associated - if you don't install to these groups directly.

    :42167
Children
No Data