Part 1- Building VDI using Remote Desktop Services (RDS)

Below is the figure of the infrastructure setup:-

By using Hyper V R2 and SCVMM 2008 R2, I have created the following Virtual machine

In this setup, I'm going to use Windows 7. You can setup client VM running on
○ Windows 7 Business, Enterprise or Ultimate,
○ Windows Vista with SP1 - Business, Enterprise or Ultimate,
○ Windows XP Professional with SP 3

I have tested on these above operating system and it work like a charm. If you would like to know more about the different between Personal and Virtual Desktop Pool, To make it more interesting, VDI01-Win7.ms4u.info is set to Personal Virtual Desktop and assigned to VDIUser1 which only use Office2007 whereby the Virtual Desktop Pool will use Office 2010 (Beta).

The Client VM name on the Hyper V host should be FQDN and identical as the computer name in the VM.

Example: VDI01-Win7 is the computer name

VDI01-Win7.ms4u.info is the FQDN

For easy and faster deployment of the VM, I using VMM feature called "Rapid Provisioning Virtual machine using Template". For those who are not familiar with this feature,
Let start to look into initial configuration:-

MS4UDC - Domain controller

You may want to take note on some criteria to deploy personal virtual desktop . Your Active Directory need functional level running in Windows 2008. To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, your functional level for AD DS must be set to Windows Server 2008 R2.

Task 1:- Create user account for VDI

1. Log on to MS4UDC VM
2. Go to Start > Program > Administrative Tools > Active Directory Users and Computers
3. Right click Users container , select New and User
4. Enter username :- vdiuser1 and click Next

5. Enter password :- P@ssw0rd , uncheck "User must change password at next logon" and click Next
6. Click Finish
7. Repeat step 3 to 6 to create user account for vdiuser2 and vdiuser3.

Task 2:- Create a group for VDI

1. Right click Users container , select New and Group
2. Enter the group name: vdigroup with Group scope:- Global and Group type: Security and Click Ok button

Task 3: Assign user account to VDI group

1. Right click Vdigroup and select Properties
2. Click on Members tab and select Add button
3. Enter vdiuser1,vdiuser2 and vdiuser3 and Click Check name
4. Click Ok button
5. Click Ok button to close the vdigroup properties

This is the last post for 2011 :-) Stay tuned for more updates on an Upcoming Year and HAPPY NEW YEAR 2012 :-)

Cheers !!
Jagadeesh

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...

My IT Blog

Search This Blog