This morning a new beta of the Microsoft Assessment and Planning toolkit has been released and now it is version 9.0
This beta release of the MAP Toolkit helps increase the agility and cost effectiveness of deploying the latest Microsoft technologies. It also enhances usage tracking to include accounting for Remote Desktop Services as well as Server and Cloud Enrollment licensed deployments. MAP 9.0 beta additionally helps organizations assess their environment for Office 2013 and Office 365, track usage of Windows Server 2012, Lync Server 2013, SharePoint Server 2013, Exchange Server 2013, System Center Configuration Manager 2012, and SQL Server 2012. The Windows Azure assessment report has also been updated to include the latest Azure sizing.
I have upgraded my 8.5 to 9.0 Beta
and when going from the 8.5 to 9 you can upgrade the database, if you have a MAP version 7 there is no possibility to upgrade to 8.5 or 9.
If you want to get the beta you can sign up at the connect site at this link.
Yesterday I was at a customer and working on configure their off site Hyper-V cluster. I was setting up live migration settings to be able to do shared nothing live migrate the VM´s between the data centers. I was setting up kerberos authentication and also delegation in the active directory but did not think of the 10 hours (600 minutes) time that a kerberos ticket could live and got some errors regarding constrained delegation, as it says if reading a bit more carefully in this technet page on how to configure live migration outside of clusters :”A new kerboros ticket has been issued. “, I did not think of this at first and checked the hosts settings and the active directory objects twice but it did not work and I did not think of the time…. If you want to purge the kerberos tickets you can use the klist command line tool.
Well during the error search I had to test to do a cold migration from SC VMM between the clusters and that looked like no problem at all. It should also be said that both clusters was configured with the same logical network, vm networks, logical switch and uplink so it was the same conf! SC VMM have been updated with the latest CU 4.
When the VM had been migrated i started it and tried to ping the IP address but got no response.. strange I thought, looked in VMM on the properties on the VM and it said that the network card was connected:
But still inside the VM it said not connected,
And then going into the Hyper-V manager and looking at the VM´s properties from there I could also see that it was not connected. I did a VM refresh also in VMM but it did not change the connection status on the VM object to reflect the status as the screen dump below from the properties in the Hyper-v Manager:
Once I connected it to the (logical) virtual switch on the host with Hyper-V Manager it started to respond to ping of course.
I will continue to exam this further and maybe it has been fixed in the VMM 2012 R2.
Today Microsoft Press released a free book about the features in Windows Server 2012 R2 written by Mitch Tulloch and the Windows Server Team. The book goes through the new features in the latest release and gives you as an IT PRO an oversight and quickly get familiar with the different areas of improvement from the 2012 to R2.
If you plan to do a migration and just happens to be one of the lucky guys that have a Netapp box with Data ONTAP 8.2 in Cluster Mode in your VMware environment you can use the MAT for shift that can be found on the gallery. It utilizes the NetApp Data ONTAP PowerShell toolkit and the features in the Netapp storage that converts the vmdk files to vhdx right in the storage and boy do that save migration time as you do not have to move loads of data for your large VM´s over the network and then convert them at the target. As the Netapp software is so intelligent it does not write over the old data and you can quite easily go back if you find any issues after the migration.
I got an error when running it though and it seems that it does not work so good with the partition on the gen 1 virtual disk.. It appears that when I have created my virtual machine with the Convert-WindowsImage.ps1 script that only creates one partition the row in the script that checks for $partitions.length fails and I could not get it to continue but when I commented that away I got my first conversion on the way
And here you can se in the PowerShell ISE my alteration
Now I am sure that John and his team will work and distribute new versions with correct error checking and I am truly glad that they have released this so I could test it right now anyway !!
Here is my VM in generation 1
And here is the converted VM,
And here you can see that during the conversion that I have two disks attached to my server and that the one at the bottom has got some new partitions for the gen 2 UEFI boot process
Happy converting and making generation 2 VM´s your standard in Hyper-V
Also as in Issue 15 there was stuff left after a canceled or failed migration
One thing that could have been a wish was that they in this UR would have added the Windows 2012 R2 as an operating system, you can run Windows 2012 R2 as virtual machines in your 2012 Hyper-V but not assign the right OS on the properties on the VMM 2012 Sp1
In Hyper-V this does not have an impact for the successful boot as in VMware VM´s where you set the best matching OS for the boot process to work flawlessly. In Hyper-V it uses the same BIOS for all your VM´s and this list is something for VMM and the database.
Now when the evaluation VHD´s have been updated with the release of the System Center R2 that was released last week I have updated my download script so you easily can get all the files at a convenient place with PowerShell and the BITS engine.
So as everyone else (at least an ITPRO with some dignity and self respect) I have started to download the System Center 2012 R2 as it was released just some hours ago! The link appeared on my technet subscription page about 1 PM in Swedish time
I started to Install the VM for my VMM and of course I created it as an Generation 2 VM on my Hyper-V R2 host.. In the preview, VMM could not manage gen2 VM´s but now we will see about that. Before installing VMM I had to download and install Windows 8.1 ADK and an SQL server.
And then when I had an successful installation I wanted to add at least one Hyper-V server, the funny part here is that I have activated Hyper-V on this Windows 2012 R2 and why it is saying unknown hypervisor beats me . Fortunately I could proceed to add the host
And then I wanted to check the Gen2 VMM server I had created and see if it was viewable in the VMM console and also the system volume could be expanded when the VM was powered on (in earlier versions of VMM that has sometimes been a nono for example with VM additions )
As you can see there is no possibility in the VMM console to shrink the disk so there I have to use the Hyper-V Manager.. ( I have tried to enter a lower value but the gui won’t allow me to do it) So much for one place for all management.. In the following screendump you can see the option to shrink the storage from the Hyper-V manager wizard.
And as you remember one of the new fine features in the Hyper-V R2 was the full feature RDP access to the VM through the VMbus, why has that not been implemented in the VMM??
This old vmm viewer reminds me of the VMM 2008 with no additional features that I get in the Hyper-V Virtual machine connection..
I will continue to explore the VMM 2012 R2 and there might be some more blog posts coming and until then, good luck in your deployments
As it is a best practice to convert your VHD´s to VHDX I wanted to do that with SCVMM 2012 Sp1 also. It is a small detail that you need to be aware of when doing it in the VMM console, it does not remove the old VHD file from the datastore and in the GUI it is no checkbox for that either. This is the case for both VMM 2012 SP1 and R2 Preview. And if you start converting several VM´s VHD´s there is a possibility that your datastore will become full quite fast and that is not so good!
And on the folder where the virtual harddisk resides you can see that the vhd still exists..
In the PowerShell cmdlet Convert-VirtualDiskDrive there is a parameter -deletesource that removes the VHD once the conversion has completed
So I have made a PowerShell function if you want to convert all your VHD´s on the virtual machine.
Convert all the VHD´s to VHDx
The gui does not delete the vhd disks after conversion