Last updated by at .

  • What's new in Hyper-V 2016
  • Microsoft Azure

Tag: VMM

System Center Logo

Summary: Update Rollup 8 for System Center 2012 R2 and Azure Pack now available

Yesterday Microsoft released Update Rollup 8 for System Center 2012 R2 and Windows Azure Pack. Again with the Update Rollups for Windows Azure Pack and System Center, Microsoft not only delivers bug fixes, they also release new features.

There are some really cool highlights in this Update Rollup:

  • Network Virtualization Improvements (Multiple External IP Addresses,…)
  • SCDPM bug fixes
  • Better Checkpoint Integration (Checkpoint Quotas,…)
  • Support for SQL Server 2014 SP1
  • Support of Tier Storage in VMM for Storage Spaces
  • Hyper-V ACL Support in VMM
  • New Network devices in SCOM

Here you can get a quick update on what’s new in Update Rollup 8:

  • Data Protection Manager (KB3086084)
    • The DPM Agent crashes intermittently during a backup.
    • If you are trying to recover data from an imported tape, DPM may crash with a “Connection to the DPM service has been lost” error.
    • If you try to back up a SharePoint site that uses SQL Always On as a content database, SQL logs are not truncated as expected.
    • You cannot verify tape library compatibility for tapes that use RSMCompatmode settings such as IBM 35xx, 2900, and so on.
    • If you have multiple SharePoint farms hosted on the same SQL cluster with different instances but the same database names, DPM cannot back up the correct SharePoint farm content.
    • If you run Update Rollup 7 for Data Protection Manager 2012 R2, and you have already configured online protection for one or more protection groups, trying to change the protection group populates the default DPM settings for the “Select long-term goals” wizard instead of the previous configured values.
    • When you try to protect a SQL failover cluster, the Data Protection Manager UI crashes for every backup or synchronization operation.
    • If you install Update Rollup 7 for Data Protection Manager 2012 R2, self-service recovery for SQL databases may not work.
  • Operations Manager (KB3096382)
    • Slow load of alert view when it is opened by an operator
      Sometimes when the operators change between alert views, the views take up to two minutes to load. After this update rollup is installed, the reported performance issue is eradicated. The Alert View Load for the Operator role is now almost same as that for the Admin role user.
    • SCOMpercentageCPUTimeCounter.vbs causes enterprise wide performance issue
      Health Service encountered slow performance every five to six (5-6) minutes in a cyclical manner. This update rollup resolves this issue.
    • System Center Operations Manager Event ID 33333 Message: The statement has been terminated.
      This change filters out “statement has been terminated” warnings that SQL Server throws. These warning messages cannot be acted on. Therefore, they are removed.
    • System Center 2012 R2 Operations Manager: Report event 21404 occurs with error ‘0x80070057’ after Update Rollup 3 or Update Rollup 4 is applied.
      In Update Rollup 3, a design change was made in the agent code that regressed and caused SCOM agent to report error ‘0x80070057’ and MonitoringHost.exe to stop responding/crash in some scenarios. This update rollup rolls back that UR3 change.
    • SDK service crashes because of Callback exceptions from event handlers being NULL
      In a connected management group environment in certain race condition scenarios, the SDK of the local management group crashes if there are issues during the connection to the different management groups. After this update rollup is installed, the SDK of the local management group should no longer crash.
    • Run As Account(s) Expiring Soon — Alert does not raise early enough
      The 14-day warning for the RunAs account expiration was not visible in the SCOM console. Customers received only an Error event in the console three days before the account expiration. After this update rollup is installed, customers will receive a warning in their SCOM console 14 days before the RunAs account expiration, and receive an Error event three (3) days before the RunAs account expiration.
    • Network Device Certification
      As part of Network device certification, we have certified the following additional devices in Operations Manager to make extended monitoring available for them:

      • Cisco ASA5515
      • Cisco ASA5525
      • Cisco ASA5545
      • Cisco IPS 4345
      • Cisco Nexus 3172PQ
      • Cisco ASA5515-IPS
      • Cisco ASA5545-IPS
      • F5 Networks BIG-IP 2000
      • Dell S4048
      • Dell S3048
      • Cisco ASA5515sc
      • Cisco ASA5545sc
    • French translation of APM abbreviation is misleading
      The French translation of “System Center Management APM service” is misleading. APM abbreviation is translated incorrectly in the French version of Microsoft System Center 2012 R2 Operations Manager. APM means “Application Performance Monitoring” but is translated as “Advanced Power Management.” This fix corrects the translation.
    • p_HealthServiceRouteForTaskByManagedEntityId does not account for deleted resource pool members in System Center 2012 R2 Operations Manager
      If customers use Resource Pools and take some servers out of the pool, discovery tasks start failing in some scenarios. After this update rollup is installed, these issues are resolved.
    • Exception in the ‘Managed Computer’ view when you select Properties of a managed server in Operations Manager Console
      In the Operations Manager Server “Managed Computer” view on the Administrator tab, clicking the “Properties” button of a management server causes an error. After this update rollup is installed, a dialog box that contains a “Heart Beat” tab is displayed.
    • Duplicate entries for devices when network discovery runs
      When customers run discovery tasks to discover network devices, duplicate network devices that have alternative MAC addresses are discovered in some scenarios. After this update rollup is installed, customers will not receive any duplicate devices discovered in their environments.
    • Preferred Partner Program in Administration Pane
      This update lets customers view certified System Center Operations Manager partner solutions directly from the console. Customers can obtain an overview of the partner solutions and visit the partner websites to download and install the solutions.
  • Orchestrator & SMA (KB3096381)
    • SQL Server 2014 Service Pack 1 (SP1) is now supported in Orchestrator 2012 R2.
    • After you export and then import a Runbook, the Password field of Run Program activity is corrupted.
    • SMA: SQL Server 2014 Service Pack 1 is now supported in Service Management Automation 2012 R2.
    • SMA: Service Management Automation 2012 R2 does not let you stop jobs that are in the queued state.
  • Service Provider Foundation (KB3096384)
    • Installing update rollups for Service Provider Foundation causes additional bindings to be created, and this makes a Service Provider Foundation website inaccessible.
    • Quotas for multiple NAT connections are not supported. For more information about this feature, see WAP Update Rollup 8 documentation.
  • Virtual Machine Manager (KB3096389)
    • Support for SQL Server 2014 SP1 as VMM database
      With Update Rollup 8 for SC VMM 2012 R2 you can now have Microsoft SQL Server 2014 SP1 as the VMM database. This support does not include deploying service templates by using the SQL profile type as SQL Server 2014 SP1. For the latest information about SQL Server requirements for System Center 2012 R2, see the reference here.
    • Support for VMWare vCenter 6.0 management scenarios
      With Update Rollup 7, we announced support for management scenarios for vCenter 5.5. Building on our roadmap for vCenter and VMM integration and supportability, we are now excited to announce support for VMWare vCenter 6.0 in Update Rollup 8. For a complete list of supported scenarios, click here.
    • Ability to set quotas for external IP addresses
      With Update Rollup 7, we announced support for multiple external IP addresses per virtual network, but the story was incomplete, as there was no option to set quotas on the number of NAT connections. With UR8, we are glad to announce end-to-end support for this functionality, as you can now set quotas on the number of external IP addresses allowed per user role. You can also manage this by using Windows Azure Pack (WAP).
    • Support for quotas for checkpoints
      Before UR8, when you create a checkpoint through WAP, VMM does not check whether creating the checkpoint will exceed the tenant storage quota limit. Before UR8, tenants can create the checkpoint even if the storage quota limit will be exceeded.
    • Ability to configure static network adapter MAC address during operating system deployment
      With Update Rollup 8, we now provide the functionality to configure static network adapter MAC addresses during operating system deployment. If you have ever done Bare Metal provisioning of hosts and ended up having multiple hosts with the same MAC addresses (because of dynamic IP address assignment for network adapters), this could be a real savior for you.
    • Ability to deploy extended Hyper-V Port ACLs
      With Update Rollup 8 for VMM, you can now:

      • Define ACLs and their rules
      • Attach the ACLs created to a VM network, VM subnets, or virtual network adapters
      • Attach the ACL to global settings that apply it to all virtual network adapters
      • View and update ACL rules configured on the virtual network adapter in VMM
      • Delete port ACLs and ACL rules
    • Support for storage space tiering in VMM
      With Update Rollup 8, VMM now provides you the functionality to create file shares with tiers (SSD/HDD).
    • Issue 1
      Creation of Generation 2 VMs fails with error 13206
    • Issue 2
      VMM does not let you set the owner of a hardware profile with an owner name that contains the “$” symbol.
    • Issue 3
      HA VMs with VLAN configured on the network sites of a logical network cannot be migrated from one host to another. Error 26857 is thrown when you try to migrate the VM.
    • Issue 4
      The changes that are made by a tenant administrator (with deploy permissions to a cloud) to the Memory and CPU settings of a VM in the cloud through VMM Console do not stick. To work around this issue, change these settings by using PowerShell.
    • Issue 5
      When a VM is deployed and put on an SMB3 file share that’s hosted on NetApp filer 8.2.3 or later, the VM deployment process leaves a stale session open per VM deployed to the share. When many VMs are deployed by using this process, VM deployment starts to fail as the max limit of the allowed SMB session on the NetApp filer is reached.
    • Issue 6
      VMM hangs because of SQL Server performance issues when you perform VMM day-to-day operations. This issue occurs because of stale entries in the tbl_PCMT_PerfHistory_Raw table. With UR8, new stale entries are not created in the tbl_PCMT_PerfHistory_Raw table. However, the entries that existed before installation of UR8 will continue to exist.
    • Issue 7
      In a deployment with virtualized Fiber Channel adapters, VMM does not update the SMI-S storage provider, and it throws an exception.
    • Issue 8
      For VMs with VHDs that are put on a Scale out File Server (SOFS) over SMB, the Disk Read Speed VM performance counter incorrectly displays zero in the VMM Admin Console. This prevents an enterprise from monitoring its top IOPS consumers.
    • Issue 9
      Dynamic Optimization fails, leaks a transaction, and prevents other jobs from executing. It is blocked on the SQL Server computer until SCVMM is recycled or the offending SPID in SQL is killed.
    • Issue 10
      V2V conversion fails when you try to migrate VMs from ESX host to Hyper-V host if the hard disk size of the VM on the ESX host is very large.
    • Issue 11
      Live migration of VMs in an HNV network takes longer than expected. You may also find pings to the migrating VM are lost. This is because during the live migration, the WNV Policy table is transferred (instead of only delta). Therefore, if the WNV Policy table is too long, the transfer is delayed and may cause VMs to lose connectivity on the new host.
    • Issue 12
      VMM obtains a wrong MAC address while generating the HNV policy in the deployments where F5 Load Balancers are used.
    • Issue 13
      For IBM SVC devices, enabling replication fails in VMM because there is a limitation in SVC in which the name of the consistency group should start with an alphabetical character (error code: 36900). This issue occurs because while enabling replication, VMM generates random strings for naming the “consistency groups” and “relationship” between the source and the target, and these contain alphanumeric characters. Therefore, the first character that’s generated by VMM may be a number, and this breaks the requirement by IBM SVC.
    • Issue 14
      In Update Rollup 6, we included a change that lets customers have a static MAC address even if the network adapter is not connected. This fix did not cover all scenarios correctly, and it triggers an exception when there’s a template with a connected network adapter, and then you later try to edit the static address in order to disconnect the network adapter.
    • Issue 15
      Post Update Rollup 6, as soon as a host goes into legacy mode, it does not come back to eventing for 20 days. Therefore, the VM properties are not refreshed, and no events are received from HyperV for 20 days.This issue occurs because of a change that’s included in UR6 that set the expiry as 20 days for both eventing mode and legacy mode. The legacy refresher, which should ideally run after 2 minutes, now runs after 20 days; and until then, eventing is disabled.Workaround:
      To work around this issue, manually run the legacy refresher by refreshing VM properties.
    • Issue 16
      Post-UR7, deleting a virtual network does not correctly clean up the cluster resources for the Network Virtualization Gateway. This causes the cluster role (cluster group) to go into a failed state when a failover of the HNV gateway cluster role occurs.
  • Windows Azure Pack (KB3096392)
    • Administrators cannot offer and tenants cannot use multiple external IP addresses through a Network Address Translation (NAT) connection.
      Even though Microsoft System Center Virtual Machine Manager (VMM) has functionality to allocate IP addresses for this purpose, the WAP administrator and tenant experiences do not provide such functionality. Administrators can now allocate a set of external IP addresses for tenants to use when you create NAT rules. The administrator can set up the IP address quota through the Administrator Portal virtual machine (VM) extension.
    • Tenants can create only one checkpoint per virtual machine.
      Administrators can create plans that include quotas that let tenants create multiple VM checkpoints.
    • An unexpected exception is generated by the PowerShell command “Get-MgmtSvcSqlDatabase.”
      The command Get-MgmtSvcSqlDatabase does not retrieve SQL database information. The following examples return exception “Object reference not set to an instance of an object”:

      • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId “someid” -DisableCertificateValidation
      • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId $hostserver.ServerId -Name “somename” -DisableCertificateValidation
      • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId ” someserverid” -Name “datatest” -DisableCertificateValidation
    • An unexpected exception is generated by the PowerShell command “Remove-MgmtSvcMySqlHostingServer.” 
      This command fails with the exception “Index (zero-based) must be greater than or equal to zero and less than the size of the argument list” when you run statements such as the following:

      • Remove-MgmtSvcMySqlHostingServer -AdminUri $AdminUri -Token $Token -HostingServerId $HostServer[0].ServerId -DisableCertificateValidation
      • Remove-MgmtSvcMySqlHostingServer -AdminUri $AdminUri -Token $Token -HostingServerId “someserverid” -DisableCertificateValidation
    • When you create a virtual machine through the Tenant Portal, the menu dropdown boxes are not sorted.
      When a tenant tries to create a VM and the list of items is larger than some items, it becomes very difficult to find the necessary machine image or template.
    • Attaching ISOs in a generation 2 (gen 2) VM fails after three or four attach or detach operations.
      The attach and detach operations on ISO disks and VM gen 2 allocate adapters never releases the adapters for reuse.After you apply this update, detaching the disk adapter enables the adapter to be reused again.

This Update Rollup is one of the bigger one Microsoft released in terms of Azure Pack IaaS Scenarios. This update brings several great improvements to the implementation of Checkpoints and Network Virtualization. Update Rollup 8 finally bringing end to end support for multiple external IP Addresses for the NVGRE Gateways inside WAP as well as VMM. Also better support for Checkpoints on Hyper-V in the WAP Portal as well as VMM.

As always, before you deploy an update rollup in production, make sure, you have tested it in your test or lab environment.

System Center Logo

Summary: Update Rollup 7 for System Center 2012 R2 and Azure Pack now available

Last week Microsoft released Update Rollup 7 (UR7) for System Center 2012 R2 and Windows Azure Pack. And as always, Update Rollup 7 does not only include a bunch of fixes, it also includes some new features. This time especially Windows Azure Pack and System Center Virtual Machine Manager got some nice updates. Components that are fixed and updated in this update rollup

  • Data Protection Manager (3065246)
    • Support for Windows 10 Client operating system
    • Ability to use an alternative DPM server to recover from Azure Backup Vault
    • Improvements for backup on Hyper-V Replica VMs
    • Other improvements and fixes…
  • Orchestrator & SMA (3069115)
    • Orchestrator: some small fixes
    • SMA
      • SMA runbook execution fails if a PowerShell execution policy is set to Unrestricted through a Group Policy Object.
      • Fixed an error when you try to save or import a runbook in SMA
  • Operations Manager (will be released later)
    • The rollup is delayed by few weeks, as engineering team is working on recently reported issues.
  • Service Manager (3063263)
  • Service Provider Foundation (3069355)
    • This update includes general API changes to improve product quality.
  • Virtual Machine Manager (3066340)
    • Support for Windows 10 Client Operating System
    • Support for new Linux Operating Systems (Debian 8)
    • Support for VMWare vCenter 5.5 management scenarios (more infos VMWare vCenter 5.5 management scenarios)
    • Support for Multiple External IP Addresses per Virtual Network
    • Option to Reassociate Orphaned virtual machines to their Service or VM role
    • Support for VMM DHCP Extension PXE/TFP Forwarding
    • Some scale improvements if you have more than 50 Hyper-V Hosts
    • Some Hyper-V Network Virtualization (HNV) fixes and improvements
    • Other fixes…
  • Windows Azure Pack (3069121)
    • Tenants cannot delete the checkpoints of their virtual machines
    • Support for VM names of up to 15 characters
    • Displaying VHD items during virtual machine creation when there are no hardware profiles in the plan
    • Incompatible VHDs are offered to the tenant when attaching a VHD to a virtual machine
    • Support for tenant plan viewing and self-subscription permission based on security groups
    • Support for Shielded Virtual Machine Management when it’s run on Windows Server 2016 Preview
    • Virtual Machine performance data displayed in the tenant portal
    • Other fixes and improvements…
  • Windows Azure Pack Web Sites (3069358)
    • Adds support for IPv6 to IP SSL functionality
    • Changes Web Deploy publishing from to
    • Other fixes and improvements…

One of the new features I want to highlight is the possibility to add multiple public (external) IP addresses to  Virtual Network (Using Hyper-V Network Virtualization HVN). This means a tenant can assign multiple public IP addresses on his NAT gateway and do port forwarding, for example if he runs multiple webservers in that VM Network. This is a feature a lot of customers especially service provider have missed for a long time.

Another improvement we can see is the support for the next release of Windows Server and also support for Windows 10.


System Center 2012 R2 Update Rollup 6

Summary: Update Rollup 6 for System Center 2012 R2 and Azure Pack now available

Microsoft just released System Center 2012 R2 Update Rollup 6, which includes a lot of new features and fixes. With this Update Rollup 6 Microsoft now supports SQL Server 2014 as databases for the System Center and Windows Azure Pack components.

Components that are fixed in this update rollup

  • Data Protection Manager (KB3030574)
    • Option to keep online backup data while deleting a protection group
    • Support for SQL Server 2014 as DPMDB
  • Operations Manager (KB3051169)
  • Service Manager (KB3039363)
  • Service Provider Foundation (KB3050307)
  • Service Reporting (KB3050321)
  • Virtual Machine Manager (KB3050317)
    • Add Azure Subscription feature
    • Improved E2A ASR protection scenario
    • Option to use Generation 2 VMs in Services and VMRoles
    • Total Networking Usage Exposure rules in Management Pack
    • Option to overcommit Cloud and Host Group capacity for Replica VMs
  • Windows Azure Pack (KB3051166)
    • Adds support for Webjobs in Windows Azure Pack Websites.
    • Adds support for Deployment Slots in Windows Azure Pack Websites.
    • Adds support for Virtual Machine Checkpoint.
    • Adds support to maintain Data Consistency between the SQL Resource Provider configured properties for resources with the actual provisioned resources on the SQL Server Hosting server.
    • Compatibility with the next version of Windows Server
    • Fixes several SQL Server Resource Provider issues
  • Windows Azure Pack Web Sites (KB3051142)

I already posted some information on the Update Rollup 6 for Windows Azure Pack and System Center Virtual Machine Manager. I also want to highlight a change which was made in several different components in System Center and Windows Azure Pack. With UR6 you are now able to track Total Networking Usage Exposure rules in Management Pack. This change introduces two rules that target Hyper-V Hosts:

  • Total Incoming VNic Network traffic collection rule
  • Total Outgoing VNic Network traffic collection rule

These rules measure the total incoming and total outgoing traffic in Kilo Bytes per VNic per virtual machine in the following method:

For each VM:

  1. Enable Hyper-V Metering if it is not enabled.
  2. Run Measure-VM.
  3. Collect metering data for every remote address of “” or “::/0” per VNic.

By default, these rules run every hour. Users may opt to override this setting by overriding the IntervalSeconds property. These rules should not be run more frequently than every five minutes (300 seconds).

Behavior in previous versions: VMM did not measure data consumption. It measured only throughput.

Scale Windows Server Storage Spaces

System Center Operations Manager Management Pack for Windows Server Storage Spaces

Microsoft just released the System Center Operations Manager Management Pack for Windows Server Storage Spaces 2012 R2 to the public. This allows you to monitor your Storage Spaces deployments with Operations Manager.

You can download the Management Pack for Storage Spaces from the Microsoft Download Site.

Monitoring Scenarios

This Management Pack contains rules to monitor physical disk and enclosure state in storage spaces.
Health is calculated by the storage service and is passed to Virtual Machine Manager (VMM) using the Storage Management API (SM-API), and is in turn passed to Operations Manager (OM) through the OM connector for VMM.

Supported Configurations

This management pack requires System Center Operations Manager 2012 SP1 or later. A dedicated Operations Manager management group is not required.

The following table details the supported configurations for the Management Pack for Storage Spaces:

Configuration Support
Virtual Machine Manager 2012 R2 with Update Rollup 4 or later installed
Windows Server File Servers 2012 R2 with KB 3000850 (November 2014 update rollup) or later
Clustered servers Yes

Management Pack Scope

This management pack supports up to:

  • 16 Storage Nodes
  • 12 Storage Pools
  • 120 File Shares


The following requirements must be met to run this management pack:

  • Operations Manager Connector for Virtual Machine Manager installed and configured.
  • Configuring this connection will install the required VMM Management Packs.
  • Storage Spaces managed by Virtual Machine Manager
  • KB2913766 “Hotfix improves storage enclosure management for Storage Spaces” must be installed on the VMM server and file server nodes

VMM 2012 R2 Update Rollup 6 Azure IaaS Management

Generation 2 Virtual Machine in Service Templates and Managing Azure IaaS VMs in VMM with UR6

Microsoft just announced System Center 2012 R2 Virtual Machine Manager Update Rollup 6 with some highly requested features. Two of them are support for VMM Service Templates with Generation 2 Virtual Machines and managing Microsoft Azure IaaS Virtual Machines directly from the Virtual Machine Manager Console.

If you want to know more checkout that video:

System Center Logo

System Center 2012 R2 and Azure Pack get supports for SQL Server 2014 in Update Rollup 5

Microsoft just released System Center 2012 R2 Update Rollup 5, which includes a lot of new features and fixes. The update also brings support for SQL Server 2014 as a database server for most of the System Center 2012 R2 components. There will be support for the rest of the System Center components in the Update Rollup 6.

Supports SQL 2014 now:

Operations Manager
System Center Orchestrator
Service Management Automation
Service Provider Foundation
Virtual Machine Manager
Windows Azure Pack

Will support SQL 2014 in UR6:

Service Reporting
Service Manager
Data Protection Manager

For information check out the Microsoft System Center Team Blog.


Update Rollup 5 for System Center 2012 R2

Summary: Update Rollup 5 for System Center 2012 R2 and Azure Pack now available

Yesterday Microsoft released a new Update Rollup for System Center 2012 R2 and Azure Pack called Update Rollup 5. Update Rollup 5 has a lot of fixes and new features especially for Windows Azure Pack and System Center Virtual Machine Manager and Data Protection Manager.

Components that are fixed in this update rollup

  • Data Protection Manager (KB3021791)
    • Protect SharePoint with SQL Always on Configuration
    • Protect SharePoint Server, Exchange Server, and Windows Client workloads to Microsoft Azure by using Data Protection Manager
    • Support for multiple retention ranges for long-term backup on Microsoft Azure
    • Ability to transfer initial backup copy offline to Azure
    • Support for protecting Microsoft workloads that are hosted in VMware
    • Display missed SLA alerts on the Data Protection Manager console
    • Enhanced reporting with Data Protection Manager central console
  • Operations Manager (KB3023138)
  • Service Manager (KB3009517)
  • Virtual Machine Manager (KB3023195)
    • Differencing disk as an option in the Windows Azure Pack VMRole deployment
    • New operating system support
    • New ExplicitRevokeRequired parameter to control IP address management when Grant-SCIPAddress is used
    • Support for SQL Server 2014
    • Azure Site Recovery
  • Windows Azure Pack (KB3023209)
    • Adds support for SQL Governor in the SQL Server Resource Provider.
    • Adds administrator support for disabling native Network RP to allow for third-party network provider
    • Provides detail on Virtual Machine Memory type, Memory Startup and Maximum values in the Tenant Portal.
    • Fix to the Get-MgmtSvcRelyingPartySettings PowerShell cmdlet.
    • Fix to the issue of failing to establish Remote Desktop Connection to virtual machines put behind a Network Address Translation (NAT) device.
    • Fix to the Attached Network dialog box where the network entries in the list were disabled.

As you can see you get several new feature with Update Rollup 5. In Data Protection Manager you finally get support for SharePoint, Exchange and Windows Client workload protection to Microsoft Azure, and support for workloads running on VMware infrastructure. Virtual Machines Manager not only brings new features such as support for the Virtual Machine Manager Database to run on SQL Server 2014 it also includes a lot of fixes and a security update (3035898
MS15-017: Vulnerability in Virtual Machine Manager could allow elevation of privilege: February 10, 2015). Some of the most interesting fixes for me are:

  • DHCP extension: Currently, users have to manually update the DHCP extension after update rollup installation on all hosts. This is now automated. After the DHCP extension is replaced in the Virtual Machine Manager server’s installation folder to the latest version, Virtual Machine Manager automatically checks the DHCP extension against all hosts. If the host has an older version of DHCP extensions, the agent version status will be displayed as “DHCP extension needs to be updated in host properties on the Status page.” The user calls the update agent and updates the DHCP extension on the Hyper-V host in the same way that the user did this for the Virtual Machine Manager agent. Also, if the VSwitch is a logical switch, the status will be shown in “logical switch compliance.” The user can remediate the logical switch. This will also update the DHCP extension on the host.
  • Bare-Metal Deployment: If a physical computer profile is created by using vNic (and by using a virtual machine network) and if there are more than one hostgroup for a logical network that also has that virtual machine network when you add a host resource on the “Provisioning Options” page, the host profile will be displayed for only one host group. The profile won’t be displayed for the rest of the host groups.

For Windows Azure Pack also includes some important fixes and improvements on of the is in the Tenant Portal, users can now see details on Virtual Machine Memory type, Memory Startup and Maximum values.

Update Rollup 5 for System Center 2012 R2 brings a lot of new features and important fixes to the table, however before deploying the fixes in your production environment, I recommend to test the Update Rollup and maybe wait for some reports about issues from other users.