Managed Installations : Bug or how to work around this
Guys
I've created a managed install job to upgrade Office 2010 to Office 2013.
The install is working fine and does what it's meant to do.
Office 2013 goes to version 15.0.4420.1017 and the info bar at the bottom will show that the application suite is installed.
However, a number of hotfixes/patches are available for Office 2013, which when applied update the version to 15.0.4569.1506
When this happens the managed install then thinks that Office 2013 is not installed and started to try to install again
I know this is because it's linked to the software title but it there a way around or updating the install to pick up all versions of Office 2013 ?
Answers (7)
Comments:
-
Hi All,
Im trying to install two different McAfee packages but both are same version with different configuration, one frame pkg for Region1 and another for Region 2, how i can do this MI ?
when I create new managed install im able to associate only one file at a time, any idea how can i perform this ? as i need to perform the two installation with different configuration at a time..I have zipped both the frame pkgs, and trying to call as below
Managed Install 1:
Override Default Installation
Full Command Line:
FramePkg1.exe FRAMEPKG /INSTALL=AGENT/SILENT
Managed Install 2:
Override Default Installation
Full Command Line:
FramePkg2.exe FRAMEPKG /INSTALL=AGENT/SILENT
would this work? - rahimpal 8 years ago
Ok - so you're including the service pack as part of the install. That's fine to a point but it doesn't get me past my issue.
I have the same issue with CRM 2013 roll up 2. Once it goes it , roll up 1 tried to reinstall as the managed install says that version isn't in place (which is true) but roll up 2 supersedes roll up 1 . It would be better to have the option to link the software to a label as opposite to the software inventory version.
Comments:
-
I agree that this is an issue with how KACE manages software installations. Our plan is to turn off the Office distribution once it has been installed on the majority of systems. Then when the next update comes out that changes the version we won't have conflicting managed installs.
I believe there's a way to sort this out with smart labels, also. - chucksteel 10 years ago-
I second the smart label suggestion; Have one smart label to target machines that need 2013 then another that they join once it's installed (dropping out of the first smart label) - rockhead44 10 years ago
Fair enough. Im still on version 5 of the Kace 1000. I don't think going to v6 gives me any benefits in terms of managed installed.
Basically, I'm not doing anything incorrect , it's just how the system handles & manages the install.
the associated file is the zip I uploaded in the MI
Comments:
-
The Mi is assigned to all windows machines. Google apps does updates and this never reruns - SMal.tmcc 10 years ago