Problem deploying Project 2016 alongside Office 2016
Hello dear community,
I am having issues with the deployment of Project 2016 when it is installed after Office 2016. I am using .MSI installers for both programs.
During OSD we install Office on every machine. When the user is ultimately working with his Computer and realizes he needs Project then we want to be able to deploy it to that machine. That in theory works fine.
So, now to my problem. When I install Project with my adminfile which I specifically created with the Project OCT, the feature installation changes I made are not applied to the final installed Project. To help you understand, I've attached a screenshot.
Office Customization Tool vs Installed Product
My admin file is called projectconfig.msp. My installation switch is Setup.exe /adminfile projectconfig.msp. That works, the silent GUI option works. I've tried to work with config files (.XML) but that didn't bear any fruits. I am legitimately at a loss here, don't know what the issue is. Probably doesn't help that I am a newbie at this. I don't really know where to upload my .msp file in case someone wants to take a peek at it.
Anyhow, if theres something unclear, please do not hesitate to contact me.
Setup /adminfile %~dp0projectconfig.msp
thanks for your comment. Yes, I've tried the 'Update' folder method. To no avail. Might be worth adding that the install works (changes made to the feature Installation apply) when theres no other Office product installed. - Nub 5 years ago
that indeed sounds like it could apply to my case. Is there an official word from Microsoft about this issue? I did not find a thing in my, admittedly sparse, googling. - Nub 5 years ago
https://community.spiceworks.com/topic/1572962-visio-2016-click-to-run-volume-license-issue - DaveMT 5 years ago