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

Secondary credentials - password gets erased

Sladey

Hi,

We are running Spohos Administration Console V4.7.0.13.

We have a secondary update server of Sophos configured and all the various updating policies have the username and password configured.

When Sophos is pushed out to clients, the username field is populated however the password field is not. This has the effect of not permitting machines to update if they are not connected to our internal network.

I have tried creating a new update policy and pushing that out instead of the existing policies but to no avail.

Any suggestions welcomed.

Sladey

:37215


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

    Hello Sladey,

    sounds strange. If I interpret your description correctly the policy (and the password) is written to the database and SEC "is aware" that one is there. It's missing though when it is "exported" to an XML file. The address is Sophos, the credentials don't contain any "funny" characters - I have no idea why it should fail.  You say the (exported) policies are correct except for the missing password?

    Do you have the SQL Management Studio?

    To narrow down where the error could occur I'd run some short tests:

    • If you are using a standard Primary update location set it also as Secondary (the credentials should automatically be populated)
    • Specify an arbitrary secondary update location (perhaps tr both UNC and HTTP) with arbitrary credentials
    • Use Sophos but enter arbitrary credentials

    Assign the changed policy and check the results on a test client, also export the policy. I assume you have to contact Support (unless the tests bring some insight) but details could speed up things.

    Christian 

    :37293
Reply
  • 0

    Hello Sladey,

    sounds strange. If I interpret your description correctly the policy (and the password) is written to the database and SEC "is aware" that one is there. It's missing though when it is "exported" to an XML file. The address is Sophos, the credentials don't contain any "funny" characters - I have no idea why it should fail.  You say the (exported) policies are correct except for the missing password?

    Do you have the SQL Management Studio?

    To narrow down where the error could occur I'd run some short tests:

    • If you are using a standard Primary update location set it also as Secondary (the credentials should automatically be populated)
    • Specify an arbitrary secondary update location (perhaps tr both UNC and HTTP) with arbitrary credentials
    • Use Sophos but enter arbitrary credentials

    Assign the changed policy and check the results on a test client, also export the policy. I assume you have to contact Support (unless the tests bring some insight) but details could speed up things.

    Christian 

    :37293
Children
No Data