We currently use sms installer's IPF file to exe for sms deployments. the problem is its calling almost 200 scripts in order and its time to replace it.

we use this single ipf to push to clients to make sure all the previous software was installed before the next. I need to come up with a new way of doing business and would like some suggestions on how to handle package/patch deployment in a similar fassion using a newer way. it seems sms installer was replaced with admin studio and MSI's. Since we are starting over with a new workstation build we can start over on the patch/app deploys for this new model.

Final.ipf more info:
1. login as admin displaying patching banner, lock out keyboard and mouse
2. check ipaddress for location site 1 or site 2. if site 1 get patches from site 1 server. else site 2 server.
3. install patch 1
4. if patch 1 is installed install patch 2 and so on. (checking for previous patch by a special reg key created at the end of patch 1 completion)
5. if patch 2 requires a reboot, reboot then continue where it left off
that is the basic logic we are using. what would be the best way to maintain the featueres of final with other more modern means? other ideas are also welcome.

0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity