Windows Server 2008 R2 Vulnerability with SP1

Windows Server 2008 R2 Service Pack 1 has a vulnerability, that cause Remote Desktop connection issues. Microsoft has released a Security Update (KB2667401) to resolve this issue. I have tested this and it works perfectly.

Download link: -

SQL Database Requirement for SCCM 2012

SQL Server 2008 SP 2 with Cumulative Update 9 CAS, Primary, Seconday Sites
SQL Server 2008 SP 3 with Cumulative Update 4 CAS, Primary, Seconday Sites
SQL Server 2008 R2 SP 1 with Culumative Update 6 CAS, Primary, Seconday Sites

TechNet :

Windows Management Intrumentation (WMI)

Windows Management Instrumentation (WMI) is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification.

Check whether WMI Repository is working?

1. Start -> Run -> "wbemtext.exe"
2. type the host name and confirm whether its working properly. (\\hostname\root\cimv2)\

How to regenerate WMI Repository: -

1. On the problematic host sopt the WMI Service ("net stop wmimgmt")
2. Rename the WMI Repository folder (C:\Windows\System32\wbem\Repository -> Repository.old")
3.Start the WMI Service ("net start wmimgmt")

Microsoft SysInternals Suite

This is a super tool to do your troublshooting stuff.

Eg: If you need to run any installation files remotly to a host, you can do the following.

1. Download the Microsoft SysInternals Suite from the Microsoft site
2. Extract the files to a path (D:\SysInternal\)
3. Open the command prompt ( Run as Administrator)
4. locate the "PSExec.exe" with the remote client UNC path and switch to cmd
("D:\Sysinernals\PSExec.exe \\ cmd")
5. After conenction gets established run the package file using a quite instalaltion method
(c:\FepInstall\FepInstall.exe quite)

Note: Check the Task Manager of the Remote PC for the running process to cross check

Windows Server 2008 Active Directory Backup

Use the following best practice for backing up Active Directory Domain Service: -

# Store OS files, AD Database (Ntds.dir) and SYSVOL on seperate volumes.
# Use System Stae regular backup for Domain controllers.
# Backups can be created on a dedicated External or Internal volume drive

Steps: -

*To create a System State Backup and store it store it on volume D, type:
wbadmin start systemstatebackup -backupTarget:d:

KMS Server Guide

Key Management service is a server which distributes windows 7 and Windows server 2008 activation licence from a centralized location.

Minimum Requirement:
25 Windows 7 / 5 Windows server 2008 clients

Installation steps: -

1. Install the KMS key on the Server
cscript c:\windows\system32\slmgr.vbs /ipk (kmskey>

2. Activate the KMS Key from Microsoft volume licencing servers
cscript c:\windows\system32\slmgr /ato

3. Restart the KMS service
net stop slsvc && net start slsvc


> KMS listens on TCP port 1688

> DNS Query: nslookup -type=all _vlmcs._tcp > kms.txt

> KMS Query (Licence key, Concurrent connections, Port no etc)
cscript slmgr.vbs /dli

ConfigMgr 2007 : Client Installation Problem

When you deploy SCCM client on host machines, you might come accross plenty of issues.

Here I am going to share some technical guide lines on Win HTTP 500 error.

If you get this error 1st thing you need to check is the Server IIS setting with logs.

1. Check whether WebDav account is configured on the "Default website" level and not with the "IIS Server" level.
(Please go through the snap to get the actual path)

2. Also make sure you check the IIS Server logs also