

Lets get to it!įirst of all, thanks for the information you provided. Horrible experience before you even start doing anything. No one likes to login to a machine and see 10 popup windows asking you do to do stuff. What we are essentially looking for here to clean and sleek deployment of whatever we need to push out to our client machines. If you’re able to achieve all of the above you’re better than most. No auto update services should be allowed to start.

Again, once installed no extra rubbish should be copied to users desktop / start menu / run once etc. II. Once installed you should run it and no popups / random windows / activation, registration dialog boxes etc. You run the install and usually don’t even know when its done unless you watch out for msiexec processes etc. I. Installation has to be silent with no user intervention required. Now, I don’t even remotely consider myself software packager but when deploying applications I usually follow few simple rules to take care of the basics. There are tons of people that will just “install” what’s necessary to get them out of trouble (even if it means doing it 100 times over and over!) The same group of people cannot really distinguish between installing and deploying and if you happen to have them on board – you’re in trouble. Deploying software in the enterprise can be quite complicated, it doesn’t have to but it can be at times.
