/bundles/itninjaweb/img/Breadcrumb_cap_w.png

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.

2 Comments   [ - ] Hide Comments

Comments

  • We are having this issue as well and it looks to be a known issue with Project 2016 and Visio 2016 stand alone installations when installing along side Office 365 (Office 2016 version). Could that be the issue in your case? The resolution we are finally having to do (because no fix in any forum site or blog or TechNet article, etc. could resolve the issue) is to upgrade our Visio/Project 2016 licenses to subscription licenses and use the Visio/Project copies packaged with Office 365.
    • Hello Dave,
      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.
      • These are the articles I found most useful:

        https://technet.microsoft.com/library/mt703272.aspx

        https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_dep365/visio-2016-click-to-run-volume-license-issue/b3a693b4-a5ae-4aae-87ac-27dc6a6254f2

        https://community.spiceworks.com/topic/1572962-visio-2016-click-to-run-volume-license-issue
  • Ah, I guess this does not apply to us. I thought you were using the .MSI version of Office 2016, not the CTR version. Unless I am misunderstanding something now.
Please log in to comment

Answer this question or Comment on this question for clarity

Answers

0
It seems to me that the MSP isn't being referenced.

By default, Office creates a login %TEMP%. That should show you whether it is or not.

Have you tried installing with the MSP in the 'Updates' folder? Also, I *always* use explicit paths when referencing files. For situations where you don't know the ultimate destination (e.g. in SCCM's 'Cache' folder structure) use good ol' %~dp0:
Setup /adminfile %~dp0projectconfig.msp
Answered 06/29/2017 by: VBScab
Red Belt

  • Hello VBScab,

    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.
Please log in to comment
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share