VMM 2008 regularly refreshes a VM to retrieve it’s configuration and settings, e.g. what ISO is mounted. What happens if you manage a machine directly in Hyper-V? That change won’t be reflected immediately in VMM. So you might need to force the refresh. You’ll have to fire up the PowerShell console for Virtual Machine Manager 2008 to do this:
First you’ll connect to the VMM server. I know, you’re probably logged into it already but PowerShell isn’t.
get-vmmserver <Vmm_Server_Name>
That’ll think for a second and then spit back a load of information about the VMM server object. That’s a sign that it worked. Next you’ll run a command to refresh your VM:
refresh-vm –vm <Virtual_Machine_Name>
I usually forget the –vm flag because it does seem a bit redundant. Here’s an example:
PS C:WindowsSystem32> get-vmmserver vmm01.mydomain.com
PS C:WindowsSystem32> refresh-vm –vm SQLServer01
In that example I’ve connected to a VMM server called vmm01.mydomain.com. The VM I want to refresh appears as SQLServer01 in the VMM console so that’s what I refresh. That’s not necessarily it’s FQDN. Give this a few seconds and the VM properties will be refreshed in VMM and the console. They’ll be displayed in the PowerShell console.