Search This Blog

Loading...

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:

image

If PowerShell remoting is not enabled you will se this:

image

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 http://go.microsoft.com/fwlink/p/?LinkID=234541.  For information about enabling GB18030 support, see http://go.microsoft.com/fwlink/p/?LinkId=234542.

image

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

select SERVERPROPERTY('Collation')

image

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!

image

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

image

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.

image

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.

http://larslohmann.blogspot.dk/2013/10/windows-81-and-windows-2012-r2-kms-keys.html

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

FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

Windows 7 Professional N

MRPKT-YTG23-K7D7T-X2JMM-QY7MG

Windows 7 Professional E

W82YF-2Q76Y-63HXB-FGJG9-GF7QX

Windows 7 Enterprise

33PXH-7Y6KF-2VJC9-XBBR8-HVTHH

Windows 7 Enterprise N

YDRBP-3D83W-TY26F-D46B2-XCKRJ

Windows 7 Enterprise E

C29WB-22CC8-VJ326-GHFJW-H9DH4

Windows Server 2008 R2 Web

6TPJF-RBVHG-WBW2R-86QPH-6RTM4

Windows Server 2008 R2 HPC edition

TT8MH-CG224-D3D7Q-498W2-9QCTX

Windows Server 2008 R2 Standard

YC6KT-GKW9T-YTKYR-T4X34-R7VHC

Windows Server 2008 R2 Enterprise

489J6-VHDMP-X63PK-3K798-CPX3Y

Windows Server 2008 R2 Datacenter

74YFP-3QFB3-KQT8W-PMXWJ-7M648

Windows Server 2008 R2 for Itanium-based Systems

GT63C-RJFQ3-4GMB6-BRFB9-CB83V

 

image

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)

image

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

image

image

Thursday, March 12, 2015

Hotfixes that breaks OSD – March 2015

And once again were have new updates breaking OSD http://larslohmann.blogspot.dk/2014/11/hotfixes-that-breaks-osd.html

Microsoft has updated the support case: http://support.microsoft.com/kb/2894518

The new problematic updates are:

3036493

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

3039976

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