my personal blog about systemcenter

All posts in Unsupported

Enabling AzureStack test enviroment using Nested Hyper-V

Categories: AzureStack, Hyper-V, Nested, Unsupported
Comments Off on Enabling AzureStack test enviroment using Nested Hyper-V

So with preview software the 2nd thing to do is go down the unspported/untested path

So after baremetal deployment on a few different host we move on to do nested AzureStack install , this is to enable faster deployment and rollback when we break something on purpose to test.

But always follow support guide lines for testing and use a dedicated phsycial machine , (we does this on mutiple other install in our testing setup)

Time from VM creation to AzureStack running 2 hours 15 minutes Smile

NOTE : Do not count this as stability testing always use supported hardware for that

So say Hello to our Little VM

image

16 Cores , 256Gb Memory , 5 drives at 300G

Invoke-WebRequest https://raw.githubusercontent.com/Microsoft/Virtualization-Documentation/master/hyperv-tools/Nested/Enable-NestedVm.ps1 -OutFile ~/Enable-NestedVm.ps1

~/Enable-NestedVm.ps1 -VmName “STACK10”

Enable it for nesting Hyper-V

image

Install a Windows Server TP4 with US locales

image

For now GUI only (Sorry Snover)

image

And we can see all our drives

image

Add a static IP address and add DNS/Gateway for access to Azure Active Directory

image

And rename to the next stack install Smile

image

I prefeer to online the drives and initialize them

image

image

Time to jump to Azure Active Directory and create a tenant admin user

image

Extract the 9GB file and run the Azure Stack Installer

image

This leaves us with a few files Smile

image

Add local credentials , and verify that all prereq are met , note the space warning is not seen on bare metal installs , need to see if its because the drives are initialised but everything is fine for install

image

Sign in with the Azure Active Directory Admin user

image

And accept the AAD

image

And we are ready to install

image

Installer is a very very cool powershell scripts series that does everything for us , it reboots a few times but signing on gives us the progress bar

image

First off is creating a domain , and joining the host to it

image

After that a Virtual Disk is created through storage spaces

image

And 2 hours later we are done Smile

image

And ready to roll

and while we are playing we might as well dedupe it

image

Smile , not really fair as there are many other installs on the same host but still fun Smile

Hyper-V 2012 R2 VLAN Blues

Categories: Broken, Hyper-V, Unsupported, Virtual Machine Manager, VMM, Windows Server 2012 R2
Comments Off on Hyper-V 2012 R2 VLAN Blues

clip_image002

We have been building another Hyper-V platform and started with the management cluster , this will just use standard switches so we created a team and a Management Fabric network on that

clip_image004

We then set a VLAN for the VM’s , but no matter what we did it didnt work , looking at switches showed that the MAC address was in VLAN 10 no matter what we did

clip_image005

After digging around we looked at the network interfaces , and we had set VLAN 10 on the nic used for the Hyper-V Switch , so no matter what we set on the VM everything was forced to VLAN10

So we removed the network , set the default adapter for ManagementVM and then everything was working as designed

So its friday so we can laugh at ourself , DO NOT set a VLAN on Hyper-V port 🙂


Protecting Windows 2003 Workload Hyper-V DPM 2012 R2

Categories: 2003, Broken, Data Protection Manager, DPM, Hyper-V, Unsupported
Comments Off on Protecting Windows 2003 Workload Hyper-V DPM 2012 R2

So far one of the big issues with Data Protection Manager 2012 R2 is the lack of support for Windows 2003 Workloads , Yes 2003 is close to slipping out of patching and support but NOT as of writing , so people still need to protect their workloads.

If people are still on 2003 there is a reason , ISV being annoying , workloads being retired and 100 different options so its critical that we are able to protect it.

So if you plan to upgrade to 2012 R2 consider the impact of the 2003 servers , either leave the 2003 workload on a downlevel DPM server , or plan to upgrade to use Hyper-V integration

image

Trying to add a older agent result in Error 307 and is unsupported.

image

And trying to browse the 2003 agent says the same , dont work and isnt supported

image

But through the Hyper-V integration we can select our 2003 VM and add it to a protection group

image

At least we can add the server to a protection group

image

And after a few minutes we can see the 2003 server being protected through the Hyper-V integration

image

And from a recovey point of view we recover the whole VM

image

And browse down though the VHD and select single files to recover.

So we can protect 2003 servers if the workload is on Hyper-V and we dont need transaction backup SQL/Sharepoint/Exchange.

So its better than nothing but not much , hopefully Microsoft will reverse on this and add 2003 support to Data Protection Manager 2012 R2