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.