Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Установка Office 365 proplus на сервер терминалов RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Добрый день! Раньше был уверен, что windows - это легко, но сегодня, что то пошло не так.

    Так вот, проблема в том, что я не могу установить Office 365 proplus терминальный сервер Windows 2016 Standart.

    Что делал:

    1. Скачал это https://www.microsoft.com/en-us/download/details.aspx?id=49117

    2. Создал папку ODT в корне диска С

    3. Перешел в папку ODT

    4. запустил officedeploymenttool_11306-33602

    5. через CMD сделал 2 команды:

    C:\ODT>setup /download configuration-Office365-x64.xml
    C:\ODT>setup /configure configuration-Office365-x64.xml

    И, как бы, office установился, НО при запуске любого приложения из пакета Office 365 proplus я получаю ошибку:

    "Эту копию Microsoft Office 2016 нельзя использовать на компьютере, на котором запущены службы терминалов. Для использования Office 2016 на компьютере, на котором запущены службы терминалов, необходимо использовать выпуск Office с корпоративной лицензией. " 

    Все куплено, заплачено немало денег, через 6 часов нужно сдать сервер, а я не могу, банально, установить office!

    Подскажите, как решить эту проблему!

    Thursday, January 31, 2019 8:09 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    As far as I know, this is an expected behavior as Click-to-Run versions of Office programs or suites can't be installed on a server that's running Remote Desktop Services(formerly known as Terminal Services). As a workaround, you can install Office 365 Pro Plus with shared computer activation. Please refer to the link below about the steps: Deploy Office 365 ProPlus by using Remote Desktop Services.

    Usually, to use the Office Deployment Tool and the configuration.xml file to install Office 365 ProPlus on the RD Session Host server, you need to create a configuration.xml file that includes the following lines:

    <Property Name="SharedComputerLicensing" Value="1" />

    Pease note: this is an English forum. In order to help us understand the issue you are encountering and current condition more accurately, I advised you to ask questions in English here. You can ask questions in the appropriate language forum as well.

    If you have any update or anything unclear, feel free to let us know.

    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.

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


    Friday, February 1, 2019 8:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am checking the status of this issue.This thread has been around for a long time. Do you have any update for it?

    Please remember to mark the replies as answers if they helped. Your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding.

    Anything unclear or any questions, feel free to post them back to let us know. 

    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.

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


    Thursday, February 14, 2019 1:07 AM