SCVMM error 609 deploying from a Template – SOLVED

If you encounter that your SCVMM – System Center Virtual Machine Manager 2012 are giving you an error 609 when you try to install a new Virtual Machine from a template, you might want to ensure this settings:

  • If you have supplied a KMS key under the “Guest OS Profile” under Library\Profiles – Change it to a KMS key.

SCVMM Guest OS Profile

  • If you forgot to define the OS version of your Template server disk, do it under Library\Library Servers\

SCVMM Library Operating System

Then try to deploy your template again.


How to import existing computer objects to a SCCM 2012 collection with PowerShell

 Sometimes you need to add a lot of different already existing computer objects to a Configuration Manager collection.

 If you are lucky, these objects are placed in another collection or in a AD group, BUT – what if you just got a specific list of computers from someone ells that they would like to have updated with a certain application?

 Instead of adding the computer objects manually to the SCCM collection membership, you can add all object to an existing collection using Configuration Manager 2012 PowerShell.

 First: Create a collection in SCCM with the name you like

 Second: save the list of computers in a 1 column CSV file with the computer names only, remove all other information.


 Third: Run this script and change the CSV file name and path and SCCM Collection Name.

$computers = Get-Content “c:\temp\computers.csv” | foreach {Add-CMDeviceCollectionDirectMembershipRule -CollectionName “COLLECTION NAME HERE” -ResourceId $(get-cmdevice -Name $_).ResourceID}

 At Last: Run this PowerShell script in the Configuration Manager Console PowerShell windows – at your own risk –  and please test with a single computer object first!


I hope this tip will help you save some time.

Updating #FEP or #SCEP definitions gives error 0x80248014 – small fix required when using Windows Update as source

If you update Forefront Endpoint Protection from the agent shown below, it will sometime not update its definitions from Microsoft Update unless you have allowed the OS to receive updates from other products than Microsoft.


If you encounter something like the error code 0x80248014 below when updating FEP – Forefront Endpoint Protection or SCEP – System Center Endpoint Protection definitions, you need to make a small adjustment.

Microsoft Antimalware has encountered an error trying to update signatures.
New Signature Version:
Previous Signature Version:
Update Source: Microsoft Update Server
Update Stage: Search
Source Path:
Signature Type: AntiVirus
Update Type: Full
Current Engine Version:
Previous Engine Version: 1.1.10502.0
Error code: 0x80248014
Error description: An unexpected problem occurred while checking for updates. For information on installing or troubleshooting updates, see Help and Support.

Forefront Endpoint Protection cannot get Definition updates from Microsoft Update unless you check this box “Give me updates for other Microsoft Products when I update Windows”:



If SCCM 2012 show this Antimalware Policy configuration, the “Updates distributed from Microsoft Update” will not work until you have checked the box.


You can use a VB script to change it:

Save the text below in a file with a VBS extension.

Set ServiceManager = CreateObject(“Microsoft.Update.ServiceManager”)
ServiceManager.ClientApplicationID = “My App”
‘add the Microsoft Update Service, GUID
Set NewUpdateService = ServiceManager.AddService2(“7971f918-a847-4430-9279-4a52d1efe18d”,7,””)

Run the below command in an elevated command prompt: cscript optinMU.vbs


The reverse step is also possible with a simple alteration:

Set ServiceManager = CreateObject(“Microsoft.Update.ServiceManager”)
ServiceManager.ClientApplicationID = “My App”
‘remove the Microsoft Update Service by GUID


Hotfix and Update List for Windows Server 2012 and R2

Look here to find recommended updates regarding Hyper-V and Windows Server 2012 and R2 installations.

Windows Server 2012 R2

Hotfix and update list for Windows Server 2012 R2 failover clusers

Update list for Windows Server 2012 R2


Windows Server 2012

Hotfix and update list for Windows Server 2012 Failover clusters

Update list for Windows Server 2012

HP Proliant BL460c G8 PXE Boot Black screen SOLVED

When booting into Windows PE with the HP Proliant BL460C G8 server (and maybe many others), it will load WinPE and go into a black screen, nothing can be done.


This is because this server does not support WinPE 5.0 (yet) which Configuration Manager 2012 R2 is using.

To fix this problem use the Boot.wim file from a Windows Server 2012 media, and import this into Configuration Manager by using the Console and right clicking “Boot Images” choosing “import”. (Remember to place it on the Distribution Points allso)

Use this image and the servers can now boot again, the downside is that Configuration Manager 2012 R2 does not give full administration possibilities with the WinPE 4.0 image, so it is not possible to import drivers using the console. But none the less it was not nessesary in my case.

I hope it will help you in your struggle.

Update: HP have supplied the following links for this issue, but i have not tested any of them.

  1. Media Driver is missing
  2. Technical White Paper

How to upgrade from Windows 8 to 8.1 in your enterprise

If you are running Windows 8 Pro or some versions below, you can start “STORE” and upgrade to version 8.1 trough here. But in Windows 8.1 Enterprise, you do not have this feature.

Instead: Download the source files for Windows 8.1 that fits your Windows 8 version. Run this  command from the media “setup.exe /auto:upgrade”

This way it is possible to use Configuration Manager to control this upgrade by creating a package with these source files and an installation sequence that has the above commands inside.

You can read this blog for more telling information regarding this feature.

Have a nice day 🙂