locked
Installing Office 2019 on RDS Server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    We are really struggling to install Office 2019 onto a Windows 2016 Server running RDS services (Terminal Servers). We provide hosted desktop solutions using SPLA licensing and have been attempting to install the latest version of Office on a server for testing prior to rolling out to our customers.

    I downloaded the ISO from the volume licensing site but this seems to be incorrect. Following some searching online it appears that you have to use a deployment tool and an xml config file to download and install. I have tried all variations I can find but am unable to get a successful installation. The closest I get is it downloading some files and then reporting that the OS is not Windows 10 and I should upgrade. 

    I have put an extract from my xml below...


      <Add OfficeClientEdition="32" 
    Channel="PerpetualVL2019"
    SourcePath="C:\Software\Office2019Pro32bit\Office" >

        <Product ID="ProPlus2019Volume"
    PIDKEY="entered our key here">
          <Language ID="en-us" />
        </Product>
        </Add>

    Can someone please confirm if it is possible to run Office 2019 on an RDS system, surely Microsoft haven't stopped the ability to do this?

    Many thanks to anyone who can offer any advice.

    Regards,

    Simon

    Wednesday, November 14, 2018 12:20 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I guess you can say it is solved.

    Had to build a build a 2019 server and was then able to install Office 2019 on it using the config file.

    So disappointing though that this is the only solution as it means either a huge amount of work building new servers or telling customers they can't use the new version of Office.

    Many thanks anyway for the assistance.

    Tuesday, November 27, 2018 11:20 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Simon,

    The page System requirements for Office tells us system requirements for Office 2019: Operating system Windows 10, Windows Server 2019. So, Windows 2016 Server doesn’t support Office 2019.

    If the system, hardware and environment meets the requirements, you should be able to install a volume license version of Office on a RDS server directly. You can refer to Deploy Office 2019 (for IT Pros) to deploy Office 2019 with the ODT, and related configuration file examples are also mentioned in the article. More information about these configuration.xml settings is available here: Configuration options for the Office Deployment Tool.

    Also, appropriate number of Microsoft Office licenses are needed - one for each desktop that accesses Microsoft Office on the servers. In addition, you need RDS CALs and Windows CALs for each device or user and one or more Windows Server licenses for each server. This Microsoft Volume License Brief should be helpful for you: Licensing of Microsoft Desktop Application Software for use with Windows Server Remote Desktop Services.

    In addition, if you use Remote Desktop Services (RDS) to provide shared computers to users in your organization, the Office product and deployment plan recommended by Microsoft is Office 365 ProPlus. In this case, you need to use the Office Deployment Tool and enable shared computer activation to do the installation. For more information, please refer to Deploy Office 365 ProPlus by using Remote Desktop Services.

    Hope it’s helpful. Anything unclear, please feel free to let us know.

    Best Regards,

    Herb Gu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Microsoft Team

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

    Wednesday, November 14, 2018 9:34 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for your reply.

    I'm not going to lie, Microsoft really frustrate me lately as they seem to make things unnecessarily difficult.

    I cannot understand why they would make an Office product that doesn't work on Server 2016 RDS systems. Server 2019 has only just been re-released following the issues the original release had. That means that there is no way we would consider putting that on production servers for our clients but it means that they locked in to Office 2016 now on our 2012R2 and 2016 servers.

    It just feels that Microsoft are trying to make it harder for resellers and partners to sell their solutions to force people into Office 365, which doesn't suit everybody!

    Wednesday, November 14, 2018 10:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's amazing to read that!

    As a reseller and partner, we do not have time to migrate all of our customers' installs to Windows Server 2019!

    We need to be able to install Office 2019 on Windows Server 2016!
    Windows Server 2016 is not at the end of life as far as I know.
    Wednesday, November 14, 2018 2:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    As we all know, Office 2019 is the latest version of Microsoft's productivity software designed and developed for the latest operating systems Windows 10 and Windows Server 2019, succeeding Office 2016. For older operating systems, Microsoft has some supported products Office 365/Office 2016/Office 2013 to meet the different needs of users.

    This forum focuses on the technical issue discussion for Office. If there is any feedback on Office 2019, you can refer to How do I give feedback on Microsoft Office? to submit feedback to product team to have a try. Thanks for your understanding.

    Regards,

    Herb

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Microsoft Team

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

    Friday, November 16, 2018 2:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am checking the status of this issue. Do you have any update for it?

    If my reply is helpful to this question, please remember to mark it as answer. Your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding.

    Best Regards,

    Herb

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Microsoft Team

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
    Tuesday, November 20, 2018 10:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Any update here? Have you solved the problem? 

    If my reply is helpful to this question, please remember to mark it as answer. Your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding.

    Best Regards,

    Herb

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Microsoft Team

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

    Tuesday, November 27, 2018 4:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I guess you can say it is solved.

    Had to build a build a 2019 server and was then able to install Office 2019 on it using the config file.

    So disappointing though that this is the only solution as it means either a huge amount of work building new servers or telling customers they can't use the new version of Office.

    Many thanks anyway for the assistance.

    Tuesday, November 27, 2018 11:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Can you post a copy of the config file you used? (w/o the key obviously)
    Wednesday, October 23, 2019 1:28 PM