Software Deployment

Didn't want to go down that route... Can you get away with running the install with a /s switch or do you really want to MSI it?

The problem you will have is with getting the services to stop and start at the right time. The other problem you have is that it will deliver files that will need to be changed/updated from the "Autoupdate" feature. You will have to find out what files will require updating and remove the component ID in order to stop self-repair/overwriting.

Windows Installer provides a facility to stop and start services...but it doesnt work very well. Move the "Stop/Start Service" phase higher and lower in your application installation sequence to see if that helps. Also make sure that you are workstation deploying the application because users may not have the rights to set personal firewall settings themselves.

If that doesn't fix it....then try finding a tool to stop the services for you and restart them at the end of the installed.

Thanks for your supplies. There is no need to MSI it... nice to have. Changing the policies would be done by the ePO from Network Associates. The Setup Application was created with Installshield. So there is the possibility to create an iss file which you can use with the -s (silent) Setup Switch.

After a reboot the Firewall is activated. By default all requests are blocked.

I need a solution to deactivate the Firewall after reboot by default for deploying the policies in the next step.