Alberto Ortega’s Blog

The experience of deploying an Hyper-V Server 2008 R2 Beta was quite friendly. It took no more than 30 minutes to be logged for the first time. I run for a couple of minutes into problems when trying to manage the box remotely using the Hyper-V Manager, here is a track of my first steps into Hyper-V Server R2 Beta:

1. Running the remote management script as it comes with Hyper-V Server 2008 R2 Beta did not allowed remote management. Moreover, this powershell script hanged up to me several times and I discarded its usage.
2. So, I run the Netsh commands manually
   1. Netsh advfirewall firewall set rule group=”Windows Firewall Remote Management” new enable=yes
   2. Netsh advfirewall firewall set rule group=”Windows Remote Management” new enable=yes
   3. Netsh advfirewall firewall set rule group=”Remote Service Management” new enable=yes
   4. Netsh advfirewall firewall set rule group=”Remote Desktop” new enable=yes
   5. Netsh advfirewall firewall set rule group=”iSCSI Service” new enable=yes
   6. Netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes
   7. Netsh advfirewall firewall set rule group=”Failover Clusters” new enable=yes
   8. Netsh advfirewall firewall set rule group=”Microsoft Hyper-V” new enable=yes
   9. Netsh advfirewall firewall set rule group=”Remote Service Management” new enable=yes
3. However I was still not able to connect to the Hyper-V Server
4. When I disabled the firewall running (Netsh firewall set opmode disable) I was able to connect using the Hyper-V Manager snap-in from my Windows Vista x64 Wks, but I received the message “You are not allowed…”
5. I joined the machine to my domain running (netdom join <ComputerName> /domain:<DomainName> /userd:<UserName> /passwordd:*) and after reboot (shutdown /t 0 /r) I was able to connect.
6. I put the firewall up again (Netsh firewall set opmode enable) and now I am still able to manage the server. This are more likely to be Beta issues.

Resources

• Install Remote Management Tools: http://support.microsoft.com/kb/952627
• Run the Hyper-V Manager snap-in and connect to MACHINE_NAME.domain
• Toubleshooting: http://blogs.southworks.net/aalvarez/2008/11/15/hyper-v-server-first-steps-and-troubleshooting/

I have applied for the MED-V beta program. This product will soon be part of Microsoft Desktop Optimization Pack (MDOP). MED-V leverages Microsoft Virtual PC to provide an enterprise solution for desktop virtualization, streamlining OS upgrades, and increasing IT control and user flexibility.

I am willing to drive a beta testing of this solution as here at Southworks we are looking for a flexible desktop image solution. You can apply to the beta program Here. The high-level architecture is quite interesting:

Where

1. Administrator defined "master" VM
2. Images repository served by IIS enabling for images version management
3. MED-V management server which maps virtual images with end-users leveraging Active Directory
4. Management console to access the Image repository
5. End-user Client which allows
• Virtual image life-cycle: Auth, get new image from server
• Virtual machine session management: Start, stop or suspend the VM running on backgroun
• Single desktop experience: Make VM applications available through the standard desktop Start Menu

This Single desktop experience is quite interesting as it resembles to VMFusion:

Source

• MED-V datasheet (PDF, XPS)
• MED-V Architecture White Paper (PDF, XPS)
• MED-V Introduction video or demo
• A Technical Springboard session about MED-V

Year 2009 started with great news!! Yesterday Microsoft has awarded me with the MVP recognition for the year 2009. I was recognized as a Management Infrastructure technical leader and this makes me very proud as It was something I were pursuing for years in my professional career.

My commitment with the community is growing stronger every year and I am willing to participate as much as I can in Systems Management events during this 2009.

I would like to thank to all people involved in this recognition and specially to Southworks for letting me grow-up between most valuable professionals which led me to this huge milestone in my career.