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

End point 10.0 uninstall itself after reboot and re-install 9.5

We have upgraded  End Point console 4.5 to 5.0 last week and  gradually updating all the pc to 10.0

Our Network

Sophos management server – Windows 2003 SP2

End point console 5.0

Previous version of End point 9.5

Active Directory sync

We have close to 50 Groups in End Point console sync with  AD

As we gradually installing Sophos this is what happening

1)      When we push 10.0 from the console some computer install the new 10.0, but in same OU some computer do nothing.

2)      Those computer not updating from Console, I tried to pull Sophos from the client PC.

3)      When I pull Sophos it will install the new anti virus 10.0 , you can see the new 10.0 shield. And all update done.

4)      Reboot the computer or manually do” Update now” , it will re-install 9.5 and auto update path goes back to old path ( 9.5) path.

5)      I opened a case with Sophos teach support. They haven’’’’t had this problem so far.

6)      They requested me to delete C:\Program Files\Sophos\AutoUpdate\Cache

7)      Done that and try to push , nothing happens.

8)      After deleting cash , pull Sophos from client PC.

9)      Again it will install  10.0 and then after reboot it will re-install 9.5

Only way I am successful if I do this

1)      Change the iconn.cfg

2)      Manually put the 10.0 update path in Sophos console and update the computer . then it will keep 10.0

Hope Sophos teach supports finds a solution for me, because I have at least 800 computers in 270 location in this situation. Remaining 500  PC updated without any problem.

Did any one encounter this problem yet?

Sam

:20291


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

    How many syncpoints do you have? As you said "gradually" there must be several.
    I'm not sure I understand how you do it. Normally there is no need to push the install - either you change the updating policy or the underlying subscription and the clients will up-(or down-)grade to whatever version the policy is pointing to.
    As for 4) the "old" path likely exists before the downgrade - it's the cause, not the result - and it looks like this is the path the clients get from the console. (as an aside: please be careful with the terminology. "console" should refer to the SEC while the thingy on the client is better named GUI - I was at first confused reading your success point 2).

    So - what are the steps before your step 1)? Assign a different policy to the syncpoint and immediately afterwards protect computers? Or?

    Christian
    :20295
Reply
  • Hello BopBop,

    How many syncpoints do you have? As you said "gradually" there must be several.
    I'm not sure I understand how you do it. Normally there is no need to push the install - either you change the updating policy or the underlying subscription and the clients will up-(or down-)grade to whatever version the policy is pointing to.
    As for 4) the "old" path likely exists before the downgrade - it's the cause, not the result - and it looks like this is the path the clients get from the console. (as an aside: please be careful with the terminology. "console" should refer to the SEC while the thingy on the client is better named GUI - I was at first confused reading your success point 2).

    So - what are the steps before your step 1)? Assign a different policy to the syncpoint and immediately afterwards protect computers? Or?

    Christian
    :20295
Children
No Data