It’s a little more trouble to set up, but the pain is manageable. To make it even less desirable, remote desktop sessions are something of a security risk as they are easier to hijack than a system that’s being managed by PowerShell Remoting or traditional RPC-based tools such as Hyper-V Manager.Ī better option is to install the management tools on a remote system and allow them to connect to and manage the Hyper-V host(s). Also, any active session requires resources, and the only place to take them from is the guests. It quickly becomes tiring when there are multiple hosts. That’s fine if you’ve only got one Hyper-V host and it isn’t doing much. Since, like any server, the best practice is to avoid working directly from the physical console, you’ll most likely carry this out using a Remote Desktop session. The easiest option was mentioned in the introductory paragraph: work locally with the management tools. Understanding Connection Options for Hyper-V Management This article will help you get connected. If you want to control Hyper-V remotely, as it was intended, things get tougher and you’ll need Hyper-V manager. If you install Hyper-V as a component of a complete GUI-based installation of Windows, then all the tools are local and work without any issues. Where you start to run into trouble is in the management area. Installing Hyper-V is fairly easy, as major infrastructure components go.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |