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

Changing update server in EC or on local PC does not work. EC 5 Endpoint 10

DougS

I changed the Primary server, and added Sophos as the Secondary, in the default Updating policy on the EC.  The workstation shows the new values, but when I do an Update Now from the systray icon, the log reflects as if no change was made, even after rebooting the pc.  I tried making Sophos the primary and my server the Secondary and the logs still reflect as if I made no change.  Anyone know what the problem is?

I checked the config files on the local workstation and verified they are as I changed them

:41885


This thread was automatically locked due to age.
  • 0

    Hello DougS,

    the log reflects as if no change was made

    I fear I don't quite figure what this means - are you saying that the updating log shows Downloading product ... from server <oldaddress>? Or that, while the old value was in effect, updating failed (and that's why you changed the policy) and updating still fails after the change?

    I tried making Sophos the primary

    This is not possible using the UIs - SEC permits Sophos only for the Secondary and for a managed computer Configure Updating does not allow changes. 

    So - could you please try to rephrase your question and describe the issue you are trying to resolve with the change?

    Christian

    :41915
  • 0

    In the Default Updating policy on the EC: The Primary was set to server GREPS3101.  There was no Secondary.  I wanted laptops to be able to update even when they had no access to GREPS3101.  I added Sophos as Secondary.  To test the Secondary, I changed the name of the Primary entry to GREPS3101x.  Pushed out the changed using Comply with...

    Under Configure updating on the workstation: The Primary location now shows GREPS3101x and the Secondary shows Sophos.  I choose Update now.  I choose View updating log.  I click Refresh.  The log entries in the appropriate date/time range that mention a server all still show GREPS3101.

    In the iconn.cfg file on the workstation:  I changed the AllowLocalConfig to 1 in all 4 places.  I set the Primary to Sophos. I set the Secondary  to GREPS3101x. Saved the file.

    Under Configure updating on the workstation: The Primary location now shows Sophos and the Secondary shows GREPS3101x.  I choose Update now.  I choose View updating log.  I click Refresh.  The log entries in the appropriate date/time range that mention a server all still show GREPS3101.

    :41933
  • 0

    Hello DougS,

    sounds strange - can't imagine where it should keep this information (especially across reboots). Is there only one client showing this odd behaviour?

    Christian

    :41975