Last updated by at .

  • Microsoft Azure
  • Virtual Machine Manager

Tag: Microsoft

centos hyper-v

Best Practices for running Linux on Hyper-V

Sometimes I just need my blog as a reminder or a database to find something in a few months so this is exactly one of this blog posts. Microsoft has a TechNet article where they describe the best practices for Linux VMs running on Hyper-V 2012 or Hyper-V 2012 R2. The article is a list of recommendations for running Linux virtual machine on Hyper-V.

Right now they have 4 recommendations on the list (Source Microsoft TechNet):

  • Use static MAC addresses with failover clustering.
  • Use Hyper-V-specific network adapters, not the legacy network adapter.
  • Use I/O scheduler NOOP for better disk I/O performance.
  • Add “numa=off” if the Linux virtual machine has more than 7 virtual processors or more than 30 GB RAM.

 



System Center Logo

SCVMM 2012 R2 Error 23317 When You Try to Apply Changes on VM That is Using Shared VHDX Disk

A customer of mine had a issue when he tried to change properties of Virtual Machines in System Center Virtual Machine Manager 2012 R2 which use shared VHDX, which were not created with VMM. The properties do he wanted to change had nothing to do with the Shared VHDX it self. He tried to set the availability set for these Virtual Machines.

The Error in SCVMM is the following:

Error (23317)
The operation Change properties of virtual machine is not permitted on a virtual machine that has shared virtual hard disks.

Recommended Action
The operation Change properties of virtual machine is not permitted on a virtual machine that has shared virtual hard disks.

Stanislav Zhelyazkov (Microsoft MVP) blogged about this in October 2013. The solution is pretty easy and is called PowerShell. Just do the modification but do not apply it. Use the script view in Virtual Machine Manager to get the code which would run behind the scene.

For example:

Remove all the things you don’t need and run the script:



System Center Universe Europe 2013

System Center Universe Europe – The Microsoft CloudOS Event you shouldn’t miss

In about 6 weeks System Center Universe 2014 opens it doors and if you want to learn and network about Microsoft CloudOS or Microsoft Datacenter solutions, you should definitely book this event.

System Center Universe Europe 2014

Register now for System Center Universe 2014 in Basel Switzerland. Date: September 17-19, 2014 Location: Basel-Switzerland Venue: Congress Center Basel Conference Language: English

SCU Europe 2014 is the successor of System Center Universe DACH 2013 in Bern, Switzerland. SCU DACH 2013 was a very successful community event, and got a lot of great feedback.

Never seen such a great event before. Thanks again for the great work and organization!

SCU DACH Is a potential succesor of MMS for people in Europe

Lineup was great.

Incredible high skilled speakers there. Loved it!Thanks to the organizators to bring up so many good speakers.Nice location, good beer and food and awesome people.

Absolut excellent! The entire team did a great job! Thank you for that.

Great job organizing this event. I would love to come back next year.

Extreme good organized, highly skilled speakers, very cool people and the content was amazing. Loved it and will be back next year for sure.

The Content

System Center Universe

This time System Center Universe Europe 2014 will be even bigger, with more speakers, more sessions and more experts. This time in for tracks there are around 60 breakout sessions around topics for the Microsoft Datacenter, Private Cloud, Public Cloud and Hybrid Cloud, focusing on technologies like:

  • Microsoft Hyper-V
  • System Center 2012 R2
  • Windows Server 2012 R2
  • Configurations Manager
  • Windows 8.1
  • BYOD
  • Software Defined Storage
  • Software Defined Networking
  • Microsoft Azure
  • Windows Intune
  • PowerShell
  • Windows Azure Pack
  • and a lot more…

For event attendees, only the best is good enough! SCU Europe will host the crème-de-la-crème of the Windows Server and System Center Community from all over the world, including a variety of Microsoft Most Valuable Professionals (MVPs) and Microsoft employees. Take the opportunity to learn from the best and most experienced experts and community leaders in the Microsoft System Center Cloud and Datacenter Management area. In addition to classic breakout sessions, attendees also have the opportunity to discuss specific topics with several experts in small groups. So make sure you bring your questions and problems with you to discuss them with the experts. A real added value!

More Value

SCU Experts

So you will have a lot of great content and real word examples in the breakout sessions. But this is not the only benefit. In this three days you will have a lot of opportunities to talk to experts and other attendees to share some real world experience.

As in SCU DACH 2013, SCU Europe 2014 will included lunch and some networking parties so there is enough time to share experiences and knowledge.

The Location

Messe Basel

The location is different this time. Last time SCU DACH 2013 was hosted in Bern Switzerland. This time, since the location had to grow, the event will be held in Congress Center in Basel Switzerland. Basel is a great city with a lot of things to see around the event it self. With it’s two train stations and it’s airport, Basel is a perfect location for an international conference like this. You can reach the event location from anywhere in about 15 minutes.

SCU Location Map Basel

Conclusion

Well if I would have the summarize all this, I would find the following reasons to go to the SCU Europe 2014:

  • A huge number of Microsoft Cloud and Datacenter Management Experts from all over the world.
  • Around 60 breakout sessions
  • Great networking opportunity, meet the who is who in the Microsoft Cloud and Datacenter Management stack.
  • 26 Microsoft MVPs
  • Speakers from Microsoft
  • Great organization
  • First Class catering
  • Perfect location
  • Networking Party
  • Perfect for a city trip in the heart of Europe
  • Cheap price CHF729 (599.88 Euro) for a three day pass including lunch and Networking party
  • exhibition & networking area with a lot of different vendors showing there products
  • Easy to reach (Airport, Train or Car)

So make sure you reserve the date and register for System Center Universe Europe 2014:

System Center Universe Europe 2014

Register now for System Center Universe 2014 in Basel Switzerland. Date: September 17-19, 2014 Location: Basel-Switzerland Venue: Congress Center Basel Conference Language: English



Veeam Task Manager for Hyper-V

Veeam Task Manager for Hyper-V

Veeam just released the Veeam Task Manager for Hyper-V. The Task Manager for Hyper-V is a lightweight tool which doesn’t need to be installed you can just run it from a USB stick for example. The Veeam Task Manager for Hyper-V visualizes real-time performance data from your Hyper-V host and each child VM running on that host. You will be able to view what resources the parent partition is using and at the same time see what compute performance your virtual machines are using. This will make your life much easier if you need to see what resources are consumed on the Hyper-V host.

You can get more information about the Veeam Task Manager for Hyper-V on Mike Resslers (Microsoft MVP and Product Strategy Specialist for Veeam) blog post: Announcing: Veeam Task Manager for Hyper-V

And you can download it directly from the Veeam Website for free: Veeam Task Manager for Hyper-V



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.

 

 

 

 

 



RemoteFX

GPU Requirements for RemoteFX on Windows Server 2012 R2

If your are planning a VDI (Virtual Desktop Infrastructure) deployment with Windows Server 2012 R2 Hyper-V  and you want to use physical graphics power with RemoteFX for your VDI machines fore example for CAD applications, you might wonder which cards are recommended and supported. Back in November 2013 Derrick Isoka (Microsoft Program Manager) wrote a blog post about recommendations and here is a quick summary.

RemoteFX GPU Requirements

To make use of RemoteFX with GPU acceleration on Windows Server 2012 R2 you require a compatible graphic card.

Most likely, the servers hosting the RemoteFX workloads will be located in a datacenter and as such, we recommend using passively cooled, server class graphics cards. However, it’s also acceptable to use a workstation card for testing on small deployments depending on your needs.

However the minimum requirements for the graphics cards to be used with Hyper-V RemoteFX are:

  • Direct 11.0 or later
  • WDDM 1.2 driver or later

DirectX and WDDM

There is some other point to this, in Windows Server 2012 R2 provides support for DirectX 11.0, DirectCompute and C++ AMP. Most of the graphics cards do support OpenGL 4.0 and OpenCL 1.1 or later, however these APIs are currently unsupported by RemoteFX in Windows Server 2012 R2.

Hardware and Driver Support

To find a graphics card also make sure you check the Windows Server Catalog.

RemoteFX Compatible GPUs

Microsoft did some tests and showed some of the results on the Remote Desktop Services blog.

RemoteFX Cards

  1. Best: These are server class cards, designed and certified for VDI workloads by hardware vendors like NVIDIA and AMD. They target the best application performance, experience, and virtual machine densities. Some of the cards are particularly recommended for designer and engineering workloads (such as Autodesk Inventor or AutoCad).
  2. Better: These are workstation class cards that provide acceptable performance and densities. They are especially capable cards for knowledge worker workloads (such as Microsoft Office or Internet Explorer).
  3. Good: These are lower-end cards that provide acceptable densities knowledge worker workloads.

Source: Microsoft

Performance and Scale

This is important, Microsoft also points out that GPU speed and memory, the performance and scale of your VDI deployment also depends on additional factors such as CPU, Storage and Network performance.