Skip to main content

VMM Maintenance Mode

By
Maintenance Mode in VMM allows you to perform upgrades or other administrative duties that would not be possible with running virtual machines.  For a non-clustered VMM server, the VMs are placed in a saved state.  In a cluster VMM environment, you will get two options:
Live migrate all highly available VMs, place non-highly available VMs in a Saved state.
Place all VMs in a saved state.

Below you can see three virtual machines that are running.  This is a screen shot from VMM.
image
To enter maintenance mode, click the Hosts management option.
image

Now click Start Maintenance Mode in the Actions pane.
image

Click Start Maintenance Mode.
image

You will see the Start Maintenance Mode job running.
image
This will take some time depending on how many VMs are running on the host, if they are being saved or failed over, and how many VHDs are involved.

Clicking on the Virtual Machines management windows shows us that our VMs are now in a saved state.
image
image
Once you have completed your maintenance, click on the Host window option and then click Stop Maintenance Mode from the Actions pane.

The Stop Maintenance Mode job will start.
Once you are out of maintenance mode, you will have to manually start any VMs that were placed in a saved state and fail back over any VMs that were moved to another node in a failover cluster.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more