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

Sophos Deployment Packager update location does not pass along port number in installed package.

DPPToronto

Every time I create a package using the Deployment Packager and try and set a non-standard port number in the Update Location (eg.  http://sav-dl.domain.com:8085/CIDs/S075/SAVSCFXP), the offline package when installed does not include the port in the update location and I have to manually enter it.

I just upgraded to SEC 5.0 earlier this week.

Link to screenshot of packager

Anyone else running into the same problem?

:20795


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

    Hello DPPToronto,

    not using a custom port I haven't run into this problem but done a few tests after reading your posts. The culprit is the ConfigUpdate tool which parses the path and removes the colon and the following characters. I've found out that it stops at the next colon though so using sav-dl.domain.com::8085 could be used as a workaround (note that this applies only when Include selected components is checked).

    Christian

    :20813
Reply
  • 0

    Hello DPPToronto,

    not using a custom port I haven't run into this problem but done a few tests after reading your posts. The culprit is the ConfigUpdate tool which parses the path and removes the colon and the following characters. I've found out that it stops at the next colon though so using sav-dl.domain.com::8085 could be used as a workaround (note that this applies only when Include selected components is checked).

    Christian

    :20813
Children
No Data