Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Introduction

This article describes the issues that are fixed in Update Rollup 13 for Microsoft System Center 2012 R2 Virtual Machine Manager. There are two updates available for Virtual Machine Manager, one for the Virtual Machine Manager server and one for the Administrator Console. This article also contains the installation instructions for this update.

Issues that are fixed

  • Fabric Administrators (Delegated Administrators) cannot modify properties of a virtual machine (VM) that is created by a Windows Azure Pack user.

  • Inter-cluster/Intra-cluster live migration causes long network downtimes.

  • HNV policies are not updated on VMs that are moved through Failover Cluster Manager (FCM).

  • Cannot connect a VM to a VLAN-based Independent networks from the VMM UI.

  • When the test VM is deleted from ASR or VMM after successful verification of test failover for Hyper-V replication, this causes the deletion of other replicated data/files (that are not related to the VM under test). For ASR, this results in critical state indication for the other replicated VMs.

  • Snapshot deletion and restore does not delete VHDs, even if they do not have any dependencies.

  • A VM is displayed as critical in System Center Operations Manager if the WinRM version is greater than 10.

  • When a HNV VM is migrated to a host that is in legacy mode, HNV policies are not updated, which causes the VM to lose connectivity.

Note Because updates for System Center 2012 R2 Virtual Machine Manager are cumulative, this update includes all the improvements and fixes that are included in the previous cumulative update. For more information, see Update Rollup 12 for System Center 2012 R2 Virtual Machine Manager

How to obtain and install Update Rollup 13 for System Center 2012 R2 Virtual Machine Manager

Update packages for Virtual Machine Manager are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has a Virtual Machine Manager component installed:

  1. Click Start, and then click Control Panel.

  2. In Control Panel, double-click Windows Update.

  3. In the Windows Update window, click Check Online for updates from Microsoft Update.

  4. Click Important updates are available.

  5. Select the update rollup package and then click Ok.

  6. Click Install updates to install the update package.

Manual download

Go to the following websites to manually download the update packages from the Microsoft Download Center:

 Download the Virtual Machine Manager Server update package now.

 Download the Administrator Console update package now.

For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Installation instructions

To manually install the update packages, run the following command from an elevated command prompt:

msiexec.exe /update packagename

For example, to install the Update Rollup 13 package for a System Center 2012 R2 Virtual Machine Manager Server (KB4014525), run the following command:

msiexec.exe /update kb4014525_vmmserver_amd64.msp

Notes

After the installation

To fix the "Another machine with the same SMBIOS GUID is found" warning on your existing Storage Spaces Direct (S2D) clusters, remove the providers, and then add them back. After the providers are added, update those providers.

Files updated in this Update Rollup

Files that are changed

File size

Version

Language ID

Utils.dll

917864

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

26984

3.2.8377.0

4

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

12

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28000

3.2.8377.0

7

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28000

3.2.8377.0

16

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28520

3.2.8377.0

17

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

1046

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

29536

3.2.8377.0

25

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

10

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

26976

3.2.8377.0

1028

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

18

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

26984

3.2.8377.0

3076

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

5

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

19

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

14

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

21

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

2070

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

27496

3.2.8377.0

29

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

27488

3.2.8377.0

31

Microsoft.SystemCenter.VirtualMachineManager.dll

2063712

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

26984

3.2.8377.0

4

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

12

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28000

3.2.8377.0

7

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28000

3.2.8377.0

16

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28520

3.2.8377.0

17

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

1046

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

29536

3.2.8377.0

25

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

10

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

26976

3.2.8377.0

1028

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

18

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

26984

3.2.8377.0

3076

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

5

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

19

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

14

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

21

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

28008

3.2.8377.0

2070

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

27496

3.2.8377.0

29

Microsoft.SystemCenter.VirtualMachineManager.resources.dll

27488

3.2.8377.0

31

Microsoft.VirtualManager.UI.Dialogs.dll

3216736

3.2.8377.0

0

Utils.dll

917864

3.2.8377.0

0

Engine.Common.dll

231784

3.2.8377.0

0

ImgLibEngine.dll

4366688

3.2.8377.0

0

Engine.Deployment.dll

689000

3.2.8377.0

0

VMWareImplementation.dll

2065768

3.2.8377.0

0

Files that are changed

File size

Version

Language ID

Utils.dll

917864

3.2.8377.0

0

vmmAgent.exe

6368616

3.2.8377.0

1033

Microsoft.SystemCenter.VirtualMachineManager.Library.mp

163296

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery.mp

445920

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.2012.Monitoring.mp

716256

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.2012.Reports.mp

1031648

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library.mp

110048

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.Pro.2012.Diagnostics.mp

23520

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.PRO.Library.mp

20448

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library.mp

69088

3.2.8377.0

0

Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.HyperV.HostPerformance.mp

56800

3.2.8377.0

0

Engine.Common.dll

231784

3.2.8377.0

0

Engine.VmOperations.dll

1285480

3.2.8377.0

0

Engine.ServiceOperations.dll

308584

3.2.8377.0

0

Engine.BitBos.dll

270688

3.2.8377.0

0

ImgLibEngine.dll

4366688

3.2.8377.0

0

Engine.Deployment.dll

689000

3.2.8377.0

0

VMWareImplementation.dll

2065768

3.2.8377.0

0

Utils.dll

917864

3.2.8377.0

0

Engine.Common.dll

231784

3.2.8377.0

0

ImgLibEngine.dll

4366688

3.2.8377.0

0

Engine.Deployment.dll

689000

3.2.8377.0

0

VMWareImplementation.dll

2065768

3.2.8377.0

0

DBUpdate.dll

762720

3.2.8377.0

0

 

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×