Where to Start
How to Articles
Software with SMS
Software Deployment Using Windows 2000 and Systems Management Server 2.0
White paper explains the desktop and system management features in the Microsoft Windows 2000 platform and in Systems Management Server (SMS) 2.0. It also provides a comparison of the features in each product and the key questions involved in determining which technology is
appropriate for use in any given organization. Source: Microsoft.com
Software Distribution with SMS
Planning is the most ignored, yet important, stage of using SMS. When you want to use SMS for software deployment, you must plan every part of the process. Follow these steps to help you plan a software upgrade with SMS.
Source: Windows & .NET Magazine (July 1997)
SMS 2.0 Software Distribution Details and Advanced
In this session, you will learn the
about the various components and details that Systems Management
Server 2.0 uses when distributing software to client computers.
You will learn the components, the process flow, and how the
various files are moved throughout the Systems Management Server
infrastructure. Information on how to troubleshooting software
distribution will also be provided
SMS Customization and Integration
Learn how you can use SMS to distribute software to 50,000 users.
Source: Windows & .NET Magazine (March 1998)
Checking Windows 2000 Readiness with Systems Management Server 2.0
The Windows 2000 Readiness Analyzer tool works by checking for Windows 2000 incompatibilities on individual systems, but its output can be collected and processed by Microsoft Systems Management Server 2.0 to assess the overall state of Windows 2000 readiness in your organization.
Deploying MS Office 2000 with Systems Management Server
Deploying MS Office 2000 with Systems Management Server Published: September 1998 Introduction Microsoft© Systems Management Server is the ideal change and configuration management tool that can help you deploy and maintain Office 2000 in your organization.
Deploying Windows 98 with Systems Management Server 2.0
Deploying Windows 98 with Systems Management Server 2.0 Published February, 1999 Abstract The purpose of this paper is to inform network administrators and IT managers how they can use Microsoft© Systems Management Server to roll out Microsoft Windows? 98 in their organizations.
Deploying Windows 2000 with SMS Requires an Unattend.txt File
Microsoft Knowledge Base Article: 255995 - Deploying Microsoft Windows 2000 by using Systems Management Server (SMS) requires the use of an Unattend.txt file. This file must supply Windows 2000 Setup with a CD Key number during installation. In addition, the Unattend.txt answer
Deploying Internet Explorer 5 using Systems Management Server
Administrators can deploy customized Internet Explorer 5 packages
in many ways, including automated deployment using Microsoft
Systems Management Server. Custom packages are still created using
the IEAK, but rather than point users to the new packages, Systems
Management Server delivers the new package directly to their
desktops. Systems Management Server also provides many additional
capabilities. Source: Microsoft.com
How To Resend Assigned Programs
Microsoft Knowledge Base Article: 235815 - When you resend advertisements to clients, the current time is not automatically updated. To resend an assigned (mandatory) advertised program, you must first update the time in the advertisement's properties. When the time has been
updated, the advertisement is automatically resent.
Planning, Deploying, and Managing Windows 2000 with SMS 2.0
Downloadable document to help administrators deploy Windows 2000 via SMS. Source Microsoft.com
SMS 2.0 to Deploy Microsoft Office XP
This white paper supplements the Office XP
documentation and the SMS 2.0 software
distribution documentation by providing information
specifically targeted at deploying Office XP
to SMS 2.0 clients in your organization.
Using Systems Management Server to Deploy Windows 2000
This paper explains a systematic approach to deploying the Microsoft© Windows? 2000 operating system using Microsoft Systems Management Server, including package preparation, package distribution, advertising, and monitoring.
Using Systems Management Server to Deploy Windows 2000
Sample Chapter 14 - Using Systems Management Server to Deploy Windows 2000 From the Windows 2000 Server Deployment Planning Guide, Published by Microsoft Press Click to Order Microsoft© Systems Management Server (SMS) provides a variety of tools to help you deploy Microsoft? Windows 2000
Article and Whitepapers
| Advertisements to Users and User Groups
Microsoft Knowledge Base Article: 199261 - In Systems Management Server 2.0, the process for delivering packages to clients provides increased flexibility through the concepts of dynamic collections and advertisements. Packages can now be advertised to user accounts independent of
the computer. This leads to questions, for example, about how
advertisements will be handled if the user account is logged on to
multiple computers simultaneously and how the status will be
reported if it fails on some computers, but not others. This
article addresses questions about how advertisements and status
messages are handled in Systems Management Server version 2.0 (updated 11/23/1999)
Client Accounts Used in Software Distribution
Microsoft Knowledge Base Article: 224286 - This article describes the client accounts that are used for software installation with Systems Management Server (SMS) 2.0 Software Distribution on 32-bit
How the 'Assignments Are Not Mandatory Over Slow Links' Feature Works
Microsoft Knowledge Base Article: 202332 - In Systems Management Server (SMS) 2.0 Software Distribution assignments can be configured so they do not run when a client has a slow connection, and yet they are still mandatory over regular Local Area Network (LAN) connections.
This article documents how this feature works.
"Remove software when it is no longer advertised" Operation
Microsoft Knowledge Base Article: 199263 - The Remove software when it is no longer advertised option
allows programs to be automatically uninstalled when the program is no longer advertised to a client. This option is only available
to programs that register through Control Panel (double-click the Add/Remove Programs icon). This option is set on the Advanced tab
of Program properties. To set this option, the administrator must provide the name of the Uninstall registry key created by the
application during installation. Note that this registry key is not necessarily the same string you see in the actual Add/Remove
Programs dialog box.
Unattended Windows NT Upgrades Require Network Card Settings to Be Specified
Microsoft Knowledge Base Article: 201985 - Microsoft Systems Management Server 2.0 has the ability to upgrade an operating system on any client computer just as if it were installing program software locally to the
How to Troubleshoot Advertisements That Are Not Seen by Clients
Microsoft Knowledge Base Article: 200967 - If an advertisement does not appear on the client or if the advertisement does not run properly, first review the following Troubleshooting Software Distribution steps, as outlined in the Systems Management Server 2.0 Administrators
Guide: (updated 2/18/1999)
When Changing Package Access Accounts You Must Update Package
Microsoft Knowledge Base Article: 210354 - Systems Management Server 2.0 gives you the ability to set access
privileges on Package access points. If you change the Access Account properties, the package must be updated on all distribution servers where this package resides in
order for these changes to take affect. To update your
distribution points after making this type of change, right-click
the Distribution Points node and select Update
Distribution Points on the All Tasks menu. (updated 3/22/1999)
© 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.