Search This Blog

Friday, July 31, 2015

VSphere client unable to connect to vCenter 6

You might be unable to connect from your vSphere client to your new vCenter 6.0 server:

The vSphere Client could not connect to xxxx. Connecting to Virtual Center is not supported by this client. You can use it to connect only to ESX server.


But wait a moment we know that this should be possible vSphere 6 - Clarifying the misinformation

In order to make the connection work you must upgrade your vCenter client version:

In this example the client not working is


You can install a newer client from the vCenter installation media:


Or download the latest from here:


At this point in time both ways will give you version (10-07-2015) and you will be able to connect as explained in the first link:


Group Policy settings in Windows 10

Microsoft has released new Excel spreadsheet with information's about the Group Policy settings in Windows 10.

You can filter settings so you are able to see only new policies or for example only Microsoft Edge settings.

Group Policy Settings Reference for Windows and Windows Server


These spreadsheets list the policy settings for computer and user configurations that are included in the Administrative template files delivered with the Windows operating systems specified. You can configure these policy settings when you edit Group Policy Objects.

To use the new policies in an enterprise environment you need to copy the new admx/adml files from a Windows 10 installation (C:\Windows\PolicyDefinitions) to your AD domain central store.

See more info here:

Create a central Store for GPO administrative templates

ADMX files available

Thursday, July 30, 2015

WinPE versions

Ok we are booting into Windows PE but how do we determine / identify the version.

First of all we need command support in the WIM file (F8), then in the command prompt we can use the command ver

From Windows 10 PE (10):


From Windows 8.1 PE (5.0):


But for 5.1 and 5.0 this command will show the same value.

If you start registry editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinPE\version you will find the real Windows PE version:

From Windows PE 10:


From Windows PE 5.1:


This leads to the following table:

Windows PE ver command Registry Based on (from Wikipedia)
2.0 6.0.6000 2.0 Vista
2.1 6.0.6001 2.1 2008
2.2 6.0.6002 2.2 2008 SP2
3.0 6.1.7600 3.0 Windows 7
3.1 6.1.7601 3.1 Windows 7 SP1
4.0 6.2.9200 4.0 Windows 8
5.0 6.3.9600 5.0 Windows 8.1
5.1 6.3.9600 5.1 Windows 8.1 update 1 (manually update)
10 10.0.10240 10.0.10240.16384 Windows 10

For older versions please take a look at this article on Wikipedia

Windows 10 Assessment and Deployment Kit (ADK) available

Microsoft has also released a new version of the AD for deployment and it is supported on SCCM 2012 R2 SP1.

On SCCM 2012 R2 SP1 you must uninstall ADK 8.1 and then installed ADK 10.

After installation, you can create new custom boot images or update the default ones. If you need USMT, you must also update that package, but be aware of this issue

Fix for Windows 7 deployments failing after upgrading to Windows ADK 10

If installing ADK 10 before upgrading to SCCM 2012 R2 SP1, setup will take care of updating default boot images and the USMT package, so a lot easier.


Download kits and tools for Windows 10
What's new in kits and tools
Windows 10 deployment tools

Tuesday, July 28, 2015

Is this the Windows 10 background in a music video :-) Nice work

Sorry just couldn't resist Smile


Windows 10 KMS keys and KMS Server update

The default KMS keys used for volume licensing editions of Windows 10 has been published:

KMS Client Setup Keys

Operating system edition KMS Client Setup Key

Windows 8.1 Professional


Windows 8.1 Professional N


Windows 8.1 Enterprise


Windows 8.1 Enterprise N


Windows Server 2012 R2 Server Standard


Windows Server 2012 R2 Datacenter


Windows Server 2012 R2 Essentials



These keys are used by VAMT (from Windows 10 ADK) and are the default keys used by Windows Enterprise editions, these type of keys need a KMS infrastructure.


When you choose Automatically select a KMS client key (GVLK), VAMT will use the KMS keys shown in the beginning of this text:


Client with KMS key (type GVLK):


In order for the KMS server to work with Windows 10, this update is necessary

Monday, July 27, 2015

Windows Profile versions

When using roaming profiles and Windows 10 you will notice that it creates V5 (version 5) profiles by default (.V5 extension)

You might ask why version 5 but there is a good explanation:

Windows 8 and Windows 8.1 could create V3 and V4 if a hotfix were used and a change was made to the registry.

Windows 8.1: Incompatibility between Windows 8.1 roaming user profiles and those in earlier versions of Windows

Windows 8: Incompatibility between Windows 8 roaming user profiles and roaming profiles in other versions of Windows

Registry change (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ProfSvc\Parameters\UseProfilePathExtensionVersion = 1 (DWORD))


This will give the following summary:

Windows versions Profile Versions created
Windows XP/2003 V1 (no extension used)
Windows Vista/2008 .V2
Windows 7/2008 R2 .V2
Windows 8/2012 .V2 or V3 if hotfix and registry change used
Windows 8.1/2012 R2 .V2 or V4 if hotfix and registry change used
Windows 10/2016 .V5

Example Userstate folder/share:


Friday, July 24, 2015

Task Sequence environment not found

Update 05-08-2015

Unfortunately Cumulative Update 1 still have this problem:

Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2

Original Post

I have written before about the problem with software updates that require multiple restarts:

Hotfixes that breaks OSD

Hotfix that breaks OSD

Microsoft support article about the  issue:

Task sequence fails in Configuration Manager if software updates require multiple restarts

Everybody was of course very happy about the new feature in System Center Configuration Manager 2012 SP2 and R2 SP1:

Beginning with System Center 2012 Configuration Manager SP2, on the options tab, you can configure this task sequence to retry if the computer unexpectedly restarts. For example, a software update installation that requires a restart


But wait there are more trouble ahead, apparently this feature only works for Windows 8 and 8.1.

Some of my customers had told me that it was not working and today I had the time to test it in my lab.

The result is that I can confirm that it is not working with Windows 7, what a shame.

Even with the option selected you will get the error Task Sequence environment not found when a software update requires multiple restart.


Thursday, July 23, 2015

System Center Endpoint Protection Update

Microsoft has released an update for the System Center Endpoint Protection client.

May 2015 antimalware platform update for Endpoint Protection clients

The update are available from Windows update as explained here:

Anti-malware platform updates for Forefront Endpoint Protection/System Center Endpoint Protection will be released to Microsoft Update.

Newly deployed clients from Configuration Manager will need this update as well.

After installation a restart may be required.

Update offered from Windows Update:


This also means that the update is available for Configuration Manager clients:


After updating the client will report version


Before updating my client reported which is the version from SCCM 2012 R2 SP1:


Monday, July 20, 2015

Problem with driver import and SCCM 2012 R2 SP1

I saw a new problem today with a driver for a Fujitsu Esprimo E700.

The driver in question had a size of 215 MB before importing to SCCM.


First thing to notice is that Validate Driver Information takes very long time:


And there are lots of INF files in this driver:


Creating the driver package also ended with a long wait period.

After import the driver package had a size over 12 GB (very big)!


It looks like SCCM creates a new Folder for every INF file and copies all contents to every folder.

I am not the only one with this problem:

SCCM 2012 R2 SP1 - Driverpack bug

The Trouble With Tribbles … I Mean Drivers

The tip from Jason about using Import-CMDriver instead of the console, saved my day (thanks Jason Smile):

First import the Drivers with Import-CMDriver (simple example):

$DrvPath = "\\sccm12r2\source\DriversImport\Fujitsu\Esprimo E700"

$CatName = "Fujitsu Esprimo E700"

$infFiles = Get-ChildItem -Path $DrvPath -Recurse -Filter "*.inf"

Import-Module ($Env:SMS_ADMIN_UI_PATH.Substring(0,$Env:SMS_ADMIN_UI_PATH.Length-5) + '\ConfigurationManager.psd1')

$PSD = Get-PSDrive -PSProvider CMSite

Set-Location "$($PSD):"

$Category = Get-CMCategory -Name $CatName

if(-not $Category) {

$Category = New-CMCategory -CategoryType DriverCategories -Name $CatName


foreach($driverFile in $infFiles) {

Import-CMDriver -UncFileLocation $driverFile.FullName -ImportDuplicateDriverOption AppendCategory -EnableAndAllowInstall $True -AdministrativeCategory $Category



Then in the console select all Drivers from the category you just added and add them to a Driver Package:


Create a New package:


Name the Package and specify UNC path for the driver source:


Click OK:


And now my driver package has the size of 215 MB:



Let hope this will fixed in a future update Smile

Hotfix that breaks OSD

Just a fast warning:

Yet another hotfix released that breaks SCCM OSD

Microsoft has updated the article that explains the problem with multiple reboots:

Luckily if you have upgraded to SCCM 2012 SP2 or SCCM 2012 R2 SP1 you are able to fix this issue using the option Retry this step if computer unexpectedly restarts and setting the number of retries that make sense in your situation:

And it actually works Smile (at least on Windows 8, 8.1, still seems to be problems with Windows 7)


Original post about this problem

Thursday, July 16, 2015

Has SCCM 2012 R2 SP1 been installed?

Service Pack 1 for  System Center Configuration Manager 2012 R2 has been released for some time now see more here Announcing the availability of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2

Also note that it can be a little bit of a problem to get the right update file so read the FAQ System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1: Frequently Asked Questions, and to further support this note that the installation says System Center 2012 Configuration manager SP2, even though we now we are upgrading to 2012 R2 SP1 Smile


But let’s take a closer look at how to determine the installation status of SP1.

After upgrading to System Center Configuration Manager 2012 R2 SP1, you will be able to identify the update as shown here.

First let us take a look at the console, after the update the console reports version 5.0.8239.1000 and Site version is now also displayed in about box:


The console reported version 5.0.7958.1604 before updating which is 2012 R2 CU5.


The Console update is also listed in Control Panel under Programs and Features:


The previously installed updates to the console also no longer shows up in Installed Updates after upgrading.

The site will also report version 5.00.8239.1000 after the update to SP1.


Before upgrading the site reported 5.00.7958.1000 for SCCM 2012 R2:


Normally we check the registry to see if a cumulative update has been applied.


CULevel is back at zero as expected after upgrading to SP1:


CULevel reports 5 after CU5 has been applied.

Before updating CULevel reported 5 because Cumulative Update 5 was installed.


I did expect the Cumulative update to be gone in installed updates but this is not the case in my lab (Installed Updates in Control Panel).


The client will report 5.00.8239.1000 after it has been updated.


With all components updated:


Before updating the client reported 5.00.7958.1604 for 2012 R2 CU5 client


SP1 includes an update for SCEP.

Which means that scepinstall.exe file in the ConfigMgr install folder “.\Program Files\Configuration Manager\Client” will be updated to version


Before updating the version was which is the version from 2012 R2 CU5 (February 2015 SCEP )


And finally as reported by the client after update