11-22-2017 07:55 AM
11-22-2017 07:55 AM
I deployed Office 2016 Pro Plus and Project as C2R installation on Remote Desktop Services (Windows Server 2016) using the Office Deployment Tool and following the advice in the support article: https://support.office.com/en-us/article/Deploy-Office-365-ProPlus-by-using-Remote-Desktop-Services-...
Everything installed without issues and I can start the Project Client and authenticate with my cloud account (this is not the Windows account used to logon to Remote Desktop).
I get the pop up in Project that advertises new features:
But for example the Agile feature doesn't show up in the New Project dialog and the Project ribbon
The Account dialog and the About Dialog look good and show the correct version:
Anyone any ideas what went wrong? @Brian Smith maybe?
11-22-2017 08:51 AM
Is that C2R-P you are running Trutz, or the true subscription product? The 'about' page looks like Project Professional 2016 and not Project Online Desktop Client. Which version do you see of the winproj.exe executable directly?
Also have you closed and opened again - and did you see a license acceptance on the first start? I have seen where the new features don't light up until after a restart of Project after having accepted the license. Also if you are connected to Project Server 2013/2016 you will not see the features, but it feels more like a non-subscription product, but it did show you the 'What's New' which seems to conflict.
If none of that helps, can you share the configuration.xml file you used to define your ODT installation?
11-22-2017 12:21 PM
I used the standard Office Deployment Toolkit, see also the configuration.xml quoted:
<Configuration> <Add OfficeClientEdition="64" Channel="InsidersFast"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> <Language ID="de-de" /> </Product> <Product ID="ProjectProRetail"> <Language ID="en-us" /> <Language ID="de-de" /> </Product> </Add> <Updates Enabled="TRUE" Channel="InsidersFast" /> <Display Level="None" AcceptEULA="TRUE" /> <Property Name="SharedComputerLicensing" Value="1" /> </Configuration>
The WinProj.exe located in C:\Program Files\Microsoft Office\root\Office16 states the following version: 16.0.8730.2074
The license acceptance doesn't come up due to the Remote Desktop installation setting:
Display Level="None" AcceptEULA="TRUE"
I was asked to enter the O365 User Account during first run though.
I started the client connected to a POL tenant in first release for all users.
Thanks for your help
11-22-2017 12:33 PM
That all looks perfect Trutz. Do you see the same if you start standalone? It should work either way. I'll also try installing with your configuration.xml settings and see what happens.
11-22-2017 12:42 PM
Yes, it looks the same if I start the "Computer" profile.
11-27-2017 03:18 PM
Did you have the chance to test the installation?
Maybe it is linked to the fact that the O365 activation on Terminal Server is not registered against the 5 regular installs that come with a subscription. At least that I noticed that the Terminal Server activation is not listed for the given account under "Install status" in the O365 portal (which is expected behavior from what I've read).
11-27-2017 03:39 PM
I haven't yet Trutz, busy over the holiday weekend/weeks. I suspect you are correct, as I have seen the features not light up until you have opened and accepted the license then restarted - ti feels like that isn't happening in this virtual environment. Is there a support case open?
11-28-2017 02:55 AM
Thanks for your feedback I just opened a support case: Ticket #6857103
12-04-2017 03:48 PM
Hi @Brian Smith,
Sorry to bother you again with the topic. I created the ticket last week but received so far no initial call nor initial email from the engineer assigned. Instead it says in the Admin portal, that an engineer is reviewing the case. Is this a normal delay?
Therefore I tried the installation on a second Terminal Server with the same results. I used the same configuration file (except for the sharing property) on a Win 10 VM and it worked without issues.
12-04-2017 03:56 PM
Ping me the case number at firstname.lastname@example.org and I'll see if I can trace where it got to Trutz.
Sorry for the runaround you are getting here.
12-05-2017 04:54 AM
At the end, the case was closed as the behavior is currently "by design" for terminal services environments, on which Project is installed using the "SharedLicensing" setting in the Office deployment tool.
I was asked to create a UserVoice entry, which I did: