Software Deployment

Hi Iburnell

I would take the below approach:

1. During the installation of the application prompt a Message Box to user saying the Citrix need to installed on their machine and they need to close the applciation(time of installation as well need to mentioned) and when they click the install button for starting the installation,run the installation program,so that they have time to save their work(a vb script can be written for this logic)
   
2. Once user click on yes,check for any running process for citirix and kill if any is running still.
3. Uninstall the Program Neighborhood and then install the higher version of the citirix.

Regards,
Sumit

In these situations, most clients send out an email prior to deployment that says, in nice flowery language:

"We're going to push this application out in [x] evening's time. If you're dumb enough to leave your app running while this happens, don't come crying to IT when you lose the documents you were working on all day and failed to save."

Then you send another one on the day itself. Truly, if they are that dumb, they deserve what they get.

As Pieter says, your package should then check for and kill any of the Citrix processes before installing the new version.

It might be wise to exclude board members from your deployment group/collection.

VBScab truly takes a very aggressive approach towards end-users. ;)

There is always an option to Run Advertised program. Do not force it through SCCM. Kill processes if needed.

you could perhaps choose the option to 'only install when no user is logged on' in SCCM.
you could start killing off Citrix processes but I imagine this would not make your users happy...
By only installing when no user is logged on, you avoid the problem alltogether.

If you just want to check for running processes, you could launch the msi install from a wrapper and do a check for running processes in there, then you can fail with whatever exit code you like.

Just my 2c ofc.

PJ