Windows Management Framework 3.0 Compatibility Update

Windows Management Framework (WMF) 3.0, (currently distributed as KB2506146 for Windows Server 2008 SP2 and KB2506143, for Windows 7 SP1 and Windows Server 2008 R2 SP1) has been temporarily removed from Windows Update to protect from accidental installations on unsupported systems. Those who want to install WMF 3.0 to take advantage of all the great features this update provides can do so by installing the update from the Microsoft Download Center, after reading the known compatibility issues detailed below.


Windows Management Framework (WMF 3.0) was released to the Download Center on September 17, 2012. On December 11, 2012,this package was released through Windows Update. Although it was released as an optional update, many customers chose to deploy the package automatically.  Because there are compatibility issues between some released server applications and WMF 3.0, we have temporarily removed WMF 3.0 from Windows Update. This should prevent customers from inadvertently installing the package on unsupported systems.

Known Compatibility Issues:

Windows Management Framework 3.0 (WMF 3.0) is not currently compatible with the following applications.

–         System Center 2012 Configuration Manager  (Configuration Manager Management Points collocated with clients fail after installing Windows Management Framework 3.0 and running Client Health Evaluation)

–         System Center Virtual Machine Manager (Managing Hyper-V hosts using Virtual Machine Manager fails with Error: 0x8033803b after installing WMF 3.0)

–         Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 (Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010)

–         Microsoft SharePoint 2010  (Windows PowerShell 3.0 and SharePoint 2010)

–         Windows Small Business Server 2008 and Windows Small Business Server 2011  (Windows Management Framework 3.0 applicability on Windows Small Business Server 2008/2011 Standard)

Systems that are running the above server applications should not run Windows Management Framework 3.0 at this time. WMF 3.0 is otherwise supported on Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2.

SCVMM change owner of a virtual machine

Have you ever found yourself in a situation where you have a bunch of virtual machines (VMs) where the OWNER value is set to UNKNOWN or domain\administrator and you wanted to set a value owner without having to modify them one VM at a time?  There’s a PowerShell command that you can use to accomplish this.

Get-VM -VMMServer “FQDN of the SCVMM Server” | where {$_.Owner -eq “Unknown”} | Set-VM -Owner “domain\accountname”
Get-VM -VMMServer “FQDN of the SCVMM Server” | where {$_.Owner -eq “domain\Administrator”} | Set-VM -Owner “domain\accountname”

Microsoft SCVMM 2008 R2 Library add folders

When you install Microsoft SCVMM 2008 R2 (Microsoft System Center Virtual Machine Manager) and you’ve created a library, mabye you want to create some custom folders. When you create some custom folders in the Library share, in my example C:\SCVMM_Data, the new folders didn’t show up in the SCVMM Management Console. After I coppied some files (.iso, .ps1 and .xml) to the share, the folders shows up!

This is by default. When you place some files in the folders, SCVMM detects this and the folders will show up now! The following file types are indexed during a Library Refresh (default every hour)

Virtual Hard Disks: .vhd (Hyper-V, Virtual Server), .vmdk (VMware)
Virtual Floppy disks: .vfd (Virtual Server), .flp (VMware)
ISO image files: .iso
Scripts (answer files): .ps1 (Windows PowerShell), .inf or .xml (Answer Files)
VMware templates: .vmtx (VMware)

When you want to force a Library Refresh, right-click on the SCVMM Library and choose Refresh.