Update: Microsoft Ignite Pre-Day Sessions are live with Speakers listed

January 28, 2015

Update: Even if the speakers aren’t listed in the full catalog yet, the speakers for the Pre-day sessions are. 🙂

From the registration page you can find the speakers of each pre-day session. I have updated the Pre conference session list below.

If you have registered for Microsoft Ignite or still work at getting approval to attend. You now have the opportunity to improve your chances and further extend your Ignite experience.
Today a list of 17 all day Pre-Day Sessions have been posted.
These sessions give you an opportunity to really dig in to a topic and retrive knowledge and insights of noted industry experts.

Pre-Day Sessions will take place on Sunday, May 3, from 9:00am – 5:00pm and are an additional investment of $500. The Pre-Day Session fee includes a full day of dedicated class time with a noted industry expert, lunch, and materials (if applicable).

C’ya in Chicago!

Advertisements

Windows 10 as primary OS here we go.

January 28, 2015

Today i will convert my primary PC to Windows 10. I have been playing around with it since the Preview and been thinking of making the shift for some time now.

I will use the Disk2vhd utility to create a VM of my old install so that I can get access to the old OS if i need to.

Disk2vhd is really easy to use, download the software, unpack and execute the disk2vhd.exe file.

image

Select the drives you need. Default format is Vhdx. If you want to upload it to Azure un-check the box to create a vhd. Since I will run this on a VM on my new Windows 10 install I keep the defaults.

image

Click Create

Disk2vhd takes a snapshot of the disk and starts to build the vhdx.


Nesting Hyper-V Part 2

January 9, 2015

In the first part of this series of blog posts I explained how to nest Hyper-V on Hyper-V.

This time we will nest Hyper-V on a VMware ESXi. This will add the functionality to have running VM:s on Hyper-V. This solution is off course not supported by either VMware or Microsoft so do not attempt to do this in a production environment. The use case for this install is to learn the beauty of Microsoft Cloud OS or perhaps install an environment to prepare for a certification exam that involved mutiple Hyper-V installations like the Microsoft Virtualization exam 74-409 covered in the MVA Course Server Virtualization with Windows Server Hyper-V and System Center, or any of the System Center Private Cloud exams 70-246 and 70-247

Create a bootable USB flash drive for Vmware ESXi

First you need to register and download the free Vmware ESXi

Once you have downloaded the ISO you either need to burn it to a CD or as in my case create a bootable USB drive and install the hypervisor.

I use the Netbootin tool which I find really easy to use.

clip_image002

Choose DISKIMAGE and browse to the location you have downloaded the ISO and click OK

clip_image003

Click Yes to overwrite the menu.c32 file

clip_image004

Click Exit to end the process. If you would like to install ESXi on the same machine click Reboot Now

Insert the USB drive to your machine and install VMWare ESXi from your USB drive.

To be able to take screenshots of the procedure I use VMware workstation. I have always use the ESXi version because I want as little overhead as possible. (The software isn’t free but you get a 30 day trial in case you want to try this on your PC)

Step 1 Install VMware ESXi

If you haven’t worked with VMware products before I made a Step by Step instruction on how to install it.

Select the ESXi standard installer

clip_image006

The installer loads

clip_image008

Once the installer has loaded you will see a screen similar to this showing your hardware configuration.

clip_image010

To start the installation press Enter

clip_image012

Scroll down to the end of the EULA and press F11

clip_image014

Select the disk where you will install ESXi (You can install it on a 1 GB flash drive to save precious storage on your rig)

clip_image016

Select keyboard layout and press Enter

clip_image018

Enter a password for root (Built in Administrator account) press Enter

clip_image020

clip_image022

To start installing press F11 (notice that the disk will be repartitioned)

clip_image024

When the installation is completed press Enter to reboot

clip_image026

When the hypervisor comes back up again you are met with a similar screen.
Make a note of the URL or type it in your browser to connect to the installs.
If you don’t want DHCP or want to configure a static IP address you need to log on using the password you created earlier. Press F2

To skip the configuration skip to the next step

clip_image028

Enter your password and press Enter

clip_image030

Select configure Management Network and press Enter

clip_image032

Select Set static IP address and network configuration and add your IP configuration. Press Enter to apply your settings.

clip_image034

You will be prompted to apply the changes and restart the management network press Y

clip_image035

Step 2 Installing the vSphere client

Open the address noted in previous step and click Continue to this website

clip_image037

Click the link Download vSphere Client

clip_image039

Download the client and install it on your PC (Next, Next,,,Finish)

Connecting to ESXi using VMware vSphere Client.

Enter your IP address and log on using root and your password

clip_image041

When you have logged on you are met by a message stating that the host lacks persistent storage, that is expected since you haven’t configured datastore. A datastore is the place where you place your VMs (virtual machines) and other system files such as ISOs, templates. Datastores are equivalent to Microsoft CSV and VMM libraries.

Step 3 Create a Datastore in the vSphere Client

Click the link click here to create a datastore

clip_image043

Select the disk that will be configured as a datastore.and click Next (If you are using VMware Workstation you will have to add another disk to the ESXi VM and rescan)

clip_image045

Select VMFS-5 click Next

clip_image047

Click Next

clip_image049

Enter a datastore name, and click Next

clip_image051

Select capacity and click Next

clip_image053

Review your settings and click Finish

clip_image055

Your datastore is created and is visible in the vSphere client.

clip_image057

Step 4 Create a VM in vSphere Client and install Windows Server 2012 R2

Click FileĂ NewĂ Virtual Machine (or right click the host)

Select Custom and click Next

clip_image059

Enter the name of your Hyper-V VM and click Next

clip_image061

Select the datastore where your VM will be stored and click Next

clip_image063

Choose Virtual Machine Version 8 and click Next

clip_image065

Select guest OS Microsoft Windows Server 2012 (64-bit) and click Next

clip_image067

Select the numbers of virtual CPUs and click Next (Take into consideration the hardware you are installing upon and the number of Hyper-V hosts you will install)

clip_image069

Configure the VM memory size and click Next (Take into consideration the hardware you are installing upon and the number of Hyper-V hosts you will install)

clip_image071

Add the number of NICs you need and click Next

clip_image073

Select LSI Logic SAS and click Next

clip_image075

Select Create a new virtual disk and click Next

clip_image077

Specify the disk size and click Next

clip_image079

Click Next

clip_image081

Review your settings and click Finish

clip_image083

When the V; is created Right click and select Settings

On the hardware tab choose CD/DVD drive and select the place where you have your Windows Server 2012 R2 media, tick the Connect at power on checkbox and click OK.

clip_image085

Start your VM and install Windows Server 2012 R2

clip_image087

When your Windows Server 2012 R2 is installed make sure you install the VMware tools to enhance the performance of the VM.

Step 5 Nesting Hyper-V on VMware ESXi

If we try to add the Hyper-V role to our installation now we get the following error message.

clip_image088

To trick Windows Server 2012 R2 into believing that it’s install on physical hardware we need to add some parameters to the configuration file.

First we need to shut down the VM.

When the VM is turned off Right click and choose Remove from Inventory. On the Confirm Remove pop up, click Yes (don’t worry nothing will be deleted.

clip_image089

Right click the Datastore where you stored your VM and select Browse Datastore

Select the folder of your VM (as you can see I have a folder called ISO from which I installed the VM to create such a folder just right click and create the folder)

clip_image091

The file we are looking for is the *vmx file. Select the file and click

clip_image093

clip_image095

Once you downloaded it we need to edit the file. I use Notepad ++ since I already have it on my PC (Don’t use Notepad the file is character sensitive and Notepad adds the wrong character set, if I remember correct WordPad does 🙂 )

Add the following rows to anywhere in the file, I add them on the end.

vhv.enable = “TRUE”

hypervisor.cpuid.v0 = “FALSE”

If you are copying the text from the blogpost make sure the “ character is correct or else it will not work.

clip_image096

Save the file and upload it again

clip_image098

Use the same button if you want to upload files like ISOs to the Datastore.

Once the file has been uploaded, Right click the *.vmx file and choose Add to Inventory

Leave the suggested name and click bNext (Having mismatch between the VM and the filenames can be a real pain when troubleshooting)

clip_image100

Click Next

clip_image102

Review the settings and click Finish

clip_image104

Before we start the VM we need to add the Intel® VT-x/AMD-V™ instruction set.

Right click the VM and choose Settings, click the Option tab and select CPU/MMU Virtualization and change the option box from Automatic to Use Intel® VT-x/AMD-V™ for instruction set virtualization and Intel ® EPT/AMD RVI for MMU virtualization click OK

clip_image106

Now start the VM and install the Hyper-V role 🙂

clip_image108

In my next blog post I will start installing the Windows Azure Pack on my lab servers.

The install will consist of two VMware ESXi hosts with three nested Hyper-V hosts on each. If you want to follow along make sure you have your nested Hyper-Vs patched and ready.