Upgrading Outlook 2003 to 2010 where some machines have a manual install of Word or Excel 2010

Hi Everyone,
I am trying to deploy the Outlook 2010 to PCs eventually updating the only Outlook in the Office 2003 Suite. The customised office application I have on SCCM works fine, when it's just the Office 2003 Suite but in few computers, there have been manual installs of other Office 2010 products such as Word or Excel and in that scenario, the SCCM deployment just finishes the installation saying it that particular computer is "Already Compliant".  When I check it, it still has Outlook 2003 in it. So, I tried changing the detection method from just looking for the Product Id (msi) to product id and the installation file path to "Outlook.exe". After this, the package is downloaded correctly but in the software center it stucks in the Installation stage and times out... I don't know why!

Any help would be appreciated.. Thanks in advance..


5 Comments   [ + ] Show comments
  • How could anyone *possibly* know what the cause of that failure is?!?!?

    Enable Windows Installer verbose logging and examine the resulting logs:

    http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx - anonymous_9363 5 years ago
  • is it hanging on a machine where a user is logged in and possible running one of the Office apps?? Have you set the correct remove properties for ALL office apps. as pointed out, you are probably better off running an uninstall job. How many manual installs are out there??? - Badger 5 years ago
  • Thanks for the response.. :)
    The installation job hangs, at the installing stage. I sort of found the reason which is, if an Office 2010 installation is already present the "/adminfile" switch is useless. Because it reported the "Setup /adminfile " can only be used during the initial installation. From the above, my understanding was that it can't reused to install a different office product say , only outlook 2010 if an word or excel 2010 was already installed... manaully / sccm. Is that correct ??

    If Yes, what would be the alternative way to install individual Office products using the office setup more than once ..??

    Thanks again..

    Zac - the dark jedi 5 years ago
  • Use OCT to create your custom MSP and then either put the MSP in the 'Updates' folder or use '/adminfile [path_to_custom_MSP]'. It's all documented on TechNet. - anonymous_9363 5 years ago
  • Hi VBScab,

    what you proposed is what exactly I am doing for the Outlook 2010 Setup..

    The actual problem starts if the Office 2010 suite products is installed along with the older Office 2003 products, the installation comes up as "already compliant" and Outlook 2010 is not installed. - The detection method here is just the product id / msi id. This works when you do not have any Office 2010 products installed previously.

    To over come, I used two detection methods to identify if Outlook 2010 is actually installed or not by adding additonal detection method and they are, 1.product id / msi id and 2. Outlook.exe itself as a path to file . In this scenario, the installation times out and fails - Outlook 2010 is not installed and the old Outlook 2003 is left behind on the PC. However, the SCCM shows that the PC is already compliant.

    That is my problem..

    Thanks again.

    Zac - the dark jedi 5 years ago

Answers (1)

Posted by: dunnpy 5 years ago
Red Belt
If you're using an Application deployment in Config Manager 2012 then the qualifiers (probably installer GUID) for the Office suite are already present on the machine, because you have a manually installed Office family title - hence the 'already compliant' message.

You'll need to look at the criteria and possibly change it from the GUID to a core Office file to validate the installation, and maybe look at the command line you're using too - the standard 'clean' installation commands probably won't work if already have a family title already installed. You'd have to look at the maintenance mode switches to modify the installation.

It might be easier/cleaner to run an uninstall job on the manually installed Excel (which could have any old configuration installed) and then run a full, clean, install of your Office package. That way every machine has the same configuration and you won't need to modify the criteria for determining Office is installed.

Hope that helps,

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ