Despool.log, MP has rejected a policy request

On some SCCM sites I have seen thousands of errors in despool.log about rejected policy. In some cases these are caused by an non-approved client but on one customer site all clients were approved and there were still 3000-3500 errors in the status every morning.

All the errors came from one single GUID but in the log there was nothing about which Netbios name this client had so the solution was this query:

SELECT
   resourceID, netbios_name0, SMS_Unique_Identifier0
FROM
   dbo.v_R_System

Select all the results and paste them into Excel or something where you can make a search for the GUID you saw in the log.

I reinstalled the SCCM client on the error-burping server and the log was fine the day after!

Latest SCCM Client version is 4.00.6487.2157

The latest version of SCCM Client is right now 4.00.6487.2157 and to get there you need to grab the client installation files from a SCCM 2007 SP2 site and then add the R3 hotfix (KB977384).

I am right now pilot testing a huge enterprise deployment of KB977384 and it seems to go smooth and does not reboot the system during the patch/upgrade.

Technorati-taggar: Sccm,2007,sp2,r3,client,version,highest,latest,newest,what

Hardware Inventory fails after client is migrated from SMS to SCCM

When a client computer is upgraded from SMS 2003 to Configuration Manager 2007 the hardware inventory scan might fail to run on the upgraded client computer. Entries similar to the following appear in InventoryAgent.log on the client computer:

Unknown error encountered processing an instance of class CCM_System: 80041013
Collection: Failed to process mandatory data item for class: CCM_System. Cycle abandoned !!   InventoryAgent
Failed to process instances of CCM_System: 80004005

Solution: Restart the client computer after migration!

Technorati-taggar: Windows,2000,migration,no,hw,inventory,sms2003,sccm2007

Export SMS/SCCM data to CSV or TXT by using SQLCMD

I often do automation work and one nice tool when we talk about SMS or SCCM data is SQLCMD.exe.

So how do I use it?

1. First I build a SQL query that gives me the data I want. I user query editor to find the right fields and then modify with functions etc.

2. I then normally store the query as a SQL view to make it more easy to call for.

3. Then I create a CMD file with SQLCMD.EXE command that calls for the view I created in step 2. SQLCMD has a lot of nice switches to format the data. See above!

4. When I get out the data in the correct format and into the right place (like to a file share where some non sms/sccm team can reach it) I create a scheduled task to run the CMD file with a user that both has SQL access and write access to the output folder.

Questions? Leace a comment!

Technorati-taggar: SMS,SCCM,Automation,Export,Schedule,Automate,Data,SQL,View,txt,csv,Separator,SQLCMD,Tool,Guide,Help,Scheduled task,user,access