Share via

Installing Office 365 on Windows Server 2012

Anonymous
2015-12-20T08:53:45+00:00

Hello fellow Microsoft users,

I want to install Office 365 (Enterprise E3) on a server with Windows Server 2012 as OS.

The installation completes normally without any warnings or popups, but when I start one of the applications e.g. Word, I get an error message telling me that this version of Microsoft Office 2013 cannot be used on a computer with Terminal Services and the volume-licensing edition is recommended.

We want to install Office locally, only on the server (if the administrator needs to open a spreadsheet by coincidence and so that he can use OneDrive for business for example), not in the user accounts. The respective users have their own Office 365 account installed on their computers. So there is no use for a volume-licensing edition. How do we fix this?

Thanks in advance!

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2015-12-21T03:30:43+00:00

    Hi Samir,

    After reading your posts, I fully understand your concerns.

    For your terminal services enabled server, using shared computer activation for Office 365 Pro Plus deployment is the only way based on your situation. You can still keep just the admin access the Office installed on this server, and the users can just use the Office applications downloaded from the Office 365 portal in their own computer. that is to say, administrator and users all use their own Office suites separately.  

    Thanks,

    April

    4 people found this answer helpful.
    0 comments

10 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-01-21T03:45:32+00:00

    Hi Samir,

    I’m sorry for the delay. Please still let us help you with this.

    Based on the situation you described, kindly know that using shard computer activation will be the only way. And you can follow two points below to give it another shot:

    a. In the configure file you attached, please note the Name is no longer a supported attribute with the logging element (hereis the reference). As a result, you can modify that sentence to <Logging Level="Standard" Path="C:\Users\XXX\Desktop\XXX_Office\tp" />.

    b. Actually, to make sure the accuracy of the configure file, you may use the Office 365 ProPlus Configuration XML Editor (a web page) to generate and edit the Office Click-to-Run Configuration.xml file. https://blogs.office.com/2015/09/30/deployment-scripts-for-office-2016/

    I am looking forward to your reply.

    Best regards,

    April

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2015-12-24T03:20:31+00:00

    Hi Samir,

    Can you share any updates with us?

    Regards,

    April

    0 comments
  3. Anonymous
    2015-12-20T14:11:34+00:00

    Thank you for your fast response Iris!

    Yes, the encountered error message is as that KB mentions.

    You mention that the workaround is installing Office with shared computer activation.

    However, what I understand from the article is that 'shared computer activation' allows for a single installation (on the server in this case) in which you can assign Office to the users as well. But this is not what we are looking for, since we've already an Office 365 license for every user on their computers. We just want Office installed on the server as for 'local' use only by the administrator.

    Please correct me if I'm wrong!

    Thanks.

    -Samir

    0 comments
  4. Anonymous
    2015-12-20T09:48:01+00:00

    Hi Samir,

    I would like to confirm if you encountered the error message as this KB mentions: https://support.microsoft.com/en-us/kb/2810023.

    If so, as the KB mentioned, the reason is that we can't install Click-to-Run versions of Office programs or suites on a server that's running Remote Desktop Services (formerly known as Terminal Services). The workaround is installing Office with Shared computer activation.

    Please let me know if we can discuss further.

    Thanks,

    Iris

    0 comments