How to create a small custom installer package which downloads components?

Hello -sd,

sorry for the delay, had a meeting.

Now what the article does not tell you is that you can configure a CID with the desired policies - but from XML policies integrated into the "Source folder" I get it you are aware of this. Note that every client updating from this CID will attempt to apply the policies - that's probably your concern. Thus if you assign differing policies from SEC client might "suddenly" revert to the policies in the CID.    

You could create a(n additional) CID especially for the purpose of setting certain policies at install time. Don't quote me on the following - last time I checked (and this is quite some time) it worked like this: AutoUpdate installed itself from the extracted directory contained in the package. It then installed all other products from the path in -updp. As last product it updated itself - honoring a potentially existing sauconf.xml and this way eventually updating from a CID different from the one it initially installed from. Thus for subsequent updates it'd use the "unconfigured" CID.

You'd have to give it a try if it still works this way. If the clients you install are managed you can of course tell them to use a different CID in the future by means of the updating policy.

Christian

Hello -sd,

sorry for the delay, had a meeting.

Now what the article does not tell you is that you can configure a CID with the desired policies - but from XML policies integrated into the "Source folder" I get it you are aware of this. Note that every client updating from this CID will attempt to apply the policies - that's probably your concern. Thus if you assign differing policies from SEC client might "suddenly" revert to the policies in the CID.    

You could create a(n additional) CID especially for the purpose of setting certain policies at install time. Don't quote me on the following - last time I checked (and this is quite some time) it worked like this: AutoUpdate installed itself from the extracted directory contained in the package. It then installed all other products from the path in -updp. As last product it updated itself - honoring a potentially existing sauconf.xml and this way eventually updating from a CID different from the one it initially installed from. Thus for subsequent updates it'd use the "unconfigured" CID.

You'd have to give it a try if it still works this way. If the clients you install are managed you can of course tell them to use a different CID in the future by means of the updating policy.

Christian