Using Systems Management Server to Deploy Windows 2000

Examining Differences Between Systems Management Server 1.2 and Systems Management Server 2.0

Systems Management Server 2.0 is dramatically different from its predecessor, Systems Management Server 1.2. Both versions have similar feature sets, but each version accomplishes the features using dramatically different techniques. If you are planning to use SMS 1.2 to deploy Windows 2000, or for domain consolidation, you need to be aware that software distribution in SMS 1.2 differs from SMS 2.0 in the following ways:

Only computers can be targeted for software distribution, and the targeting is not dynamic (new computers that meet the requirements for upgrade must be targeted with new jobs).
Windows NT–based computers, where the logged-on user does not have administrative privileges, must be given the Package Command Manager as a Service facility. There is no charge for this addition to SMS 1.2, but you need to deploy this facility before you begin the Windows 2000 deployment.
The status subsystem for jobs is more awkward to work with.
The originating site for the package must keep a compressed copy of the package.
Programs cannot force another program to run before them and cannot be disabled centrally.
Windows 2000 computers might not be supported by SMS 1.2 as clients. Therefore as computers are upgraded to Windows 2000, they might stop functioning as SMS 1.2 clients or they might no longer be supported. For more information about SMS 1.2 support of Windows 2000 computers, see the Microsoft Systems Management Server link on the Web Resources page at http://windows.microsoft.com/windows2000/reskit/webresources.

Other differences between the two versions are relevant to other SMS features that might benefit your Windows 2000 deployment. For more information about those features and differences, see "Using Systems Management Server to Analyze Your Network Infrastructure" in this book.