- HOW TO SETUP WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES INSTALL
- HOW TO SETUP WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES UPGRADE
Once the permissions are corrected complete the wizard: Turns out that the computer account of the rdcb broker did not have enough permissions to create a SQL database on the specified SQL server: I had a problem at this point as per the following error message. This name does not need to be resolved externally as the gateway servers will take care of that for internet users: DNS records need to be manually created to resolve this name and point to all the connection broker servers. Specify a folder on the SQL server itself that the database files will be stored in and a DNS Round Robin name of the connection broker.
HOW TO SETUP WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES INSTALL
If the SQL instance was running SQL 2012 we would need to install and specify SQL Server Native Client 11. Here Version 10.0 means we are connecting to a SQL 2008 R2 Server. On all the connection broker servers the correct version of the SQL Server Native Client must be installed.
Note that the wizard will create the database itself:Įnter the database connection string as follows:ĭRIVER=SQL Server Native Client 10.0 SERVER= sql_server\instance Trusted_Connection=Yes APP=Remote Desktop Services Connection Broker Database= dbname It is required to store the database on a SQL server that all connection brokers servers can access when using more than 1 connection broker. Make sure you have the connection details of the SQL server that will store the RDCB database. If you have an additional Connection Broker server to be used and it recommended to have more than 1, then right click the Connection Broker icon in the Deployment Overview screen and click Add Connection Broker: Note that additional gateway servers will be added shortly that is not done here:Īdd any additional RD Web Access servers that will be used and complete the wizard: You might want to create an internal DNS zone for this URL if the external namespace is different from your Active Directory domain. over the internet then the URL used for the farm name must be resolvable externally as well as internally. If the farm is to be accessed from outside the corporate environment i.e. From Tasks choose Edit Deployment Properties: Now the rest of the servers can be added to the deployment and various other properties configured. One exception is RD Gateway CAP’s and RAP’s that are managed through the RD Gateway console on the gateway servers. In Server 2012 nearly all of the management of the RDS Farm is done from Server Manager. Server Manager now show you the deployment.
Choose Remote Desktop Services from Server Roles:Ĭhoose Remote Desktop Services Installation:Ĭhoose Standard Deployment as we are building an environment with multiple servers:Īdd one of the connection brokers, the wizard only allows you to add one component server for each role and the rest can be added later: In Server Manager add all of the new vanilla servers to the pool of managed servers and start the roles and features installation process. The configuration wizard will install all of the necessary roles and features on the servers you specify so there is no need to go through them one by one. We also required a SQL server on which to install the connection broker database (this is not required unless you wish the connection broker to be highly available). In this deployment the gateway and web access servers will be running on the same servers. The following are components of RDS and the number of each we decided to deploy:ġ* RD Session Host (1 initially as more will be added once we are finished). The first step is to build the servers that will be part of the farm, that is to install Windows Server 2012 R2 on them.
HOW TO SETUP WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES UPGRADE
We decided to rebuild our RDS Farm completely rather than upgrade the individual components one at a time. Server 2012 R2 improved up this and added more features, specifically the ability to shadow users sessions was the one that got us interested: Server 2012 changed the way Remote Desktop Services (formerly Terminal Services) worked and was managed.
0 kommentar(er)
