Virtual Machine Manager 08 R2 and Citrix XenDesktop.

Hi
I have VMM08 with Citrix XenDesktop.
Yes, We have in our company this infraestructure. There is a few around the world ;-).
I migrated VMM08 to VMM08 R2 , so CitrixXendestop was down.
I upgrade the VMM08 R2 agent.
I reboot the CitrixXenDesktop Server
I reconfigured the options in the farm (view picture).
And everything starts to run again.


sANTos

Windows Serve 2008 R2. Not Activate Server if you have a VM

hi
I have a VM with Windows Server 2008 R2.

If you delete the machine, and you copy de .vhd file you need to activate again the machine.

You need VMM08 or Export the VM with the Hyper-V MMC.

When you export the VM, you save everything and you save inside the folder:
a config.xml file
a .reg file.
You can edit these files, and rename the options. So you can use like a template to import new machines inside your HYper-V and you dont need activate the Windows Server 2008 R2.

sAnTos

VMM 08 R2

Hi





We can download VMM 08 R2 from MSDN and TechNet subscription.





I am going to test it.





I will write something about the news in VMM08 R2

Move SCVMM database

Hi

We have a SCVMM 08 in a VM.
We have the Database in a old serve. we need to move it to the new server.

I was searching to do it with a few steps.

I founded this link:
http://social.technet.microsoft.com/Forums/en-US/virtualmachinemanager/thread/e3a76bb7-e769-482c-9135-49896d764eb9
The steps:
1) Backup the database by going to Administrator Console, Administration Page, on right hand side select "Back up Virtual Machine Manager". This will create a SQL backup (.bak) file on your specified location.
2) Uninstall the server
3) Install the server and now point it to the new SQL server location in the install wizard.
4) This will create new database
5) Run scvmmrecover.exe to recover the data from SQL backup (.bak) file created above into the new database


There is a SCVMMrecover script aswell.

I am going to use the link. I will write my experience in the next post.

Santos

Move VMM08 Virtual Server. Export and Import Hyper-V Machine.

Hi again


I have many VM in our infraestructure.
I can move the VM with VMM08 Server.
Note: See previous post. If I have the same hyper-v version I can move all machines. Otherwise, I can only move the stopped VM from one host to other.

But I had a problem.
My VMM08 is a VM in an hyper-v server.
I need to move it.

I tryed to moved with itself. Ofcourse I got an error because the server saved the state and give me an error. I knew it. But I did it to catch this error.




So, What is the solution?
The solution is very easy.
If you don't have VMM08, you need to use the Export and Import options in Hyper-V console.
Thus, you don't miss the NIC for example. If you set up a new machine with the .vhd file, the hyper-v server understand this machine like a new server. You need to set up the ip address and you need to activate the Windows again.

The Guy's Weblog explain everything very well:
http://blogs.msdn.com/virtual_pc_guy/archive/2008/08/26/hyper-v-export-import-part-1.aspx


Santos

VMM08 and vmms.exe version

hi again
Following the previous post.
I updated the vmms.exe file, thus I moved the stopped VM, the running VM, the saved VM without problems.


Moving a running VM. (Yes, It is quick migration (Windows Server 2008), so the machine stops 10-12 pings). I will test this machine in a Windows Server 2008 R2 with Live Migration soon.


Moving a Stopped VM.

NOTE: If you update the hyper-v version (vmms.exe file), you must close the vmm08 console. After re-running the mmc console you must refresh the servers to get the new update. Otherwise you got the "unable to migrate..." error.

Santos

VMM08 and Unable to migrate

Hi again




We have an Hyper-V environment with 46 VM.
We have VMM08 to control them.

We try to move VM from a host to another an I got this error:


Unable to migrate the virtual machine sw2k8av because the version of virtualization software on the host sw2k8dtc01.cartv.int (6.0.6001.18125) does not match the version of virtualization software on the source host (6.0.6001.18221). To be migrated, the virtual machine must be stopped and should not contain any saved state

If you look for the vmms.exe in the c:\windows\system32 directory:


The vmms version is different.
The guilty?
The Microsoft update.
One machine had the update service up, the other one it had'nt.
So I need to update the both machines.

NOTE: I refresh the vmm08 mmc in the client. If you won't do it. The error continues, even you had upgrade both hyper-v servers.

You can read more information :(spanish link)
http://blogs.technet.com/davidcervigon/archive/2009/04/01/otra-de-parches-para-hyper-v-marzo-2009.aspx

Santos