I believe in Hyper-V!

Adding Hyper-V host to VMM 2012 RC that is in Perimeter network (DMZ)

In this post I would like to describe how to add Hyper-V host to Virtual Machine Manager 2012 RC when host isn’t in a trusted domain. In this scenario I ‘ll add Hyper-V host which is in Perimeter network.

To do that you must meet all requirements.

Step 1.

First you need to install VMM Local Agent on Hyper-V host just like in the picture below.

agent

agent1

Step 2.

Go to your VMM 2012 RC Server, open Console –> VMs and Services –> right click on selected container –> Add Hyper-V Hosts and Clusters and follow procedure.

agent3

Because your Hyper-V host is in the Perimeter network you need to mark that option.

agent4

Fill in all fields. Pay attention to Security file path.

agent5

We are done with the wizard.

agent6

agent7

Our Hyper-V host with guests appeared in the VMM Console.

agent8

Step 3.

The most important thing if you want to connect via Console or via RDP to VM’s through VMM Console is to export Hyper-V server certificate and import to VMM server. How to do that? Follow instructions below.

On Hyper-V server open MMC and Add/Remove Snap-in, add Certificates –> Service Account –> Local Computer. Expand WinRM\Trusted Root Certification Authorities –> Certificates. Export certificate and import to your VMM server.

agent9

agent10

After you import certificate on VMM server you will be able to connect via Console or via RDP.

agent11

Done!

Transferring FSMO roles (How to Transfer FSMO Roles?)

Today I had to transfer FSMO roles from one domain controller to another. In this post I want to explain how to do. First of all I want to explain what is FSMO (Flexible Single Master Operation).

We have a five FSMO roles;

1. Schema – Forest-wide and one per forest.
2. Domain Naming – Forest-wide and one per forest.
3. RID – Domain-specific and one for each domain.
4. PDC Emulator – Domain-specific and one for each domain.
5. Infrastructure – Domain-specific and one for each domain.

If you want to transfer the FSMO role must be a member of the following group:

Capture

In most cases we keep the FSMO role holders in the same DC (domain controller) as has been configured by Active Directory installation process.
The transfer of an FSMO role is the suggested form of moving a FSMO role between DCs and can be initiated by the administrator for some reason or by demoting DC. The transfer process is not initiated automatically by the operating system.
FSMO role transfer initiated by the administrator is very simple, but when you have demoted DC then you have a problem.
The process of moving the FSMO role from non-operational role holder to a different DC is called Seizing, and is described in the Seize FSMO roles to a domain controller article.

You can transfer FSMO roles via ntdsutil.exe command-line or by using the GUI. If you prefer the GUI, you can use the following three MMC snap-in tools:
– Active Directory Schema snap-in (Schema master)
– Active Directory Domains and Trusts snap-in  (Domain Naming)
– Active Directory Users and Computers snap-in (RID, PDC, Infrastructure)

NOTE: You must be logged on the target domain controller. If you are NOT logged onto the target domain controller, in the snap-in, right-click the icon next to Active Directory Schema, Active Directory Domains and Trusts and Active Directory Users and Computers and press Connect to Domain Controller. Select the domain controller that will be the new role holder and press OK.

4

Transferring the Schema Master via GUI.

1. Register the schmmgmt.dll library by pressing Start>Run and typing; regsvr32 schmmgmt.dll and Enter.

2

2. From the Run command open an MMC Console by typing MMC.
3. On the console menu, press Add/Remove snap-in and select Active Directory Schema.
4. Right-click the Active Directory Schema and press Operations Master.
5. Press the Change button and then press OK.

3

 

Transferring the Domain Naming master via GUI.

1. Open the Active Directory Domains and Trusts snap-in from the Administrative Tools folder.
2. Right-click the Active Directory Domains and Trust icon and press Operations Master, press the Change button.
3. Press OK all the way out.

5

6

Transferring the RID Master, PDC Emulator and Infrastructure Master via GUI.

1. Open the Active Directory Users and Computers snap-in from the Administrative Tools folder.
2. Right-click the Active Directory Users and Computers icon and press Operations Master.
3. Select the appropriate tab for the role you wish to transfer, one by one (RID, PDC, Infrastructure),  and press the Change button.
4. Press OK all the way out.

7

8

Transferring FSMO roles from the ntdsutil.command:

Caution: Using the ntdsutil incorrectly may result to loss Active Directory functionality. Be careful!

 

1. On domain controller, click Start, Run, type ntdsutil and click OK. The cmd will appear.

9

 

2. Type roles

10

3. Type connections

11

4. Type connect to server <servername>, where <servername> is the name of your domain controller you want to use.

12

5. Type q and then press Enter again.

13

6. Type transfer <role>, where <role> is the role you want to transfer.
    An example; transfer schema master, transfer RID, and so on.

14

7. After you transfer all five roles, type q and press Enter until you quit ntdsutil.exe.

8. Restart the server.

That’s all for today!

Migrate Virtual Machine from one Hyper-V host to another using Virtual Machine Manager

Today I had to migrate a Virtual Machine from the host on which there is no place to another Hyper-V host and I would like to share with you how it works.

First of all I would like to explain what types of migration have Virtual Machine Manager.

– Quick migration (cluster migration)
– SAN migration
– Live migration and VMware VMotion
– Network migration – This type of migration will be explained in this post.

As always it will be lots of pictures Smile

I this scenario, I’ll migrate virtual machine named vm-appv01 from the host eko-virtual03 to the host eko-virtual05.

Open your VMM Console and choose which VM would you want to migrate. Click Migrate Virtual Machine and the process will start.

1

This is a network migration and we will get this message.

2

Select host on which you want to migrate a virtual machine. In my case it’s eko-virtula05.

3

On the next window choose path for the virtual machine and virtual disk or even better do it when configuring the Virtual Machine Manager.

5

4

Select the available LAN adapter on the new host.

6

At the end of the wizard click Move. If you want to turn on the server after migration to click on
Start the virtual machine after deploying it on the host.

7

Migration process begins.

8

 

After migration is complete and the virtual machine is turned on you need to do one restart because of the new hardware configuration.

9

As you can see through Hyper-V manager or Virtual Machine Manager, whatever, your migrated virtual machine is up and running on a new host.

10

That’s all for today.