Search results for 'app:weblogs' matching tag 'HyperVServer'

Windows 2012 first look

Anonymous — Thu, 23 Aug 2012 05:00:00 GMT

So if you have a client who has SA on SBS 2011, you already have access (unkeyed of course) of the RTM bits of Windows 2012. I can't find the bits yet on Technet or MSDN, so it looks to me that unless you have access to someone's VLSC, you don't have access yet to RTM bits. All of this appears to be coming out on September 4th, so if you can hold on a little bit more... otherwise download that VLSC Windows 2012 version and start playing with Windows 2012.

Now I'm not convinced in the SMB space that the HyperV 2012 only version (aka the command line) is the way to go. For several reasons. For one, I'm not a command line gal. For two, you'll need a Win8 workstation to control it. For three, when the you know what hits the fan and something happens, I'm just more comfy with a GUI, for four, in the 2012 era you get a One plus Two virtualization rights. I'm still hoping that Microsoft will open up the purse strings and allow those of us with SA rights on SBS 2011 standard to get a copy of Windows 2012 Essentials which will give us a RWA ability as well as extra room to stand up Exchange in a Windows 2012, and SharePoint in 2012 and throw WSUS in there somewhere.

So I've rebuilt my HyperV test box - AGAIN - this time with the final RTM of Windows 2012

hmmmm why does the final RTM have the number in the corner?

So the first thing I do when setting up a new HyperV play box is ... of course.. install the HyperV role and nothing but the HyperV role.

Well okay so the very very first thing I did was enable RDP so I could remote into it from my desktop and be lazy and do screen shots remotely.

Okay so the second thing I do is disable IE ESC on a play/test box. If you need to get ISO's and stuff down on the box, the IE browser is still the fastest way. Don't load up Java and Flash (especially since we just got two updates in the last week) and surf safely and on a play box you should be fine.. and beside this isn't production anyway.

So launch the "UI formerly known as Metro" Server manager and click on Local Server. On the right hand side is IE Enhanced Security Configuration.

Turn this to off

I already renamed this box as "Hyper2012" btw

As you can see, dig under the hood a bit and that "UI formerly known as Metro" looks like the old Server 2008 R2 UI

Now finally go back to the Dashboard

Click on add roles and features

Click Next

Click role based

Remember.. this is in a workgroup, we're not doing anything fancy here, merely a basic 8 gig server.

I'm going to pick the HyperV role and nothing but the HyperV role

Click next next next.

Now we come to the networking. Because this is a simple box with merely one network adapter I'm going to manage and virtual the networking all through the same nic. Normally you'll want at least two.

Click that box and select next.

The next screen is kinda irrelevant if you don't plan to do live migrations. For a play box, click next

Next comes..what I think is the stupidest defaults...

Why these suckers are on the C drive is beyond me

For play, do whatever, for production, stick them on another drive, with NTFS permissions to allow access.

Confirm everything looks good, click install.

And we restart... we we do once we figure out where the restart button is.

Over a RDP window you need to swipe over to the right

Ah yes, swipe to the right and there it is

..up next tomorrow, installing a guest operating system

Windows 2012 first look

bradley — Wed, 22 Aug 2012 05:00:00 GMT

So I've rebuilt my HyperV test box - AGAIN - this time with the final RTM of Windows 2012

hmmmm why does the final RTM have the number in the corner?

So the first thing I do when setting up a new HyperV play box is ... of course.. install the HyperV role and nothing but the HyperV role.

Well okay so the very very first thing I did was enable RDP so I could remote into it from my desktop and be lazy and do screen shots remotely.

So launch the "UI formerly known as Metro" Server manager and click on Local Server. On the right hand side is IE Enhanced Security Configuration.

Turn this to off

I already renamed this box as "Hyper2012" btw

As you can see, dig under the hood a bit and that "UI formerly known as Metro" looks like the old Server 2008 R2 UI

Now finally go back to the Dashboard

Click on add roles and features

Click Next

Click role based

Remember.. this is in a workgroup, we're not doing anything fancy here, merely a basic 8 gig server.

I'm going to pick the HyperV role and nothing but the HyperV role

Click next next next.

Now we come to the networking. Because this is a simple box with merely one network adapter I'm going to manage and virtual the networking all through the same nic. Normally you'll want at least two.

Click that box and select next.

The next screen is kinda irrelevant if you don't plan to do live migrations. For a play box, click next

Next comes..what I think is the stupidest defaults...

Why these suckers are on the C drive is beyond me

For play, do whatever, for production, stick them on another drive, with NTFS permissions to allow access.

Confirm everything looks good, click install.

And we restart... we we do once we figure out where the restart button is.

Over a RDP window you need to swipe over to the right

Ah yes, swipe to the right and there it is

..up next tomorrow, installing a guest operating system

Where does your DC go?

bradley — Sun, 19 Aug 2012 05:00:00 GMT

So where should be your DC in a virtual machine setup?

Should you do snapshots of virtual machines?

For the first - I've been told never ever ever do a domain controller that has the hyperV role. But when I went looking for info on how this is not supported - I'm finding blog posts that are more wiggly - http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/11/24/the-domain-controller-dilemma.aspx

In my office I'm using the parent as a workgroup. So that it's independent of the domain. One item of note in that blog post is the statement that if you have the dc role and the HyperV role together, you need to shut down the HyperV children before rebooting the box. Right now in my workgroup mode, when I patch I don't. I just reboot the box, the hyperV does a 'saved state' and then turns back on when done.

"You should never use saved state / snapshots with domain controllers - as this can be catastrophic"

Yet that post indicates that saved state is a no no? Mind you I only have one Domain controller so that the issue of tombstoning won't occur.

I do not take snapshots on domain controllers, nor on my real HyperVs. I've taken a snapshot on my test box and accidentally put the snapshot files in a small size drive and ran the drive out of room. This in turn paused the child machines. Thus I'm not comfy with snapshots on real virtual machines for fear of my stupidity kicking in.

I'll be adding some of these comments to the HyperV for SMB build doc.

Now setting up a HyperV2008R2

bradley — Sun, 12 Aug 2012 05:00:00 GMT

Back again, I've enabled RDP so I can remote into the server from my workgroup based Win7.

I'm going to hit number 2 to change the name of the server to Hyperv - and reboot

Then I'm going to hit number 1 to change it to the same name of the workgroup that this computer is in

And I'm going to enable remote management again - http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/11/configuring-remote-management-of-hyper-v-server-in-a-workgroup.aspx

The major diff between 2k8r2 and HyperV 2012 is that PowerShell is already enabled.

The server will want to reboot.

Go back into remote management and do item number 3 and enable remote management

Don't forget to add a local admin that is the same as the user account on your workgroup based PC. Enable the Server manager tools and put in the hosts menu to point to your remote HyperV machine.

NOW.. if I've done everything right.... keep our fingers cross this time... I should be able to use the server manager on the local RSAT tools/PC to manage the remote HyperV

Restart the Server...

Now install the RSAT tools on your Windows 7 PC - http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=7887

AH HA it worked... okay now let me set up a HyperV networking stuff.

Next up building a network

Setting up networking

bradley — Sun, 12 Aug 2012 05:00:00 GMT

In this simple HyperV I have one nic and one nic only. So it will share duties as the nic for me managing the box as well as providing the networking stack for the HyperV.

In the HyperV manager, I will click on Virtual network manager and build a new "external" network.

Click creat virtual network

External

Then on Add

In this test server because I only have one nic

I'm going to make sure the "allow the Management Operating system to share the nic card" is enabled.

I did not check the Enable virtual lan identification.

Now when I enable a virtual machine I just choose the networkingi to be bound to that external nic that I set up.

The roadblock.

Anonymous — Fri, 10 Aug 2012 05:00:00 GMT

So I've hit a roadblock.

It's confirmed.

Deploying Windows 8 Remote Server Administration Tools (RSAT) - Server Manager - Site Home - TechNet Blogs:
http://blogs.technet.com/b/servermanager/archive/2012/07/30/deploying-windows-8-remote-server-administration-tools-rsat.aspx

Want to support a Windows HyperV 2012 server - have to have Windows 8.

Want to support it (RSAT tools) with a Windows 7 machine? Good luck.

So I'll be firing up a Windows 8 for grins and then rolling back to a HyperV 2008 r2 server. Hang tight, sorry for the delay in the proof of concept.

Hitting a little issue

bradley — Thu, 09 Aug 2012 05:00:00 GMT

So I've hit a slight stumbling block in http://msmvps.com/blogs/bradley/archive/2012/08/07/next-step-in-hyperv.aspx

I can't use the RSAT tools in Windows 7 to launch the server manager to then control a Windows 2012 HyperV server.

I will need to probably use Windows 8 to remotely manage this system. Hmmm.. let me see if I can find some other way to do what I want to, otherwise I may be rolling back to do this proof of concept on HyperV 2008R2.

Hang tight while I see if I can work around this roadblock.

Hitting a little issue

Anonymous — Thu, 09 Aug 2012 05:00:00 GMT

So I've hit a slight stumbling block in http://msmvps.com/blogs/bradley/archive/2012/08/07/next-step-in-hyperv.aspx

I can't use the RSAT tools in Windows 7 to launch the server manager to then control a Windows 2012 HyperV server.

Hang tight while I see if I can work around this roadblock.

The roadblock.

bradley — Thu, 09 Aug 2012 05:00:00 GMT

So I've hit a roadblock.

It's confirmed.

Want to support a Windows HyperV 2012 server - have to have Windows 8.

Want to support it (RSAT tools) with a Windows 7 machine? Good luck.

So I'll be firing up a Windows 8 for grins and then rolling back to a HyperV 2008 r2 server. Hang tight, sorry for the delay in the proof of concept.

How I got here

Anonymous — Wed, 08 Aug 2012 05:00:00 GMT

So let me back up a bit to how I got here.

http://technet.microsoft.com/en-us/library/ee731893(v=ws.10).aspx

I did NONE of that. Way too complicated. I merely downloaded the Server 2012 HyperV iso and then I used this tool - http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool to build a bootable flash drive.

Tons easier.

Install that on your computer and never buy a cdrom player again (at least not for installing operating systems these days)