It does this by encapsulating Remote Desktop Protocol (RDP) traffic over an
HTTPS tunnel. This is a big advantage, because without TS Gateway, you would have
to open up port 3389 for RDP connections. This has the added benefit of eliminating
the need to implement a VPN solution if the VPN connection is used only for accessing
terminal servers. You can configure policies to restrict access based on local user groups
or Active Directory resources to which they can connect, or even domain membership of
the client computer. You can even control whether device or disk redirection is allowed
and whether smart cards are required for authentication. TS Gateway is tightly integrated
with Network Access Protection (NAP), which allows you to limit access further,
based on NAP policies. For even more protection, you can place TS Gateway servers in
your private network by implementing a Microsoft Internet Security and Acceleration
(ISA) server in your perimeter network.
NOTE TS Gateway gives you access to any RDP-enabled service so you can use this to connect
to your terminal server, as well as your clients, with Remote Desktop enabled.
Since it relies on other services to provide some of its functionality, TS Gateway requires
the following:
?–? Windows Server 2008 server
?– Remote Procedure Call (RPC) over HTTP Proxy service
?– Web Server (IIS 7.0)
?– Network Policy Server
?–? SSL Certificate
TS Gateway Architecture
Depending on the number of users and servers you need to support, many of the previous
services can sit on the same server or multiple servers.
Pages:
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342