Client Center for ConfigurationManager 2012

release notes

Alpha release
To Pass the Computername, open the URL with a Parameter:




1.Installing IIS 7.5 on Windows Server 2008 R2


2.Add the remote desktop services role





SCCM 2012 Prerequisite Checker from a command prompt and run primary site checks

1. Open a command prompt and browse to \SMSSETUP\BIN\X64 or ConfigMgrInstallationPath\SMSSETUP\BIN\X64.
2. Copy the files from following location and check
(I) In Windows Explorer, browse to one of the following locations:
(ii) Copy the following files to the destination folder on the other computer:
• prereqchk.exe
• prereqcore.dll
• basesql.dll
• basesvr.dll

3. Type prereqchk.exe and choose from the following command-line options to check requirements for a primary site installation.
Example : Prereqchk.exe /noui
Usage examples (optional options are displayed in brackets):
• prereqchk.exe /NOUI
• /PRI
Verifies that the local computer meets the requirements for the primary site.
• /SQL
Verifies that the specified computer meets the requirements for SQL Server to host the Configuration Manager site database.
• /SDK
Verifies that the specified computer meets the requirements for the SMS Provider.
• /JOIN ]
• /MP ]
• /DP ]
• /SEC
When you run the command-line, unless you use the NOUI option, Prerequisite Checker opens and starts scanning the specified servers using prerequisite checks applicable to the specified command-line options. Prerequisite Checker creates a list in the Prerequisite result section for any problems found.

4. Click an item on the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you install the site server, site system, or Configuration Manager console. You can also open the ConfigMgrPrereq.log file in the root of the C drive to review the prerequisite checker results.

sccm obsolete clients detail

Obsolete Clients

  1. When the SMS server finds that the client hardware ID has been updated or superseded by another machine and if multiple records are in place having the same hardware ID value for the machine, the older records are marked as obsolete.
  2. When the SMS server finds systems which are not sent the DDR from past xx days.
  3. When the SMS server finds systems which are not sent heartbeat more than xx weeks

 Manage Obsolete Clients

If you want to get accurate deployment success rate(%), it’s required to manage obsolete client on daily basis.

What I do normally:

Open SMS Administrator Console-> Expand Site Hierarchy-> Expand Site Settings->Expand Site Manitenance-> Select tasks-> open “Delete obsolete Client Discovery data” properties and enable it.

You need to delete data older than 1 days.

After that click on the “All Systems” collection and check whether any client still shows as obsolete. You can delete those  client from the console itself.

Note: During the deployment, package can be targeted to non obsolete clients only.