Forum Discussion

Trutz_Stephani's avatar
Trutz_Stephani
Steel Contributor
Nov 22, 2017

Deploying Project 2016 C2R (Insider) on Terminal Server doesn't show new features

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-af9d7621-8c2c-4181-84b4-27778b1e7920

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:

New features Popup

 

 

 

 

 

 

 

 

 

 

But for example the Agile feature doesn't show up in the New Project dialog and the Project ribbon

 

New Project dialog without Agile featureProject Ribbon without Agile feature

 

 

 

 

 

 

The Account dialog and the About Dialog look good and show the correct version:Account dialogVersion number

 

 

 

 

 

 

 

Anyone any ideas what went wrong? Brian-Smith maybe?

  • Brian-Smith's avatar
    Brian-Smith
    Icon for Microsoft rankMicrosoft
    Nov 22, 2017

    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?

     

    Best regards,

    Brian.

    • Trutz_Stephani's avatar
      Trutz_Stephani
      Steel Contributor
      Nov 22, 2017

      Hi Brian,

      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

      Trutz

       

      • Brian-Smith's avatar
        Brian-Smith
        Icon for Microsoft rankMicrosoft
        Nov 22, 2017

        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.

        Best regards,

        Brian.

Resources