Migration of Virtual Server to Hyper V

I've performed migration from Virtual Server 2005 to Hyper V.
Dell Poweredge 2950 is used to host Hyper V.

Previously VM is running on Virtual Server 2005 whereby it is not a suitable product to host VM. The limitation of Virtual Server 2005 R2:-

a) Limited 1 processor with only 25% utilization.
b) Running on top of host operating system. This has caused VM running in Virtual Server is consider slow and take a lot of resources.
c) Only host 32x platform VM
d) No snapshot
e) Max 3.6 GB RAM

With the migration to Hyper V, the performance of the VM has increase. Some important features of Hyper V:-
a) hypervisor based virtualization. Child VM is directly access to the resources
b) support 32x and 64x platform VM
c) Snapshot is included.
d) Can support more than 3.6GB RAM per VM
e) Fully utilize processor. Up to 32 logical processor is supported.
and a lot more...

Read the experiment lab result (Hyper V, Xen, Vmware) from
http://virtualizationreview.com/Articles/2009/03/02/Lab-Experiment-Hypervisors.aspx?Page=1

Cheer Hyper V !!!

Courtesy : MS4u

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

DNS Scavenging.

DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997. Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy. Remember that old test server that you built two years ago that caught fire before it could be used? Probably not. DNS still remembers it though. There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening. Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying. What happened?" This post should help us figure out when the first issue will happen and completely av...

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