Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 12591 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

Creating packages with Deployment Packager

Alphateam

I'm sure this has to be easy, but I just can't get it to work right. I has to be a simple mistake I'm making, but for the life of me can't figure it out. 

For the source folder I have: C:\ProgramData\Sophos\Update Manager\Update Manager\CIDs\S000\SAVSCFXP 

I have holes in the firewall and updating setup off site. I know it works because Sophos consulting helped me do that part of it. The site is http://sophos.mysite.org/SophosUpdate

I then choose RMS because I want it to use our updating locations. Then hit Build Package. After install it says the Primary Location is c:\user\myusername~1\AppData\Local\Temp\cid_p..... and nothing for secondary. 

If I try not and select RMS and put in that address above it can't connect to the server. 

:50372


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

    Hello Alphateam,

    After install it says the Primary Location is c:\user\...

    this suggests that AutoUpdate could not obtain an updating location and uses the default, which is the location it has been installed from.

    There are two ways it can get the address(es)

    1. you include RMS in the package (if you select this combination you can't enter an update location)

    • setup.exe installs RMS from the package
    • RMS has to be able to connect to the management server
    • It requests the updating policy from the console
    • the console supplies the applicable policy iff the endpoint is in a group other than Unassigned
    • If RMS fails to retrieve the policy it remains set to the install directory

    2. you do not select RMS or elect to not include it in the package and configure the Primary update location

    • setup.exe is started with the -updp parameter which is used to set the Primary location
    • If RMS is requested, no Secondary is set at install time; RMS is installed by AutoUpdate and attempts to retrieve the policy - if it fails the Primary remains the one set in the packager
    • If RMS is not requested the Secondary is set after initial install

    Note that in contrast to the policy in SEC you have to specify the complete path to the SAVSCFXP directory, i.e. if you Policy has h__p://sophos.mysite.org/SophosUpdate, in the Deployment Packager  you have to use - given your source - h__p://sophos.mysite.org/SophosUpdate/CIDs/S000/SAVSCFXP.

    Christian

    :50428
Reply
  • 0

    Hello Alphateam,

    After install it says the Primary Location is c:\user\...

    this suggests that AutoUpdate could not obtain an updating location and uses the default, which is the location it has been installed from.

    There are two ways it can get the address(es)

    1. you include RMS in the package (if you select this combination you can't enter an update location)

    • setup.exe installs RMS from the package
    • RMS has to be able to connect to the management server
    • It requests the updating policy from the console
    • the console supplies the applicable policy iff the endpoint is in a group other than Unassigned
    • If RMS fails to retrieve the policy it remains set to the install directory

    2. you do not select RMS or elect to not include it in the package and configure the Primary update location

    • setup.exe is started with the -updp parameter which is used to set the Primary location
    • If RMS is requested, no Secondary is set at install time; RMS is installed by AutoUpdate and attempts to retrieve the policy - if it fails the Primary remains the one set in the packager
    • If RMS is not requested the Secondary is set after initial install

    Note that in contrast to the policy in SEC you have to specify the complete path to the SAVSCFXP directory, i.e. if you Policy has h__p://sophos.mysite.org/SophosUpdate, in the Deployment Packager  you have to use - given your source - h__p://sophos.mysite.org/SophosUpdate/CIDs/S000/SAVSCFXP.

    Christian

    :50428
Children
No Data