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

Initial install source help

RogueViper

I've been having trouble with using the 'protect' function in SEC. We have a synchronised laptop group based on an AD OU. When a laptop syncs over I go along and use the protect function; this pushes out the update client and the iconn.cfg file. At this point the install becomes stuck unless I manually copy over a working iconn file from another laptop to the config folder. 

It seems the iconn file is defined in the 'Initial install source'; for us it defines a UNC path as \\[Server IP]\SophosUpdate

The primary update source we use is web, so the source is http://[Server IP]/sophos with a secondary address set as \\[server name]\SophosUpdate plus the credentials for this share. 

Why won't the clients update using the initial install UNC path? The error we get in the update logs is - 

CIDUpdateLocation::SyncProduct: Failed to update product (Sophos AutoUpdate) from "\\[Server IP]\SophosUpdate\CIDs\S001\SAVSCFXP\", Error is :CIDSYNC_E_SRCNOTFOUND (Source not found.)

My initial thoughts were a permissions issue, but if I'm using my domain admin account details in the protect function and I can navigate to the initial install source in my own PC surely this isn't the issue?

Any help would be greatly appreciated.

Mike

:27393


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

    HI,

    The initial install source must get the credentials from the primary update location as if I setup the following:

    • primary location as: "http://1.com/1" with no username and password specified.
    • the initial install source in the updating policy has: "\\server\sophosupdate"
    • the secondary update location has a UNC, with a username and password.  

    The task that gets created on the endpoint has the following switches.

    -ouser "" -opwd "" -mng yes -s -xp "\\server\sophosupdate\CIDs\S000\SAVSCFXP" -crt R

    I would check that the account specified in the primary update location allows you to get updates from the initial install location, and that the password is correct.  I would suggest re-typing it back into the updating policy linked to the group, just to be sure it is stored correctly.

    Regards,

    Jak

    :27423
Reply
  • 0

    HI,

    The initial install source must get the credentials from the primary update location as if I setup the following:

    • primary location as: "http://1.com/1" with no username and password specified.
    • the initial install source in the updating policy has: "\\server\sophosupdate"
    • the secondary update location has a UNC, with a username and password.  

    The task that gets created on the endpoint has the following switches.

    -ouser "" -opwd "" -mng yes -s -xp "\\server\sophosupdate\CIDs\S000\SAVSCFXP" -crt R

    I would check that the account specified in the primary update location allows you to get updates from the initial install location, and that the password is correct.  I would suggest re-typing it back into the updating policy linked to the group, just to be sure it is stored correctly.

    Regards,

    Jak

    :27423
Children
No Data