You will find a summary of some new or updated KB articles for December that might come in handy for you belov.
SMS: Information on Scaling Software Metering
http://support.microsoft.com/kb/263023/en-us
SMS: Many 9224 Status Messages from Software Metering Server
http://support.microsoft.com/kb/304584/en-us
SMS: Mouse and Keyboard May Not Work in Remote Control Session to a Windows XP Computer
http://support.microsoft.com/kb/304591/en-us
SMS: Software Metering FoxPro Drivers Are Not Compatible with Windows Server 2003
http://support.microsoft.com/kb/307769/en-us
SMS: Systems Management Server 2.0 SP3 Support of Window XP Professional
http://support.microsoft.com/kb/321372/en-us
SMS: How to Manage the Deletion of Aged Status Messages
http://support.microsoft.com/kb/262034/en-us
SMS: How to Remove a Systems Management Server 2.0 Client
http://support.microsoft.com/kb/199078/en-us
SMS: How SMS Uses the SMS_DEF.MOF in Hardware Inventory
http://support.microsoft.com/kb/199318/en-us
SMS: Assigning Class and Instance Security Rights with the SMS User Wizard
http://support.microsoft.com/kb/199869/en-us
SMS: Distributing SMS Network Monitor
http://support.microsoft.com/kb/238919/en-us
SMS: “Table Corrupt” When Running DBCC Checkcatalog Against SMS Database
http://support.microsoft.com/kb/242953/en-us
SMS: Required Hotfixes Before Installing SMS 2.0 SP2
http://support.microsoft.com/kb/261931/en-us
SMS: Windows Performance Alerts Cannot Run if they Contain SMS Counters
http://support.microsoft.com/kb/315690/en-us
How to troubleshoot problems with software inventory in SMS 2.0 and SMS 2003
http://support.microsoft.com/kb/826849/en-us
How to identify SMS Executive process threads that are responsible for high CPU use on an SMS site server
http://support.microsoft.com/kb/837372/en-us
You receive a “Setup encountered an error and could not continue” error message when you try to upgrade an SMS 2003 Advanced Client to SMS 2003 Service Pack 1
http://support.microsoft.com/kb/893652/en-us
When you use the SMS 2003 Operating System Deployment (OSD) Feature Pack to install an image on an SMS client computer, the installation process is unsuccessful
http://support.microsoft.com/kb/923922/en-us
SMS: Troubleshooting server, component, and hierarchy issues
http://support.microsoft.com/kb/241001/en-us
And below a SMS 1.x and 2.x article for thoose of you who want to know want keywords that its possible to search for a bit fun in my opinion so I had to post it 
Happy reading
SMS: Keywords List for Searching
http://support.microsoft.com/kb/199435/en-us
Below you will find recently updated SMS KB articles.
If you would like to change the location of the client cache on your client you can do this with the following scipt. Where D: is where you want to set the cache location. Change for your own usage.
On Error Resume Next
Set oUIResource = CreateObject(“UIResource.UIResourceMgr”)
Set objCacheInfo = oUIResource.GetCacheInfo
nValueToSet = “D:”
objCacheInfo.Location = nValueToSet
Note: It will create a folder ccmcache under the folder you select. The folder does not need to exist but the drive needs to exist.
Today I had a customer who wanted new collections based on what service pack version the SMS clients had so I wrote them real quick for them. And I guess they are not the only once in need of this so ill post it here.
Clients pre SP3
Select Name, ClientVersion
From SMS_R_System
Where ClientVersion < “2.50.4253.3000″
SP3 Clients
Select Name, ClientVersion
From SMS_R_System
Where ClientVersion = “2.50.4253.3000″
Do you want to change the sms/sccm client cache size setting in your environment you can do this with a script. I will show you 2 examples of doing it.
If you would like to deploy it via SMS/SCCM with different sizes you can use the script below. Save it as a ex. setclientcachesize.vbs script and create a folder in our package area and create different programs for it.
On Error Resume Next
Set oUIResource = CreateObject(“UIResource.UIResourceMgr”)
Set objCacheInfo = oUIResource.GetCacheInfo
nValueToSet = wscript.arguments(0)
objCacheInfo.TotalSize = nValueToSet
Program values would for an example be like this. (Examples show the preferred size of the client cache in MB.)
setclientcachesize.vbs 1000
setclientcachesize.vbs 2500
setclientcachesize.vbs 5000
If you would like to set your client cache size to a static value a script like this would to it. Save the code and save it as a .vbs script, and deploy in preferred way. To change the size change the value 3000 to preffered value in MB.
On Error Resume Next
Set oUIResource = CreateObject(“UIResource.UIResourceMgr”)
Set objCacheInfo = oUIResource.GetCacheInfo
nValueToSet = 3000
objCacheInfo.TotalSize = nValueToSet
Have you ever wanted to get a visio drawing of your SMS environment and a documentsion of your site settings ? SMSmap is the answer !
In the latest Technet Magazine there was a great article about this written by Jeff Tondt. Its about a utility he created to make it easier to understand the configuration of the sms environment. You can read more about it here. Thanks Jeff its a great tool.
If you want to download it you can download the tool from here.
KB, SMS 2003 | stesch | 
December 25, 2007 23:52 | 
Comments (0) 
Subscribe 