Last updated by at .

  • Microsoft Azure
  • Virtual Machine Manager

Tag: Virtual Machine Manager

System Center Logo

Update Rollup 3 for System Center 2012 R2 available

Today Microsoft released Update Rollup 3 for System Center 2012 R2. With the release Microsoft did not only fix some bugs they also added some features. Especially Data Protection Manager (DPM) and Virtual Machine Manager got some new features and fixes which will help especially in large scale Cloud and Virtualization deployments.

Data Protection Manager

Features

  • Scalable VM backup
    This update rollup improves the reliability at scale for Virtual Machine (VM) backups on Hyper-V and Windows Server 2012 R2 infrastructures. This feature is supported on both Cluster Shared Volumes (CSV) and scale-out file server (SOFS) storage configurations for VM.
  • Backup and consistency check windowImportant This feature is supported only for disk protection for VM data sources.This feature, configured through Windows PowerShell, enables specific time windows to restrict backup and consistency check (CC) jobs. This window can be applied per protection group and will limit all jobs for that protection to the specified time window.After the backup job has ended, all in-progress jobs can continue. Any queued jobs outside the backup and consistency jobs will be automatically canceled.This feature affects only scheduled jobs and does not affect specific jobs that are triggered by the user.Windows PowerShell script examples

    are available on Microsoft TechNet. These examples show how to use PowerShell cmdlets to create the backup and consistency window.

    Notes

    • This feature is not supported for tape or cloud protection jobs.
    • This feature is not supported for non-VM data sources.
    • Setting these windows is the same as running a Modify Protection Group workflow.
  • Support for synthetic fiber channel-to-tapeThis update rollup introduces support for the synthetic fiber channel-to-tape process. Follow the tape certification process

    for third-party tape devices when you use Data Protection Manager 2012 R2 and Windows Server 2012 R2.

 

Fixes

  • A backup of a mirrored SQL instance fails if the principal SQL instance that was first backed up is now the mirror.
  • DPM console crashes while a recatalog or “mark as free” operation is performed on an imported tape.
  • The MSDPM service crashes when protected data sources have long names.
  • The DPMRA service crashes during replica creation when the database name on one of the SQL instances matches or is a substring of a SQL instance name that is hosted on the protected server.

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Data Protection Manager

Virtual Machine Manager

Features

  • This update includes a Linux guest agent upgrade to support the following new operating systems:
    • Ubuntu Linux 14.04 (32-bit)
    • Ubuntu Linux 14.04 (64-bit)
  • This update also includes the following:
    • Host DHCP extension driver upgrade
    • Several performance improvements
    • Several Management Pack package improvements

 

Fixes

  • Total storage for a User role is reported incorrectly. For example, the User role can use only half of the allowed quota.
  • A host cluster update fails intermittently because of a locked job.
  • Virtual machine (VM) refreshers do not update highly available virtual machines (HAVMs) after failover to another node.
  • A cluster IP address for a guest cluster configuration in a Hyper-V Network Virtualization (HNV) environment is not updated correctly by using HNV policies during failover. For more information about this issue, see the following article in the Microsoft Knowledge Base:

    2981736

    The cluster IP address in an HNV environment is updated incorrectly during failover

  • Server Message Block (SMB) shares may not be usable by high availability (HA) workloads if they are also connected to stand-alone hosts.
  • Storage objects discovery does not occur on a Virtual Machine Manager server if the discovery item is too big.
  • A Virtual Machine Manager job that assigns network service backend connectivity fails.
  • Enable maintenance mode fails when you evacuate failed-state VMs.
  • The Virtual Machine Manager service cannot be restarted because of database corruption.
  • The ZH-TW language incorrectly appears in the tooltip of the VM Network icon.
  • Library refresher rewrites the alternative data stream on every file during every update.
  • For iSCSI hardware storage-based array, when the MaskingPortsPerView property option is set to “multi-port per view,” the target endpoint is not obtained as the port address.
  • The virtual hard disk (VHD) is left in the source folder after storage migration is completed.
  • The addition of a bandwidth limitation to an existing virtual private network (VPN) connection is not added to the generated script.
  • A VM that is attached to an HNV VM network loses connectivity when it is live migrated to another node in the failover cluster that is not currently hosting other VMs that belong to the same VM network.
  • VM network shared access is lost after a service restart or an update interval.
  • The Remove-SCFileShare command fails for a network-attached storage SMI-S provider.
  • Setting the template time zone to UTC (GMT +0:00) is incorrectly displayed as “Magadan Standard Time.”
  • The System Center 2012 R2 Virtual Machine Manager crashes when you add groups that contain the at sign (@) character in User roles.
  • VM deployment fails in a VMWare environment when you have virtual hard disk (.vmdk) files of the same size in your template.
  • Deployment of an application host on HAVMM fails and generates a 22570 error.
  • Live migration of an HAVM cross cluster creates a duplicate VM role in the target cluster.
  • An error occurs when you apply physical adapter network settings to a teamed adapter.
  • A VMM agent crashes continuously when the HvStats_HyperVHypervisorLogicalProcessor query returns a null value.
  • A host refresh does not update the VMHostGroup value of a VMWARE cluster after the cluster is moved from VCENTER.
  • VMM reports an incorrect Disk Allocation size for dynamic VHDs that are mapped to a virtual machine.
  • A VMM service template script application does not work for a self-service role.
  • VM creation fails if Virtual Machine Manager undergoes failover during the creation process.
  • The Access Status value of a file share is incorrect in the user interface.
  • The Virtual Machine Manager service crashes because of an invalid ClusterFlags value.
  • VMs cannot be deployed from a service template to a cloud across multiple host clusters (multiple datacenters).

More information can be found on the Microsoft Page for: Update rollup 3 for System Center 2012 R2 Virtual Machine Manager

Orchestrator and Service Management Automation

Fixes

  • When a runbook calls other runbooks, Service Management Automation (SMA) concatenates all the participating runbooks into a single script and then passes the script to the PowerShell Workflow engine for compilation. The resulting script may contain multiple signature blocks, and SMA receives a compilation error from the Powershell Workflow.
  • When child runbooks contain a signature block, the child runbooks cannot be compiled into inline runbooks. If there is more than one signature block, the resulting runbook will be corrupted.
  • Cmdlets should request information from the server, up to a limit on the number of records that are returned, and then request the next “page” of records, until all records are retrieved.
  • When a Windows PowerShell user uses the Set-SmaCertificate cmdlet, the user cannot receive private key information when he or she uses the Get-AutomationCertificate activity.
  • The Automation menu stops working in Administrator Portal, and you may notice that the Orchestrator ODATA API controller cannot return Modules data. Additionally, you receive the following error message:
    Microsoft.Data.OData.OdataInnerError
    Message: The file exists.
    TypeName: System.IO.IOException
  • Service Management Automation (SMA) resources are paged. The cmdlets have to evaluate the response from the web service for the presence of a continuation token and then make a sequence of ListNext web requests if a continuation token is present.
  • SMA may not return the latest job ID for the runbook. The Invoke-ConfiguratorRunbook activity will have the job ID when it calls the Start-SMARunbook cmdlet, and the job ID should be returned to the caller. This occurs because SMA does not return the most recent job for a runbook. This issue occurs occur in a multiple-run scenario. If the configurator passes the first run, this issue has no effect.
  • The Orchestrator Runbook Service (RunbookService.exe) may crash, and you receive the following error message:
    Application: RunbookService.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ServiceModel.CommunicationException
  • If a runbook is large enough to exceed the default Windows Communication Foundation (WCF) channel size, an exception occurs. This issue causes the job to be stuck in the “New” state.
  • When Update Rollup 2 is uninstalled, the connection properties to the instance of Microsoft SQL Server are cleared.

 

 

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Orchestrator

Service Manager

Fixes

  • The Microsoft Systems Center 2012 Operations Manager configuration item (CI) connector does not retrieve disk mount point information for the Service Manager database.
  • When a service request is created from a request offering in the console and when every user prompt is of the Simple List prompt type, the console shows options from all simple lists in each user prompt.
  • When you try to close a customized change request, you cannot close the change request, the task throws an error, and the close is not actioned.
  • MPSync job failures that are logged to the event log do not contain enough information to allow for a quick diagnosis of the problem.
  • All Service Manager workflows may stall when any invalid XML characters (control characters) are used in a work item property.
  • Using the “Set First Response or Comment” task in a service request creates a “Private” flag that cannot be used for evaluation in a notification action log or a user comment update. This behavior occurs because the private flag is undefined.
  • If the configuration management database (CMDB) is down (that is, if it is offline or unable to connect because of network issues) at the time that the Health service is restarted and if the CMDB continues to be offline for a long time, the Health service may enter an unrecoverable state even if the database comes online again later.
  • Configuration Manager Connector synchronization may stop after Update Rollup 2 for Service Manager 2012 SP1 or Update Rollup 6 for Service Manager 2012 R2 is applied. This issue occurs when the connector tries to synchronize malformed or incomplete software version information from the Configuration Manager database.

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Service Manager

Operations Manager

Fixes

  • A deadlock condition occurs when a database is connected after an outage. You may experience this issue may when one or more HealthServices services in the environment are listed as Unavailable after a database goes offline and then comes back online.
  • The Desktop console crashes after exception TargetInvocationException occurs when the TilesContainer is updated. You may experience this issue after you leave the console open on a Dashboard view for a long time.
  • The Password expiration monitor is fixed for logged events. To make troubleshooting easier, this fix adds more detail to Event IDs 7019 and 7020 when they occur.
  • The Health service bounces because of high memory usage in the instance MonitoringHost: leak MOMModules!CMOMClusterResource::InitializeInstance. This issue may be seen as high memory usage if you examine monitoringhost.exe in Performance Monitor. Or, the Health service may restart every couple of days , depending on the load on the server.
  • The Health service crashes in Windows HTTP Services (WinHTTP) if the RunAs account is not read correctly.
  • Windows PowerShell stops working with System.Management.Automation.PSSnapInReader.ReadEnginePSSnapIns. You may see this issue as Event ID 22400 together with a description of “Failed to run the Powershell script.”
  • The PropertyValue column in the contextual details widget is unreadable in smaller widget sizes because the PropertyName column uses too much space.
  • The update threshold for monitor “Health Service Handle Count Threshold” is reset to 30,000. You can see this issue in the environment, and the Health Service Handle Count Threshold monitor is listed in the critical state.
  • An acknowledgement (ACK) is delayed by write collisions in MS queue when lots of data is sent from 1,000 agents.
  • The execution of the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails with the error “Subquery returned more than 1 value.”
  • The MOMScriptAPI.ReturnItems method can be slow because a process race condition may occur when many items are returned, and the method may take two seconds between items. Scripts may run slowly in the System Center Operations Manager environment.
  • When you are in the console and click Authoring, click Management Pack, click Objects, and then click Attributes to perform a Find operation, the Find operations seems unexpectedly slow. Additionally, the Momcache.mdb file grows very large.
  • A delta synchronization times out on SQL operations with Event ID 29181.
  • Operations Manager grooms out the alert history before an alert is closed.
  • The time-zone settings are not added to a subscription when non-English display languages are set. Additionally, time stamps on alert notifications are inaccurate for the time zone.
  • Web Browser widget requires the protocol (http or https) to be included in the URL.
  • You cannot access MonitoringHost’s TemporaryStoragePath within the PowerShell Module.
  • The TopNEntitiesByPerfGet stored procedure may cause an Operations Manager dashboard performance issue. This issue may occur when a dashboard is run together with multiple widgets. Additionally, you may receive the following error message after a time-out occurs:
    [Error] :DataProviderCommandMethod.Invoke{dataprovidercommandmethod_cs370}( 000000000371AA78 )
    An unknown exception was caught during invocation and will be re-wrapped in a DataAccessException. System.TimeoutException: The operation has timed out.
    at Microsoft.EnterpriseManagement.Monitoring.DataProviders.RetryCommandExecutionStrategy.Invoke(IDataProviderCommandMethodInvoker invoker)
    at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Operations Manager



SCVMM Bare-Metal Fails

Add drivers to SCVMM Bare-Metal WinPE Image

A long time ago I wrote a blog post on how you can use System Center Virtual Machine Manager Bare-Metal Deployment to deploy new Hyper-V hosts. Normally this works fine but if you have newer hardware, your Windows Server Image does may not include the network adapter drivers. Now this isn’t a huge problem since you can mount and insert the drivers in the VHD or VHDX file for the Windows Server Hyper-V image. But if you forget to update the WinPE file from Virtual Machine Manager your deployment will fails, since the WinPE image has not network drivers included it won’t able to connect to the VMM Library or any other server.

You will end up in the following error and your deployment will timeout on the following screen:

“Synchronizing Time with Server”

SCVMM Bare-Metal Fails

If you check the IP configuration with ipconfig you will see that there are no network adapters available. This means you have to update your SCVMM WinPE image.

First of all you have to copy the SCVMM WinPE image. You can find this wim file on your WDS (Windows Deployment) PXE Server in the following location E:\RemoteInstall\DCMgr\Boot\WIndows\Images (Probably your setup has another drive letter.

WDS SCVMM Boot WIM

I copied this file to the C:\temp folder on my System Center Virtual Machine Manager server. I also copied the extracted drivers to the C:\Drivers folder.

After you have done this, you can use Greg Casanza’s (Microsoft) SCVMM Windows PE driver injection script, which will add the drivers to the WinPE Image (Boot.wim) and will publish this new boot.wim to all your WDS servers. I also rewrote the script I got from using drivers in the VMM Library to use drivers from a folder.

Update SCVMM WinPE

This will add the drivers to the Boot.wim file and publish it to the WDS servers.

Update WDS Server

After this is done the Boot.wim will work with your new drivers.

 

 

 

 

 



Cisco Microsoft

Cisco and Microsoft Announce Sales and Go-to-Market Agreement

At the Worldwide Partner Conference 2014 Cisco and Microsoft announced a multi-year sales and go-to-market agreement designed to modernize data centers through the delivery and acceleration of integrated solutions. This will focus on bringing a deeper integration between the datacenter technologies of both companies. This includes Cisco UCS and Nexus products as well as Microsoft’s CloudOS solutions based Windows Server, Hyper-V, System Center, SQL Server and Microsoft Azure.

Highlights:

Go-to-Market:

  • Cisco and Microsoft agree to a three-year go-to-market plan focused on transforming data centers through the delivery of integrated solutions for enterprise customers and service providers.
  • In year one, the companies will focus on six countries — the United States, Canada, UK, Germany, France, and Australia — with expansion to additional countries in the following years.
  • Cisco and Microsoft will align partner incentive programs to accelerate solutions selling via mutual channel partners.
  • Cisco and Microsoft sales teams will work together on cloud and data center opportunities, including an initial program focused on the migration of Windows 2003 customers to Windows 2012 R2 on the Cisco UCS platform.

Integrated Solutions:

  • Integrated solutions will focus on private cloud, server migration, service provider, and SQL Server 2014
  • Cisco technologies to include Cisco UCS, Cisco Nexus switching, Cisco UCS Manager with System Center integration modules, and Cisco PowerTool.
  • Cisco-based integrated infrastructure solutions will include FlexPod with NetApp and Cisco Solutions for EMC VXPEX.
  • Microsoft technology includes Windows Server 2012 R2, System Center 2012 R2, PowerShell, Microsoft Azure and SQL Server 2014
  • Cisco Application Centric Infrastructure and Cisco InterCloud Fabric to be integrated in the solutions in future releases

Source and More information: www.streetinsider.com

As you may know I am a Microsoft MVP and a Cisco Champion and I really like doing project with Cisco Hardware since they do a lot of integration with the Microsoft Stack especially System Center and PowerShell. In my opinion this could be a strong partnership and will make life of a lot of people a lot easier.



Azure Site Recovery

Microsoft Azure Site Recovery Preview

Microsoft today announced the preview of Disaster Recovery to Azure called Microsoft Azure Site Recovery. This also replaces HRM (Hyper-V Recovery Manager). Microsoft Azure Site Recovery (ASR) allows you to orchestrate disaster recovery to a second site or directly to Azure.

Microsoft ASR

Both solutions use Microsoft on-prem technology like Windows Server Hyper-V Replica and System Center Virtual Machine Manager and you can start using them via the Microsoft Azure Management Portal.

In addition to enabling Microsoft Azure as a DR site in multiple geographies, this preview also includes an impressive list of features for enabling virtual machine replication to Azure:

  • At-Scale Configuration
    You can configure the protection and replication of VM settings in a private cloud and configure and connect on-prem networks with Azure Networks. Those VM’s are then only replicated to customer-owned and managed geo-redundant Azure Storage.
  • Variable Recovery Point Objective (RPO)
    This feature provides support for near-synchronous data replication with RPOs as low as 30 seconds. You can also retain consistent snapshots at desired frequency for a 24-hour window.
  • Data Encryption
    VM Virtual Hard Disks can be encrypted at rest using a secure, customer-managed encryption key that ensures best-in-class security and privacy for your application data when it is replicating to Azure. This encryption key is known only to the customer and it is needed for the failover of VM’s to Azure. Simply put: All of this service’s traffic within Azure is encrypted.
  • Self-Service Disaster Recovery
    With ASR you get full support for DR drills via test failover, planned failover with a zero-data loss, unplanned failover, and failback.
  • One-Click Orchestration
    ASR also provides easy-to-create, customizable Recovery Plans to ensure one-click failovers and failbacks that are always accurate, consistent, and help you achieve your Recovery Time Objective (RTO) goals.
  • Audit and Compliance Reporting with Reliable Recovery
    DR testing and drills can be performed without any impact to production workloads. This means you get risk-free, high-confidence testing that meets your compliance objectives. You can run these non-disruptive test failovers whenever you like, as often as you like. Also, with the ability to generate reports for every activity performed using the service, you can meet all your audit requirements.

ASR does not only help you in terms of Disaster Recovery, it also allows you to quickly and easily migrate your Virtual Machines to Azure or create a new dev environment.

Check out the ASR session at TechEd 2014 and Brad Andersons blog about the release of the Azure Site Recovery Preview.

Once you’re ready to see what ASR can do for you, you can check out pricing information, sign up for a free trial, or learn more about the product specs.

 

 



Savision Whitepaper

On Demand Webinar: VMM Fabric and Cloud Management by MVP Thomas Maurer

Together with Savision I worked on a whitepaper about System Center Virtual Machine Manager Fabric Management and Resource Pooling. After the whitepaper was released I also did two webinars where I presented the information from the whitepaper about Fabric and Cloud Management with Virtual Machine Manager.

Now the webinar recording is available for an on demand online.

On Demand Webinar

On Demand Webinar: VMM Fabric Management and Resource Pooling by MVP Thomas Maurer

 



Savision Whitepaper

Whitepaper and Webinar “VMM (fabric) Management and Resource Pooling”

One of the most challenging things during the shift to Cloud Computing is to manage Fabric Resources efficiently. Together with Savision I have worked on a whitepaper in which it is outlined how Fabric resource like Compute, Storage and Network can be managed efficiently and how System Center Virtual Machine Manager provides a solution to build a datacenter abstraction layer.

The whitepaper is focused on building a datacenter abstraction layer of your fabric resources, self-service and service deployment. If you would like to know more about it, join our webinar.

Register for EU webinar

Register here for the EU webinar on Webinar “VMM (fabric) Management and Resource Pooling” by MVP Thomas Maurer – 7th May 3.00pm CEST (English)

Register for US webinar

Register here for the US webinar on Webinar “VMM (fabric) Management and Resource Pooling” by MVP Thomas Maurer – 8th May 2.00 pm EDT (English)

We’re looking forward having you logged in!

Btw you can download the Whitepaper right here:

Download the Whitepaper

Download the Free Whitepaper on “VMM (fabric) Management and Resource Pooling” by MVP Thomas Maurer

If you have questions join the webinar or feel free to comment.



PowerShell NetAdpater Advanced Property

Hyper-V Network Virtualization NVGRE: No connection between VMs on different Hyper-V Hosts

I have worked on some project with Hyper-V Network Virtualization and NVGRE, and today I have seen an issue with Encapsulated Task Offloading on some HP Broadcom Network adapters.

 

Issue

I have Hyper-V Hosts running with 10GbE Broadcom Network Adapters (HP Ethernet 10Gb 2-port 530FLR-SFP+ Adapter) with driver version 7.8.52.0 (released in 2014). I have created a new VM Network based on Hyper-V Network Virtualization using NVGRE. VM1 is running on Host1 and VM2 is running on Host2. You can ping VM2 from VM1 but there is no other connection possible like SMB, RDP, HTTP or DNS. If you are using a NVGRE Gateway you can no even resolve DNS inside those VMs. If VM1 and VM2 are running on the same Hyper-V host everything between those VMs works fine.

Advanced Driver Settings

If you are using Server Core, which you should by the way, you can use the following command to check for those settings:

PowerShell NetAdpater Advanced Property

 

Resolution

The Broadcom Network adapters have a feature called Encapsulated Task Offloading which is enabled by default. If you disable Encapsulated Task Offloading everything works fine. You can disable it by using the following PowerShell cmdlet.

After that connection inside the VMs started to work immediately, no reboot needed.