I'm trying to set up Microsoft Office for about 50 users on an RD Session Host within an EC2 instance. I've checked out AWS License Manager, but it doesn't quite fit my needs, and WorkSpaces isn't an option for other frustrating reasons. I'm considering using Office 365 installed in Shared Computer Activation mode. Has anyone had experience with this setup or any suggestions?
3 Answers
You should be fine if you use the shared installer tool, assuming all users are properly licensed. Each user just needs to log in to Office 365 once after installation to verify their license; no product key is necessary. The setup is a bit different from standard installs, but the instructions are pretty clear.
Actually, you'd be violating Microsoft’s licensing if you did that.
Unfortunately, you can’t run Microsoft Office on AWS unless you're using an AMI provided by AWS or deploying it through WorkSpaces due to licensing restrictions from Microsoft. If you own a 2019 version of Office with perpetual licenses, you could run it on a dedicated host without violating Microsoft’s policies. Another option to consider is using Workspace Pool to run M365 for multiple users on shared WorkSpaces.
I was worried you’d mention that. I already have a self-managed Active Directory, and switching to another would just add unnecessary costs. It’s a bummer that I can’t retrofit Office onto my existing session hosts.
If you're looking for a straightforward option, you could set up a Windows Connection Broker with several EC2 instances. I’ve seen this architecture support over 1000 users without issues.
My main concern is the licensing for Office though. Is it alright to run Office 365 with the desktop apps on a shared EC2 instance?
Thanks for the clarification! I’ve never installed O365 before—can I just log the users in for them so they don’t have to deal with it? I want a super simple terminal server experience.