I run a Hyper-V server running several Hyper-V VMs. I was wondering if there is any way for me to manage
the Hyper-V server itself (just Hyper-V role, not the rest of the server box) and
the Hyper-V VMs (like connecting into them)
via Mac OS?
I'm on Mac OS 10.8 on my main laptop. From what I've been seeing the Hyper-V management tools are all Windows based.
I'm planning to update my server from Win Server 2008 Rs to 2012 when it is released.
I'm very interested in the new "Storage Spaces".
I log in to my Hyper-v host server
I open the Hyper-V manager, select my server S1 and click Connect
When I want to shut down server S1 or reboot server S1, I just click the start button and select shut down or restart (it's a server 2008 r2).
Now this is my problem.
I’m having several Windows Servers 2008 R2 which I previously accessed using Hyper-V Manager from Windows 7. On upgrading to Windows 8 and enabling the feature Hyper-V, this is no longer possible.
Im lost and desperate. I have been running with a setup where i have a ubuntu server running in hyper-v. My windows server running hyper-v has two network cards. my internet is coming in to one of them and the other is hooked up with a switch. I then direct both to the ubuntu-server running in hyper-v.
I have just installed a new Hyper-V host machine running Server 2008 R2. Created the first VM (also Server 2008 R2 SP1) and all is working apart from a bizare problem with network packets.
Host machine has two Intel Nic's one is dedicated to Hyper-V and is setup as an "External" network in Virtual Network Manager. It's also removed from the management OS, so dedicated just to Hyper-V.
Assume I installed Hyper-V Server 2012. Networking is working fine. The server is locked down, only RDP is enabled. Enabling other ports may not be an option as the server is directly connected to the internet. As I understood it, Hyper-V Server 2012 is simply Windows Server 2012 with the Hyper-V role installed. No other roles are available.
I'm setting up a test "server" on my laptop with Hyper-V. When I go to install from an MSDN ISO I have two choices for standard edition. SERVERSTANDARD or SERVERSTANDARDV.
Googling gives me lists of cracked windows keys, but one site claims that SERVERSTANDARDV is the non Hyper-V flavor. I assume that doesn't contain the Hyper-V server, but wold be safe for a Hyper-V client?
This will sound strange but Windows 8 client OS does pretty much everything I want from a small home office server - that is, file sharing, it contains some HDD fault protection (Storage Spaces) and it contains Hyper-V which I need to virtualize a few testing machines.
However, only after full installation I have found out that the Hyper-V hypervisor in the client OS is actually stricter than the
Email this page
