Advertisements to Users or Groups Are Not Sent If IBM DB2 Is Installed
Microsoft Knowledge Base Article: 271556 - An advertisement that is sent to users or groups may not be sent when the Systems Management Server (SMS) 2.0 Service Pack 2 (SP2) client and IBM DB2 for Windows NT 4.0 are installed on the same computer.
Admin Console Installation From
\sms\bin\i386 Subdirectory Causes Dr. Watson
Microsoft Knowledge Base Article: 235766 - Since Microsoft's Systems Management Server version 2.0 is a network management application, there is a need to be able to install an Administrator's Console on various Windows NT computers throughout the
SMS 2.0 Administrator's Guide Site System Roles Listed Incorrectly
Microsoft Knowledge Base Article: 226889 - The Systems Management Server (SMS) 2.0 Service Pack 1 (SP1) Release Notes, under "Supported Site System Platforms," state that Microsoft Windows NT 3.51 (SP5, x86 only) is supported as a logon point. This information is
Clients that Are Not in the Targeted Collection Are Executing Programs
Microsoft Knowledge Base Article: 227032 - When advertising a program to a collection you may find other clients in your site executing the program even though they are not in the targeted collection. Not only will the clients execute the program but they will also create a status
message stating the success or failure of the program that was
executed. For example, if you advertise to a collection that
contains fifty client machines and you receive over fifty status
messages stating that the program was run, you can safely assume
that clients that were not in the collection ran the program.
Common Issues and Resolutions for Crystal Info Reports
Microsoft Knowledge Base Article: 199357 - This article describes some of the common causes of Crystal Info report issues, and provides methods you may be able to use to solve
Msg: "A Temporary File Needed for Initialization Could Not Be Created"
Microsoft Knowledge Base Article: 213289 - When you send packages to a Systems Management Server client, the following error message appears on the desktop of the
How to Fix the WMI Repository of a Site Server
Microsoft Knowledge Base Article: 199359 - Windows Management (WMI) Microsoft's implementation of Web-based Enterprise Management
(WBEM) has become an integral part of Systems Management Server version 2.0. The Administrator console must use WBEM to talk to the providers that get
information for the Administrator to use. If the WBEM repository
stops functioning correctly, the Administrator console is useless
and the site is not manageable, because the Administrator console
is unable to ask the Systems Management Server Provider to pull
information from the database.
Identical Site Names on Multiple Sites Can Cause Inconsistencies in SMS Administrator
Microsoft Knowledge Base Article: 229857 - When you name a site in Systems Management Server (SMS), ensure that site names are not duplicated. If you use duplicate site names, problems may occur when you retrieving information from the database.
These problems occur because the site name is used as part of the
key for retrieving data.
Manually Stopped Threads of the SMSEXEC Service Will Automatically Restart
Microsoft Knowledge Base Article: 199816 - SMS_SITE_COMPONENT_MANAGER is the service that restarts the threads of
SMS_EXECUTIVE. If SMS_SITE_COMPONENT_MANAGER is running, it restarts the stopped threads when it executes a polling cycle. By default, the polling cycle occurs every
NET TIME Offered as a Package Will Not Traverse Domains
Microsoft Knowledge Base Article: 199041 - When NET TIME is sent as a package and the package is set to "run with administrative rights," NET TIME will not be able to connect to another
Non-Computing Devices May Not Be Discovered by Network Discovery
Microsoft Knowledge Base Article: 225352 - Network Discovery may not be able to discover non-computing devices such as UNIX hosts and
Shared DLLs Are Not Removed During a Silent Uninstall
Microsoft Knowledge Base Article: 206101 - When you perform a silent uninstall to remove an
application using the Systems Management Server Installer, shared
.dll files are not removed. The shared .dll files, which are
listed in the Install.log, are not removed because the
Uninstall.exe program defaults to "no to all," which you
cannot change for a silent uninstall.
Site Does Not Function After You Change the Domain Name or Computer Name of a Site Server
Microsoft Knowledge Base Article: 213186 - A Microsoft Systems Management Server (SMS) site no longer functions after you change either the name of the domain or the name of the computer on which the site was
SMS Database Schema Is Not Published
Microsoft Knowledge Base Article: 185910 - A common question for Systems Management Server support is "How do I run queries against the Systems Management Server database?" Another common question is "Where can I find the Systems Management Server database
Systems Management Control Panel Tool Displays Previous Version for Some Components After Upgrade
Microsoft Knowledge Base Article: 235161 - When you use the Systems Management tool in Control Panel to view client component version information after a site upgrade, the old version information is displayed even though the components have been successfully
Trap Receiver Not in SMS 2.0
Microsoft Knowledge Base Article: 198978 - The trap receiver thread and functionality is not provided in Systems Management Server version 2.0. You can still convert events to traps using the Systems Management Server Event to Trap Translator, but you cannot send the traps to a
System Management Server 2.0 site server to store in the Systems
Management Server 2.0 database.
Using /Upgrade Switch with Command Line Setup Causes Error "Setup cannot upgrade the SMS database" and Disables SMS 1.2 Site
Microsoft Knowledge Base Article: 235768 - When you run the Systems Management Server setup to upgrade a version 1.2 site from a command line, the following error
appears: Setup cannot upgrade the Systems
Management Server database. Contact your SQL Administrator
Microsoft has seen the problem in both Single Domain and Master
Domain environments. This error occurs regardless of the security
implementation of Microsoft SQL Server.