A WordPress.com site dedicated to System Center and Cloud Management

Archive for January, 2015

MiCloud Website Now Migrated To Azure

Hello everyone,

As previously planned, I have now successfully migrated this site onto an Azure-based WordPress site. This means that the URL will change from http://AdinErmie.Wordpress.com, to the new URL of http://micloud.azurewebsites.net/.

This means you will need to re-follow this site based on the new URL, and re-share are articles you have previously shared.

I will be setting up a re-direct as well from the old URL to the new one.

Installing .NET Framework 3.5 on Windows Server 2012 R2 Fails with Error Code 0x800F0906

I encountered this issue while working on a project for a client, involving server build automation.

The client provided me with a copy of their Windows Server 2012 R2 ISO, which I was using in my SCCM Build and Capture task sequence. As you can see from the screenshot, the Task Sequence includes copying the SXS folder onto the local system, in order to be able to install .NET Framework 3.5 (using the -Source parameter).

Build And Capture TS - Scrubed

However, after the OS was installed, I noticed that the .NET Framework 3.5 and PowerShell options (which are also apart of the build) were not installed successfully. I checked, and confirmed that the SXS folder was still present (at the root of C:\). So, I attempted to run the PowerShell install command manually to see if/why it failed. I encountered the following error.

Install Error Results

This was odd, since it worked for my Build and Capture of Windows Server 2012. So, off to Google with the error code, and I came across this TechNet article which explained everything:


In a nutshell, there was a Security Update that was released that updated some of the .NET components (KB2966828). According to the TechNet article “If either of these updates are installed, you will run into the above issue if your server does not have access to the Internet to pull the updated components.”

The solution?

  1. Uninstalled the security update
  2. Install .Net Framework 3.5
  3. Reinstalled the update

Refer to the TechNet article for additional options/details. Hopefully this will help anyone that comes across this issue.

Patching Hyper-V Hosts with SCVMM 2012 R2 – Part 3: Update Baselines

In the last post we performed additional configurations. In this post we will create and configure Update Baselines to apply updates to our Hyper-V cluster.

Update Baselines

Launch the VMM console, if it isn’t already open, and navigate to Library > Update Catalog and Baselines Update Baselines.

Config Baselines - 01 - Update Baselines

You should see two built-in baselines named Sample Baseline for Security Updates and Sample Baseline for Critical Updates.

Config Baselines - 02 - Sample Baselines

Click on the Sample Baseline for Security Updates.

In the top menu, click Properties.

Config Baselines - 03 - Baseline Properties

In the Baseline Properties dialog, select the Updates menu from the left. This will list the updates that are a part of this baseline. From here you can Add/Remove Updates.

Config Baselines - 04 - Baseline Properties - Updates

Next, click on the Assignment Scope menu on the left. From here you can select host groups, host clusters, and computers to add to the baseline. After you have made your changes/assignments, click OK.

Config Baselines - 05 - Baseline Properties - Assigment Scope

You can also create your own Baseline, by clicking on Create > Baseline from the top menu.

Config Baselines - 06 - Create Baseline

Host Compliance

Now that we have a Baseline assigned to our Hyper-V Host, let’s examine the Host’s compliance.

Navigate to Fabric > Host Group > and select a Host.

Config Baselines - 07 - Fabric - Host Group

Config Baselines - 08 - Fabric - Host

Click on the Compliance button in the top menu, and then click Scan to initiate the compliance check.

Config Baselines - 09 - Host Scan

Once the Compliance Scan has completed, the console will show the Compliance Status for the Host(s) scanned.

In my Lab example, my Host is showing as “Non Compliant”.

Config Baselines - 10 - Scan Results

At this point, you can click on the Remediate button from the top menu. This will launch the Update Remediation dialog. Within this dialog, you can select the Update(s) to apply to Host(s) to bring it into compliance, and then click Remediate.

Config Baselines - 11 - Update Remediation

SCVMM will now initiate its automated workflow that will do the following:

  1. Start Maintenance Mode on the Host, which will Live Migrate the VMs to another node in the Hyper-V Cluster
  2. Install any updates required to become Compliant
  3. Reboot the Host
  4. Re-check if the Host computer is now compliant
  5. Stop Maintenance Mode on the Host
  6. Repeat all 5 steps on each node in the cluster

Config Baselines - 12 - Remediation Complete

This concludes this series on Patching Hyper-V Hosts with SCVMM 2012. As always, if this post helped you in any way, and you would like to show your appreciation, please rate it, comment on it, and share it with others. Also, feel free to contact me (via the About Me page) with requests for future articles.

Tag Cloud

%d bloggers like this: