I am looking for feedback as I plan on using it when we do our 12.2 upgrade.
Mike Zavolas
Tallahassee Neurological Clinic
What is the .msi deployment?
Hi Mike,
My understanding is that the MSI deployment will only be available for service pack upgrades. Example:
- Upgrading from 12.0.x to 12.2: MSI not available
- Upgrading from 12.2.0 to 12.2.1: MSI available
I think you have to uninstall the old client first if you wanted to use it to push 12.2. From then on out you can use it.
MSI (Microsoft Installer) deployment is a way to deploy the client software to your fat clients or to a farm of Citrix/Terminal servers. The nice thing is you can configure the "package" a certain way so that the deployment is identical on each target. This is most important in a Citrix/Terminal Server farm so that the user experience is the same on each Citrix/TS host.. This deployment method is a feature of Microsoft networking and Group Policy where you assign the installation by group. When the targeted computers are powered on, the installation of the software is done before the user logs in (no admin rights necessary). It is a slightly crude way to do installs but it works. There are some other things you can use like Microsoft Systems Center 2012 to have more features but I have had very good luck with Group Policy deployment and I don't require the additional features of SC 2012.
We have begged GE for this functionality for more than a few years. The CPS client was not able to be packaged into a .msi file due to it's complexity until CPS 12.2 (and EMR version equivalent)
Bottom line-For me, it will be nice to not have to touch 145 machines when I do CPS upgrades in the future.
Mike Zavolas
Tallahassee Neurological Clinic
I think you're right...this matches up with what I recall from CHUG. It will still require that all computers be touched at least once in a FAT client environment like ours.
Thank you Mike!