Following Brian Keller (Microsoft Technical Evangelist for Team System) Blog on "
Installing the Windows 7 Beta with Virtual PC 2007 SP1". I created a Word document on "
Installing Windows 7 Beta on Hyper-V" that can be downloaded (its a 4MB file).
I have to admit I'm impress with the stability of this Beta to the point that I even installed it on a non-capable Vista computer. And, for my surprise, it works. All essential drives were recognized: network adapter, video, and it didn't even crash.
There's a few thing you are going to find out during your installation using Hyper-V. First, during the initial setup you won't have a mouse until it does the first reboot. Second, make sure to assigned the network adapter so it can access the network. Third, you need to authenticate to your network Directory Services to access the internet and Activate Windows.
The document I'm providing is a pictorial of the installation in Hyper-V with few comments, connecting and authenticating to your network.
To be a Beta, I'm very impress. Here's the end result:
After acquiring our new Windows Server 2008 w/Hyper-V we needed a tool to manage both Hyper-V’s and Virtual Server’s 2005. With our recent integration of PowerShell into our infrastructure make more sense to upgrade our
System Center Virtual Machine Manager (SCVMM) 2005 to 2008. PowerShell has become an effective tool to built automation solutions in our network, systems, and even our business applications.
Building a 64bit virtual machine with Windows Server 2008 and installing SCVMM 2008 was hassle-free. Installing the agents was effortless and with less downtime. So, after the SCVMM installation we can monitor and manage both Virtual Server 2005 and Hyper-V from one single console.
Using
PowerShell bring added security to our scripting tools not provided by any predecessors (VBScript/Jscript) scripting tools. The first time security prompt will be displayed:
Then, with a simple cmdlet “
Get-VM -VMMServer Topaz”, we can list all your virtual machines in your managed SCVMM2008 :
.aspx)
We can later build a PowerShell script to create reports about our Virtual Machines.
Flexible, powerful, and efficient.
Join the crowd!
While I was cleaning my developer hard drive I just found the MSCVMM PowerShell Reference manual. I would considered it a "lost and found" item due to the fact that I can't find it on Microsoft website. So, for does who may want to find our what cmdlets are available in this application... here's the document you can download from this site: <click here to get to document>
I work for Claire’s Stores Inc. at their office in Pembroke Pines, Florida. The purpose of our applications is to provide financial information to everyone in our organization. For the last few years I have help deploy Virtualization solutions using both Virtual PC 2007 and Microsoft Virtual Server 2005. Now, the need to build a new Stores application using “OutlookSoft CPM 4.2” for our top management started the process to take advantage of Microsoft new emerging technology. This new application will be deploy to few Management users through our organization world-wide.
So, what technologies will be needed to build and deploy this new application? Here’s the list:
1. Windows Server 2008 Enterprise Edition w/Hyper-V
2. Windows Server 2008 Terminal Server - Remote Application option
a. MS Office 2003
b. “OutlookSoft CPM 4.2” – Client application
3. Windows PowerShell - for building ETL and extracting data solutions
4. Windows Server 2003 Enterprise w/SQL Server 2000 (Virtual Machine)
a. MS Office 2003
b. SQL Server 2000 w/Analysis Services
c. “OutlookSoft CPM 4.2” - Our legacy serve application.
5. Microsoft System Center Virtual Machine Manager 2007
Thanks to the recent release Hyper-V technology and the MSCVMM 2008, it’s the perfect combination to implement and manage virtual machines across our network. With the help of PowerShell its makes it incredibly flexible to build solutions that can be integrated and use with many applications on the server: such as IBM i5, SQL Server, and MSCVMM. Also, the simplicity of deploying the remote application using email makes is a breeze.
Of course, not everything went as planned. But, there’s always a work-around the corner. During this project I wrote a document describing
how to migrate VS 2005 Virtual Machines to Hyper-V. Also, due to our legacy application server, I had problem were I found that the User profile in our new Terminal Server wasn’t fully built when using the Remote Application option. And, yes, I did use the Momentum support but they couldn’t duplicate the error. So, through trial and error, I discovered that I needed to have the user logon once on the full terminal session to clear my error on my legacy application.
So, you may find some obstacle along the way but there will be a way to fix it. Now, we started to deploy the new application. I’m looking forward to keep implementing Microsoft new technology in our organization.