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

Deployment Packager 1.2

QC

Gave version 1.2 of the deployment packager (that Jak has "found") a quick try.

The GUI now lets you specify a secondary location. I have inspected the created packages (though not actually used them to install) and don't see that the secondary location is set. If you include RMS the updating location can only be specified when Configure AutoUpdate to download components is used, but then the package is small and uses the -updp switch to set the primary location - no trace of a secondary. It probably relies on RMS.

If you omit RMS ConfigUpdate.exe is used to set both locations although the bug/glitch/whatever when an alternate port is specified still seem to be present, the circumvention should still work.

It's close now, but no cigar. I can't quite understand why including RMS omits the setting of the updating policy. I'd like to have both RMS and a predefined policy. We want to have one package whether the user is "inside" when installing or not. Thus all components should be included (the UNC path is not available and AFAIK you can't install from a WebCID) but the client should be manageable when inside.

Christian

:25469


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

    Thanks, Elmo

    Didn't say it isn't documented (although the documentation lacks details) :smileywink:

    If you include RMS in the package no location is set at all. Instead, as I've briefly mentioned, it relies on RMS contacting the server and requesting a policy. If the install is done at a location where it can't contact the server (usually known as "outside") it won't be able to update.

    That it ignores the secondary location with the download option isn't actually the problem you won't get farther than installing AutoUpdate. You are likely using a WebCID for "outside" clients but it is not valid as initial install path - thus configuring the WebCID as primary doesn't help (article 64639 isn't very explicit but that's what I read between the lines :smileywink:).

    Yes, maybe worth contacting Support

    Christian

    :25931
Reply
  • 0

    Thanks, Elmo

    Didn't say it isn't documented (although the documentation lacks details) :smileywink:

    If you include RMS in the package no location is set at all. Instead, as I've briefly mentioned, it relies on RMS contacting the server and requesting a policy. If the install is done at a location where it can't contact the server (usually known as "outside") it won't be able to update.

    That it ignores the secondary location with the download option isn't actually the problem you won't get farther than installing AutoUpdate. You are likely using a WebCID for "outside" clients but it is not valid as initial install path - thus configuring the WebCID as primary doesn't help (article 64639 isn't very explicit but that's what I read between the lines :smileywink:).

    Yes, maybe worth contacting Support

    Christian

    :25931
Children
No Data