June 2008 - Posts
Here is a new Version. not much has changed since the 1.4 version but this should be more stabel and it has some added Mini Mof Additions
Changes
- Added Local Share/ Printer and Admin tracking
- Added SQL 2005
- Added MDAC
- Added Support for Mcafee 8.5
- Fixed Issue with DPW and DOH tracking
I last updated this in January but never got around to posting it (Sorry bin buisy with ConfigMgr 2007)
Chris Stauffer
Sorry for the quick release between versions but i needed to address a few changes quickly so enjoy this new version
********************************************************************************************************************************************
One of the big complaints that I heard at MMS 2008 during the Client Health Check breakout (by Paul Thomsen) was that most solutions require yet another product and client. A key part of Microsoft’s solution (discussed in Paul’s session) is a tool by 1E . 1E uses their 1E Wakeup tool to monitor the client’s health when the Wakeup service isn’t being used. Unfortunately some of us can not afford to purchase everything we need to get ConfigMgr up and running, let alone another product. While the 1E Client Health features are beneficial, due to budgetary restraints some people cannot go that route just yet. So this is simply a free solution that can get you moving in the right direction. The direction being a more healthy ConfigMgr environment.
This tool will check the health of a client from the machine itself instead of from the server or collections. It is to be used in addition to the Client Health Checks. I will be updating the checks once I have SCCM Deployed in production. So I was thinking what if instead of a service that runs all the time why not just have a task sequence that fires off once or twice a day. This would allow you to do the same check without having to have something running all the time. So I created a script that will create a Scheduled task that will trigger a script to scan the system for problems.
This solution is meant for SCCM 2007 client but the script could be altered to use it on SMS 2003 as well.
Please read attached doc for full explination of how this works.
Note: this Script is very complex so I may have missed some things that it does. If so let me know and I will add it to the description. Note: all executable files have been renamed so that they can get though virus scanners without being striped so make sure that you rename things.
This application includes the following:
- check.mof
- This can be added to the Configuration.mof for tracking the usage of this toll in SCCM
- Client_Health_Check.ipf
- This is the SMS installer Script to allow you to make changes to the scripts before you compile it and deploy it to you clients
- Client_Health_Check_Local.doc
- Create_Task.vbs
- The script to create the Scheduled Task that will fire the Health Check task Script
- Health_Check.reg
- Just an example of the Reg keys that are created by the Script
- Health_Check.vbs
- The Script that will do all of the health checks and attempt to repair issues if you have any.
Please feel free to make any changes that you find necessary. If you make changes that are to fix bugs or make the script better as a whole please share them with me so I can release a new version for everyone to use.
Special Thanks To the following For code snippets:
- 1E And Richard Threlkeld For the original Health Check tool
- David Turner For cache expander Function
- DudeWorks For script functions from their original Health Check scripts
- Sherry Kissinger For Error checking And Function editing
- Authors of SMS 2003 Recipes (a must have book For any SMS admin)
- My beta testers. I’ve been asked by some to not mention there names so I will not.
- The rest know who they are and I will gladly give them recognition if they want it.
- The guys and gals on the MyITForum MSSMS list For chiming in when needed
- And anybody else that added their 2 cents :-)
Thanks
Chris Stauffer <><
At my job we Audit Remote Control so that if someone is somewhere they are not suppose to be there is a trail and proof.
I used John Nelson's tool to find the message codes I needed for SCCM
http://myitforum.com/cs2/blogs/jnelson/archive/2008/05/21/117428.aspx
Here are the Audit numbers for remote control functions in ConfigMgr 2007 SP1
The remote tools can be tracked by creating a new "Status Filter Rules" for the event ID's listed below. Set the Action to:
- Report to the Event log
- Replicate to the Parent Site
- Replication Priority: Medium
Then we use a tool that tracks the event ID's that this generates on the Central site. Since Status messages are passed up to the parent site you only need to create the Status Filter Rules on the central site.
|
MessageID |
MessageType |
Source |
Component |
Example Description |
|
30076 |
Audit |
SMS Provider |
Remote Tools Console |
User "Domain\User" at "XXX" initiated Remote Control with "XXX". |
|
30077 |
Audit |
SMS Provider |
Remote Tools Console |
User "Domain\User" at "XXX" ended Remote Control with "XXX". |
|
30084 |
Audit |
SMS Provider |
Remote Tools Console |
User "Domain\User" at "xxx" started a Remote Tools session with "xxx". |
|
30085 |
Audit |
SMS Provider |
Remote Tools Console |
User "Domain\User" at "xxx" failed to start a Remote Tools session with "xxx". Solution: Verify that the Remote Tools Client Agent is installed on the client. If the agent is installed and you cannot start a Remote Tools session, use the "Show Status" command on Control Panel, Remote Tools on the client to verify that the Remote Control Agent is listening on the right protocol. |
|
30090 |
Audit |
SMS Provider |
Remote Tools Console |
User "Domain\User" at "xxx" is ending a Remote Tools session with "xxx". |
In SMS 2.0 and 2003 there where additional numbers to be audited but i do not see those numbers in 2007 because the remote tool doesnt have the smae functionality that the old Remote.exe had so the other audit numbers may not be needed but i have attached the list incase you find that you need it.
Chris Stauffer <><
http://support.microsoft.com/kb/953649/en-us
Fix list
loadTOCNode(2, 'moreinformation');
For more information about the updates that are included in System Center
Configuration Manager SP1, click the following article numbers to view the
articles in the Microsoft Knowledge Base:
| Article number |
Article title |
| 942536
(http://support.microsoft.com/kb/942536/) |
You cannot move created objects into a folder or out of a folder if the
folder was created on a secondary site of System Center Configuration Manager
2007 |
| 942700
(http://support.microsoft.com/kb/942700/) |
The task sequence does not run on the protected branch distribution points
in System Center Configuration Manager 2007 |
| 944342
(http://support.microsoft.com/kb/944342/) |
Users cannot edit advertisements that they created in the Microsoft System
Center Configuration Manager 2007 Administration Console |
| 944542
(http://support.microsoft.com/kb/944542/) |
The "wake on LAN" feature does not work as expected if a site server uses a
non-daylight saving time zone in System Center Configuration Manager 2007
|
| 945306
(http://support.microsoft.com/kb/945306/) |
Execution requests may remain in the WaitingDisabled state after an
Operating System Deployment task sequence is executed in Configuration Manager
2007 |
| 945501
(http://support.microsoft.com/kb/945501/) |
Some users do not receive a program that is advertised to a user group in
System Center Configuration Manager 2007 advertisements |
| 945898
(http://support.microsoft.com/kb/945898/) |
The System Center Configuration Manager 2007 Offer Status Summarizer does
not process advertisement status summary data |
| 946518
(http://support.microsoft.com/kb/946518/) |
Inventory data is not completely removed after you delete a system resource
in System Center Configuration Manager 2007 |
| 946519
(http://support.microsoft.com/kb/946519/) |
Every even task sequence reports exit error code 183 if you advertise
several task sequences to a Systems Management Server client in System Center
Configuration Manager 2007 |
| 950531
(http://support.microsoft.com/kb/950531/) |
The Configuration Manager 2007 International Client Pack installation
process fails, and you receive a "Setup cannot start SQL Server to perform the
upgrade" error message |
| 949767
(http://support.microsoft.com/kb/949767/) |
When you use PXE to run a task sequence on a System Center Configuration
Manager 2007 client computer, the task sequence does not run |
| 949025
(http://support.microsoft.com/kb/949025/) |
Users who have sufficient instance rights cannot delete a collection in
System Center Configuration Manager 2007 |
| 949209
(http://support.microsoft.com/kb/949209/) |
After you use the Transfer Settings Wizard to transfer status filter rules
from one site to another in System Center Configuration Manager 2007, the
receiving site no longer processes status messages |
| 950653
(http://support.microsoft.com/kb/950653/) |
A software inventory operation does not work correctly in System Center
Configuration Manager 2007 if the inventoried file has invalid time attributes
|
| 950527
(http://support.microsoft.com/kb/950527/) |
"Windows Vista SP1, Windows Server 2008, Windows Server 2003 SP2, and
Windows XP SP3 are not listed as supported platforms for software distribution,
update management, or desired configuration management in System Center
Configuration Manager 2007 " |