Hi,
wanted to share with the community how I solved this task of upgrading already installed Office 2010 (Office 2007 was tested also) to Office 2013 Pro Plus Sp1 VL via Application Model.
In short: in order for it to work, .msi should not be use but the .msp file that you create when you customize your Office installation because .msp contains already a step to remove old Office versions before installing a new version!
Prerequisites:
Prepared .msp file for Office 2013 -> This is important because when specifying installation program on "Content" tab you have to use the .msp (setup.exe /adminfile yournameoffile.msp /config en-us.xml)
Detection clause which you need if you want to specify Detection rule, obtained from a dummy app which you create before.
So, SCCM 2012 R2 with test machine which has installed Windows 7 x64 Enterprise version with Office 2010 Pro.
1. Create Application -> Manually specify the application information.
Fill out Name and other field according to your needs. Same for next step "Application Catalog"
2. Deployment types -> Manually specify the deployment type information.
General Information step -> Fill out Name and language.
Content -> specify network path to the folder containing Office 2013 (do not specify proplus.ww folder)
-> specify Installation program and enter "setup.exe /adminfile yournameoffile.msp /config en-us.xml"
Detection Method -> Best way to obtain would be to create a dummy application with .msi file and the you get all the data automatically filled in including clause needed in this step.
-> Setting Type: Windows Installer, Product code: {90150000-0011-0000-0000-0000000FF1CE} (02.06.2015, Office 2013 Pro Plus SP1 VL)
User Experience -> Install for System - Only when I user is logged on - normal (if you want your users to see the progress)
Requirements - fill in according to you needs.
Dependencies - fill in according to you needs.
Notes: Under application catalog maybe it is not a bad idea to Write under "Localized description" that the user should first close all running Office apps. This is a more friendly approach when type of deployment is set to "Available".
Suggestions welcome,
Cheers,