LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 16, 2003

 

SMS Server
  Where to Start
  Administration
  Clients
  How to Articles
  Installation
  Inventory
  Novell Integration
  Remote Control
  SMS Installer
  Software Deploy
  Software Metering
  Troubleshooting

 

BackOffice
  AppCenter
  BizTalk Server
  Exchange
  Host Integration
  IIS
  ISA Server
  MOM
  Proxy Server
  Site Server
  SMS Server
  SNA Server
  SQL Server
Book Reviews
Career Tools
Networking
Resource Centers
Scripting
Security
User Groups
Utilities
Cybercheese

 

 

 

 

 

 

 

Installing and Configuring SMS

Deploying SMS in your organization is not a task that should be taken lightly. A little bit of preplanning and lab work goes a long way to ensuing a smooth deployment. Site design, server configurations, bandwidth limitations, and  
Where to Start...
Architectural Design and Implementation Plan: MS Systems Management Server 
Architectural Design and Implementation Plan: MS Systems Management Server By Paul Bethany ABSTRACT: This document is a detailed look at a sample Microsoft Systems Management Server (SMS) system implemented in a large electronics company. It provides generalized technical recommendations.

MS Systems Management Server Deployment Project Plan
MS Systems Management Server Deployment Project Plan By David Millett Microsoft Consulting Services March 1997 1 Background This document, created by Microsoft© Consulting Services (MCS), describes the tasks typically performed during the deployment of SMS.

SMS Infrastructure and Deployment Strategy: A Large Company Scenario
SMS Infrastructure and Deployment Strategy: A Large Company Scenario By Jeff Hamer, Microsoft Consulting Services, Kansas City AT A GLANCE Key Point: Microsoft Systems Management Server (SMS) allows you to organize your existing network structure into logical groupings called sites,

Systems Management Server 2.0 Server Sizing in an Organization
Systems Management Server 2.0 Server Sizing in an Organization Published August 1999 Abstract A realistic example of sizing servers to support Microsoft© Systems Management Server (SMS) 2.0, including relevant theory and details, and pointers to related documentation.

 

MS Systems Management Server Planning Guide 
MS Systems Management Server Planning Guide The Systems Management Server Planning Guide covers the following: Introducing Systems Management Server Getting to Know Systems Management Server Understanding Sites Managing Sites Managing Inventory Managing Software

How to Articles
Defining Site Boundaries in Systems Management Server 2.0
Microsoft Knowledge Base Article: 200344 - Systems Management Server 2.0 now uses TCP/IP subnets or IPX networks to define the site boundaries, rather than Windows NT domains. If the site server is a domain controller, the subnet of the site server is used by default. (updated 11/23/1999) 

How to Configure SQL Server User Connections for SMS 2.0
Microsoft Knowledge Base Article: 199249 - When setting up a Systems Management Server 2.0 primary site server, you are prompted to configure the maximum number of user connections for your SQL Server. This article describes how the setup program determines the default number of connections and how you can change this setting after the Systems Management Server site server is installed (updated 371999)

Worth Reading...
Required Hotfixes before installing SMS 2.0 SP2
Microsoft Knowledge Base Article: 261931 - When you prepare your Systems Management Server (SMS) 2.0 hierarchy for an upgrade to SMS 2.0 Service Pack 2 (SP2), you may need to apply two specific updates to every SMS 2.0 site server in your existing hierarchy. Please review this article thoroughly to determine which updates you need to apply to your hierarchy.  Source Microsoft.com (updated June 20, 2000)

SMS Site Design Best Practices
SMS Best Practices introduces the key issues that administrators face during deployment, suggests preferred methods, and provides links to further information. It is strongly recommended that administrators refer to SMS Best Practices before deploying SMS in their organization. SMS Site Design Best Practices is a downloadable HTML Help file (.chm) and requires Internet Explorer version 4.0 or later.

Setup Does Not Install SQL Server 7.0 Unattended
Microsoft Knowledge Base Article: 200615 - During Microsoft Systems Management Server (SMS) 2.0 Setup, you receive the option to install Microsoft SQL Server. Installation of SQL Server version 6.5 is accomplished without user interaction. However, if you install SQL Server 7.0, you you must complete SQL Server Setup by entering data when prompted, and you must have sufficient SQL Server licenses for the installation. (updated 5/10/2000)

Seminars for Deploying Windows 2000 with SMS

Upgrading from SMS 1.2 
Deploying SMS 2.0 in an Existing SMS 1.2 Site
Microsoft Knowledge Base Article: 200953 - When Systems Management Server 2.0 is deployed in an existing Systems Management Server 1.2 site, and Windows Networking Logon Discovery is enabled, Systems Management Server 2.0 will enumerate all domain controllers in the domain and create the SMSLOGON share on all domain controllers. (updated 2/26/1999)

SMS 1.2 to SMS 2.0 Changes
Appendix B from the SMS Administration Manual - Even a quick look at Systems Management Server version 2.0 (SMS) will reveal substantial changes to its architecture, database structure, and feature set. The tables in this appendix summarize the structural and functional changes between SMS 1.2 and SMS 2.0 

Upgrading from SMS 1.2 to SMS 2.0
Chapter 5 from the SMS Administration Manual. Upgrading from SMS 1.2 to SMS 2.0 Systems Management Server version 2.0 (SMS) includes major changes to the architecture, structure, and function of earlier versions. Many of these changes affect the upgrade process. This chapter identifies the upgrade issues, decision paths, 

Functions of Migrat1x.exe?
Microsoft Knowledge Base Article: 199227 - This article describes the functions of Migrat1x.exe, which is used to upgrade a Systems Management Server version 1.2 client to Systems Management Server version 2.0. (updated 351999)

Migration from 1.2 to 2.0 Causes PGC & PCM Warning Dialogs
Microsoft Knowledge Base Article: 215125 - When migrating Windows clients from Systems Management Server (SMS) version 1.2 to SMS version 2.0, the clients may get "Cannot reach server Error" error messages from the Package Command Manager (PCM) and/or the Program Group Control (PGC)

MS Systems Management Server Version 1.2 and 2.0 Interoperability
MS Systems Management Server Version 1.2 and 2.0 Interoperability Abstract Describes the concepts and features of Microsoft© Systems Management Server 2.0 as they relate to the process of interoperating with the 1.2 product. Introduction The purpose of this document is to assist 

SMS 1.2 and 2.0 Interoperability
Downloadable whitepaper designed to assist SMS Administrators in managing a Systems Management Server version 1.2 and version 2.0 mixed hierarchy.

SMS 1.2 to SMS 2.0 Upgrade
Downloadable whitepaper describing the recommended upgrade path to SMS 2.0 
Source Microsoft.com

Upgrading to SMS 2.0 When Packages Rely on MSTEST Directory
Microsoft Knowledge Base Article: 200399 - The MSTEST folder no longer exists in the Microsoft Systems Management Server (SMS) 2.0 directory structure. In SMS 1.2, the path to this folder is \sms\site.srv\maincfg.box\mstest.

Version 1.2 to 2.0 Secondary Site Upgrade Options
Microsoft Knowledge Base Article: 199250 - This articles describes the three methods to upgrade a Systems Management Server secondary site from Systems Management Server 1.2 to version 2.0 after the primary site server has been upgraded to 2.0

Systems Management Server Version 1.2 to 2.0 Upgrade
Describes the concepts and features of Microsoft Systems Management Server version 2.0 as they relate to the process of upgrading from version 1.2. 

 

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.