Search This Blog

Friday, March 27, 2015

Detect if PowerShell remoting is enabled

In some scenarios I need to now if PowerShell remoting is enabled on the local host, this can be done in many different ways, but this is an easy way to do it:

Start PowerShell on the local machine and enter the command Enter-PSSession -ComputerName localhost

If PowerShell remoting is enabled you should see no errors:


If PowerShell remoting is not enabled you will se this:


Very easy way to determine and identify if remoting is enabled.

Monday, March 23, 2015

SCCM SQL database not using right Collation

When installing SCCM 2012 R2 you might see this error:

Required SQL Server Collation

Configuration Manager requires that you configure your SQL Server instance and Configuration Manager site database (if already present) to use the SQL_Latin1_General_CP1_CI_AS collation, unless you are using a Chinese operating system and require GB18030 support.  For information about changing your SQL Server instance and database collations, see  For information about enabling GB18030 support, see


You can se the current SQL server Collation using this query in SQL Server management Studio

select SERVERPROPERTY('Collation')


To change server collation run setup.exe from the SQL Installation media again (in quite mode). In my example the command is:

D:\setup /q /action=rebuilddatabase /INSTANCENAME=MSSQLSERVER /SQLCollation=SQL_Latin1_General_CP1_CI_AS /SQLSYSADMINACCOUNTS=domain\administrator

SQL 2012 DVD is mounted at drive D

Rebuild System Databases

Before doing this please be aware that all user databases you might have will be dropped, so this will primary make sense on a dedicated SCCM SQL server without data!


Let check the collation again and yes it has been changed.


And now we don’t see any error about collation, but notice the new warnings about SQL configuration, that wasn’t there before.

When changing the collation all previously SQL configuration was lost, so you have to do this again.


Monday, March 16, 2015

Windows 7 and Windows 2008 R2 KMS keys

Still working with Windows 7 and Windows 2008 R2 Smile

Not that long ago I needed the KMS keys for Windows 2008 R2, but realized that I only had posted the keys for Windows 2012 and Windows 8.1 on this blog.

Time to change this.

The default KMS keys used for volume licensing editions of Windows 7 and  Windows Server 2008 R2 are:

KMS Client Setup Keys

Operating system edition

KMS Client Setup Key

Windows 7 Professional


Windows 7 Professional N


Windows 7 Professional E


Windows 7 Enterprise


Windows 7 Enterprise N


Windows 7 Enterprise E


Windows Server 2008 R2 Web


Windows Server 2008 R2 HPC edition


Windows Server 2008 R2 Standard


Windows Server 2008 R2 Enterprise


Windows Server 2008 R2 Datacenter


Windows Server 2008 R2 for Itanium-based Systems




You can use the KMS keys if for example you have a task sequence were you some times need to deploy with a MAK key and in other scenarios need a KMS key.

The keys are also used by VAMT from the AIK, of course activation will only work if a KMS server is available.

The Windows® Automated Installation Kit (AIK)


When you choose to configure a host for KMS activation these are the keys VAMT will use.



Thursday, March 12, 2015

Hotfixes that breaks OSD – March 2015

And once again were have new updates breaking OSD

Microsoft has updated the support case:

The new problematic updates are:


MS15-030: Description of the security update for Remote Desktop protocol: March 10, 2015


MS15-030: Vulnerability in Remote Desktop protocol could allow denial of service: March 10, 2015


Don’t we all just love this returning problem (or maybe not) Sad smile

Thursday, March 5, 2015

System Center Endpoint Protection Update

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

Revised February 2015 anti-malware platform update Endpoint Protection clients

The update are available from Windows update ad 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, unless you use the scepinstall.exe in this package, this is because CU4 only includes the October 2014 SCEP update.

Identify Whether SCCM 2012 R2 CU4 has been installed

Your System Center Configuration Manager 2012 R2 must have Cumulative Update 1 or later installed.

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 it will report version


Tuesday, March 3, 2015

Identify Whether SQL 2012 SP2 Cumulative Update 4 (CU4) has been installed

I often need to know the current version of a SQL 2012 installation to determine if it need an update.

This KB includes a number of ways to do the work How to determine the version and edition of SQL Server and its components

Latest update is Cumulative Update 4 for SQL Server 2012 SP2

Here is an excellent place to find the latest updates for your SQL servers Microsoft SQL Server Version List

So lets se the results after updating to Cumulative Update 4:

You will be able to find CU4 (hotfix 5559) in installed updates together with the SP2 update and previous Cumulative Updates installed:


Before updating I only had update 5556 which is CU3:


Let try some of the other ways to identify current version.

Method 1:

Start SQL Server Management Studio


In the object Explorer window you will se the current version just right of the server name:

After updating the version is 11.0.5569 for CU4:


Before updating the version was 11.0.5556 for CU3:


Method 2:

Look at the first few lines of the Errorlog file for you current instance. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQL.11.instance\MSSQL\LOG\ERRORLOG

As you can see, this entry gives all the necessary information about the product, such as version, product level, 64-bit versus 32-bit, the edition of SQL Server, and the OS version on which SQL Server is running.


And the file before updating to CU4:


Method 3:

As the last thing lets try the query (in SQL Server Management Studio)

Select @@version

When you execute the query you will see the same information as in method 2: