DotVBS | Windows Systems Management

Not long ago, I had to rename an SMS Site, here are the steps I used, from Jase T. Wolfe's blog . If an SMS Primary Site server, stop the SMS_SITE_COMPONENT_MANAGER, SMS_EXECUTIVE, SMS_SERVER_LOCATOR_POINT, and SMS_SQL_MONITOR services. If an SMS Secondary Site server, stop the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services. Open the "\SMS\inboxes\sitectrl.box\sitectrl.ct0" site control file. Search for the section "BEGIN_SITE_DEFINITION". Within this section, locate the third value, which is the site name. Change this value to the new site name, leaving the brackets intact. Do not change any other values. Save the "\SMS\inboxes\sitectrl.box\sitectrl.ct0" site control file. Open RegEdit and find HKLM\Software\Microsoft \SMS\Identification. Change the Site Name value to the new site name. Done!

Well, not quite, but the scripting guys would prob add that feature if they could. The script-o-matic is a priceless tool that helps create a variety of scripts. Including making WMI easy for the WMI Challenged. Download Scriptomatic from Microsoft .

Have you upgraded your SMS SQL 2000 installations yet? With the end of SQL 2000 support just around the corner, now is a good time to move if you havn't already. Check out Brian Tucker's blogcast on upgrading .

When examining your SMS Systems health, a few good counters to look at include the following: Memory Physical Disk Processor Access Methods Buffer Manager Cache Manager Databases General Stats Latches Locks Memory Manager SQL Stats SQL Settable Also take a look at the SMS operations Guide, which talks about the cache hit ratio .

I can't wait to try out reporting services in SCCM R2, for those of you with very large SMS and SCCM installations, this will hopefully bring a bit of relief from the old ASP SMS Web Reporting. One particular feature I'm eager to try out, is the conversion tool which will convert SMS Web Reports into Reporting Services Reports. Get the SCCM R2 Beta from Microsoft Connect