Previously, the licensing token was always saved to a specific folder on the local computer and was associated with that specific computer. Software assurance provides something called roaming use rights which allows for the terminal services setup that you are planning. It prompts with a message that this version can't be installed on a terminal server. This option is not workable if the intent is for users to be able to access from anywhere as every single client device needs to be licensed for Office. Thank you for assistance and support. Note: To insert a screenshot, please click on Use rich formatting and select the Insert Image icon.
This is done by the user logging into O365 and installing from the click to run. Regards, Ethan Hua Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. This prevents Office 365 ProPlus from trying to activate during the installation. Please refer to the link below about the steps: If this is not the situation, please share a screenshot about the error message with us. Make sure the application you want to install is supported in a Terminal Services Environment, and on your specific version of Windows Server.
Thank you for both of your comments, I wouldn't have found the resolution to this as fast without your input. I argued with them that the microsoft site states Enterprise plan they offer is stated as offering it but they refused to budge. Once you hit 5 activation you will not be able to activate anymore until the admin can manually remove the devices. These three things cost me a day in deployment. Currently there is 2010 on the server. It's up to you to keep track and to ensure you have the proper licensing.
I am looking through articles Microsoft gave me but I don't see one specifically for Office 365 non retail versions. For your convenience: Regards, Steve Fan TechNet Community Support Please mark the reply as an answer if you find it is helpful. This cloud-ready, scalable product supports deployment through Microsoft Azure and Amazon Web Services. Office needs to be able to write to that folder location. This includes situations where you run the software on your local device or access the software installed on another device like a server. Dear Office 365 Team, Can you please advise.
It's in Public Preview now so it's free and the cloud deployment comes with a Windows Server 2012R2 + Office image. This prevents Office 365 ProPlus from trying to activate during the installation. Office will automatically activate and configure the applications as needed. It has a Allow the licensing token to roam. Do you think it is possible for the RemoteApp executed by users on their desktop to be installed on our server and to access network files as fast as if they were stored locally? I am going to be moving the customer to Office 365, then will migrate the organization to their own private cloud.
Local prior testing assures if a test environment does not exist, using virtualization helps. When a copy of Microsoft Office is installed on a desktop, the primary user of the desktop may remotely access and use the software from any other device. Unlike your scenario listed in the blog, I will only have one server as opposed to 3. It was licensed per end-user device 60 thin clients or thin-client desktops. Is there anything else I need to consider before deployment? You can request access via Azure portal and give it a try when you will get accepted into the Preview program in a couple of days. So not sure what's up with that yet.
Clients can be either Windows 7 or 8. We really only need Excel and Word to work on these servers. For example, if a customer is using a device licensed for Microsoft Office Standard 2016, they may access Office Standard 2016 running on a server. . I was caught up in another project last week.
I read recently that is no longer an officially sanctioned option so you have to install using the Office 365 downloaded media and use shared computer activation. What do others do for a remote desktop solution when you dont have volume licensing. Often when a removal is done, a restart might be required, in such a case a subsequent install attempt without restart might not go forward as it may still see ref to prior version that it can not uninstall as it has already been, awaiting a restart. I think I am good to go now. The Microsoft website that I found was about installing Office 2016 on Windows 2012R2 and not later versions. Remember that the installation is run in silent-mode, that means that there will be no indication that Office is being installed. It me see up the Server Manager deployment and things start breaking.