Skip to main content

Part 4:- Building VDI using Remote Desktop Services (RDS)


Task 1: Enable Remote Desktop and Add VDIGroup to the local Remote Desktop Users group

1. Log on to RDSRedirect VM with administrative rights.
2. Click Start, right-click Computer, and then click Properties.
3. Click Remote settings.
4. Under Remote Desktop, click Allow connections only from computers using Remote Desktop with Network Level Authentication (more secure), and then click Apply
5. Click on select Users button
6. On the Remote Desktop Users, click Add
7. Enter VDIGroup and click Check name
8. Click OK button to close the Remote Desktop Users
9. Click OK button to close the System Properties

Task 2: Add RDSBroker to the TS Web Access Computer group

1. Log on to RDSRedirect VM with administrative rights.
2. Open Computer Management. Click on Start > Administrative Tools > Computer Management.
3. Expand Local Users and Group and Groups
4. Double click TS Web Access Computer and Click Add button
5. Click on Object Types and Tick Computers and click OK
6. Enter RDSBroker and Click Check name
7. Click OK to close the select Users, Service Account and Group
8. Click Ok to close the TS Web Access computer properties





Task 3: Add RDSRedirect to the Session Brokers Session

1. Log on to RDSBroker VM with administrative rights.
2. Open Computer Management. Click on Start > Administrative Tools > Computer Management.
3. Expand Local Users and Group and Groups
4. Double click Session Brokers Computers and click Add button
5. Click on Object Types and Tick Computers and click OK
6. Enter RDSRedirect and Click Check name
7. Click OK button
8. Click OK to close the Session brokers Computers





Task 4: Configure RDSRedirect for virtual machine redirection mode.

1. Log on to RDSRedirect VM with administrative rights.
2. Open Remote Desktop Session Host Configuration snap in. Click Start > Administrative Tools > Remote Desktop Services > Remote Desktop Session Host configuration
3. Scroll down to RD Connection Broker , Right click Member of farm in RD connection broker and select Properties



4. On the RD Connection Broker tab and click change setting.



5. Select option Virtual machine redirection6. Enter the RD Connection Broker server name: RDSBroker.ms4u.info and click OK



7. Click Yes





8.Click OK

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this...