SCCM Client to Wait due to Conflicting Records

If you have an SCCM client that's installed correctly, but seems to not be performing any usual SCCM actions, check the the "ClientIDManagerStartup.log" log file (located under %WIN%\SYSTEM32\CCM\LOGS).

Look for the following lines in the "ClientIDManagerStartup.log" log file:

RegTask: Client is not registered. Sending registration request...
RegTask: Client registration is pending.
Client is pending registration. Sending confirmation request...
Server requested reset. Restarting client registration
Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.

This indicates the Hardware ID for the SCCM client has recently changed, and there are multiple records for the client in the SCCM database. The SCCM client will not perform any actions until the "conflicting records" issue is resolved.

To resolve the issue, an SCCM administrator must open the SCCM console and merge the multiple records together into a single record. Once this is completed, the client will update its records and start performing normal tasks.

Client Inventory is not showing in DATABASE

I recently had a problem with client inventory data not being present in the SCCM database. I was making a query to find machines running Windows XP with Service Pack 3, and it only reported back 6 or 7 clients,Knowing that a lot more had the service pack installed.

I checked the logs on some of my clients and they seemed to report both hardware and software inventory just fine, and sent it to my management point. I checked the logs on my SCCM server and every time i recieved the inventory report from clients I got an SQL error saying that the rows in my table could not be updated. This lead me to believe that the client had never been in the table, and as suspected, my OperatingSystem table (the table that contains data about a client operating system, and in this case what service pack is installed) only had a few machines present. Somehow my management point had stopped inserting data into the tables.

I resolved this issue simply by removing and re-installing my management point role on my SCCM server, but it lead to several hours of head-scratching!

WMI Reapir

Steps to rebuild WMI manually
1. Assure your account has administrative privilege
2. Type the command in a command prompt window (or paste below commands on the window).

net stop winmgmt /y



c:
cd %windir%\system32\wbem
if exist %windir%\system32\wbem\repository.old rmdir /s /q repository.old
rename %windir%\system32\wbem\repository repository.old
for /f %i in ('dir /b *.dll') do regsvr32 /s %i
for /f %i in ('dir /b *.mof *.mfl') do mofcomp %i

Blogger Buzz: Blogger integrates with Amazon Associates

Blogger Buzz: Blogger integrates with Amazon Associates

Pending packages/Task Tequence troubleshooting

To resolve this issue is to modify the PkgStatus table on the central site server SQL database, and then refresh the affected distribution points.Run The SQL query for each affected distribution point.

update pkgstatus set Status = 2 where id = '< package ID >' and sitecode = '< site code >' and type = 1

update pkgstatus set SourceVersion = 0 where id = '< package ID >' and sitecode = '< site code >' and type = 1

Note:
Microsoft stated that this issue can randomly occur in larger SCCM environments with large packages and slow WAN links, and they are unable to exactly pinpoint the problem due to its random nature

SCCM console get hanged in monthly patch cycle

- Run WBEMTest and connect to Root
- Click 'Open Instance', enter __ProviderHostQuotaConfiguration=@ and click OK
- Locate the MemoryPerHost property and double click it to bring up the editor
- Note the current value, replace it with 402653184 and click Save Property
- Locate the HandlesPerHost property, note the current value, set it to 16384 and click Save Property
- Click Save Object and then Exit WBEMTest