- #Add registry key for chrome remote desktop curtain full
- #Add registry key for chrome remote desktop curtain license
- #Add registry key for chrome remote desktop curtain windows 8
Some of my session hosts connect fine and other don't.
#Add registry key for chrome remote desktop curtain windows 8
I have been trying to connect with Windows 8 and Windows 7 clients as the domain\administrator account. The GW servers RAS/RAP policies are set to be pretty open for testing with using any port, any network resource, and Domain Users and Domain Admins listed. I've checked that both WA servers are listed in the TS Web Access group. Lastly each group/user that has access to RDS is listed in the Remote Desktop users.
#Add registry key for chrome remote desktop curtain full
Also for WMI Root\CMIV2\TermicalServcies Security has the domain\Ts Web Access group set with full perms. With full perms for the Access and Launch/Activation. I have also verified that COM Security has the domain\TS Web Access group set On each session host I have verified that the *inucoda and *ucoda certs are installed and the internal CA and Comodo CA/Intermediate CA is installed in the correct stores. Security is set to only use NLA, SSL 1.0, High. I can confirm that the * cert is used for the WA part and all other parts are reporting the *, all with no errors or warnings.įor each session collection only one session host is used with no apps, (just RDP). The *. cert is used for the CB SSO, CB Publishing, and GW while the *. cert is used for the WA.Īll session hosts have been configured to use the *. for their RDP sessions. We also have a wildcard *. created by our inside CA. (This is not a public IP, we require you be on our VPN to be able to access the IP).įor certificates we have a Comodo issued wildcard of *. with the corresponding Comodo Root Trust and Intermediate Certs. Up steam from our inside Windows Domain at our ISP level there is a DNS entry of and it points to the NLB IP of the WA NLB Cluster.
The WA servers are also in a NLB Cluster with an extra adapter and a DNS of pointing to the NLB IP. Also both GW servers were added to the GW Server Farm part of the the There is a DNS name of that points to the NLB IP of the GW Cluster. The GW servers each have the NLB role installed with an extra network adepter for NLB use.
Both LIC servers have been added to the RDS deployment properties.
#Add registry key for chrome remote desktop curtain license
On each CB server there is a RDS License server role installed with CALs installed and activated/registered. There are two entries of this each with one of the two IPs of the CB1 and CB2 servers. They use a SQL Server 2012 Fail-over cluster that is on a separate set of VMs for their database and the DNS is configured as round The connection brokers have all servers used including session hosts added to the server pool and are configured in HA mode. My outside domain that you can get to from the web is is an network that is the Domain that all servers are joined to via 2 Domain Controllers splits between each ESXi Host. I have 6 servers a VM's split evenly between 2 ESXi 5.1 Hosts.ġ. Below is my setup.Ī full RDS environment using all Windows Server 2012 Data Center. I also cant find anything useful in the event logs about this. I have compared them and can't findĪ single difference. This is only happening to some of my session hosts and not all. This one is driving me NUTS! The problem itself is when I go to connect to a session host using a web access server I get the error in the title.
0 kommentar(er)
