Posts in category Hans Vredevoort

Update Rollup for June 2014

The update rollup for June 2014 fixes the issues that are documented in the following Microsoft Knowledge Base (KB) articles:

  • ( )

    Update for data deduplication to improve scalability in Windows Server 2012 R2

  • ( )

    You are prompted for BitLocker recovery key when Windows enters the automatic repair process

  • ( )

    “Hyper-V Replica Cluster Broker is not installed” error when you replicate private clouds to Windows Azure

  • ( )

    DNS server crashes after you install update 2919355 for Windows Server 2012 R2.

  • ( )

    Connectivity lost between two nodes when a node reconnects to a Windows Server 2012 R2-based cluster

  • ( )

    CPrepSrv.exe process crashes or Failover Cluster Manager freezes when you validate storage in Windows Server 2012 R2

  • ( )

    Removed nodes can access shared disk resources unexpectedly in Windows Server 2012 R2

  • ( )

    You cannot stop the cluster service on a Windows Server 2012 R2-based failover cluster

  • ( )

    Storage spaces take a long time to move to another node after a node fails on a Windows Server 2012 R2 failover cluster

  • ( )

    STS passive sign-in fails when a sign-in request is sent to a Windows Server 2012 R2-based STS server through STS proxy

  • ( )

    AD FS device authentication is slow or fails in Windows Server 2012 R2

  • ( )

    Authentication failures and event 422 when AD FS STS servers and AD FS proxy servers are in Windows Server 2012 R2

  • ( )

    Long wait when you first open File Explorer in Windows RT 8.1 or Windows 8.1

  • ( )

    Virtual machine network fails when you start the second VM on a Windows Server 2012 R2-based Hyper-V server

  • ( )

    Windows Update does not download drivers for shared printers in Windows 8.1 or Windows Server 2012 R2

  • ( )

    Error occurs when you run Get-VirtualDisk|Get-ClusterResource cmdlet in Windows 8.1 or Windows Server 2012 R2

  • ( )

    OneDrive improvement update for Windows RT 8.1 and Windows 8.1: June 2014

  • ( )

    “0x80041013” error on a WMI provider in Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2

  • ( )

    “There was a problem” error when you redeem a promotional CSV token in Windows 8.1 or Windows Server 2012 R2

  • ( )

    Cannot select Chinese suggestion words from on-screen keyboard in Windows 8.1 or Windows Server 2012 R2

  • ( )

    Settings are migrated incorrectly after you refresh the system by using PBR in Windows RT 8.1 or Windows 8.1

  • ( )

    Logon UI crashes when you connect to a remote server that is running a Windows Server 2012 R2 Core installation

  • ( )

    Update to improve the OneDrive experience in Windows RT 8.1 and Windows 8.1

  • ( )

    Excel freezes when you convert Japanese characters in Windows

  • ( )

    Audit event ID 4661 triggers an invalid XML error in a Windows Server 2012 R2 or Windows Server 2008 environment

  • ( )

    “The CA certificate could not be retrieved, element not found” error occurs when the CA server host name is longer than 52 characters

  • 2936341( ) The WebClient service does not send cookies in Windows

Workaround for Updating a Hyper-V Generation 2 VM with KB2920189

During my last updating round, I noticed that a number of VMs in my Windows Azure Pack lab, had problems with security update KB2920189. Reading the Microsoft Security Advisory, it states that Microsoft is revoking the digital signature for four private, third-party UEFI (Unified Extensible Firmware Interface) modules that could be loaded during UEFI Secure Boot.

These UEFI (Unified Extensible Firmware Interface) modules are partner modules distributed in backup and recovery software. When the update is applied, the affected UEFI modules will no longer be trusted and will no longer load on systems where UEFI Secure Boot is enabled. The affected UEFI modules consist of specific Microsoft-signed modules that are not in compliance with our certification program and are being revoked at the request of the author.

Microsoft is not aware of any misuse of the affected UEFI modules. Microsoft is proactively revoking these non-compliant modules in coordination with their author as part of ongoing efforts to protect customers. This action only affects systems running Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 that are capable of UEFI Secure Boot where the system is configured to boot via UEFI and Secure Boot is enabled. There is no action on systems that do not support UEFI Secure Boot or where it is disabled.

I concluded that this update only targeted Hyper-V Generation 2 VMs with Secure Boot enabled, which was in fact the case for all VMs involved.

No matter how many times I tried, each update ended up failed. READ MORE »

Offline Update of Windows Azure Pack and 3rd Party Components

Recently I needed to update a Windows Azure Pack installation from RTM to Update 2. Because the servers had no Internet access, I needed an offline approach.

One way is to download the Windows Azure Pack 2013 Update 2 components, extract the files and install them one by one, thereby carefully checking that only the installed components are updated. It is very easy to make a mistake and add unwanted ones on a WAP portal server.


Because this approach only works for the WAP 2013 Update 2 components and doesn’t give you the partner components such as Gridpro and Cloud Cruiser, the offline Web Platform Installer approach is the best choice. In fact WebPI has been upgraded from version 4.6 to 5.0 containing Update 2 plus the 3rd party components.

  READ MORE » Speakers at TechEd 2014 NA and HASMUG

Fellow blogger at Marc van Eijk did an amazing job. At his first TechEd he delivered no less than three presentations. I went to every single one of them and was really proud to see him be so successful. Great job Marc!

Lessons Learned: Designing and Deploying the Windows Azure Pack in the Real World

Effortless Migration from VMware to Windows Server 2012 R2 Hyper-V

Transforming Bare Metal into Logical Switches Using Microsoft System Center 2012 R2 Virtual Machine Manager

Cameron Fuller and Maarten Goet realized that there was still a full day available and many MVPs were still hanging around in Houston on Friday. In cooperation with the Houston Area System Management User Group (HASMUG) they found enough sponsors to organize #TE14D5 or an informal community event offering two tracks: Enterprise Client Management (ECM) and Cloud and Datacenter Management (CDM).

Both Marc van Eijk and Hans Vredevoort delivered a presentation:

Windows Azure Pack Usage Service and the System Center Components that it depends on
by Hans Vredevoort

WAP showdown – VM Template vs. VM Role
by Marc van Eijk

Reported problems after installing Update Rollup 2 for DPM 2012 R2

Today I saw several users having problems with their Data Protection Manager 2012 R2 Server after installing KB2958100 which is the specific update for DPM in Update Rollup 2.

My advice is to postpone the DPM update and allow Microsoft to look into the user reports. Correction is quite complex and requires modifications in the DPM database.

See the thread for more details:

Update 2 for Windows Azure Pack (April 2014)

Along with Update Rollup 2 for System Center 2012 R2 (KB2932881), also Update 2 (KB2932946) for Windows Azure Pack was released. Update 2 fixes 10 known issues, amongst others a fix for the problem created with the Usage Collector in Update 1. Because WAP does not currently support rolling upgrades, it is necessary to schedule downtime for the WAP machines. Please be careful running this update in your production environment and expose them to a test environment first. There are so many components which depend on each other so take any precautions in the form of checkpoints (formerly called Hyper-V snapshots) and make sure you have recent full backups of your environment.

Although it is stated nowhere, you would be advised to first start with the System Center 2012 R2 Update Rollup 2 and run the documented SQL Scripts for VMM and SCOM first (important!) before you approve the Windows Azure Pack Update 2 installation. The SQL Script for VMM can be found in A reference to the path of the SQL Scripts for the SCOM OperationsManager and OperationsManagerDW databases can be found in


Veeam Rapidly Fixes Host Level VSS Backup for Hyper-V after KB 2919355 (WS2012 R2 Update)

Update (16 April 2014): see bottom of blog

I recently blogged about Windows Server 2012 R2 Update. As usual any update and certainly an update as large as this, has some risks. Therefore we usually advise to postpone Windows Updates, Update Rollups an Hotfixes and leave a couple of weeks before deploying updates in production. Always test in a lab if you can and if you can’t, keep an eye on the forums and the blogs from MVP’s specializing in the related technology.

Testing Host Level Hyper-V Backup

This weekend I came across a tweet from Richard Skinner who reported an issue related to Veeam Backup & Replication and Hyper-V Backup after applying the Windows Server 2012 R2 (Spring) Update. Meanwhile, Veeam had already confirmed the problem and was working frantically into the weekend to fix this nasty problem.

I decided to report a support case with Veeam as well, even though I’m only running it in a Windows Azure Pack lab. I found that the problem was easily reproducible, but only if VSS was enabled in the backup job.

The Problem: Using Hyper-V Checkpoints

When this selection is made as an alternative to Veeam’s default changed block tracking (CBT), the backup fails because it cannot deal with the file path of the checkpointed VHDX files. When you zoom in on the directory of a VM that is being protected, as soon as VSS kicks in, a checkpoint is made of the active disks. This causes the writes to be redirected from the VHDX to a corresponding AVHDX file which makes it possible for the backup software to take a clean and ‘frozen’ copy of the virtual hard disk. When the backup is ready, the written data to the AVHDX file is merged back into the VHDX file. Only briefly you’ll see n AutoRecovery.avhdx file created which is deleted when it is ready with the merge operation.

Important: Microsoft started to coin the term checkpoint in VMM. After Hyper-V had used the term Snapshot for a long time, this changed with Windows Server 2012 R2. We can now better distinguish between VSS snapshots and Hyper-V checkpoints. Backup software now uses Hyper-V checkpoints just as in Hyper-V Replica.

If you want to read more about the changed method of Hyper-V backup in Windows Server 2012 R2, please take a look at fellow MVP Aidan Finn’s post:


Boot from VHDX for Windows 8.1 Update

You may have seen my previous blogs on how to very quickly make your computer multi-boot into another operating system.

Now that Windows 8.1 Update and Windows Server 2012 R2 Update has been released, I’ll briefly repeat the steps.

  1. Download Convert-WindowsImage.ps1 and copy it to a temporary directory
  2. Start Windows PowerShell ISE in Administrator mode
  3. Run it with .\Convert-WindowsImage.ps1 -ShowUI
  4. Choose the required ISO file
  5. Choose the SKU
  6. Choose the VHD/VHDX Format, Type and Size
  7. Modify the Working Directory if necessary
  8. Type a name for the VHDX
  9. Optionally add an existing Unattend.xml file for further customization
  10. Hit Make the VHD!

You will see

My Windows 8.1 Enterprise VHDX was only 7.6GB small which came as a pleasant surprise.

The VHDX should still be mounted under a drive letter. If not, right-click the VHDX and mount it.
In my case I had ejected the mounted disks and manually re-mounted under drive F:

The following steps are needed to make your computer boot from the VHDX file:

  1. Open an administrative command prompt via WIN+X Command Prompt (Admin)
  2. Type bcdboot F:\Windows
  3. Type bcdedit /v to see the result in the Windows Boot Loader section

Taking the identifier you can change the description in your bootlist by typing:

bcdedit /set {545a3023-1918-11e2-bed1-bd8926e5c774} description “Windows 8.1 Enterprise with Update”

If you had configured Hyper-V on your Windows 8.1 computer, don’t forget to enable the hypervisor launchtype:

bcdedit /set hypervisorlaunchtype auto

Memory Leak on HP ProLiant Servers with NIC Teaming

HP recently published a customer advisory explaining that HP ProLiant servers running Microsoft Windows 2012 as well as Windows Server 2012 R2 and using Microsoft Windows NIC Agent 9.40 may report a memory leak up to 5Mb/hour.

The memory leak is caused by HP’s Microsoft Windows NIC Agent 9.40.

The problem can be easily observed in Task Manager under Processing as you can see in below diagram.

Windows Server 2012 R2 Update is Important

Today we received a note from Microsoft about the importance of Windows Server 2012 R2 Update which is coming to Windows Update on April 8th, 2014. For MSDN and TechNet subscribers this update is already available in the form of an ISO of Windows Server 2012 R2 with the Update included and a smaller collection of 6 updates for Windows 8.1 and Windows Server 2012 R2

In a blog post published on April 2nd, the Microsoft Windows Server Team explains the importance of this update as it provides an easy way to get up to date with the patches, bug-fixes, and improvements that Microsoft has provided since the release of Windows Server 2012 R2. For failover clustering, this update is certainly important as it contains many of the “hoster patches” that Microsoft has worked on in the past six months. The Update consists of six files:

Microsoft recommends to install the Update in this order:

  1. KB2919442
  2. KB2919355
  3. KB2932046
  4. KB2937592
  5. KB2938439
  6. KB2949621

I tried the update on my Windows 8.1 tablet. Because of the large size of KB2919355 (707MB) this update can take a while, so a little patience is required. Of course for multiple clustered Hyper-V hosts, the manual update method is not to be advised. If you have not yet tried Cluster Aware Updating (CAU), an automated cluster aware update tool included with Failover Clustering and available since Windows Server 2012, I strongly advise you to try this out. It not only allows you to install Windows Updates, but also hotfixes, drivers and firmware for your server hardware. Take a look at fellow MVP Didier van Hoye’s blog and video Hands on with Hyper-V Clustering Maintenance Mode & Cluster Aware Updating TechNet Screencast. Another good explanation can be found in chapter 8 of Windows Server 2012 Hyper-V Installation and Configuration Guide by Aidan Finn, Patrick Lownds, Michel Luescher and Damian Flynn.



Our Sponsors

Powered by