SMS 2003 supports two different types of clients, the legacy client (for Windows 98 and NT4.0SP6) and the Advanced client (for Windows 2K, XP and 2K3). Client software can be installed in various methods. Most installation methods (Client Push, Logon Scrip) allow you to configure the client to perform an automatic discovery of its assigned site code.

Here is a description of the site code discovery process for the Advanced client.

• Client will contact AD to find the site code based on the boundaries created in SMS.
• If the AD schema has not been extended to accomodate the publication of SMS information or no SMS information is found in AD, the client will fall back to querying a WINS server to find a Server Location Point (SLP) to retrieve the site code.
• If the /SLP switch is set with the Capinst.exe, the client will bypass the AD search process and query the SLP directly to find the site code.
• If the SLP=servername parameter set for the push installation (CCMSETUP.EXE parameter), the client will bypass the AD search process and query the SLP directly to find the site code.

A couple of things that are important to remember about the Advanced client:

• Client.MSI, the Advanced Client installation files, are cached locally after an installation to allow for potential repair through Windows Installer.
• All client agents are installed by default with the Advanced client and only need to be activated through configuration on the SMS server.
• Post SMS 2003 SP1, the Advanced client is required on Windows 2000 OS and up.

and you're getting confused about the number of requirements and prerequisites to the installation. When I teach the MS official course for SMS, installation of the SMS server is not really covered properly, in fact, barely... So I often get questions about installation,IE. what do I need on my server to install SMS.

Quick list: W2k3, IIS (webdav, bits, ASP.NET), SQL 2ksp3a, SMS container in AD (if you're going to use schema extensions), SMS 2k3 + SP1 (will give you many new supported options ie. support for VPC2k4 and VS2k5 and client computers installed in workgroups)

For more detailed information on SMS 2003 installation, check out these links:

http://blogs.msdn.com/mkleef/archive/2004/11/08/253787.aspx

http://www.microsoft.com/downloads/details.aspx?FamilyId=784838B3-34E0-4122-B3E2-17C5B4EEF8F4&displaylang=en

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/deploy/spgsms03/spsms05.mspx

http://redmondmag.com/features/article.asp?EditorialsID=424

I often get questions about the proper method for imaging a computer with the SMS client already installed. Now, with the Advanced Client for SMS 2003, achieving this goal is even easier. Basically you need to perform all typical steps on your computer that will remove all information that makes the computer unique. Of which the most important step is running the System Preparation Tool (sysprep.exe).

Once you're ready to prepare your image, install the Advanced Client without assigning the client to an SMS site. Ensure the client services are not running. The best way to achieve this is by using the CCMSTARTSERVICES=FALSE parameter with CCMSETUP.exe. The last step before imaging is running a utility from the SMS Toolkit, CCMDELCERT.exe. This will delete any certificates generated by the SMS client.

Now you're ready to run your favorite imaging app!

I've been looking into MIF files for the past few days and trying to figure out valid implementations of the technology. I've never seen anyone use these files in live environments.

As you may know, MIF files get collected during the Hardware Inventory cycle of the SMS client. A specific directory is specified in the client computer, where these MIF (IDMIF and NOIDMIF) files are stored. The MIF files must be generated on the client computer and will then provide additional information about the client.

I came across this utility, which can be used on HP/COMPAQ servers to generate HP specific MIF information. http://h18004.www1.hp.com/products/servers/management/sms2003/. Once the MIF files are collected, they extend the viewable information in the Resource Explorer.

Most of us need to associate a picture with a concept. Basically a graphic representation of a technical process flow. I tend to remember concepts better if I can visualize them, most of my students tell me they work the same way...

SMS 2003 has many components that interact together in a multitude of different ways. The MS team in charge of SMS documentation does a great job of describing most SMS processes in flowcharts. These flowcharts can be very usefull for troubleshooting problems and understanding the communication between SMS components. Click HERE to access the SMS flowcharts. Look for much more SMS 2003 tips over the next two weeks.

As you're working hard to maintain an up-to-date inventory of the hardware running on your systems, there are now more options to assist you.

In order to modify the parameters that will be returned by the SMS clients during a hardware inventory cycle, you modify the SMS_def.mof file on your site server. The following link maintains a reference .mof file which includes most WMI classes and attributes supported.

Another great piece of news coming out of Microsoft today is the announcement of the new SMS 2003 Inventory Tool for Dell Updates. Read up on this new tool, it will basically allow you to do a similar scan to the MBSA, followed by applying the necessary Dell patches available.

IMHO, with the high visibility of Dell servers in most large size corporations today, this type of tool will drive a higher adoption rate for SMS 2003. I may finally be able to convince a few clients to move away from Altiris ;)

Well since SMS is becoming more and more part of my daily life, I thought I would update this blog with information, tips and tricks for SMS 2003. I really believe most of the growth in our high skilled consulting business will come from SMS. Let's hope to see an adoption similar to Exchange in the business world.

Look for my first entry on SMS later tonight!