Problem:

Recently I noticed that clients had not received my changes to my SCCM 2007 software meeting rules, they still had rules that I had previously deleted and they had not received my new rules.

Solution:

After I lot of digging around I found the below error in the policypv.box log on the SCCM server.

CPolicySource::HandleMeteringPolicy: could not retrieve metering rule RULECHG from SQL

Problem:

Recently after running sysprep on a Windows 7 I was greeted with the message “Windows could not parse or process the unattend answer file for pass….”

I was not tring to use an unattended answer file at the time so a bit of a strange messge.

Problem:

When tring to perform a image capture of a Windows 7 client using a SCCM 2007 CD I received the message “Task Sequence: Image Capture Wizard has failed with error code (0x80004005)….”

Also when I tried to run Sysprep.exe manually from C:\Windows\System32\sysprep I received the error “A fatal error occurred while trying to sysprep the machine”

Problem:

Recently I noticed that one of my Deployment Management items holding Microsoft software updates had a little greyed out icon

Cause:

After a little digging I found that this icon meant that that the Deployment Management item contained Expired updates.

I recently spent a bit of time tring to create a Search Folder in SCCM 2007 that would show me all of the updates that were required by machines but had not yet been approved, to make selecting updates for deployment a little easier.

Here is how I did it in the end;

Recently I have been setting up Software Updates in SCCM 2007 to take over from an existing WSUS Server.

The setup went fine however I quickly noticed computers were not returning any status to the SCCM server and when I checked the report "Scan 3 - Clients of a collection reporting a specific state" I  found that ever computer had a "State Name" of "Scan Failed" and an "Error Status ID" of "11423"

SCCM 2007 has some great reports such as 14A and 14B which allow you to view how many and what computers are using a license from you volume license agreements, and what software you are under licensed for.

But first you will need to get you license details from Microsoft into SCCM. If you read the documentation on how to do this it pretty much says go to the Licensing poratl and download your licenses without an explanation of how, the below aims to explain this further.

Obtain Information from the Microsoft Licensing Portal

Problem:

For some time I had WSUS and Microsoft SCCM integrated together but installed on seperate servers, recently I wanted to break the integration so I removed the software update role from SCCM but I found that reporting on the WSUS server no longer worked, no machines had reported their status since SCCM was configured.

Cause:

Apparently when you integrate SCCM with an existing WSUS server by default SCCM takes over the reporting meaning the WSUS Server no longer records the status of machines etc.

This page will go though how to create a "Microsoft System Center Configuration Manager 2007" collection that contains all systems that do not have a specific exe file at a certain version present on any local drive.

I personally use this method to distribute software to systems that either do that have it already or have an old version installed.

The aim of this article is to configure Microsoft System Centre Configureation Manager 2007 SP1 or R2 to report on the locally installed printers, this in my case is very useful for reporting on printers installed and shared on our Print Server.

The fields we will report on are Netbios name of the computer, ShareName, Driver Name, Location, Port Name and Print processor but there are several other fields you can add.

This article assumes you already have SCCM up and running