Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 4 subscribers
  • Views 11876 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

Published SEC SophosUpdate in IIS over tcp/8080 - new installs say 'Could not contact server' during install

David Lewis1

Hi,

We recently published the Sophos Enterprise Console SophosUpdate folder in IIS 8.5 following the steps listed in https://community.sophos.com/kb/en-us/38238.

From member servers, we're able to test the networking by pulling a random DLL from SEC (http://a2adm2:8080/SophosUpdate/CIDs/S000/SAVSCFXP/SetupEnu.dll).

The IIS site has anonymous auth enabled, and the Windows folder itself has Everyone Read access on the Share and NTFS.

The Update policy in SEC was updated to the new site http://a2adm2:8080/SophosUpdate.

 

We deployed a new Windows Endpoint installer using the Deployment Packager (under Primary update source, we leave username and password blank).  When we try to install the package on a server, they all are saying 'Count not contact server', but we know the networking allows it.

How should we proceed?

 

The installs were working fine when the installer package pointed to a SMB share (\\a2adm2\SophosUpdate) but now published in IIS, it isn't working.

 

Thanks,

David



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to David Lewis1

    Hello David,

    indeed SAVSCFXP is missing from the path. Has the correct package been used (I know, it's a question like is the power cord plugged in but ...)?

    I'm not aware that setup.exe would strip the path. If you open the package (...AA.exe) with e.g. 7zip you should find a setup.vbs that calls setup.exe with wshShell.run, the -updp  should be (with added quoting for the vbs) what you've specified in the DP.

    Christian

  • 0 in reply to QC

    Hi QC,

    I extracted the package and see this in setup.vbs:

    Set wshShell = WScript.CreateObject ("WSCript.shell")
    wshShell.run sDstFolder + "\SAVSCFXP\setup.exe -crt R -s -mng yes -updp " + Chr(34) + "http://a2adm2:8080/SophosUpdate/CIDs/S000/SAVSCFXP" + Chr(34) + "" + Chr(32) + scriptArgs,, true
    sDstFolder = oFSO.GetSpecialFolder(2) + "\cid_packager_temp"
    oFSO.DeleteFile sDstFolder + "\cid_packager.tmp"

    When we try installing, the Autoupdate MSI runs and installs, but when it updates, it says Cannot contact server.

     

    Should setup.exe be in sDstFolder + \SAVSCFXP?

    David

  • 0 in reply to QC

    setup.exe appears to be there:

  • 0 in reply to David Lewis1

    Hello David,

    setup.exe is apparently in the correct folder, otherwise AutoUpdate wouldn't get installed. The URL in -updp should be passed to AutoUpdate without modification. As far as I can (just tested with this URL) this is the case.
    Hm, as it is not clear what happens where I'd try to narrow it down. Please replace S000 with, say, S999 and check the URL in the logs. If it's again truncated try without the port. And, just to make sure, AutoUpdate is the only component installed.

    Christian

Unfiltered HTML