Remote Desktop Web Access and Gateway - the way they work together
as far remote web access component of remote desktop services in r2, need gateway service enable it? or can without running gateway component? in other words can have users go specific url points specific terminal server/remote desktop server , web interface show let's 3 icons - full remote desktop la old ts, virtualized app e.g. word or full virtualized workstation image - vdi - e.g. windows 7?
hi,
yes, can use remote desktop web access access rdsh, remoteapp, or vdi pool without using rd gateway. name/ip address of each server associated with an icon must resolvable reachable client pc. rdwa mechanism tell client pc server/remoteapp/pool/etc. should try connect to. example, let you have three icons in rdwa like mentioned:
1. desktop -- rdsh server named rds01 ip address 10.2.2.30 (this server rdwa server)
2. microsoft word -- remoteapp runs microsoft word 2007 located on rdsh server named rds02 10.2.2.31
3. vdi pool -- connects virtual desktop pool consisting of 2 vms: vdi01 10.2.2.40 & vdi02 10.2.2.41
if logon to remote desktop web access pc within same local lan of rds/vdi related servers, when client pc attempts connect server able resolve the name reach server's ip address.
the situation different if client pc attempts same thing home using internet. in case have several challenges. first need way them access rdwa server perhaps open port in firewall , create public dns record that. @ point user able logon rdwa page, however, if try use 1 of icons not work because a) server name not resolvable and b) ip address of server unreachable (since private address).
now, there variety of ways potentially solve without rd gateway, example, give of servers public ip addresses/public fqdns and program firewall forward necessary ports internal ip addresses. or perhaps assign custom tcp ports each server , program firewall forward them appropriate internal ips using port address translation, etc. way have outside users connect via vpn, able resolve names reach ip addresses of various servers. can see how things complicated.
if require access local lan or have relatively simple environment then rd gateway (or vpn) may not needed.
thanks.
-tp
yes, can use remote desktop web access access rdsh, remoteapp, or vdi pool without using rd gateway. name/ip address of each server associated with an icon must resolvable reachable client pc. rdwa mechanism tell client pc server/remoteapp/pool/etc. should try connect to. example, let you have three icons in rdwa like mentioned:
1. desktop -- rdsh server named rds01 ip address 10.2.2.30 (this server rdwa server)
2. microsoft word -- remoteapp runs microsoft word 2007 located on rdsh server named rds02 10.2.2.31
3. vdi pool -- connects virtual desktop pool consisting of 2 vms: vdi01 10.2.2.40 & vdi02 10.2.2.41
if logon to remote desktop web access pc within same local lan of rds/vdi related servers, when client pc attempts connect server able resolve the name reach server's ip address.
the situation different if client pc attempts same thing home using internet. in case have several challenges. first need way them access rdwa server perhaps open port in firewall , create public dns record that. @ point user able logon rdwa page, however, if try use 1 of icons not work because a) server name not resolvable and b) ip address of server unreachable (since private address).
now, there variety of ways potentially solve without rd gateway, example, give of servers public ip addresses/public fqdns and program firewall forward necessary ports internal ip addresses. or perhaps assign custom tcp ports each server , program firewall forward them appropriate internal ips using port address translation, etc. way have outside users connect via vpn, able resolve names reach ip addresses of various servers. can see how things complicated.
if require access local lan or have relatively simple environment then rd gateway (or vpn) may not needed.
thanks.
-tp
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment