Manage Hyper-V from SMT, plus tool updates to File Explorer & Device Manager


With Server Management Tools (SMT) as a hosted service, it gives us the ability to deliver functionality incrementally - we want you to have it as soon as it works! We prioritize our new functionality directly based on your feedback - let us know what you'd like to see next! Visit our Uservoice forum to submit feedback and vote up your favorite ideas. You can also follow & reach out on twitter!

We have listened and addressed the top piece of feedback we have received when we talk to customers (either in our regular usability studies or at conferences, such as Ignite ): Hyper-V VM management. Today I'm happy to announce that we've brought basic Hyper-V VM management to SMT.

Before we dive in to Hyper-V, let's take a look at some incremental updates that have been added to the existing File Manager & Device Manager tools.

File Explorer

File explorer functionality was initially read-only, so we've taken the next step and added copy & move functionality.

To copy or move a single file, open the context menu by clicking the ellipsis or right-clicking the row.

If you select multiple files, use the move and copy buttons at the top of the blade.

Once you choose to copy or move, a new blade will open prompting you for the destination path. If you know the path to the destination, you can type it in, or select the browse button at the top of the blade to spawn a folder picker.

In addition to copy & move, users let us know that they wanted to view the properties for files/folders, and it was specifically important to see the folder sizes.

You can access the properties of any file or folder from the context menu (click the ellipsis, or right-click on the row.)

Device Manager down-level support

We've enabled down-level support in device manager for WS2012 and WS2012R2. This is the first time you've been able to access device manger remotely since remote access to the Plug and Play (PNP) RPC interface was removed in Windows 8 and Windows Server 2012. When you connect to a down-level server, you can enumerate all the devices & enable/disable. Properties are not yet supported on targets other than WS2016.

We'd love to hear more from you on device manager! Let us know what you need.

Hyper-V

In this update to SMT, we support the following VM management functionality:

  • Start/Shutdown/Turn off/Pause/Resume
  • Save State/Delete Saved State
  • Take/Apply & Rename checkpoints

When you first open he Hyper-V tool by selecting it in the SMT tool menu, you will see a blade that lists all the VMs on the host, as well as information about their health, operational status, and resource usage. These values update every 10 seconds.

On this page you can right-click the row or select the ellipsis to open the context menu, where you can take action on the VM. If you click on the VM a new blade will open with properties of the VM and the action buttons along the top. Applying or renaming checkpoints on the VM happen here on this blade. Clicking a checkpoint will open an additional blade with the checkpoint properties.

Main Hyper-V Blade

VM Properties blade

Checkpoint Properties Blade

What do you think? We would love to hear from you.

Comments (5)

  1. Romain Serre says:

    Hi,

    I'm sorry but I'd prefer a new GUI for Hyper-V On-Premises. A GUI that enables me to sort and filter VM, to manage all Cluster features and so on. Something like vCenter.

    I will never manage my Hyper-V from Azure.

    Regards,

    Romain

    1. Hi Romain,
      Thanks for your comment. Just to clarify, is the reason you say you won't manage Hyper-V from Azure due to the lack of functionality you mentioned, or something else?

  2. In my opinion, Azure is not a good option to manage Hyper-V. However, I'd like all the management tools to be on-premises, close to my infrastructure.
    I don't know a customer ready to open communication between servers as virtualization host to Internet and/or a Cloud Provider.

    Thanks,
    -Charbel

    1. Monty Harris says:

      If you are doing cloud backup direct from the servers you are already doing it. If you are using direct updating from Windows Update even as a back up source you are already doing it. You may not be doing that on a host, in fact its probably a good idea if you aren't. With that being said I think the upside of this is not managing a holistically on premise environment. Rather it creates a unified dashboard for Azure and On-Premise VM management. That makes a lot of sense in a hybrid environment.

  3. In my opinion, Azure is not a good option to manage Hyper-V. However, I’d like all the management tools to be on-premises, close to my infrastructure.
    I don’t know a customer ready to open communication between servers as virtualization host to Internet and/or a Cloud Provider.

Skip to main content