What is SMS Server Tools?
SMS Server Tools is a group of tools that I have developed (Bernard White) to help manage Microsoft Systems Management Server 2003 (SMS 2003) environments. Initially they were for my use only, however after a bit of prompting from several of my peers if have been working to clean up these tools and make them usable for the community.
Currently all the tools included are command-line based, which offers the flexability of being easily integrated in to scripts or batch files and run as scheduled tasks. Each tool has been designed to be light weight and independant of components such as .Net Framework for portability.
What is the lastest version of these tools and how do I get them?
The lastest release is 0.2.2 and it is available here. The release notes are also available here.
Do I need to be logged on to my Primary SMS Server to run these tools?
No, you don't. This is one of the primary reasons and issues that I was tring to solve when developing these tools. Some tools or scripts require direct access to the Primary SMS Server so that they can read from the Site Database via a SQL connection. These tools don't, any access to the Site Database is done through the SMS WMI Provider. So they can be used from any workstation or user account that has access to the SMS WMI Provider. If unsure on what an SDK server is, see below.
What is the recommended configuration for these tools?
It is recommended that your SMS 2003 environment is service packed and patched to the lasted available version from Microsoft. At this time that is Service Pack 3 for Microsoft Systems Management Server 2003 which is available here http://technet.microsoft.com/en-au/sms/bb676774.aspx. You should also consider installing KB941395 or KB941214 available here http://support.microsoft.com/kb/941395 and http://support.microsoft.com/kb/941214 if upgrading to SMS 2003 SP3.
If running these tools on Windows XP, the minimum recommended Service Pack is SP2 for Windows XP.
If running these tools on Windows 2003, the minimum recommended Service Pack is SP1 for Windows 2003.
Is Microsoft System Center Configuration Manager 2007 Supported?
No. At this time these tool are only for use with Microsoft Systems Management Server 2003. In reality, they may or may not work when connected to a SCCM 2007 SDK server, however no testing has been done with SCCM 2007, so use at your own risk.
Do I need .Net Framework installed to run these tools?
No, you do not. These tools use Windows Management Interface (WMI) to manipulate SMS objects.
What's this about a SDK server?
An SDK server is any SMS Server with the SMS WMI Providers installed. This is normally installed on your first Primary Site Server / Central Site Server but can be installed on any Primary Site Server. An SDK server can not be a Secondary Site Server.
I have multiple SDK servers, which one do I connect to?
For the purpose of these tools, it is recommended that you connect to the first Primary Site Server / Central Site Server. If connecting to a Primary Site Server reporting to a parent Primary Site Server then access to configuration items that are inherited from the parent may be limited or inaccessable.
Is there a way to permanently set the SDK server for SMS Server Tools?
Yes there is. Added to release 0.2.1+, the default SDK server can be set by using the "--set sdk <serverName>" parameter on any of the package tools.
For releases older than 0.2.1, the SDK server is automatically configured via a wizard by the SMS Administrator Console MMC the first time it is opened. It can however be manually changed by setting a value in the Windows Registry.
As always, take care when editing the Windows Reigstry. Use the information provided in this article as a guide only. I accept no liability for damage caused directly or indirectly by changes that you make.
By setting the REG_SZ value "Server" under the key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\AdminUI\Connection" to the server name of the SDK Server. eg. \\server01\ will set the SDK server to server01. If you do not have the SMS Administrator Console installed on your workstation then this key will not exist, and will need to be manually created.

