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

Enterprise Console - Computers Showing No Update Source

closetgeek

Our SUM / EC server recently crashed and we were forced to setup on a new server. I was not able to retrieve certificates, etc. so consider this a "new install" of the Sophos Endpoint in Clients.

I have initiated the RMSReinit.hta on all computers and made the appropriate changes to the Updating Policy on the new server.
To date, only about half of our systems are showing up in the new Enterprise Console. Most of these computers are showing they have not updated in some time. Upon checking the details of individual computers, I see that they have no Primary or Secondary updating source listed.  The iconn.cfg on these computers shows the new Primary server, but the client is not receiving updates.  Is there anything else I should be doing / checking to ensure these clients become protected and receive updates?

What about the systems that are not checking in at all?

Thank you.

:34699


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

    Hello closetgeek,

    let's try to unravel the issues as there seems to be more than one.

    I have initiated the RMSReinit.hta on all computers

    Did you run Jak's RMSReinit.hta or the EndpointMigrationUtility.hta from How to redirect Windows endpoints to a new management server (can't say if there are significant differences though)? Anyway, I get it that for about half of your clients it has worked but not for the other half, so you should try to determine why it has apparently failed. What about the systems that are not checking in at all? By default both the script's and ClientMRInit.exe's logs are in the system %TEMP% directory (if you can't make out an error please post them here). BTW: Did you direct the clients to a specific group?

    no Primary or Secondary updating source listed

    Normally the clients report their configuration to the management server. Absence of these values indicates a communication error (usually client-internal) or an AutoUpdate issue (as you say the client is not receiving updates - BTW: clients pull updates - I assume the latter). What's the value in the column Updating policy under the Update Details tab?

    iconn.cfg is "just" a store and its existence and contents don't indicate that AutoUpdate is actually working as it should (I assume you have also ensured the updating credentials are correct). Thus you should also check the update locations as well as the updating log using the GUI on the client. I assume there are no errors reported to the console other than the out-of-date indicator?

    Are the Sophos services running (except the SWI update), particularly Agent and AutoUpdate? If not, please try to start them and check the Windows Event log for errors.  If AutoUpdate is running the detailed logs (ALUpdate...log) will show the reason for the update failure.

    I'm not sure where to start - I'm leaning to chasing the ReInit issue first and then the policies.

    Christian

    :34803
Reply
  • 0

    Hello closetgeek,

    let's try to unravel the issues as there seems to be more than one.

    I have initiated the RMSReinit.hta on all computers

    Did you run Jak's RMSReinit.hta or the EndpointMigrationUtility.hta from How to redirect Windows endpoints to a new management server (can't say if there are significant differences though)? Anyway, I get it that for about half of your clients it has worked but not for the other half, so you should try to determine why it has apparently failed. What about the systems that are not checking in at all? By default both the script's and ClientMRInit.exe's logs are in the system %TEMP% directory (if you can't make out an error please post them here). BTW: Did you direct the clients to a specific group?

    no Primary or Secondary updating source listed

    Normally the clients report their configuration to the management server. Absence of these values indicates a communication error (usually client-internal) or an AutoUpdate issue (as you say the client is not receiving updates - BTW: clients pull updates - I assume the latter). What's the value in the column Updating policy under the Update Details tab?

    iconn.cfg is "just" a store and its existence and contents don't indicate that AutoUpdate is actually working as it should (I assume you have also ensured the updating credentials are correct). Thus you should also check the update locations as well as the updating log using the GUI on the client. I assume there are no errors reported to the console other than the out-of-date indicator?

    Are the Sophos services running (except the SWI update), particularly Agent and AutoUpdate? If not, please try to start them and check the Windows Event log for errors.  If AutoUpdate is running the detailed logs (ALUpdate...log) will show the reason for the update failure.

    I'm not sure where to start - I'm leaning to chasing the ReInit issue first and then the policies.

    Christian

    :34803
Children
No Data