Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 2538 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

Update endpoint clients from 9.5 to 9.7 - No longer showing connection- RESOLVED

toddh

Hello,

Over the weekend I updated our Sophos Enterprise Console from 4.5 to 4.7.

The update went perfectly.

This morning, I prepared a second subscription, and update policy to test out the updating of the endpoint clients.

I moved a few PC's into a new group and assigned them the new update policy.

The PC's updated their clients from 9.5 to 9.7 without a problem.

However, now all of the client PC's are showing no connection back to the server on the Sophos Enterprise Console (there is the red 'x' over the PC icon).

I have to push the endpoint client software update down to the machines again manually, then they start showing that they are connected

I have the client software 9.7 downloading into the same share location as version 9.5

Sophos has created a new directory called "S002" - Not sure if this is correct or not but I thought I should mention it

Has anyone else experienced this issue?

According to the endpoints themselves, they have  a connection with the Sophos server.

Any help would greatly be appreciated.

Thank you,

Cheers

----------------------------------------------------------

Sorry for the late bit of information.

I just noticed, for the endpoint clients that update automatically, they are getting version 9.5.5 VDL4.67G - This is what the Enterprise Console is reporting. But the clients themselves show that they have version 9.7

So there must be a communication error between Sophos Server and the endpoint software.

I have no idea where this is coming from... That's definitely not what the subscription/Updating policy is set to install.

I will have to dig more!

===========================================

Okay so I managed to figure it out.

For whatever reason, if I left the clients to auto update, their mrinit files were getting populated with the incorrect information.

I shutdown my test Sophos server and tested with a new computer.

The autoupdate went through and the mrinit file was populated with the correct information.

I still don't know why or how they were picking up the test server - I have absolutely no clients managed by that server.

Shutting it down though appears to have fixed my issue.

Sorry to have wasted everyone's time :(

:14963


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

    Hello QC,

    Thank you for your reply.

    When I saw the name change in the mrinit file I immediately went to check the CID location to see if  the mrinit coming from the CID on the production server had the incorrect information as well. The CID on the production server had the correct information in the mrinit file.

    The test Sophos Server was setup as though it was going to go into production so it is a full install.

    Sorry for my lack of knowledge but I am not entirely sure what you mean by "..does not use the same certificates as your production server.."

    I have done my best to try and keep the two server's completely separate from one another.

    IP's and DNS/Computers are all different for the two server's.

    I will bring the test server back online though and test a few more clients to see what they do.

    I would like to try and get to the bottom of why these clients pull from the wrong server when they are allowed to auto update.

    Especially when the clients are not managed by the test Sophos Server to begin with.

    The ALUpdate logs, should I be checking these on the clients themselves? Or on the Server?

    Thanks again for your response.

    Cheers

    :14981
Reply
  • 0

    Hello QC,

    Thank you for your reply.

    When I saw the name change in the mrinit file I immediately went to check the CID location to see if  the mrinit coming from the CID on the production server had the incorrect information as well. The CID on the production server had the correct information in the mrinit file.

    The test Sophos Server was setup as though it was going to go into production so it is a full install.

    Sorry for my lack of knowledge but I am not entirely sure what you mean by "..does not use the same certificates as your production server.."

    I have done my best to try and keep the two server's completely separate from one another.

    IP's and DNS/Computers are all different for the two server's.

    I will bring the test server back online though and test a few more clients to see what they do.

    I would like to try and get to the bottom of why these clients pull from the wrong server when they are allowed to auto update.

    Especially when the clients are not managed by the test Sophos Server to begin with.

    The ALUpdate logs, should I be checking these on the clients themselves? Or on the Server?

    Thanks again for your response.

    Cheers

    :14981
Children
No Data