Archive

Posts Tagged ‘TroubleShooting’

SCCM ConfigMgr 2012 Support Center Viewer, a useful tool, is available!

February 5, 2014 Leave a comment

system center

Hi SCCM Geeks!

Troubleshooting SCCM is not a so easy work. SCCM is centralized (SCCM Site roles) and distributed (managed clients). So it is not obvious to find the source of your issue.

SCCM generates lot of log files on the servers and the clients and studying them is so difficult and time consuming.

Microsoft offers us this great tool : SCCM ConfigMgr 2012 Support Center Viewer.

This tool allows you to collect and consolidate logs to use for troubleshooting purposes and  simulate some client actions like requesting client policies.

You can find further information in this blog.

Hope it helps!

Advertisements

Resolving “RegTask: Failed to send registration request message. Error: 0x87d00231” by repairing the Management Point

November 15, 2012 26 comments

Hi again!

When you install a new SCCM 2012 agent you can easily be a victim of this well known error “RegTask: Failed to send registration request message. Error: 0x87d00231”.

 

So, the client is installed successfully, but no information is collected on the SCCM console. This problem can cause another issue; the inactivity of the agents that were installed previously.

Searching for the right solution is not a so easy way because it depends on your case. In some posts or forums, they are speaking about certificates. However, in my case, the MP is configured to communicate using HTTP protocol.

In this article, I will describe the steps to follow in order to solve the problem. In my case the windows authentication module used by the MP was my issue. This article is not just applied on the case of the windows authentication module, you can try it to ensure that your MP is repaired correctly.

First of all, you have to understand the protocol of registering a new client :

  • The new client performs a CCM_POST to CCM_System_WindowsAuth on the MP.
  • The MP responds with a 401 as the request is anonymous and contains no security data.
  • The client requests a Kerberos ticket for http://MP_FQDN from Active Directory (e.g.http://SCCMMP.Contoso.com).
  • On obtaining the Kerberos ticket, the client performs another CCM_POST including the security data.
  • If the MP accepts the ticket then the client is authenticated and is considered to be trusted.
  • Whether the client is trusted or not, the MP executes the spUpdateClientRegistration stored procedure to update the database. If the client has authenticated properly, both the @ApprovalMethod and @IsIntegratedAuth parameters will be set to 1. If not, they are both set to 0. 

All these steps were described in this great article.

So I have tried to test the following request  http://mysccmserver/ccm_system_windowsauth/request  and bingo 403 error!

To have more details, I have consulted the IIS logs at %systemdrive%\Inetpub\Logs\LogFiles\W3SVC1\.

I have consulted my IIS manager and the SMS_MP_WindowsAuth Application under the default site was corrupted. In my case, this application was not associated to an application pool. I have created a new one but that does not solve my problem.

So, I have tried to uninstall and reinstall my MP. Unfortunately, the problem is still existing and the application is not repaired.

How to repair an MP? that is the question. Here you are a method that worked for me:

  • On the SCCM console select Administration Section
  • Select Site Configuration Group
  • Select Servers and Site System Roles
  • Select your Site System containing the right MP
  • Right Click on the MP role and select Properties
  • On General Tab, Select HTTPS Client Connection

This action will reinstall the MP and repair it. Please check the right SMS_MP_CONTROL_MANAGER log to verify if it is successfully repaired. If it is done, you have to redo the above steps to select HTTP as the Client Connection Protocol. This action will also reinstall and repair the MP.

Finally, I have Checked all Web Applications and the issue is solved. The Clients are registered and the inactive clients become active.

A nice document for SCCM Clients Troubleshooting

November 15, 2012 Leave a comment

Hi SCCM Geeks,

I have encountered recently a serious problem with my MP (Management Point) in the primary site. You can find some solutions like uninstalling IIS and reinstalling it with the MP.

But I have found during my search this great paper that learns us how to troubleshoot SCCM Clients. This nice present is offered by SolarWinds and developed by Matthew Hudson.

The big points treated are as follows:

  1. How to Telnet to the Ports
  2. Using Policy Spy and Client Spy
  3. WMI Errors Resolved
  4. Key Error Codes Defined
  5. Using Logs for Troubleshooting – How and Where to Find Relevant Data
  6. Top 5 Patch Downloading Issues Resolved
  7. WMI from Primary to Machine to Ensure Connection
  8. Certificate Errors Resolved
  9. Signature Verification Failure

I have really appreciated this document. You can download it form this link.

Categories: SCCM Tags: ,

Who is suffering from Active Directory Troubleshooting headache? : This tool is for you!

September 1, 2012 Leave a comment

Hi friends!,

When I have some AD troubleshooting issues, I apply generally some practices and follow some steps to diagnose the AD health like using dcdiag, repadmin and netdom tools.

You have also to consult different consoles (AD Users and Computers, AD Sites and Services, etc.) to verify some aspects like the AD topology.

It is, in some cases, a real nightmare and the Microsoft IT Environment Scanner is an excellent tool that could be used to do all diagnostic tasks.

You can download it here. this tool assesses your AD infrastructure by analyzing the following services:

  • Configuration of sites and subnets in Active Directory
  • Replication of Active Directory, the file system, and SYSVOL shared folders
  • Name resolution by the Domain Name System (DNS)
  • Configuration of the network adapters of all domain controllers, DNS servers, and e-mail servers running Microsoft Exchange Server
  • Health of the domain controllers
  • Configuration of the Network Time Protocol (NTP) for all domain controllers

After installation on any computer joined to the domain, launch it to discover its beauty.

To understand the different analyzed services, try to consult the detailed generated report.

A very useful tool, Enjoy it!

SCOM Agent Installation Failure

July 30, 2012 2 comments

Hi,

If you are encountering this error “Product: System Center Operations Manager 2012 Agent — Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).” when installing SCOM agent on a target machine, so obviously you have a problem in the registry.

This can occur when the agent is uninstalled previously improperly or another WMI based program has corrupted the registry.

To verify the issue, try to launch PerfMon and add a given performance counter.

The solution is to rebuild the performance counters. the complete procedure is described here.

However, try first to use a recovery tool like CCleaner to fix the issue. In my case that has worked efficiently.

NB: Don’t forget to backup your registry before any operation.

Finding SCOM Objects from IDs

July 28, 2012 Leave a comment

Hi,

In many cases, you have to troubleshoot SCOM problems by consulting the alerts and the event viewer for deeper information.

However, the objects are referenced by their GUIDs.

So how to retrieve their names?

The first manner to do it is by PowerShell. You have just to execute the following command:

Get-SCOMMonitoringObject -Id The-Requested-Guid.

The second manner is executing the following sql request (let’s suppose that the name of the SCOM database is OperationsManager and you are searching for agents names):

SELECT [NetworkName]
FROM [OperationsManager].[CS].[Agent]
WHERE [AgentGuid]=’The Guid’
GO

Finally, here you are an example by an image:

Image