Due to reasons I won't go into, the vast majority of Applications set up at some of our clients call scripts that in turn call the install. Since many of them are MSI's we're still able to use the Windows Installer detection method. There are some caveats to calling a script instead of the direct install (make sure you use /qn for the msiexec command line if you don't want the Windows Installer progress bar coming up), but it works just fine.
-Phil From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Monday, August 26, 2013 3:48 PM To: '[email protected]' Subject: RE: [mssms] RE: Dealing with Software reinstalls Well then I have been lied to by our consultants... time to investigate. Thanks. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Monday, August 26, 2013 3:43 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Dealing with Software reinstalls Just have to manually create your detection rules, etc. Works for me too... From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Sent: Monday, August 26, 2013 3:42 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Dealing with Software reinstalls I haven't had any issues with the script installer method on applications... It works well with our Winbatch scripts! On Mon, Aug 26, 2013 at 2:38 PM, Kevin Johnston <[email protected]<mailto:[email protected]>> wrote: Okay. So the reason it is a Program is because it is running a vbs script to call the installer (so it notifies the user, then when they click OK it installs then lets them know it's done). I was told that if I am running any scripts I should use Program not Application. And since this installs for the User as the user this seems like the logical step. I don't have compliance ready yet, but it looks like I may have to rethink this deployment. Thanks, Kevin From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Schwan, Phil Sent: Monday, August 26, 2013 3:02 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Dealing with Software reinstalls Two main choices: 1. Old school - Use Compliance Settings (DCM) to detect whether present and install if not (that's way oversimplifying it) 2. New school - Move it to the new application model and rely upon the Detection Method -Phil _________________________________________________________________ Phil Schwan | Technical Specialist, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Mobile: 419.262.5133<tel:419.262.5133> www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Monday, August 26, 2013 2:53 PM To: '[email protected]<mailto:[email protected]>' Subject: [mssms] Dealing with Software reinstalls Not sure how some of you would deal with this type of situation, but it seems like I missed a step. I have an outlook plugin that is deployed to all users (it is the design of the plugin) not devices. So when a user logs onto their machine after we deployed it, the script would run, they would install it and everything is great. But then an issue comes up, the user uninstalls it using Control Panel - Programs and Features cause the y want to reinstall it but the program will not re-run and I assume it is because CM12 already knows it was successful the first time. This is a Package not an Application, so I am wondering if there is a way for CM12 to detect that it is not installed and re-run it. I looked through the settings and I don't see anything. Thanks, Kevin Johnston ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
