Terminal server licensing white paper

In this, part 1 of a two part series on creating a Terminal Services Gateway solution using Windows Server 2008, we went over installing the Terminal Server services and Terminal Services licensing on the Terminal Server, we then configured Terminal Services licensing, then installed the Desktop Experience on the Terminal Server and finally configured the licensing mode for the terminal server. Next time we will finish up by installing and configuring the Terminal Services Gateway and the RDP client. We will then finish up by making the connection from an external location. See you then! -Tom.

We have found this technology to be especially impressive with its ease of implementation, use, and customizability. Rather than spending a huge amount of time and money to recreate an existing Windows application for the web, we're able to support remote users with the existing application immediately. For situations where supporting a few remote users is the primary driver for converting an application (and where the application is not intended to be used as a public website), it is no longer necessary to incur the extra expense of converting this suitable Windows application to a web application. With the savings from not having to rewrite the application, we can add new features to the existing application and make it more powerful for local and remote users without giving up any of the Windows features people expect.

Terminal server licensing white paper

terminal server licensing white paper

Media:

terminal server licensing white paperterminal server licensing white paperterminal server licensing white paperterminal server licensing white paper