KACE Product Support

If you have an installer that installs Office 2010 with SP1, then just remove the RTM managed install and have the SP1 install instead. Otherwise you'll need to create a smart label or add an argument to an existing label that disregards machines with Office 2010 SP1 and associate that with the Office 2010 managed install.

It depends on the way you set up the label that the Managed Installation deploys to. If you set it up to just deploy to a group of systems, then yes, that will happen.

If you set it up to deploy to a group of systems that meet a certain criteria, then it would not. For example, you can set it to check and make sure that the systems do not have XX software installed at all or that they do not have XX software version YY or higher installed. It all depends on your environment, and no one knows it better than you do.

For all of my MIs I create two labels, one that I use to mark the PC as needing the installer (Office, TrueView, etc) and another that is a smart label (M_NeedOffice, M_NeedTrueView, etc) that checks to see 1. If the PC has the label marking the software as needed and 2. If the software is installed (ex. Does software title include Office).

Then I just tell my MIs to install based on the smart label.

Casey

Right, but the patch gets released before I know its going to cause a version change, and then I get reports from users that they are getting an error from the attempted re-install, now I have to disable the RTM install until I can fix the situation.

Is the same thing going to happen with apps like Java, Flash, Acrobat, etc, when patches that change the version number get applied?