Hi Friends,

I have been working in the areas of Software distribution on Windows for more than 5 years. There are some hard problems I'm facing in managing software deployment. I just thought I'll get some comments and suggestions from the experts here which would help me. Please note that I've did my ground work (searching in newsgroups,KB's etc).

My environment.
- We have ~400 different applications.
- ~2000 Office machines and ~1500 remote machines. By remote machines I mean laptops and homesetups which we do not know when they will be connected to Office network.
- We use Managesoft for software distribution.

Problems being faced.

1. handling in-use upgrades.
Say we have app 1.0 deployed to all the machines. Later when there is the next version app 2.0 how do we do the upgrade seemlessly. i.e while the user is logged in and working. The main problem is how to upgrade app 1.0 while the user is using app 1.0.

2. Upgrade on remote machines.
Say we have app 1.0 deployed to remote machines. later when there is app 2.0, we deny app 1.0 and assign app 2.0. how to handle the case when the PC/laptop gets disconnected from Office network after 1.0 is uninstalled and before 2.0 is installed. there will be no app on the PC/laptop.

0 Comments   [ - ] Hide 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