This type of situation used to be called a “terminal server” session but the official term that Microsoft has been using the last several years is “remote desktop” session. The endpoint can be either a thin client or a full-fledged PC. This type of session simulates a physical desktop. In a remote desktop environment, the users are able to log into Windows Server and fire up a remote desktop session. One question I get on a regular basis is this: “How do I license Office for a remote desktop environment?” Or, in other words: “How do I license my terminal server for Office?” First I’ll explain what type of environment we’re talking about, and then I’ll explain how to license it properly. Update: The following article provides information about how to properly license Office in a remote desktop environment using traditional, perpetual licenses. For information about how to properly license this type of environment using Office 365 subscriptions, see this follow-up post.
