Copyright: Copyright 1993 Microsoft Corp.
Citation: Copyright 1993 Microsoft Corporation. All rights reserved.


 Microsoft Systems Management Server Knowledge Base

Prepared 07/14/95

 Knowledge Base Articles

 Obtaining Updated Versions of this Help File

THE INFORMATION IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES EITHER EXPRESSED OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FORGOING EXCLUSION OR LIMITATION MAY NOT APPLY.Copyright (c) 1994 Microsoft Corporation.  All rights reserved.


Knowledge Base Articles
 Microsoft Systems Management Server Knowledge Base

 Knowledge Base Articles

 SMS Remote Control Fails if Not Enough LANAs are Available

 Problems with Client PCMWIN16 and Manditory Jobs

 Standard Template Files Restrict Word Backward Compatibility

 Enabling Help Desk Options from Logon Servers Unsupported

 SMS Sender Properties Help Incorrectly References HERMSRHx

 SMS Doc Err: Package Rule Filename Incorrect

 Event ID 7000: RDR Service Failed to Start

 ERROR: Could Not Load Language DLL _MIFGEN.DLL

 PATCH.EXE Fails When Launched by PCMSVC32.EXE

 SMS Administrator Err Msg: Socket () failed, 10047

 Required Number of SQL Connections Needed for SMS

 DOS Inventory Agent Hangs on HP Vectra

 Cannot Remote Control Windows IPX/NetBIOS Client

 QuickPrep Sales Resource for SMS Server 1.0

 SMS: Doc Err: INVDOS /N Command Line Option is Incorrect

 SMS: INVDOS Fails with Large PKG_16.CFG File

 Unable to Install SMS Client Software with VSAFE

 Querying Macintosh Clients in Systems Management Server

 Obtaining Package ID From Within an Microsoft Test Script

 Using Batch Files in Sharing Packages

 Cannot Print From SMSTRACE Utility

 SMS Remote Control Fails on AST Manhattan Pentium

 Site Config Manager's Stages of Operation

 How to Install OS/2 1.3x System Management Server Clients

 SMS Site Config Manager Fails to Add Domain/Server

 Systems Management Server Inventory Via RAS Causes STOP Screen

 Systems Management Server Upgrade with Debug Option Fails

 Shared Packages Not Distributed to NetWare Volumes

 Eight or More Clauses Causes Query Execution Error

 NetWare 3.x Server Required for NetWare 4.x Bindery Emulation

 PCM and Archiving Unexecuted Mandatory Jobs

 Docerr: SMSVIEW Program Item Not Available

 SETLS32 Fails To Remap Windows NT Clients

 WINMIF Fails If XNF File Has Text Before Numeric Fields

 Incorrect Swap File Size Reported for Client Computers

 Network Monitor Displays Expiration Notice

 Shadow Effect with SMS MachineIDs and NetWare 500/1000 Licenses

 SMS Inventory Processor: Compilation Error on Dell Computers

 DOCERR: Moving Sender Outbox In SMS 1.0 is Unsupported

 Terminate Viewer Option in Remote Control Agent Does Not Work

 PCM and PGC Cannot Connect to Servers With Long Names

 Access 2.0 Err Msg with SMS: Can't Find Wizard, or There is...

 Bad .RAW File Hangs Inventory Processor

 SMS Package Number is <null>

 SMS: WUSER GP Faults with Compaq Qvision Adapter

 Macintosh Clients Generate Event ID 180 and MIF Files

 Cannot Use Icon When Setting Up Share Package

 System Management Server Setup Limits Path of Devices

 Systems Management Server Executive Service Hangs

 SMSRUN16 Fails To Detect SECONDNET.DRV in Windows for Workgroups

 INVDOS Does Not Report TCP/IP-32 3.11a Client IP Address

 SMS Fails To Create Jobs On Non-US SQL Server 4.21a

 SMS Reports Incorrect Disk Information on NetWare Servers

 SMS: Inventory Does Not Distinguish Individual Raid 5 Drives

 SMS Administrator Doesn't Show New Architectures

 Sub-directory and File Permissions Not Set on Macintosh Volume

 Scheduler Overwrites Package Property Information

 Non-Existing Administrative Share Causes Incomplete Site

 APPCTL Err Msg: Failed to Connect to SMS Network Server...

 SMS Err Msg: PowerPoint Could Not Locate or Start the Quick....

 AppStart Doesn't Change Cursor to Hourglass

 SMS Inventory Disables Speaker on Client Computer

 Blank APPSTART Icon

 VIEWNAD Does Not Display Platform Type Correctly

 WIN.INI Not Found by SETLS from DOS on LAN Manager Clients

 INVDOS Crashes AutoCAD Mouse/Tablet Driver

 Err Msg: Application Database Cannot Server, Share or Dir...

 SMS Will Not Deinstall On Windows for Workgroups clients

 SMS Hierarchy Manager Fails Due to Stack Overflow

 Problem Running SMS on CNTFS Partition

 SMS Does Not Use Local Thesaurus for Word for Windows 6.0

 SMS Modifies Application INI Files

 INVDOS Does Not Detect NEC 3x CDROM drives

 SMS: Visual Basic Application Setup Fails When Executed by PCM

 Program Group Control Requires Logon Validation

 Systems Management Server Inventory Reports Incorrect CPU Speed

 16-bit Program Group Control Requires Drive Letter

 Switch Required for USERTSR for WFW 3.1 Clients

 SMS Error 5000 on Macintosh Client

 Remote Control Works Only Once with Micromatic VTD/8 Gateway

 TSRs Knows to Conflict with USERTSR(IPX)

 Running Macintosh Installer from a Package Subfolder

 Using Windows NT Server Standard Server as SMS Helper Server

 SMS Program Group Controller and AutoDisconnect

 Using Systems Management Server in a Split-Domain Model

 Use of the %0\..\ Syntax in SMSLS.BAT

 Controlling LM and NT Logon Script Configurations with SMS

 Compression Performance Tuning in Systems Management Server

 Third-Party Companion Products for Systems Management Server

 Memory Performance Tuning in Systems Management Server

 SMS Site Configuration Manager Internal Error Codes

 Network Client Support for Systems Management Server

 How to change Your Systems Management Server Site Name

 Systems Management Server Tracing and Log Capabilities

 How to Use Remote Control with TCP/IP

 Cannot Use Leading Spaces in a String for an Inventory Rule

 SMS Network Applications Database Synchronization

 SMS Site Reset Recommended Before Upgrade

 Systems Management Server Event Log Codes 0 Through 99

 Systems Management Server Event Log Codes 100 Through 199

 Systems Management Server Event Log Codes 200 Through 249

 Systems Management Server Event Log Codes 250 Through 349

 Systems Management Server Event Log Codes 350 Through 400

 Foreign NAD Items Remain After Child Detaches

 DEC Turbo Port Addresses Appear Reported Incorrectly

 Problems Running SMS w/Non-English Versions of Windows NT

 Enabling Help Desk Options for MS-DOS Clients

 Using SMS to Share Document Files with PGC

 SMS Installation Incomplete with Missing Admin Drive Share

 How Set Up SMS to a Remote SQL Server

 Requirements of a SMS Network Monitor Agent

 DumpSend: Send Request File Formats

 Checklist for Enabling SMS in Logon Scripts

 Adding a Pure LAN Manager Domain to SMS

 PCMDUMP and Package Command Manager Instruction Files

 Orphan Machine Inventory, Ghost Sites, and Domains

 SMS: ViewNAD and the Network Applications Database (NAD)

 How to Remove Systems Management Server Clients

 SMS Shared Version of Works 3.0 Displays OLE Error on Startup

 Information on the SMSLOG.TXT File

 Automatically Starting Shared Applications Under SMS

 Connecting to a Remote Network Monitor Agent across a Router

 NICs That Work with Network Monitor

 Err Msg: ...the Package Requires an NTFS Drive to Install...

 Why SMS Creates Macintosh Volumes for Shared Applications

 Using the SMS Tracer Utility

 Windows NT Account Requirements for SMS Site to Site Com.

 SMS Service Account Requirements for Different Configurations

 SMS Administrator Unable To Retrieve Machine List

 Creating the SMS Administrator Log File UI.LOG

 SMS Server Selection Using Appstart

 LMSCRIPT.PIF and the SMSLS logon script

 Different Language Site Reporting Not Supported in SMS

 Troubleshooting SMS Inventory Collection Problems

 Troubleshooting SMS Workstation Package Installations

 SMS Unique ID (SMSID) Allocation

 Installing SMS Client to Drive Other Than Most Free Disk Space

 Systems Management Server: Error 5016 When Running INVMac

 Unrecognizable Characters Displayed Using Remote Control

 Err Msg: Remote Control Agent Cannot Load IDIS_IPX.DLL

 Functional Description of SMSWORK

 Using Systems Management Server Remote Control over a RAS Server

 Changing From Auto to Manual Logon Scripts In SMS

 SMS: Automating Installations of Windows for Workgroups 3.11

 Manual Installation of INVWIN32 on Windows NT Workstation

 Inventory Update Reporting Interval

 How to Change the SQL Login ID for the SMS Database

 How To Speed Site Property Changes

 Propagating MIF Entry Forms (XNF files) to SMS Clients

 Sample SMSVIEW Reports and Queries Not Included in SMS

 Obtaining Updated Versions of this Help File


Obtaining Updated Versions of this Help File
 Microsoft Systems Management Server Knowledge Base

 Knowledge Base Articles

 Obtaining Updated Versions of this Help File

 How to Obtain SMSKB.HLP


SMS Remote Control Fails if Not Enough LANAs are Available

Article ID: Q121658

----------------------------------------------------------------------

 The information in this article applies to:

  - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

Help Desk and Diagnostics fail from the Systems Management Server

Admin user interface (UI) if the protocol binding needed is greater than

the number of default LANAs in the Windows NT Registry. For example, if the

LANA number for the binding is 5 and the Registry only shows default for 4

LANAs, the UI attempts the command but fails.

RESOLUTION

==========

To correct this problem:

WARNING: Using Registry Editor incorrectly can cause serious,

   system-wide problems that may require you to reinstall Windows NT to

   correct them. Microsoft cannot guarantee that any problems resulting

   from the use of Registry Editor can be solved. Use this tool at your

   own risk.

1. Start REGEDT32.EXE and locate the following Registry subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS

      \Components\SightNT\Lana

2. Add the Default entries for the needed LANAs. For example, from the

   Edit menu, choose Add Value. Enter values for the following:

      Value Name: Default# (where # is the next LANA number)

      Data Type: REG_DWORD

      Data: (Enter the LANA number you are adding, in Hex)

3. Choose OK and quit the Registry.

4. Close the Admin UI and restart Systems Management Server.

Additional reference words: sms prodsms 1.00 systems management

KBCategory: kbnetwork

KBSubcategory: nthowto ntconfig


Problems with Client PCMWIN16 and Manditory Jobs

Article ID: Q122320

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When the client PCMWIN16 pops up with multiple new pending jobs and one

manditory job, the program counts down and executes the manditory job only

and closes the window. The remaining pending jobs do not run until

additional new jobs become pending.

WORKAROUND

==========

To work around this problem, do one of the following:

   - Have the user log off and log on again.

   -or-

   - Go to the Systems Management Server Client program group and run the

     Package Command Manager icon to force PCM to refresh.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntnetserv ntutil ntui

Additional reference words: sms prodsms 1.00 1.10


Standard Template Files Restrict Word Backward Compatibility

Article ID: Q122797

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you use Program Group Control to perform a workstation installation of

Microsoft Office version 4.2 and you use the standard template files that

ship with Office version 4.2, you may not be able to save Microsoft Word

version 6.0 files in Microsoft Word version 2.0 format. The same problem

also occurs with any batch workstation installations that uses the standard

template files of Office.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. We are researching this problem and will post new information

in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 mom 4.2a 4.2b 4.2c

KBCategory: kbinterop

KBSubcategory: ntinterop nt16ap


Enabling Help Desk Options from Logon Servers Unsupported

Article ID: Q123317

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SUMMARY

=======

This article discusses enabling Help Desk Options on Systems Management

Server clients by default from a logon server.

MORE INFORMATION

================

Administrators cannot modify Registry settings or the DOMAIN.INI file on

logon servers to force help desk options on clients to "Yes" or enabled by

default.

Remote control in a reasonably secure environment requires that the user

intentionally make Help Desk Options available to ensure proper permission

is granted. If an administrator is allowed to set Help Desk Options for a

client, then important control is removed from the user, who is ultimately

responsible for his or her own data security.

It is possible to write an application to modify the SMS.INI file on

clients with a Package Command Manager command and to place a copy of WUSER

in the startup group. The implementation and use of an application designed

to modify SMS.INI is not supported by Microsoft, and is entirely up to the

administrator.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 munge


SMS Sender Properties Help Incorrectly References HERMSRHx

Article ID: Q124068

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

The Microsoft Systems Management Server Sender Properties dialog box

context sensitive help says you should create HERMSRHx if it does not

exist. The file name is incorrect; you should create SMS_SHRx if it does

not exist.

KBCategory: kbdocerr

KBSubcategory: ntdocerr

Additional reference words: sms 1.00 1.10 docerr doc err prodsms


SMS Doc Err: Package Rule Filename Incorrect

Article ID: Q124297

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

Page 219 of the Microsoft Systems Management Server version 1.0

"Administrator's Guide," shows the following syntax for the RUL2CFG.BAT

file:

   rul2cfg packagerulefile cfgfile

For the audit process to work correctly, the package rule file output file

must be named AUDIT.CFG; you cannot use an arbitrary filename.

When the package rule file process completes, AUDIT.CFG is placed in the

appropriate platform directory. For example, for Intel-based platforms,

the file is placed in the SMS\PRIMSITE.SRV\AUDIT\PACKAGE\X86.BIN directory.

You can test this file by running AUDIT32.EXE. If the file is named and

compiled correctly, you will see the Audit Status count slowly to 100

percent. If the file is incorrectly named, the Audit Status immediately

displays 100 percent.

Additional reference words: sms prodsms 1.00 prodsms

KBCategory: kbdocerr

KBSubcategory: ntdocerr ntconfig


Event ID 7000: RDR Service Failed to Start

Article ID: Q124641

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

When you reboot a computer running Windows NT Server the following text is

written to the System Log (Event Id 7000):

   The RDR service failed to start due to the following error;

   An Instant of the service is already running.

   The SRV service failed to start due to the following error;

   An Instant of the service is already running.

This problem occurs when you are using a beta release of System Management

Server.

To correct this problem, remove the beta version of SMS or install a

released version of SMS.

KBCategory: kbnetwork

KBSubcategory: ntgeneral

Additional reference words: sms 3.50 prodnt stop errors prodsms


ERROR: Could Not Load Language DLL _MIFGEN.DLL

Article ID: Q125623

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you try to run MIFGEN.EXE, the following error message appears:

   Could not load language DLL MIFGEN.DLL

CAUSE

=====

This problem occurs when the Language setting in the International portion

of Control Panel has been changed to something other than "English

(American)."

By default Systems Management Server puts _MIFGEN.DLL in the 00000409

subdirectory of \SMS\SITE.SRV\<PLATFORM.BIN>. The 00000409 subdirectory is

the Language ID associated with the English (American) setting.

RESOLUTION

==========

There are currently two ways to solve this problem:

1. Change the Country and Language settings back to "United States" and

   "English (American)."

2. Create a subdirectory in \SMS\SITE.SRV\<PLATFORM.BIN> with the same

   Language ID as the Language setting in the International portion of

   Control Panel (See below for supported Language IDs). Then copy

   _MIFGEN.DLL into that subdirectory.

Example: If you were using "United Kingdom" for Country and "English

(British)" for Language then you would create a subdirectory called

00000809 in the \SMS\SITE.SRV\<PLATFORM.BIN> directory.

MORE INFORMATION

================

Below are the Language IDs supported by Windows NT 3.5:

   00000402  =  "Bulgarian"

   0000041a  =  "Croatian"

   00000405  =  "Czech"

   00000406  =  "Danish"

   00000813  =  "Dutch (Belgian)"

   00000413  =  "Dutch (Standard)"

   00000409  =  "English (American)"

   00000c09  =  "English (Australian)"

   00000809  =  "English (British)"

   00001009  =  "English (Canadian)"

   00001809  =  "English (Irish)"

   00001409  =  "English (New Zealand)"

   0000040b  =  "Finnish"

   0000080c  =  "French (Belgian)"

   00000c0c  =  "French (Canadian)"

   0000040c  =  "French (Standard)"

   0000100c  =  "French (Swiss)"

   00000c07  =  "German (Austrian)"

   00000407  =  "German (Standard)"

   00000807  =  "German (Swiss)"

   00000408  =  "Greek"

   0000040e  =  "Hungarian"

   0000040f  =  "Icelandic"

   00000410  =  "Italian (Standard)"

   00000810  =  "Italian (Swiss)"

   00000414  =  "Norwegian (Bokmal)"

   00000814  =  "Norwegian (Nynorsk)"

   00000415  =  "Polish"

   00000416  =  "Portuguese (Brazilian)"

   00000816  =  "Portuguese (Standard)"

   00000418  =  "Romanian"

   00000419  =  "Russian"

   0000041b  =  "Slovak"

   00000424  =  "Slovenian"

   0000080a  =  "Spanish (Mexican)"

   00000c0a  =  "Spanish (Modern Sort)"

   0000040a  =  "Spanish (Traditional Sort)"

   0000041d  =  "Swedish"

   0000041f  =  "Turkish"

KBCategory: kbtool

KBSubcategory: ntconfig ntutil

Additional reference words: sms prodsms 1.00


PATCH.EXE Fails When Launched by PCMSVC32.EXE

Article ID: Q125934

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

The Release Notes for Systems Management Server version 1.0 give

instructions for using SMS to distribute updated files to Windows NT 3.5

Servers. These instructions include:

 - Creating a package using PATCH.PDF and PATCH.EXE supplied with SMS.

 - Setting the command line properties for the Windows NT redirector patch

   to "System (Background) Task" and "Automated Command Line." NOTE: This

   implies that the PCM service can execute this.

 - Creating a "Run Command On Workstation" job to run the executable on the

   servers.

This procedure works fine when the job is executed by PCMWIN32.EXE. However

PATCH.EXE fails if it is executed by the Package Command Manager Service

PCMSVC32.EXE. The PACMAN.LOG file will display something similar to the

following.

   sleeping 60 minutes

   SMS PCM Service Started

   CWinstService::ReadIniFile

     ReadIniFile:  OK

     ReadIniFile: Parsing the INI file.

   Check current server\share

   Results Location

   \\CSARWEN\SMS_SHR\despoolr.box

   SMS PCM Service Running = TRUE

   working.................................

    SMS PCM Service::Refresh

     Refresh: Getting server name

     Refresh: Looking for file:

   \\CSARWEN\SMS_SHR\pcmins.box\YAO01000.INS

     Refresh: Packages before filter:1

   Begin SetRegData

   Value = YAO000R

   Data  = New

   End SetRegData

     Refresh: Packages after filter: 1

   installing package SMS 1.0 Patch...............

    SMS PCM Service::RunJob

   Process died, cleaning up.

   Begin SetRegData

   Value = YAO000R

   Data  = Executed

   End SetRegData

   Begin WriteCommissarRecord

   Results Location is:

   \\CSARWEN\SMS_SHR\despoolr.box

   ISV MIF is:

   End WriteCommissarRecord

   sleeping 60 minutes

The PCM service is limited to packages that do not require user input and

do not display windows on the server. PATCH.EXE does not require user

input, but it does write to the screen. If you attempt to get around this

by redirecting the output from PATCH.EXE to a file, the PCM service will

still report that the process died, and the file will list the following

error:

   PATCH: the "windir" environment variable was not set

MORE INFORMATION

================

Below are excerpts from the instructions given by the Release Notes for

using SMS to distribute Windows NT Server patches.

   Patching Windows NT Server(TM) on the Site Server

   For the Windows NT update, the files and the utility program PATCH.EXE

   are located in the PATCHES\NT subdirectory of the SMS CD-ROM. For the

   Windows for Workgroups update, the files and the utility program

   PATCH.EXE are located in the PATCHES\WFW subdirectory of the SMS CD-ROM.

   To use the PDF, perform the following steps:

   1. Set up the package source directory:

      a. Create a package source directory.

      b. Create an NT subdirectory and a WFW subdirectory beneath the

         package source directory.

      c. Copy all the files from the PATCHES\NT directory on the SMS CD-ROM

         to the NT subdirectory of the package source directory.

      d. Copy all the files from the PATCHES\WFW directory on the SMS CD-

         ROM to the WFW subdirectory of the package source directory.

   2. Create a package. When you do so, import the PDF by choosing the

      Import button in Package Properties, then choosing PATCHRDR.PDF from

      the list.

   3. Choose the Workstations button.

   4. In the source directory box, type the path to the package source

      directory you created in step 1.

   5. Select Windows NT Patch of Redirector and choose the Properties

      button.

   6. In the Command Line Properties dialog box, select both the Automated

      Command Line and System (Background) Task options.

   7. Choose OK to close all the open dialog boxes.

   8. Create Run Command On Workstation jobs to run the appropriate package

      command on the appropriate computers.

WORKAROUND

==========

Use PCMWIN32.EXE to execute the job, or run PATCH.EXE manually from the

PATCHESNT directory on the SMS CD-ROM.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server version 1.0. We are researching this problem and will

post new information here in the Microsoft Knowledge Base as it becomes

available.

KBCategory: kbnetwork kbbug1.00

KBSubcategory: ntutil ntdocerr nt32app

Additional reference words: sms prodsms 1.00


SMS Administrator Err Msg: Socket () failed, 10047

Article ID: Q126158

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to use Systems Management Server Administrator to

remotely control a NetWare client, the following error message appears and

remote control is not available for any NetWare clients:

   Socket () failed, 10047

CAUSE

=====

Although remote control of NetWare clients uses IPX sockets, SMS

Administrator requires the NetBIOS NWBLINK driver.

MORE INFORMATION

================

NetBIOS support for NWLINK (NWBLINK) is installed under Windows NT when you

install NWLINK. However, if you install a Windows NT service that requires

NWLINK, and you have not yet installed NWLINK support, NWBLINK is not

installed. This happens when you install Gateway Services for Netware

(GSNW) on a Windows NT server.

RESOLUTION

==========

To correct this problem, remove and reinstall NWLINK so that NWBLINK is

installed, and then install the other software that depends on NWLINK.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: sms prodsms 1.00 administrators


Required Number of SQL Connections Needed for SMS

Article ID: Q127857

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

------------------------------------------------------------------

SYMPTOMS

========

The Microsoft Systems Management Server Administrator's Guide

incorrectly specifies the recommended number of SQL server connections

needed for setting up SMS on page 55:

   Make sure that the SQL Server has a maximum user connection

   setting that has at least 5 connections for use by SMS. Ten

   connections are recommended.

If you attempt to setup SMS version 1.0 with less than 20 connections, then

the following error appears during Setup:

   Not enough SQL connections are available for correct

   execution of SMS. At least 20 connections are recommended.

If you choose OK, the following error appears:

   Error: Number of requested connections must be >= 20.

RESOLUTION

==========

Increase the number of connections available to SQL to 20 or greater.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server versions 1.0 and 1.1. We are researching this problem and

will post new information here in the Microsoft Knowledge Base as it

becomes available.

KBCategory: kbdocerr kbbug1.00 kbbug1.10

KBSubcategory: ntdocerr

Additional reference words: sms prodsms 1.00 1.10


DOS Inventory Agent Hangs on HP Vectra

Article ID: Q128039

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

-------------------------------------------------------------------------

SYMPTOMS

========

When you run SMSLS.BAT file for the first time in Microsoft Systems

Management Server version 1.0 on a Hewlett Packard (HP) Vectra

computer, the DOS Inventory agent (INVDOS.EXE) may stop responding (hang)

during the video detection process.

CAUSE

=====

This problem occurs if you are using an onboard video card (Cirrus CL-

GD542x chipset) on an HP Vectra computer.

RESOLUTION

==========

Run the SMSLS.BAT file again.

After the first failure of INVDOS, SMS places a file (SMSSAFE.TMP) at the

root directory of the client computer's system drive (Drive C). This file

indicates that a video detection failure occurred during the previous

execution of the SMSLS.BAT file. The next time you run SMSLS.BAT, SMS.INI

is updated to indicate that the video detection should be skipped when you

run SMSLS.BAT. The SMSSAFE.TMP file is then deleted by SMS.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

1.0. We are researching this problem and will post new information here in

the Microsoft Knowledge Base as it becomes available.

KBCategory: kbsetup kbdisplay kbbug1.00

KBSubcategory: ntgeneral

Additional reference words: prodsms 1.00 sms ms-dos msdos


Cannot Remote Control Windows IPX/NetBIOS Client

Article ID: Q128145

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you try to initiate a remote control session with the client, a Quick

Window appears and it looks like it is trying to connect. It close itself.

No error message appears.

CAUSE

=====

You cannot remotely control Windows for Workgroups clients configured to

support both Microsoft Windows Network and NetWare.

This problem occurs because NetBIOS is loaded when Windows for Workgroups

is booted. When you try to initiate a Remote Control session from SMS Admin

Tools it fails because it sees NetBIOS but no USERTSR.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server version 1.0. We are researching this problem and will

post new information here in the Microsoft Knowledge Base as it becomes

available.

KBCategory: kbnetwork kbbug1.00

KBSubcategory: nt32app ntinterop

Additional reference words: 1.00 SMS prodsms remote control sms


QuickPrep Sales Resource for SMS Server 1.0

Article ID: Q128427

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

The QuickPrep Sales Resource for Microsoft Systems Management Server

version 1.0 is a 22 page document that contains the following information:

 - Overview of Systems Management

 - Systems Management Server: Overview

 - Elevator Message

 - Target Markets and Customers

 - Selling Strategies

 - Features and Advantages

 - Extending Systems Management Server

 - Competition

 - Licensing

 - Licensing a Systems Management Server Hierarchy

 - Order and Promotion Facts

 - Cross-Selling

 - System Requirements

To order this SMS Server Sales Resource document, contact Microsoft Sales

at (800) 426-9400 and request for Part #098-58435.

KBCategory: kbref

KBSubcategory: ntgeneral

Additional reference words: prodsms 1.00 sms pre


SMS: Doc Err: INVDOS /N Command Line Option is Incorrect

Article ID: Q128610

-------------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server version 1.0

-------------------------------------------------------------------------

Page 532 of the Microsoft Systems Management Server Systems Guide

states the following for the DOS Inventory Agent (INVDOS) command line

options:

   /n  Instructs the Inventory Agent to request a unique computer name.

This is incorrect. The /m switch instructs the Inventory Agent to request

a unique computer name. For a correct list of the DOS Inventory Agent

command line options, type INVDOS /? at the MS-DOS Command Prompt.

KBCategory: kbdocerr

KBSubcategory: ntdocerr ntutil

Additional reference words: prodsms 1.00 sms invwin32 invos2


SMS: INVDOS Fails with Large PKG_16.CFG File

Article ID: Q128614

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

If you create too many inventory packages in the Microsoft Systems

Management Administrator and you run SMSLS.BAT from a Windows for

Workgroups 3.11 computer the following error message appears:

   The inventory output file has not been created.

   Run INVDOS /v to determine why.

When you run INVDOS /V you will see something similar to the following:

   Keyboard

   Dma

   Disks

   DriveA

   DriveB

   DriveC

   Volume

   DriveD

   Volume

   ConventionalMemory

   CMOSMemory

   ExtendedMemory

   XMSMemory

   DPMIMemory

   EMMMemory

   MouseInfo

   Video

   Video Skipped

   A hardware test failed

   The inventory output file has not been created.

   Run INVDOS /V to determine why.

   Done.

CAUSE

=====

This happens when the PKG_16.CFG file becomes to large.

WORKAROUND

==========

Use the Audit utility to inventory software instead of creating packages

solely for inventory.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server version 1.0. We are researching this problem and will

post new information here in the Microsoft Knowledge Base as it becomes

available.

Additional reference words: prodsms 1.00 sms

KBCategory: kbnetwork kbenv kbbug1.00

KBSubcategory: ntconfig ntdosap ntinterop ntutil


Unable to Install SMS Client Software with VSAFE

Article ID: Q129550

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

If you install Systems Management Server client software on a computer

running Windows 3.1, and VSafe was started from the AUTOEXEC.BAT file,

WIN.INI LOAD= entry, WIN.INI RUN= entry, or from the Startup group, several

error messages appear referring to the Systems Manager Server client

software files.

WORKAROUND

==========

To work around this problem, change the entry of VSafe to "VSAFE /8-"

(without the quotation marks), or:

1. Clean boot to MS-DOS and run VSafe (Detect and Clean).

2. Run SMSLS and exit Windows. You may receive an error message

   from VSafe. Choose the Update option and reboot the computer.

3. When the following error message appears, run VSafe (Detect and

   Clean) again:

      Access to the specified device, path or file is denied.

4. If you receive errors during verification of files, choose Update

   on all files and reboot the computer.

5. Install the Systems Management Server client software again.

KBCategory: kbnetwork

KBSubcategory: ntconfig ntinterop

Additional reference words: prodsms 1.00 1.10 sms wfw wfwg


Querying Macintosh Clients in Systems Management Server

Article ID: Q129911

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SUMMARY

=======

If a Macintosh client computer is not registered in the Macintosh Sharing

Setup application, the Macintosh computer's name is not displayed in the

Systems Management Server Administrator utility. This article describes

a method of querying for all client computers detected by the Systems

Management Server.

MORE INFORMATION

================

In order to query all client computers without computer names in Systems

Management Server:

1. From the Systems Management Server Administrator Utility File menu,

   choose Query.

2. Select the <Ad Hoc Query> option from the Query field, then choose OK.

3. Select Add OR.

4. Select the SMSLocation attribute from the Identification group.

5. Change the Operator to "is".

6. Enter the following information in the Value field for a Systems

   Management Server domain in which you want to query:

      <Sitecode>|<Domain>|

7. Choose OK.

8. Repeat steps 3 to 7 for each Systems Management Server domain to be

   queried.

9. Choose OK.

The query method above displays all Macintosh clients within the specified

Systems Management Server domains that have blank name attributes. In

Systems Management Server, the inventory agents for all clients (except

Macintosh clients) require that all clients have an entry for their name

attributes.

The SMSLocation is defined as a concatenation of the client's site code,

domain, and name delimited by the pipe (|) symbol. Therefore, only

Macintosh clients will be returned using the above query.

KBCategory: kbnetwork

KBSubcategory: nthowto

Additional reference words: prodsms 1.00 sms


Obtaining Package ID From Within an Microsoft Test Script

Article ID: Q130373

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

When you write a custom detail status MIF, you may wish to obtain the

package ID for the current package during the execution of a Package

Command Manager job.

You should be able to obtain the name of the directory one-level up from

the current working directory at the time PCM launches the job. This is

available because PCM changes the current working directory to the package

source before launching the specified workstation command.

The parent directory name can be obtained from an EXE file, or from within

an Microsoft Test script, and then easily added to the information written

by the administrator-written detail. For examples, see the BackOffice SDK

Systems Management Server samples.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00


Using Batch Files in Sharing Packages

Article ID: Q130898

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SUMMARY

=======

When using a batch file as the command line executable for a sharing

package in Microsoft System Management Server, the "Requires Drive Letter"

option should be used. If "Runs with UNC Name" is used, the program

item gives the following error upon execution:

   Could not start application with command line 'batch filename'.

   File not found."

MORE INFORMATION

================

Windows 3.x clients do not process batch files when they are executed

through a Universal Naming Convention (UNC) connection. When the batch file

is executed, an MS-DOS virtual machine is opened to process the batch file.

However, the virtual machine does not support running batch files through

UNC connections and is unable to continue.

If instead, the package is defined to use a drive letter, the client will

assign a drive letter to the package share which will be available to the

virtual machine for processing the batch file.

KBCategory: kbnetwork kbenv

KBSubcategory: ntdosap ntconfig

Additional reference words: 1.0 share prodsms


Cannot Print From SMSTRACE Utility

Article ID: Q130899

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SMSTRACE.EXE (located in the \SMS\SITE.SRV\X86.BIN directory) can be used

to monitor Systems Management Server related log files. The print option

is available, but does not work.

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbtool kbbug1.00 kbbug1.10

KBSubcategory: ntutil

Additional reference words: prodsms 1.00 1.10 trace tracer sms


SMS Remote Control Fails on AST Manhattan Pentium

Article ID: Q130900

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

If you remove Remote Control for the second time from a Windows for

Workgroups 3.11 client  using a 3COM 3C503 or 3C509 network interface card

(NIC), the following error message may appear:

   An application error has occurred and an application error

   log is being generated.

   exe\SMS.DBG (pid=33)

   Exception: access violation (0xc0000005), Address <Hex address>

This problem occurs when Systems Management Server is installed on an AST

Manhattan Pentium computer with 64 megabytes of RAM.

To work around this problem, do one of the following:

 - Use another supported NIC on the Windows for Workgroups client.

   -or-

 - On the Systems Management Server, reduce the RAM to 16 MB.

KBCategory: kbnetwork kbprb

KBSubcategory: ntutil

Additional reference words: prodsms 1.00 sms mb


Site Config Manager's Stages of Operation

Article ID: Q130906

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SUMMARY

=======

The Site Config Manager component for Systems Management Server performs

numerous operations during its "watchdog" cycle. This article describes

four stages of the cycle. Each stage, as it is performed, can be monitored

via the service trace log file (SCMAN.LOG) for Site Config Manager located

in the root directory of the drive that Systems Management Server is

installed in.

MORE INFORMATION

================

Stage 1

-------

1a. Calculate if intervals have timed out for logon scripts, status file or

    user group mif.

1b. Write site identification information to registry.

1c. Write domains and logon servers to registry.

1d. Write site account, addresses, outboxes, misc config information to the

    registry.

1e. Write SQL Server information to registry.

NOTE: Steps 1b through 1e are only performed if a site control image

(*.CT1) file is detected. The alternative is that the Site Config Manager

woke up due to a polling interval, and there is no *.CT1 file present.

Stage 2

-------

The Site Config Manager reads the list of domains for the site (found in

the registry) and for each domain, it enumerates the servers to find all

logon servers. The logon servers are added to the registry and are marked

as pending-install if they are new.

Stage 3

-------

The Site Config Manager now uses the registry as the definition for the

site installation and verifies that the actual installation of domains and

components exist as defined. It removes any domains, servers, or components

that are marked as pending-uninstall and installs any that are marked as

pending install. For any that are marked as active, it verifies the

installation.

Stage 4

-------

The Site Config Manager reports the installation status of the site by

writing a site control file (*.CT2) and sending this file back to the

Hierarchy Manager. If this site was installed remotely, a mini-job is used

to send the file to the parent.

KBCategory: kbnetwork

KBSubcategory: ntdomain

Additional reference words: prodsms 1.00


How to Install OS/2 1.3x System Management Server Clients

Article ID: Q130938

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

Microsoft System Management Server does not properly install files on OS/2

1.3x clients. When the client files are not correctly installed, the OS/2

client is not properly inventoried.

CAUSE

=====

System Management Server uses the SMSLS.CMD file to install files to OS/2

client computers. SMSLS.CMD determines whether a file named MDOS is located

in the client's %COMSPEC% directory. If the file is not present, the client

files are not installed.

NOTE: The MDOS file is shipped with the IBM Windows for OS/2 product. The

%COMSPEC% directory is defined by the %COMSPEC% system variable on the

client computer. To determine %COMSPEC% directory, type "SET" at a command

prompt.

RESOLUTION

==========

If the MDOS file is not present, create a MDOS file of 0 bytes length and

place it in the %COMSPEC% directory. This will allow Systems Management

Server to install the client files correctly.

STATUS

======

Microsoft has confirmed this to be a problem in System Management Server

1.0. This problem was corrected in Systems Management Server version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntsetup nthowto

Additional reference words: prodsms 1.00 sms


SMS Site Config Manager Fails to Add Domain/Server

Article ID: Q123771

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

The SMS Site Config Manager fails to correctly add a domain to the site

when the domain contains a server name that exceeds 13 characters.

CAUSE

=====

When the NetServerEnum2 call is made to list the servers in the domain, the

correct list is returned by the primary domain controller (PDC). Because

the API returns error 2140 "An internal error has occurred," SMS Site

Config Manager ignores the domain.

When a server is added using the Use Specified Servers option, and the

server name exceeds 13 characters, the API (application program interface)

function return error 2453. Again, SMS Site Config Manager ignores the

domain.

WORKAROUND

==========

To work around this problem, use server names with 13 characters or fewer.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.This

problem was corrected in Windows NT version 3.51.

Additional reference words: sms prodsms 1.00 1.10 servername

KBCategory: kbnetwork kbbug3.50 kbfix3.51

KBSubcategory: ntconfig nthowto ntdomain


Systems Management Server Inventory Via RAS Causes STOP Screen

Article ID: Q129482

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you start the Systems Management Server inventory management from a

remote computer over a Remote Access Service (RAS) connection, a STOP

message screen appears.

CAUSE

=====

The SMSLS.BAT runs INVWIN32.EXE for inventory collection. The asyncmac

driver fails to forward an I/O request packet (IRP) down the NDIS chain

correctly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in Windows NT version 3.51.

KBCategory: kbnetwork kbbug3.50 kbfix3.51

KBSubcategory: ntstop ntras ntdriver

Additional reference words: prodnt prodsms 1.00 1.10 3.50 sms


Systems Management Server Upgrade with Debug Option Fails

Article ID: Q121847

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you run Windows NT Server version 3.5 in Kernel Debug mode, the

Systems Management Server software upgrade process fails on several

dynamic-link library (DLL) files, thus not completing the upgrade process.

RESOLUTION

==========

Restart Windows NT Server without the debug option and perform the Systems

Management Server upgrade process.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntinterop

Additional reference words: sms prodsms 1.00


Shared Packages Not Distributed to NetWare Volumes

Article ID: Q121383

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

Shared packages of applications are not distributed to specified volumes on

the NetWare servers.

CAUSE

=====

If the NetWare volume specified for the distribution of shared packages

does not exist, the de-spooler tries the volume on which Systems Management

Server is installed. The de-spooler will not use the NetWare SYS

volume if the NetWare package server is not a Systems Management Server

logon server.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

More information regarding this issue is available in the Package

Distribution section of the Release Notes.

NetWare is manufactured by Novell Inc., a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntdomain ntinterop

Additional reference words: sms prodsms 1.00


Eight or More Clauses Causes Query Execution Error

Article ID: Q121384

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

If you attempt to run a query consisting of eight or more clauses, the

following message appears in the Query Results dialog box:

   Query Execution Error

CAUSE

=====

This problem occurs due to the 16-table limit from SQL Server. Querying

eight or more clauses calls eight references to the particular table as

well as eight instances of the machine data table, thus reaching the 16-

table limit.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kberrmsg kbbug1.00 kbfix1.10

KBSubcategory: ntnetserv

Additional reference words: sms prodsms 1.00


NetWare 3.x Server Required for NetWare 4.x Bindery Emulation

Article ID: Q122135

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SUMMARY

=======

For Microsoft Systems Management Server to support any NetWare

version 4.x servers on a network, a NetWare version 3.x server must be

available somewhere on the network for administration purposes.

MORE INFORMATION

================

Systems Management Server only supports NetWare version 4.x servers when

they are running with Bindery Emulation Mode enabled. While NetWare version

4.x does support this mode, it does not ship with utilities that allow

administration of this bindery. SYSCON ships with NetWare version 3.x and

is used to assign user rights on NetWare version 3.x servers. This same

utility is used to administer NetWare version 4.x servers user accounts in

bindery emulation mode.

The SYSCON tool is required to assign the user group Everyone, and all

associated users, to the NetWare version 4.x servers bindery. This group is

used by Systems Management Server to assign rights to SMS-created shares

and directories on NetWare servers.

The NetWare products discussed here are manufactured by Novell, Inc., a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: sms prodsms 1.00

KBCategory: kbnetwork kb3rdparty

KBSubcategory: ntinterop


PCM and Archiving Unexecuted Mandatory Jobs

Article ID: Q122202

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When Package Command Manager (PCM) detects a mandatory job, it is possible

for someone to archive the job while the 5 minute countdown timer is still

running. If this happens, there are several resulting problems which

prevent PCM from being able to execute the job.

WORKAROUND

==========

If someone archives a mandatory job just before execution, delete the

PCMHIST.REG file on the client computer. This will force PCM to put the job

into the pending commands folder and re-enable the job for execution.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

Additional reference words: sms prodsms 1.00

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntdomain


Docerr: SMSVIEW Program Item Not Available

Article ID: Q123425

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

In the "Running SMSVIEW Generator" section of the Microsoft Systems

Management Server Help file (SMS.HLP), the first paragraph states:

   The SMSVIEW program is automatically installed on primary site

   servers. You can start SMSVIEW using the SMSVIEW program item

   from the Systems Management Server program group. The SMSVIEW

   program runs on the Windows NT operating system.

The second sentence is incorrect because the SMSVIEW program item (icon) is

not created or available in the Systems Management Server program group by

default. If you want to use the SMSVIEW program, the location of the

program is as follows:

   SMS\SITE.SRV\<platform>.BIN

where <platform> can be one of the following:

   x86   (for Intel-based computers)

   MIPS  (for MIPS-based computers)

   Alpha (for Alpha-based computers)

KBCategory: kbnetwork kbdocerr

KBSubcategory: ntutil ntdomain

Additional reference words: sms prodsms 1.00


SETLS32 Fails To Remap Windows NT Clients

Article ID: Q123770

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

If you log onto a Master User Domain (MUD) from a Windows NT workstation

that is a member of a resource domain, the workstation will report to the

MUD instead of the resource domain even though the SMSLS.INI file maps the

workstations domain and workgroup to the resource domain.

CAUSE

=====

The incorrect domain mapping results because there is no application

programming interface (API) call that can retrieve the current resource

domain, only the authenticating user domain.

A possible workaround would be to use the [workgroup] section of the

SMSLS.INI file and add the "resourcedomain=resourcedomain" line. Because

this line would match the check made by SETLS32.EXE, the workgroup

"resourcedomain" should be enumerated (even though there is no real

workgroup by this name), a server should be found, and mapping should

complete. Unfortunately, the default server is passed to the enumeration

call and set to the authenticating server in the MUD. Because of this,

there is no known workaround for the problem except a [machine]-based

mapping.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00


WINMIF Fails If XNF File Has Text Before Numeric Fields

Article ID: Q124995

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you create a MIF form (XNF file), such as the example below, the form

fails when a client enters the number field. If numbers are inserted into

the text field, the data entry continues without problems.

Example

-------

Item                Type    Length/Default    Storage

------------------------------------------------------

first name          txt         20            specific

last name           txt         20            common

phone number        txt         20            common

organization        txt         40            common

department          txt         50            common

manager             txt         30            common

mail station        txt          9            common

monitor bar code    number       0            common

Computer bar code   number       0            common

WORKAROUND

==========

If the form is altered such that the number fields are first, then the data

entry continues.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig

Additional reference words: sms prodsms 1.00


Incorrect Swap File Size Reported for Client Computers

Article ID: Q124996

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you look at the PC Memory icon from within Machine Properties of the

Systems Management Server Admin user interface, the swap file size

for Windows for Workgroups version 3.11 or Windows version 3.1 is

incorrectly reported as only 16 megabytes (MB).

WORKAROUND

==========

To work around this problem, use the Diagnostics icon and look at the

Windows Memory. The correct swap file size is reported.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

Additional reference words: sms wfw wfwg prodsms 1.00

KBCategory: kbui kbbug1.00 kbfix1.10

KBSubcategory: ntui ntinterop


Network Monitor Displays Expiration Notice

Article ID: Q125059

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you start the version of Network Monitor that is shipped with Systems

Management Server version 1.0, the following error message appears:

   The expiration date on this product will be reached within 10

   days. If the support situation has not been resolved, please

   contact your support representative for more information.

CAUSE

=====

Network Monitor is located in the NMWFW directory on the SMS version 1.0

CD. Before Network Monitor was shipped with SMS, the program included a

built-in timer that would disable the use of the program after a certain

number of days. The code that displays the expiration message was included

with this version of Network Monitor, but the disabling feature was not.

RESOLUTION

==========

The error message can be ignored. Network Monitor will continue to work

normally.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

Additional reference words: sms prodsms 1.00 netmon.exe wfw wfwg 16-bit

Windows

for Workgroups

KBCategory: kbtool kbbug1.00 kbfix1.10

KBSubcategory: ntutil


Shadow Effect with SMS MachineIDs and NetWare 500/1000 Licenses

Article ID: Q125455

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you use Systems Management Server to administer a NetWare 4.x

server with a 500- or 1000-client license, the SMS MachineID starts

repeating after the 255th user connects. Because SMS uses the IPX address

for NetWare MachineIDs, duplicate MachineIDs are assigned for SMS clients

in the SMS Administrators Sites window. The SMSID is not duplicated.

CAUSE

=====

SMS uses the NetWare bindery and the 3.x NetWare application program

interface (API) calls to get the IPX address for a machine on a NetWare

domain. The IPX address is then used to create the MachineID for each

client. The NetWare 3.x APIs that support bindery calls wrap at the 255th

connection. For example, when the 256th client connects, SMS attempts to

get the IPX address for that client. The NetWare API call returns the IPX

address for connection one instead of 256, connection two instead of 257,

etc. This creates a shadow effect as the 256th SMS client gets the same

MachineID in the Sites window as the first SMS client.

Older NetWare IPX stacks were designed to work with NetWare 2.x and 3.x

servers which had a maximum of 250 users and connections available. This

allowed the IPX stack to use only one byte to represent the connection ID.

With NetWare 4.x servers, 500 and 1000 users and connections are supported.

The problem occurs when an older IPX stack connects to a NetWare 4.x server

that currently has 255 or more connections already assigned. If the

connection ID is returned by the server as 256 or greater, the IPX stack

can only store the lower 8 bits. The IPX stack thinks the connection IDs

256, 512, and 768 are 1, and IDs 257, 513, and 769 are 2, and so on.

When INVDOS asks the IPX stack on a client to return the IPX address, the

IPX stack then requests the IPX address from the server. Since the request

includes connection "1" instead of connection "256," the return IPX address

is incorrect. This incorrect IPX address is then reported through the SMS

system and ends up in the SQL database. This is why SMS seems to be

reporting duplicate MachineNames for unique SMS clients.

The NetID property is always returned correctly. This only affects the IPX

address.

RESOLUTION

==========

Use the latest version of IPXODI. Do not use IPX.COM or MSIPX.COM.

KBCategory: kbnetwork kbinterop

KBSubcategory: ntinterop

Additional reference words: sms prodsms 1.00 Novell net machine id


SMS Inventory Processor: Compilation Error on Dell Computers

Article ID: Q126027

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

Some Dell computers are reporting the BIOS date in European format instead

of United States (American) format, causing the SMS Inventory Processor to

report the following error when processing a RAW file from one of the

computers:

   Compilation Error

NOTE: All errors are posted in the INVPROC.LOG file.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.0 kbfix1.0

KBSubcategory: ntconfig ntdomain

Additional reference words: sms prodsms 1.00


DOCERR: Moving Sender Outbox In SMS 1.0 is Unsupported

Article ID: Q126229

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

--------------------------------------------------------------------------

SUMMARY

=======

The "Microsoft Systems Management Server Administrator's guide" states the

following on page 188:

   You can change the name of an outbox or move the outbox to

   a different server or drive.

Changing the location or the name of the sender outboxes used by the

Systems Management Server senders has not been tested by Microsoft

and is not supported in SMS version 1.0. For more information, refer to

section 17 of the SMS Release notes (README.TXT).

MORE INFORMATION

================

Following the instructions on page 189 of the SMS Administrator's guide

to move the outbox results in errors similar to the following in the

LANSEND.LOG file:

   Checking for sending capacity. Used 0 out of 5.

   Connecting to D:\SMS\Site.srv\sender.box\requests\LAN_DEFA.000

   No (more) send requests found to process

   Registry indicates no outbox for the sender to scan.

You may be able to effectively relocate the outbox by initiating three

updates to the proposed properties (watchdog cycles) by the

SMS_Site_Config_Manager:

1. Choose Site Properties.

2. Choose Outboxes

3. Choose Proposed Properties.

4. Choose OK until you are prompted to update the site.

This causes one watchdog cycle to occur. Since three watchdog cycles are

required to make the requested change take effect, repeat these steps two

more times.

These steps are also required to move the outbox back to the original

supported location. You need to do this if you attempted to move the outbox

as explained in the "Systems Management Server Administrator's Guide."

REFERENCES

==========

The SMS release notes are located in the root directory on the SMS

CD in README.TXT.

KBCategory: kbdocerr

KBSubcategory: ntdocerr

Additional reference words: sms 1.00 prodsms


Terminate Viewer Option in Remote Control Agent Does Not Work

Article ID: Q126639

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you take remote control of a client computer from Help Desk and

minimize the Quick Windows Viewer in Systems Management Server version

1.0, the Terminate Viewer option in the Remote Control Agent on the client

computer does not work.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntutil

Additional reference words: sms prodsms 1.00


PCM and PGC Cannot Connect to Servers With Long Names

Article ID: Q126643

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When Package Command Manager (PCM) or Program Group Control (PGC) attempt

to connect to some logon servers, they error messages indicating that they

were unable to complete their configurations appear. Other servers work

properly. PCM indicates that it was unable to find a server. PGC indicates

that it could not complete updating the client; the SMSLOG.TXT shows that

Error 20 occurred. Any connections to servers than contain 12 characters or

less work correctly. When you run the /DEBUG switch or watch a network

trace of the transaction, you see that the programs appear to be connecting

to the server properly.

CAUSE

=====

The applications are attempting to connect to a logon server with more than

12 characters in it's server name.

WORKAROUND

==========

To work around this problem, use 12 or fewer characters for the server

name.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbother kbbug1.00 kbfix1.10

KBSubcategory: nt16app nt32app

Additional reference words: sms prodsms 1.00


Access 2.0 Err Msg with SMS: Can't Find Wizard, or There is...

Article ID: Q127073

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

After you install Microsoft Access 2.0 as a Shared Application package

in Microsoft Systems Management Server version 1.0 using the

supplied ACS200.PDF, the Access Wizards are not installed. If you choose

a Wizard, the following error message appears:

   Can't find Wizard, or there is a system error in the

   Declarations section of an Access Basic module. Check the

   [libraries] section of msacc20.ini for required libraries, and

   compile all Access Basic modules in the database.

WORKAROUND

==========

To work around this problem, use a text editor such as Notepad and add

the following entries to the [LIBRARIES] section of the MSACC20.INI file:

   wzlib.mda=rw

   wzTable.mda=rw

   wzQuery.mda=rw

   wzfrmrpt.mda=rw

   wzbldr.mda=rw

NOTE: You must add the above entries for each client installation.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig

Additional reference words: prodsms 1.00 sms


Bad .RAW File Hangs Inventory Processor

Article ID: Q128143

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

No new inventory shows up in Personal Computer Properties, .RAW files

continue to get added to the SMS\SITE.SRV\INVENTRY.BOX directory on the

site server, and the inventory processor appears to be hung. In some cases,

the SMS_EXECUTIVE will stop suddenly.

CAUSE

=====

SMS has no mechanism to pass over a bad .RAW files. As a result, bad .RAW

files passed to the INVENTRY.BOX directory on the Site Server, remain in

that directory without being processed and all other inventory files will

backup behind it.

WORKAROUND

==========

To work around this problem, stop SMS_EXECUTIVE, remove the bad .RAW file,

and restart SMS_EXECUTIVE.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server version 1.0. This problem was corrected in Systems

Management Server version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntnetserv

Additional reference words: 1.0 SMS prodsms sms stop stops responding hang

hangs


SMS Package Number is <null>

Article ID: Q128144

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

Package Number is an inventory attribute for software that appears when a

NetWare distribution server is introduced into a Systems Management Server

site. However, only NetWare servers report a value for this field.

All other machines report null.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server version 1.0. This problem was corrected in Systems

Management Server version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: nt32app

Additional reference words: 1.00 SMS prodsms sms nul


SMS: WUSER GP Faults with Compaq Qvision Adapter

Article ID: Q128613

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you use the Remote Control Applet (WUSER.EXE) to remotely control a

16-

bit Windows client, the following error appears:

   WUSER2 caused a general protection fault in module IDIS_LM.DLL at

   0005:0dd0

This GP-fault occurs when the client workstation has Compaq Qvision Windows

driver CPQLQV04.DRV and is using 640x480 16 colors 16 dot fonts.

WORKAROUND

==========

Change the Qvision driver resolution from 16 colors to 256 colors or use

the Standard VGA driver instead of the Qvision driver.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Systems

Management Server version 1.0. This problem was corrected in Systems

Management Server version 1.1.

Additional reference words: prodsms 1.00 sms

KBCategory: kbnetwork kb3rdparty kbbug1.00 kbfix1.10

KBSubcategory: nt16ap ntdriver


Macintosh Clients Generate Event ID 180 and MIF Files

Article ID: Q129125

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

At a Systems Management Server Site which contains Macintosh clients,

Event ID 180 may be frequently written to the system log and several .MIF

files may be created, along with corresponding events in the Windows NT and

Systems Management Server Event Viewers. The Windows NT Event Viewer

application Log and SMS Event Viewer messages have the following syntax:

   Information from module: SMS_INVENTORY_DATA_LOADER.

   Operation:   Validation

   Object:      MIF

   Object name: SMS

   A new machine is being entered into the database. Some of the

   identification attributes for the machine being added overlap with

   another machine in the database.

   Current Machine:

   <SMSID = LAM00002, SMSLocation = LAM|LAMWORLD|, NetCardID =

   08:00:07:B4:AD:65>

   Overlapping Machine:

   <SMSID = LAM0000L, SMSLocation = LAM|LAMWORLD|, NetCardID =

   08:00:07:B4:AD:90>

   MachineName = LAMJAM

   SiteCode = LAM

   Component = SMS_INVENTORY_DATA_LOADER

CAUSE

=====

Microsoft Systems Management Server checks the inventory .MIF files from

each Macintosh client for a unique SMSLocation attribute (no other client

in the Systems Management Server Database has the same SMSLocation). The

SMSLocation attribute is a concatenation of the client's Systems Management

Server Site code, Domain, and Name attributes. If Systems Management Server

determines that an inventory .MIF file contains an SMSLocation attribute

that is not unique, Systems Management Server generates a Windows NT Event

and a Systems Management Server Event .MIF file for each machine in the

Systems Management Server database that has the same SMSLocation.

When the Systems Management Server Macintosh Inventory Agent determines

that a Macintosh client does not have a Macintosh Name defined in the

Macintosh Sharing Setup, the inventory leaves the Systems Management Server

Name attribute blank. Therefore, when multiple Macintosh machines reside in

the same site/domain combination have no Macintosh names, their SMSLocation

is not unique. This generates Event Viewer messages and Event MIF files.

RESOLUTION

==========

To workaround this problem, define a unique Macintosh name for each

Macintosh client. The Macintosh computer name is created by running the

Sharing Setup application in the Macintosh System Folder's Control Panel.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntinterop

Additional reference words: prodsms 1.00 sms


Cannot Use Icon When Setting Up Share Package

Article ID: Q129576

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you create a share package and select an icon for that package, some

icons fail to appear when the file containing the icon is chosen. A

specific case can be reproduced with MSOFFICE.EXE and MACRODE.EXE from the

Microsoft Office CD:

1. Create new share package.

2. Choose the New button next to Program Items.

3. Choose Change Icon.

4. Choose the "..." button next to the File Name box.

5. Change to the directory that contains the setup and .EXE files for

   Microsoft Office.

6. Choose MSOFFICE.EXE.

No icon is displayed for this file. In Program manager, you can create a

new program item, change the icon using the same file name as above, and it

will show the icon.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntgeneral

Additional reference words: 1.00 prodsms sms


System Management Server Setup Limits Path of Devices

Article ID: Q130540

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you install a primary site, Systems Management Server Setup limits the

length of the path for the location of the database and log devices. The

text field for the path does not scroll and the computer beeps when the

limit is reached. The total number of characters allowed for the path

depends on the width of the character used (and may be fewer than 40

characters).

WORKAROUND

==========

To work around this problem, create the database and log devices using the

Microsoft SQL Administrator utility. This method requires the user

specifies only the database device name and the log device name, rather

than the full path of the database and log devices.

STATUS

======

Microsoft has confirmed this to be a problem in System Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig ntsetup

Additional reference words: prodsms 1.00 sms


Systems Management Server Executive Service Hangs

Article ID: Q131698

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you have multiple parent-child relationships with primary sites,

Systems Management Server may stop reporting inventory from the child sites

to the central sites. Large amounts of jobs may be waiting in the

Scheduler.

CAUSE

=====

This problem occurs if you have large number of clients and helper servers.

If you separate Systems Management Server and SQL Servers onto separate

servers and move the Scheduler and Despooler services to the SQL Server

server, the Executive service may lose which server controls which service.

WORKAROUND

==========

To work around this problem:

1. Restore the Scheduler and Despooler services back to the Systems

   Management Server.

2. Stop and re-start the services and inventory should start being

   reported.

3. To move the services back to the SMS site server, from the SMS ADMIN UI:

   a. Go to the site properties windows

   b. Choose the Services button

   c. Click on Proposed Properties

   d. Change the server name of the services back to the SMS site server

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig ntdomain

Additional reference words: prodsms 1.00


SMSRUN16 Fails To Detect SECONDNET.DRV in Windows for Workgroups

Article ID: Q131777

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

In a multi-network environment (such as IPX/ODI and TCP/IP-32 for

Windows for Workgroups), SMSRUN16 does not check the secondary network

for a logon when it attempts to run the Systems Management Server Client

programs.

CAUSE

=====

This problem occurs when you log on to the NetWare network through

SECONDNET.DRV, but select Cancel when you are prompted to log on to the

Microsoft network. As a result, at system startup, SMSRUN16 runs from

the WIN.INI file Load= line and attempts to check for a valid network so

it can run Program Group Control and Package Command Manager. SMSRUN16

finds no primary network through NETWORK.DRV because you have not logged

on, but it fails to evaluate the NetWare network through SECONDNET.DRV.

WORKAROUND

==========

To work around this problem, the driver statements can be swapped so that

the network that you are logged on to appears for the primary network

(NETWORK.DRV=).

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management

Server version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 3.11a sms


INVDOS Does Not Report TCP/IP-32 3.11a Client IP Address

Article ID: Q131904

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft TCP/IP-32 for Windows for Workgroups version 3.11a

----------------------------------------------------------------------

SYMPTOMS

========

INVDOS does not report the IP address of a Windows for Workgroups 3.11

client computer using TCP/IP-32 3.11a and dynamic host configuration

protocol (DHCP).

CAUSE

=====

This problem occurs when there is no Default Gateway defined for Microsoft

TCP/IP.

WORKAROUND

==========

To work around this problem:

1. Run Network Setup and choose Drivers.

2. Select Microsoft TCP/IP-32 3.11a and choose Setup.

3. Enter an IP address for the Default Gateway.

4. Choose OK and quit Network Setup.

5. Restart the computer and Windows for Workgroups.

The next time this client computer is inventoried, the IP address is

reported.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 sms inventory automatic

configuration enabled


SMS Fails To Create Jobs On Non-US SQL Server 4.21a

Article ID: Q132248

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

Systems Management Server fails to create jobs on site servers using a non-

U.S. version of Microsoft SQL Server version 4.21a and the following

appears in the Systems Management Server event log:

   323  The job has been failed without performing any actions,

        because the generated list of target workstations was empty.

        The provided query, machine group, or machine path, along

        with any site limiting, resulted in zero machines being

        targeted. Therefore, the job has nothing to do.

CAUSE

=====

The time and date format used for SQL Server do not match the required

formats used for Systems Management Server. For example, if you install

a French version of SQL Server on a U.S. version of Windows NT, French

is the default language for the SQL Server.

WORKAROUND

==========

To work around this problem:

1. Run SQL Administrator and connect to SQL Server.

2. Choose Logins to open the System Logins Management window.

3. Double-click on the SMS account used for SQL operations to open the

   System Logins Properties window for that account.

4. From the Language scroll box, select "us_english".

5. Restart SQL Server.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem was corrected in Systems Management Server

version 1.1.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntconfig ntdomain

Additional reference words: prodsms 1.00


SMS Reports Incorrect Disk Information on NetWare Servers

Article ID: Q132250

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

The Disk information in Systems Management Server Administrator Personal

Computer Properties incorrectly reports the amount of Free Storage and

Storage Size on NetWare volumes larger than two gigabytes (GB).

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management

Server version 1.0. This problem was corrected in Systems Management Server

version 1.1.

MORE INFORMATION

================

This may adversely affect the distribution of packages to NetWare servers

if the compressed package being distributed is larger than the available

storage space Systems Management Server sees. Therefore, ensure your

NetWare distribution servers each have sufficient storage space prior to

distributing any packages.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntinterop ntfilesys

Additional reference words: prodsms 1.00 Novell


SMS: Inventory Does Not Distinguish Individual Raid 5 Drives

Article ID: Q121207

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When running Inventory from  a Systems Management Server on a machine

that has a RAID 5 disk array, Systems Management Server reports only one

drive controller.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kbui

KBSubcategory: ntui


SMS Administrator Doesn't Show New Architectures

Article ID: Q122203

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

If a new architecture is added to the Systems Management Server database,

it does not appear in SMS Administrator until you exit and restart SMS

Administrator.

CAUSE

=====

The Systems Management Server Administrator code currently caches

architecture information and does not refresh itself when new architectures

are added.

WORKAROUND

==========

Exit Systems Management Server Administrator and restart it to see newly

added architectures.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntutil


Sub-directory and File Permissions Not Set on Macintosh Volume

Article ID: Q122225

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When Microsoft Systems Management Server creates a Macintosh volume

(SMS_SHR for example), it does not create file-level permissions for any

sub-directories. This results in Macintosh systems having write privileges

for the LOGON.SRV\MAC.BIN and other sub-directories.

CAUSE

=====

The SMS_MAINTENANCE_MANAGER service does not set the Macintosh file

permissions on the ..\LOGON.SRV directory on servers where Windows NT

Services for Macintosh have been installed. Macintosh directory permissions

(which are similar but not the same as Windows NT file and directory

permissions) default to write access on ..\LOGON.SRV and its sub-

directories. This creates a security leak, since some user could replace

executable files in the ".BIN" directories.

WORKAROUND

==========

Once the Macintosh volume is created by the SMS_SITE_CONFIG_MANAGER

service, the SMS_MAINTENANCE_MANANGER service ignores permissions if it

updates these directories during the normal maintenance cycle. This allows

the Systems Management Server administrator to configure the sub-directory

and file permissions manually to deny Macintosh users write privileges.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbfix1.10

KBSubcategory: ntmac

Additional reference words: sms sfm prodsms 1.00 1.10


Scheduler Overwrites Package Property Information

Article ID: Q122382

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

After Scheduler processes a job on a package, the package information is

written back into the original database overwriting any changes that were

made to the package properties by the Administrator.

For example, when the Scheduler reads and compresses a package, it may take

a long period of time, depending on the size of the package. During the

same time, the Administrator may be changing the properties of the package.

This information is overwritten when Scheduler completes the process.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntutil


Non-Existing Administrative Share Causes Incomplete Site

Article ID: Q122386

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you install a Systems Management Server version 1.0 site to a

non-existing Windows NT Server's administrative share (for example: C$),

the Setup program does not display a warning message, and installs an

incomplete site (missing subdirectories).

WORKAROUND

==========

To work around this problem, do the following:

1. Remove the site.

2. Restart the Windows NT Server.

3. Install the Systems Management Server site again.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntsetup


APPCTL Err Msg: Failed to Connect to SMS Network Server...

Article ID: Q122569

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

In Microsoft Systems Management Server, when Application Control

(APPCTL) runs out of memory trying to allocate a buffer space to determine

which user groups a user belongs to, the following error message may

appear:

   Failed to connect to SMS network server. Cannot determine which user

   groups the user belongs to.

In addition, if the same behavior occurs during the logon process, APPCTL

displays a dialog box with the same error message every 15 minutes until

the allocation of a buffer space is successful.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kberrmsg kbbug1.00 kbbug1.10

KBSubcategory: ntnetserv ntutil

Additional reference words: sms prodsms 1.00 1.10 appcontrol program

control pgc


SMS Err Msg: PowerPoint Could Not Locate or Start the Quick....

Article ID: Q122989

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you start a shared version of Microsoft PowerPoint Quick Viewer, the

following error message appears:

   PowerPoint could not locate or start the Quick Preview. It can be

   installed using PowerPoint Setup.

When you attempt to start PowerPoint Quick Viewer a second time, the

application runs fine.

CAUSE

=====

This problem is caused by a communication failure between AppStart and

Quick Preview in correctly distinguishing a busy condition from a failure

to launch the application.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kberrmsg kbbug1.00 kbbug1.10

KBSubcategory: nt16ap


AppStart Doesn't Change Cursor to Hourglass

Article ID: Q122990

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you start a Microsoft Systems Management Server shared

application, AppStart does not change the cursor to the "waiting" hourglass

cursor. This may cause the user to think the application wasn't launched.

CAUSE

=====

AppStart isn't changing the cursor type when it is called. Because AppStart

can take up to 15-20 seconds before the actual application loads and

starts, the cursor will remain an arrow for this amount of time until the

actual application takes over and changes the cursor type.

This can result in the user thinking the application didn't launch and

attempting to launch the same application again, resulting in multiple

copies of the application being launched when AppStart finally catches up

with the user's input.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntui


SMS Inventory Disables Speaker on Client Computer

Article ID: Q123106

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you use the Microsoft Systems Management Server Inventory Agent

on a client computer, the speaker on the client computer stops working.

For example, you can load the speaker by adding the following line to the

[drivers] section of the SYSTEM.INI file:

   Wave = speaker.drv

After the SMS client runs the inventory, you lose the speaker; that is, if

you test the CHIMES.WAV file from the Control Panel Sound applet, there is

no sound, regardless of the volume setting.

CAUSE

=====

This problem occurs when you use the SPEAKER.DRV file that was written for

the MCI sound driver.

RESOLUTION

==========

Restart (reboot) the client computer but do not run the inventory

(SMSLS.BAT); the speaker will return to normal.

STATUS

======

Microsoft is researching this problem and will post new information here in

the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbenv

KBSubcategory: ntdriver


Blank APPSTART Icon

Article ID: Q123616

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

A Systems Management Server client's SMS-created program group

contains a blank icon with the title APPSTART instead of the proper icon

for that application. Choosing the icon results in the associated program

running normally.

CAUSE

=====

The program item created in SMS Administrator has a name that exceeds 40

characters. While SMS Administrator allows names up to 64 characters,

Applications Manager cannot handle names greater than 40 characters.

Applications Manager will log the following information during its watchdog

cycle when this problem happens.

NOTE: Error 10 translates to NADERR_INVALIDDATASIZE.

APPMAN.LOG

----------

Checking for transactions to process.

Checking Integrity of NAD.

UPD ##> Error setting program item for package 'BPC00014'. (10)

Checking the server lists for all program items in NAD.

Updating foreign package master transfer file data.

Additionally, the SMS clients PGC will log errors in its SMSLOG.TXT file:

SMSLOG.TXT

----------

[12/02/94 09:49:05] Program Group Control ==> Failed to delete the network

connection k:

[12/02/94 09:54:04] Program Group Control ==> Could not execute Program

Manager DDE command [CreateGroup ("MCP Info (SMS)", 0)] [AddItem

("APPSTART.EXE BPC00025", "")] [ReplaceItem ("")]

[AddItem("APPSTART.EXE BPC00025","","C:\WINNT\HMSICONS\BPC00025.ICO",0,,,""

,,0)].

[12/02/94 09:54:05] Program Group Control ==> Could not execute Program

Manager DDE command [CreateGroup ("MCP Info (SMS)", 0)] [AddItem

("APPSTART.EXE BPC00024", "")] [ReplaceItem ("")]

[AddItem("APPSTART.EXE BPC00024","","C:\WINNT\HMSICONS\BPC00024.ICO",0,,,""

,,0)].

[12/02/94 09:54:07] Program Group Control ==> Could not execute Program

Manager DDE command [CreateGroup ("MCP Info (SMS)", 0)] [AddItem

("APPSTART.EXE BPC00022", "")] [ReplaceItem ("")]

[AddItem("APPSTART.EXE BPC00022","","C:\WINNT\HMSICONS\BPC00022.ICO",0,,,""

,,0)].

WORKAROUND

==========

Rename the program item to a name of 40 characters or less.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntui

Additional reference words: sms prodsms 1.00 1.10 NAD applications database


VIEWNAD Does Not Display Platform Type Correctly

Article ID: Q124038

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When using VIEWNAD to display the network applications database (NAD) for a

Systems Management Server site, the Platform entries display 10 byte

values. These entries do not contain valid platform bitmasks and are not

usable.

CAUSE

=====

VIEWNAD is parsing the NAD incorrectly for platform data. This causes the

data to be invalid.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntutil

Additional reference words: sms prodsms 1.00 1.10


WIN.INI Not Found by SETLS from DOS on LAN Manager Clients

Article ID: Q124381

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you run NET LOGON on a LAN Manager client from the AUTOEXEC.BAT file,

and an SMSLS.BAT file exists in the client's logon script, SETLS16.EXE

cannot find the WIN.INI file pointed to by the SMSLS.INI file on the logon

server. This causes inventory to be reported to the logon server's Systems

Management Server site instead of the domain/site pointed to by the

[SMS] section in the WIN.INI file.

CAUSE

=====

SETLS16 looks for the WINDIR environment variable and from that determines

the location of WIN.INI. This fails because WINDIR doesn't exist yet when

you execute the logon script. This is true regardless of the current

directory the user is in. Putting WIN.INI in drive C allows this to work.

Logging on to the domain from within Windows works.

This does not affect CLI_DOS which looks in the WINDIR and also walks the

PATH statement looking for WIN.INI.

WORKAROUND

==========

Do one of the following to work around this problem:

 - Logon from within Windows only.

   -or-

 - Set up the AUTOEXEC.BAT file to contain the line "SET windir=C:\<windows

   directory>". Note the variable "windir" needs to be in lowercase.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: sms prodsms 1.00 1.10 Win16 resource master

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntinterop


INVDOS Crashes AutoCAD Mouse/Tablet Driver

Article ID: Q125624

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

While using Systems Management Server to inventory MS-DOS or Windows

(16-bit) systems that have AutoDesk's AutoCAD versions 10, 11, or 12

installed, INVDOS will disable the CCMOUSE driver. CCMOUSE is used to

emulate a mouse while using a graphics tablet. The tablet becomes unusable.

INVDOS will complete normally and not report any errors.

CAUSE

=====

When INVDOS is run on systems using CCMOUSE, the mouse detection and

identification tests disable the tablet; the tablet/mouse cursor cannot be

used. The only recovery is to cold boot (power down) the computer and

tablet, and use AutoCAD setup to reconfigure the tablet.

NOTE: When INVDOS completes normally, any SMSSAFE.TMP file is deleted.

Since this file doesn't show that a hardware failure has occurred, the next

time INVDOS is run the same problem will occur.

WORKAROUND

==========

Create an SMSSAFE.TMP file that contains a "MouseInfo=CRASHED" line. The

next time INVDOS is run, it will find the MouseInfo line, and will not run

the mouse test. It will modify the SMS.INI file, "FailedHardwareCheck" to

include the mouse test. This will prevent INVDOS from attempting to run the

mouse test on that client from then on.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbhw kbbug1.00 kbbug1.10

KBSubcategory: nthw nt16ap ntdosap

Additional reference words: sms prodsms 1.00 1.10


Err Msg: Application Database Cannot Server, Share or Dir...

Article ID: Q125626

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When using Program Group Control (PGC) on a Systems Management Server

client, error message 11114 appears in the SMSLOG.TXT file:

   Application database cannot server, share or directory entries in SMS

   Profile

This error is ambiguous and does not explain what problem was encountered

by PGC.

CAUSE

=====

Error 11114 actually indicates that PGC was unable to read a server, share,

or directory name from the SMS.INI file. This could be caused by a number

of problems like a corrupted file or mismatched [Server] and [Share]

sections.

RESOLUTION

==========

The SMS administrator will need to examine the SMS.INI file to determine

what entry is causing the problem.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: nt16app nt32app ntdocerr

Additional reference words: sms prodsms 1.00 1.10


SMS Will Not Deinstall On Windows for Workgroups clients

Article ID: Q125978

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you run DEINSTAL.BAT on a Windows for Workgroups SMS client machine

and Logon at Startup is not selected, the following message appears:

   Your machine has successfully been prepared for deinstallation.

   Microsoft SMS will be deinstalled the next time you start Windows. Phase

   1 of Client de-install complete. If this is a Windows machine, you must

   start or restart Windows now for the deinstallation to complete.

The next time you start Windows for Workgroups, SMS is not removed.

However, the next time you start Windows for Workgroups, choose the Log

On/Off icon in the Network group, and log on, a similar message appears.

Neither the SMS nor program groups are removed. In addition, the

applications specified on the SMSRUN16.INI autostart line are not run.

CAUSE

=====

SMS does not display a dialog box asking the user to logon when it detects

that the Windows for Workgroups machine is not logged on.

WORKAROUND

==========

To work around this problem:

1. Run Control Panel and choose the Networks icons.

2. Choose Startup.

3. Select Log On at Startup.

4. Choose OK.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

================

When you run DEINSTAL.BAT or UPGRADE.BAT, Client Setup flags the SMS.INI

file to indicate that SMS needs to do one or more of the following:

 - Install a new client component.

 - Remove a client component.

 - Complete client upgrade.

 - Remove the client.

When Windows is restarted, SMSRUN16/32 checks the SMS.INI file. If SMS

determines in needs to perform one of the previously mentioned tasks, it

connects to the logon server and launches SMSSRV16/32. SMSRUN16/32 then

calls Client Setup to do the actual installation or removal of files. When

Client Setup is done, SMSSRV16/32 processes the SMSRUN*.INI file and loads

the applications to be automatically started.

SMS uses this sequence because SMSRUN16/32 has to ensure that none of the

SMS client components, including itself, are running while Client Setup

tries to delete or overwrite their files.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: nt16app ntinterop ntutil

Additional reference words: sms 1.00 1.10 3.11 prodsms section SMS.INI

SetupPhase=deinstall [WorkstationStatus] (CLI_DOS, CLI_NT) deinstall

autostarted deinstalled


SMS Hierarchy Manager Fails Due to Stack Overflow

Article ID: Q126283

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

The SMS Hierarchy Manager process terminates unexpectedly due to a stack

overflow. If you attempt to manually start the SMS_HIERARCHY_MANAGER

service from Services in Control Panel, the following error appears:

   Error 1067: The process terminated unexpectedly.

In addition, a Dr. Watson error log is generated which indicates a stack

overflow occurred in the PREINST.EXE module.

CAUSE

=====

You may have inadvertently implemented a Systems Management Server

version 1.0 hierarchy which contains a circular path. For example,

Site A reports to Site B, Site B reports to Site C, and Site C reports to

Site A.

RESOLUTION

==========

To correct this problem, use an SQL query of the Sites table to reveal the

current parent assignments. Correct the tree from the bottom up using the

PREINST /DELSITE command. You can also correct the tree manually from the

Sites table. For complex hierarchies, determining the location of the

circular reference can be difficult.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


Problem Running SMS on CNTFS Partition

Article ID: Q126284

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.51

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

Systems Management Server version 1.0 performance degrades after

upgrading to Windows NT Server version 3.51.

CAUSE

=====

Windows NT version 3.51 includes support for file compression on Windows NT

file system (NTFS) partitions (called Compressed NTFS [CNTFS]). CNTFS is

based on a new compression file attribute. If SMS resides on a CNTFS

partition, both SMS and CNTFS may attempt compression of the same files.

This imposes unneeded overhead.

For example, if the SMS Scheduler compresses a package for distribution, a

compressed data stream is written to a file. If the file attributes have

the compression bit set, CNTFS attempts to compress this data stream when

writing to the disk. Redundant compression attempts waste server resources

causing performance to degrade.

WORKAROUND

==========

To prevent this redundant operation, ensure that directory and file

attributes in the SMS\SITE.SRV directory and subdirectories do not have

the compression bit set. To do this, type the following at the MS-DOS

command line:

   COMPACT /U /I /S <x>:\SMS\SITE.SRV\*.*

where <x> is the host drive of the SMS installation. This clears the

compression bit on current files and directories and prevents CNTFS from

compressing the files in the future. SMS still compresses package files

according to its own configuration settings.

NOTE: In addition to file compression on package files, server performance

can also be affected by the compression of files located in the

subdirectories below LOGON.SRV. If these files are compressed by CNTFS,

additional server overhead is required to make the data available to SMS

clients.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


SMS Does Not Use Local Thesaurus for Word for Windows 6.0

Article ID: Q126576

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you specify the location of the thesaurus during a workstation

installation of Word for Windows version 6.0 on a Windows for

Workgroups version 3.11 system, Systems Management Server version

1.0 overwrites the user-modified entries in the WINWORD6.INI file with the

Universal Naming Convention (UNC) location of the Windows for Workgroups

shared thesaurus.

For example, after you install Word for Windows, the WINWORD6.INI file

contains:

   [Microsoft Word]

   Thesaurus 1033,0=\\<server name>\<share name>\PROOF\MSTHES.DLL,

   \\<server name>\<share name>\PROOF\MSTH_AM.LEX

You modify the WINWORD6.INI file to read:

   [Microsoft Word]

   Thesaurus 1033,0=C:\WINWORD\PROOF\MSTHES.DLL,

   C:\WINWORD\PROOF\MSTH_AM.LEX

After you install SMS, the WINWORD6.INI file contains:

   [Microsoft Word]

   Thesaurus 1033,0=\\<server name>\<share name>\PROOF\MSTHES.DLL,

   \\<server name>\<share name>\PROOF\MSTH_AM.LEX

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbinterop kbnetwork kbsetup kbbug1.00 kbbug1.10

KBSubcategory: ntinterop nt16ap

Additional reference words: sms prodsms 1.00 1.10 winword word6


SMS Modifies Application INI Files

Article ID: Q126577

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you specify the location of the WORKGROUP-DOT-PATH during a

workstation installation of Word for Windows version 6.0 on a Windows for

Workgroups version 3.11 system, Systems Management Server overwrites the

user-modified entries in the WINWORD6.INI file.

For example, after you install Word for Windows, your WINWORD6.INI file

contains:

   [Microsoft Word]

   USER-DOT-PATH=C:\WINWORD\TEMPLATE

   WORKGROUP-DOT-PATH=<net drive>:\TEMPLATE

   where <net drive> is the network drive letter of the shared application.

You modify the WINWORD6.INI file to read:

   [Microsoft Word]

   USER-DOT-PATH=C:\WINWORD\TEMPLATE

   WORKGROUP-DOT-PATH=C:\WINWORD\TEMPLATE

After you install SMS, the WINWORD6.INI file contains:

   [Microsoft Word]

   USER-DOT-PATH=C:\WINWORD\TEMPLATE

   WORKGROUP-DOT-PATH=<net drive>:\TEMPLATE

   where <net drive> is the network drive letter of the shared application.

KBCategory: kbinterop

KBSubcategory: ntinterop nt16ap

Additional reference words: sms prodsms 1.00 1.10 winword word6


INVDOS Does Not Detect NEC 3x CDROM drives

Article ID: Q126715

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

INVDOS does not detect a NEC 3X CD-ROM drive installed on an MS-DOS or

Windows workstation, even though Microsoft Diagnostics (MSD) does detect

the drive and the version of MSCDEX that is installed.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbusage kbbug1.00 kbbug1.10

KBSubcategory: nt16ap ntinterop ntutil

Additional reference words: sms prodsms cdrom SMS


SMS: Visual Basic Application Setup Fails When Executed by PCM

Article ID: Q128612

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When Package Command Manager (PCM) for Windows 3.x tries to execute a

Visual Basic (VB) Setup Wizard setup program, the setup program prompts for

floppy disks even though all the necessary files are located in the package

directory along with the SETUP.EXE file.

Executing the same command from the File manager works correctly.

CAUSE

=====

The VB Setup Wizard, SETUP.EXE, spawns SETUP1.EXE and then exits. When PCM

(PCMWIN16) sees SETUP.EXE exit, it expects setup is complete and deletes

the network connection to the package share. When SETUP1.EXE looks for

necessary files, it cannot find them and prompts for disks.

NOTE: SETUP1.EXE is only the default name of the file spawned by SETUP.EXE.

Developers are free to name it differently. See SETUP.LST for the filename

that is actually being used.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: prodsms 1.00 1.10 toolkit sms

KBCategory: kbnetwork kbinterop kbbug1.00 kbbug1.10

KBSubcategory: nt16ap


Program Group Control Requires Logon Validation

Article ID: Q129232

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When a Systems Management Server version 1.0 client (such as Windows 3.1 or

Windows for Workgroups 3.11), runs SMSRUN16.EXE and the Program Group

Control (PGC), APPCTL16.EXE is called. One or all of the following error

messages may appear if the client user is not logon-validated by the

Windows NT domain controller:

 - PGC-Could not enemurate applications in applications database.

 - PGC-Application database gave error 20

 - PGC-Could not find object application list in application database.

 - PGC-Could not complete the updating of the program configuration,

   contact admin.

CAUSE

=====

This problem occurs because the API call used to determine the global group

membership fails when the user has not been validated by a domain

controller. This most commonly occurs on clients that are located on the

other side of a router from a domain controller and therefore cannot locate

a domain controller to be validated. Real mode TCP/IP stacks that cannot

use the #DOM: entry in the LMHOSTS file encounter this error when they are

located across a router.

WORKAROUND

==========

To workaround this problem, ensure users are validated by a domain

controller when logging into the network.

MORE INFORMATION

================

For the Program Group Controller to determine the user groups the logged-on

user belongs to, it must contact a domain controller to obtain the list of

groups. This will likely be the same server in the domain that validated

the logon request, so if the logon is not validated, the group list will

likely not be obtained either. To ensure the users group memberships can be

obtained by PGC, please ensure the user's logon request is validated by a

domain controller.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntdomain nttcp

Additional reference words: prodsms 1.00 1.10 sms


Systems Management Server Inventory Reports Incorrect CPU Speed

Article ID: Q131701

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

On certain types of processors, Systems Management Server reports the wrong

speed of the processor as well as the incorrect machine type.

CAUSE

=====

Only the following approximate CPU speeds are evaluated and reported:

   8088 (5Mhz)

   80286 (12Mhz)

   80386 (33Mhz)

   80486 (66Mhz)

   Pentium (60Mhz)

Items outside this range may be reported incorrectly.

The following computers are incorrectly identified:

   PS/2 Mod 57-059 - Reported as PS/2 Model 70

   PS/2 Mod 57-OBA - Reported as PS/2 Model 70

   PS/2 Mod 76 - Reported as PS/2 Model 70

   PS/2 Mod 77 - Reported as PS/2 Model 70

The following computers are not recognized as laptops, even though they

are:

   IBM ThinkPad 700, 750C, CS, CE, 720C, CE, 360C, CS, CSE

   NEC Versa V M P

The following also show up incorrectly:

   Compaq Deskpro

   Deskpro XL

   Proliant

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntui

Additional reference words: prodsms sms 1.00 1.10


16-bit Program Group Control Requires Drive Letter

Article ID: Q131716

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

Setting up a package for sharing using "Runs with UNC Name" under Program

Item Properties results in a drive letter being used on a Windows 16-bit

client computer.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms sms 1.00 1.10 pgc appctrl unc naming


Switch Required for USERTSR for WFW 3.1 Clients

Article ID: Q127025

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

When you configure a computer running Windows for Workgroups version 3.1 as

a Microsoft Systems Management Server version 1.0 client, you may

need to add a -W switch to USERTSR in the CLIENT.BAT file located at the

MS\SMS\Bin directory. However, Windows for Workgroups version 3.1 is not a

supported client system for SMS Server version 1.0.

The -W switch loads USERTSR for clients running Windows for Workgroups.

When you use the switch, USERTSR waits for the Remote Control Agent

(WUSER.EXE) to start before initializing itself on the network. Client

Setup does not add this switch because it handles Windows for Workgroups

version 3.1 as if it were a LAN Manager client.

KBCategory: kbnetwork

KBSubcategory: ntinterop ntconfig nthowto

Additional reference words: prodsms 1.00 1.10 wfw 3.10 wfw sms


SMS Error 5000 on Macintosh Client

Article ID: Q127026

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

When you configure a Macintosh computer as a Microsoft Systems Management

server version 1.0 client, the following error message may appear:

   Error 5000, in file shicsetting.cp line 150.

   AFP Access denied.

   AFP Access denied.

   Reading INI file, new SMS.INI.

To correct this problem:

1. From the MacFile menu on the Macintosh computer, select the following

   directory in File Manager:

      SMS\Logon.srv\SMSID

2. Select Permissions from the MacFile menu.

3. Verify Make Changes is selected for all user groups.

KBCategory: kbnetwork

KBSubcategory: ntinterop ntmac

Additional reference words: prodsms 1.00 1.10 mac sfm SMS sms


Remote Control Works Only Once with Micromatic VTD/8 Gateway

Article ID: Q127925

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

If you use the Micromatic VTD/8 gateway with Microsoft Systems Management

Server version 1.0 Helpdesk Remote Control, you may not be able to

take remote control of a Windows for Workgroups version 3.11 client

computer more than once.

CAUSE

=====

Network Monitor reveals that the Micromatic VTD/8 gateway forwards name

requests back onto the NetBEUI protocol, which results in a name conflict.

Echoing name request packets causes SMS Server Viewer not to work.

WORKAROUND

==========

To work around this problem, disable the NetBEUI protocol on the gateway

and use TCP/IP-32 as the default protocol. For more information, contact

Micromatic.

The third-party products discussed here are manufactured by Micromatic, a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

KBCategory: kbnetwork kb3rdparty

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 1.10


TSRs Knows to Conflict with USERTSR(IPX)

Article ID: Q130910

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

The following table documents some terminate-and-stay-resident (TSR)

programs may conflict with USERTSR(IPX) when they are loaded in memory, and

how you may resolve the conflict:

Program                       Resolution

-------                       ----------

McAfee Virus Protection       Remove it from memory

Alcom Fax Redirector          Change multiplex option from 203 to 204

KBCategory: kb3rdparty kbinterop

KBSubcategory: ntgeneral

Additional reference words: sms prodsms 1.00 1.10


Running Macintosh Installer from a Package Subfolder

Article ID: Q121234

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

-----------------------------------------------------------------------

SYMPTOMS

========

If a Macintosh software package is created that contains the actual

Installer in a subfolder of the root of the original source package, and

the package is then distributed to a Macintosh client, the following

message appears and Installer cancels:

   The files needed for this installation could not be found on your server

   volume "SMS_SHR." Please contact your network administrator.

CAUSE

=====

This problem can be caused by a path name syntax error in the Command Line

box in the Command Line Properties dialog box of the Systems Management

Server Administrator program for the package.

RESOLUTION

==========

Make sure that if there is an executable file inside a subfolder of the

package root, that the path begins with a colon (:), followed by the folder

names and ending with the name of the executable file. If there are spaces

in any of the folder or file names, then the entire path needs to be

surrounded by quotation marks. For example, ":Master Set 1:Installer" for a

package named "Mac Fonts," which includes folders Master Set 1, Master Set

2, and so on, and the Installer application inside Master Set 1 is the

executable file.

The path needs to begin with a colon because while MS-DOS, PC-DOS, and

clone operating systems use a backslash (\) to delimit paths, Apple

Macintosh System software uses a colon (:). Without the leading colon, the

Macintosh System software interprets any path as starting with a volume

name.

Additional reference words: sms prodsms 1.00 1.10 mac systems management

KBCategory: kbnetwork

KBSubcategory: nthowto ntinterop ntmac


Using Windows NT Server Standard Server as SMS Helper Server

Article ID: Q121235

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The Windows NT Server Standard Server configuration is not supported by

Systems Management Server version 1.0. However, if a Standard Server is

configured properly, it can be used in a Systems Management Server site

under certain conditions.

MORE INFORMATION

================

A Standard Server can be used in a Systems Management Server site under the

following conditions:

 - A Standard Server that is a member of a domain with SMS installed can be

   used by SMS. A server set up in this configuration is treated similar to

   a Helper Server. A Standard Server that is a member of a workgroup

   rather than a domain cannot be used by SMS. A server set up in this

   configuration is similar to a workstation.

 - For a Standard Server that is a domain member, SMS attempts to install

   the Inventory Agent (INVWIN32) and Package Manager (PCMSVC32). These are

   installed into the SMS\HELPER.SRV directory. A Standard Server behaves

   similar to a Helper Server, but the full functionality of a Helper

   Server has not been tested, so it is not officially supported.

There currently are difficulties with Systems Management Server

differentiating whether a Standard Server is a member of a domain, or a

member of a workgroup that has the same name as a domain.

The Site Configuration Manager insures that all servers in a domain are

accessible with administrator rights. A Standard Server that is a workgroup

member does not have a copy of the domain SAM database, and will not have

the proper Systems Management Server services account.

A Standard Server that is a workgroup member will be used by Systems

Management Server if the following conditions are met:

 - The workgroup must have the same name as a domain that has Systems

   Management Server installed.

 - The Standard Server must have an account identical to the Systems

   Management Server account in the domain mentioned above.

This feature is under review and will be considered for inclusion in a

future release.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


SMS Program Group Controller and AutoDisconnect

Article ID: Q121385

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Windows NT and LAN Manager servers default to 15 minutes of idle time per

connection before marking the connection as available for AutoDisconnect.

This behavior is intended to keep system resources available, and assumes

that clients will transparently reconnect when the client application

accesses the server. Sometimes this AutoDisconnect behavior can cause

strange application problems such as segment load failures or "drive not

ready" errors.

When the Systems Management Server Program Group Controller (PGC)

invokes APPSTART to execute a shared application off a server, it opens the

executable file in read-only mode and keeps it open until the user exits

the application and PGC detects that the connection needs cleaned up.

MORE INFORMATION

================

This became a critical issue for shared applications under Systems

Management Server and this technique eliminates the need to disable

AutoDisconnect for the server, and lets PGC manage the connection. The

Windows NT Server component correctly maintains the connection for clients

running an application through PGC and APPSTART over all supported

protocols.

If problems occur:

 - Disable AutoDisconnect and run the application as usual from PGC.

   -or-

 - Run the application from the server, bypassing PGC controls (through

   File Manager).

If these steps fail to pinpoint the issue, the application may not be

network-aware and you should contact the vendor of the application.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Using Systems Management Server in a Split-Domain Model

Article ID: Q121386

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The use of Systems Management Server in certain domain structures can

sometimes lead to confusion about the capabilities and limitations of

Systems Management Server version 1.0; specifically, when Systems

Management Server is used in a wide area network (WAN) consisting of a

single domain separated by routers. In this situation, special

consideration must be given to site type and placement and logon script

configuration, as well as package distribution technique.

MORE INFORMATION

================

Example

-------

Consider a common retail company utilizing a primary domain controller

(PDC) at the corporate office, and a backup domain controller (BDC) at each

outlet (to perform logon validation locally) linked to each other by 19.2-

kilobyte (K) routed links.

1. In this situation, Systems Management Server should be implemented as

follows:

   a. Install a central Systems Management Server site at the corporate

      office.

   b. If the remote offices have a large number of clients, install a

      primary site there; if not, a secondary site should be installed.

   c. Establish the needed parent-child assignments and addresses.

   d. If logon scripts are to be used, ensure replication is set up at the

      PDC and all BDCs.

   e. Ensure that NONE of the Systems Management Server sites in the domain

      selected Automatically Detecting Logon Servers, and that NONE of the

      sites in the domain are using the Automatically Configure Logon

      Script options.

2. Now, each client at outlet xyz will have a site-domain assignment such

   as "xyz:corpdom" for example, and clients at the corporate office will

   have an assignment such as "abc:corpdom" (these assignments will be used

   again later). Systems Management Server makes the "ownership"

   distinction based on the combination of the 3-letter site code combined

   with the domain name.

3. If logon scripts are going to be used, manually assign a script to each

   user account (through multi-select in User Manager) and ensure the

   needed script files are copied into the REPL$\SCRIPTS directory on the

   export server (usually the PDC). Here is a list of the files needed in

   REPL$\SCRIPTS directory or wherever you run your logon scripts from:

      CHOICE.COM     : When a slow network connection is detected, choice

                       prompts the user.

      CLRLEVEL.COM   : Needed to reset the DOS errorlevel flags.

      DOSVER.COM     : Temporary only to detect Windows 95 clients.

      NETSPEED.COM   : Used to detect if a slow network link is being used

                       for the logon.

      NETSPEED.DAT   : Companion to NETSPEED.COM.

      SETLS16.EXE    : Finds logon servers and manages client mapping and

                       connections (MS-DOS clients).

      SETLS32A.EXE   : Windows NT Alpha clients.

      SETLS32I.EXE   : Windows NT Intel clients.

      SETLS32M.EXE   : Windows NT MIPS clients.

      SETLSOS2.EXE   : OS/2 clients.

      SMSLS.BAT      : Main SMS script file for Windows NT and MS-DOS.

      SMSLS.CMD      : For OS/2 clients.

      SMSLS.INI      : Mapping file for resource domains (optional).

4. If a BDC goes down, a client logon request will most likely be serviced

   by the PDC and the logon script will execute through the 19.2K link. The

   SMSLS script will detect that this client belongs to site xyz and that

   the current site is abc. When these site codes differ, the script will

   gracefully exit two times and on the third time, the client will be

   MOVED to the abc site. This is not a desirable situation, so it is

   recommended that you increase the following registry item to a higher

   number depending on the link speed and BDC availability:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

           SMS\Components\SMS_Maintenance_Manager

      REG_DWORD: Inventory False Logon Limit (default=3)

      WARNING: Using the Registry Editor incorrectly can cause serious,

         system-wide problems that may require you to reinstall Windows NT

         to correct them. Microsoft cannot guarantee that any problems

         resulting from the use of the Registry Editor can be solved. Use

         this tool at your own risk.

5. The other area to discuss is that when sending packages from the central

   site to the child sites, each child site must be separately targeted (a

   different job for each destination site). This is needed so that the

   client station's PGC and PCM will not see another site's distribution

   servers in the list of servers hosting the package (this list is

   generated at job activation time).

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Use of the %0\..\ Syntax in SMSLS.BAT

Article ID: Q121387

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

When programs are run from a logon script, and they are located in the

NETLOGON share, the actual logon script does not know what drive or path

from which to execute the program, and the NETLOGON share is not included

in the DOS path statement. To resolve this, Systems Management Server

utilizes a little known feature of DOS to "determine" the drive and path

the script is running from. Windows NT systems include the NETLOGON share

in the path, so this %0\..\ syntax is not needed.

MORE INFORMATION

================

During a logon and when the logon script is running, the LMSCRIPT.EXE

program runs its commands from the NETLOGON share. However, batch files

have no way of determining where they are running from, and the current

directory set by LMSCRIPT.EXE is not the NETLOGON share.

As a workaround, Systems Management Server uses the %0\..\ path to indicate

the argv[0] present when the batch file was run. The batch file can then

refer to this path and know its own location and look for other files

there.

An example of this can be found in the Slow Network detection portion of

the SMSLS.BAT logon script file:

   REM SNET_DOS

   %0\..\netspeed

   if not errorlevel 1 goto NET_DOS

   if not errorlevel 2 goto END

   if errorlevel 2 %0\..\choice /T:Y,30 Slow network detected. Continue

   if not errorlevel 2 goto NET_DOS

   goto END

Prior to use of this technique, Systems Management Server was forced to use

a hard coded drive letter of Z: to reference needed files. Now the drive

used during a NET LOGON can be arbitrary, and dynamically determined.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Controlling LM and NT Logon Script Configurations with SMS

Article ID: Q121388

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

This information applies to Microsoft LAN Manager and Windows NT products

only. For information on NetWare script modifications, refer to other

articles in the Microsoft Knowledge Base.

Selecting the Automatically Configure Logon Scripts option in Systems

Management Server Administrator causes Systems Management Server to attempt

modifications to both user account profiles and existing logon scripts for

those users. To prevent these modifications from happening to selected

accounts, the administrator can alter the behavior of Systems Management

Server to accommodate the needs of network users.

MORE INFORMATION

================

1. The Systems Management Server Site Configuration Manager will only

   attempt to modify a users profile if it is blank (no logon script

   specified), or if it already contains the SMSLS script name.

   If an existing script is detected that is not SMSLS, Systems Management

   Server then performs several operations:

   a. Systems Management Server first makes a copy of the script as it

      exists in the REPL$\SCRIPTS directory using a temporary name. The

      temporary file will be opened and the following two (start and end)

      encapsulation comment strings will be looked for:

         REM Microsoft Systems Management Server (start)

         REM SMS Build <xxx>

         if "%OS%" == "Windows_NT" call smsls

         if "%OS%" == "" call %0\..\smsls

         REM Microsoft Systems Management Server (end)

   b. If the start and end strings are present, the file will not be

      modified (allowing the administrator to edit the changes between them

      and preserve them). If these strings are not present they will be

      added in, either at the top of the script or appended to the bottom

      of the script depending on the selections made in Systems Management

      Server Administrator (<Site Properties><Clients>). The modified file

      will then replace the actual script file and the original script file

      will be saved with a sequentially numbered extension like "000".

2. If the script specified does not include either a .BAT or .CMD file

   extension, Systems Management Server will ignore this script and will

   not attempt items 1a or 1b above. This is by design for Systems

   Management Server version 1.0 to provide the administrator with the

   capability of bypassing certain user accounts from the Systems

   Management Server logon script automatic configuration. This feature is

   under review and will be considered for inclusion in a future release.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Compression Performance Tuning in Systems Management Server

Article ID: Q121555

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The process of creating a data-compressed package (*.PKG) to be transmitted

through a Systems Management Server sender involves intense use of

the central processing unit (CPU) for the data-compression algorithm. The

frequency at which Systems Management Server will yield the CPU during

compression can have a dramatic effect on performance; this article

discusses this type of tuning. There are several Registry parameters for

this purpose.

MORE INFORMATION

================

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of

Registry Editor can be solved. Use this tool at your own risk.

 - During a package compression, a block of data is submitted to the

   compression algorithm and this call returns a compressed block. A large

   number of these calls can take a large amount of CPU time, so we have a

   timer that allows Systems Management Server to yield the processor for

   the specified amount of time. The default is 75 milliseconds. In

   addition, you can set a Registry entry under:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Compression\

      "Yield Time" (DWORD) [this is in milliseconds of yield time per

      compression block]

   If compression appears to be hogging your system, try setting this to

   100 or 125. For systems with lots of RAM and CPU power, values of 1-20

   might be usable, and this would speed up compression somewhat.

 - There are 7 levels of compression (1 through 7); a level of 1 (default)

   providing the least compression and greatest speed, and a level of 7

   providing maximum compression and taking additional time. This value is

   located at:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Compression\

      "Compression Level" (DWORD)

   In addition to the degree of compression desired, compression can be

   disabled by setting the value below to "No". The default is "Yes".

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Compression\

      "Enable Compression" (REG_SZ)

   Two-to-three megabytes (M) of memory resource can be saved by disabling

   compression; however, greater disk space will be required to store the

   package files because they will not be compressed.

 - Decompression Buffer size:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Compression\

      "Decompression Buffer Size (Log2 Value)" (DWORD)

   This value specifies the number of buffers to be used when decompressing

   a package file. It defaults to 15 and can be set to a value of 1 through

   31; however, for Systems Management Server version 1.0, values greater

   than 15 are ignored.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Third-Party Companion Products for Systems Management Server

Article ID: Q121656

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article lists the product name, company name, phone number and address

of vendors who have developed or are developing companion products for

Microsoft Systems Management Server.

Product Name    Company             Phone and Address

-----------------------------------------------------------------------

Asset Manager   Netlabs             (415) 961-9500

                                    (415) 961-9300 Fax

                                    4920 El Camino Real

                                    Los Altos, CA 94022

                                    Type: Asset Management software

Express Meter   Express Systems     (206) 728-8300 x414

                                    (206) 728-8301 Fax

                                    2101 4th Avenue

                                    Seattle, WA 98121-2314

                                    Type: License Management software

Customer One    BateTech Software   (303) 763-8333

                                    (303) 985-0624 Fax

                                    7500 W. Yale Avenue, B100

                                    Denver, CO 80277

                                    Type: Help Desk Management software

DP Umbrella     Vycor               (800) 888-9267

                                    (301) 220-0727 Fax

                                    5411 Berwyn Rd.

                                    College Park, MD 20740

                                    Type: Help Desk Management software

PC Galaxy       Apsylog             (415) 812-7700

                                    (415) 812-7707 Fax

                                    1900 Embarcadero Rd.

                                    Palo Alto, CA 94303

                                    Type: Help Desk Management software

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kb3rdparty

KBSubcategory: ntgeneral


Memory Performance Tuning in Systems Management Server

Article ID: Q121682

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

This article addresses how you can set, and how Systems Management Server

will set the Working Set for Systems Management Server processes.

The Working Set of a process is the set of memory pages currently visible

to the process in physical RAM memory. These pages are resident and

available for an application to use without triggering a page fault. The

size of the Working Set of a process is specified in bytes. The minimum and

maximum Working Set sizes affect the virtual memory paging behavior of a

process.

The Systems Management Server Executive service is the most resource

intensive process in Systems Management Server. The settings described in

this article are for the Systems Management Server Executive process.

Although the settings differ, the information in this article can also be

applied to other Systems Management Server processes such as the Hierarchy

Manager, Site Configuration Manager, Package Command Manager, and Inventory

Agent.

MORE INFORMATION

================

The operating system allocates Working Set sizes on a first-come, first-

served basis. For example, if an application successfully sets 40 megabytes

as its minimum Working Set size on a 64-MB system, and a second application

requests a 40-MB Working Set size, the operating system denies the second

application's request.

Using this capability to set an application's Working Set size does not

guarantee that the requested memory will be reserved, or that it will

remain resident at all times. When the application is idle, or a low-memory

situation causes a demand for memory, the operating system can reduce the

application's Working Set.

The net result of establishing an appropriate Working Set for a

process is that whenever the system can allow it, a [WorkingSet] amount of

the process' data will be resident in physical memory for greater speed.

To Manually Set The SMS Executive Working Set

---------------------------------------------

WARNING: Using the Registry Editor incorrectly can cause serious, system-

wide problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of the

Registry Editor can be solved. Use this tool at your own risk.

In the Registry Editor, traverse to this key:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_Executive

and set this value appropriately (in bytes):

   Working Set Limit (DWORD)

The default value is zero. If you do not set this value, the Systems

Management Server Executive uses a 4.5-MB Working Set. This will control

the maximum Working Set of the Systems Management Server Executive.

In situations where a lot of RAM is available (40+ MB), this should be set

to at least 6 MB(600000 hex). For systems at the low end, the value should

be about 4 MB.

You cannot use values less than 2 MB or the Systems Management Server

Executive will set the Working Set back to 4.5 MB. After you change the

value, you must restart the Systems Management Server Executive. If you do

not override the Systems Management Server Executive Working Set size, it

will automatically self-scale depending on the amount of physical RAM

available.

Resetting the Working Set, may still be necessary, since having many other

processes running could still render these figures invalid.

The defaults are:

Physical RAM        Working Set

-------------------------------

28 MB or less       3.5 MB

29-33 MB            4.5 MB

33-41 MB            5.5 MB

More than 41 MB     6.5 MB

Tuning the parameters discussed in this article will not effect the amount

of memory resource used by Systems Management Server, rather it will only

modify how the available memory resources are used in an attempt to keep

them resident as opposed to paged out to disk.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto


SMS Site Configuration Manager Internal Error Codes

Article ID: Q121683

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The Systems Management Server Site Configuration Manager has internal

error code information that is separate from the Event Codes used when

logging events. This article documents the Site Configuration Manager

internal error and information codes. These codes should be used in

conjunction with actual event data.

MORE INFORMATION

================

Internal Error Codes

--------------------

7400 INSTALL_ACCTPSWDCHANGEERROR    - Error changing acct/pswd for server

7401 INSTALL_CANTCOPYCOMPONENTFILES - Copy file error for component on svr

7402 INSTALL_CANTCOPYLOGONSCRIPT    - Error copying logon script files

7403 INSTALL_CANTCREATECOMPONENTDIR - Create dir error for component on svr

7404 INSTALL_CANTCREATEINBOXES      - Error creating inbox dir. or share

7405 INSTALL_CANTENUMSHARES         - Error in enum. of shares for svr

7406 INSTALL_CANTFINDOUTBOXSERVER   - Outbox server not in network

7407 INSTALL_CANTSTARTCOMPONENT     - Error installing/starting component

7408 INSTALL_ERRORINSYSMAPFILE      - Syntax/content error in sys. map file

7409 INSTALL_NOEXPORTSERVER         - No logon svr to use to export scripts

7410 INSTALL_NOTENOUGHMEMORY        - Insufficient memory; alloc failed

7411 INSTALL_OUTBOXCREATEERROR      - Error creating outbox share or dir.

7412 INSTALL_SERVERINOTHERSITE      - Server already used in other site

7413 INSTALL_SERVERSCRIPTSERROR     - List of svrs whose script changed(NW)

7414 INSTALL_USERSCRIPTSERROR       - List of users w/error changing script

                                      (NT/LM)

7415 INSTALL_CANTENUMUSERS          - Error enumerating users

7100 SITEINS_BADDIRECTORY           - Site ctrl file directory not valid

7101 SITEINS_BADDOMAINTYPE          - Cannot determine domain NOS; domain

                                      ignored

7102 SITEINS_CANTENUMSHARES         - Error in enum. of shares for svr

7103 SITEINS_CANTFINDDOMAIN         - Error in enum. of servers for domain

7104 SITEINS_CANTFINDSERVER         - Sserver from specified server list

                                      not in network

7105 SITEINS_CANTSAVEBASEID         - On de-install unable to save next

                                      available SMS ID

7106 SITEINS_ENUMSERVERINACTIVE     - Svr from enumeration not in network

7107 SITEINS_NEVERCTRLINFILE        - Can't watchdog because never received

                                      site ctrl file

7108 SITEINS_NOSERVERSINDOMAIN      - No servers found in domain

7109 SITEINS_NOTENOUGHMEMORY        - Insufficient memory, alloc failed

7110 SITEINS_NOTSETUP               - Ident. section of registry not setup

7111 SITEINS_SITECTRLINERROR        - Error reading site control file

7112 SITEINS_SITECTRLOUTERROR       - Error writing site control file

7113 SITEINS_SITECTRLSENDERROR      - Error sending site control file

7114 SITEINS_USERGROUPMIFERROR      - Error writing user group mif file

7115 SITEINS_CANTENUMUSERS          - Error in enum. of users for domain

Internal Information Codes

--------------------------

7200 SITEINS_ACCTPSWDCHANGEDONE     - Acct/pswd done for all services

7201 SITEINS_CANTFINDCOMPONENTSERVER- Server not in network for component

                                      or sender

7202 SITEINS_SITECTRLDIFFPARENT     - Site ctrl file differs from registry

7203 SITEINS_SQLACCTPSWDCHANGEDONE  - SQL acct/pswd/server change done

7500 INSTALL_CANTFINDVOLUME         - Error finding drive w/free space

7501 INSTALL_SERVERSCRIPTSCHANGED   - List of svrs whose script changed(NW)

7502 INSTALL_USERSCRIPTSCHANGED     - List of users whose script changed

                                      (NT/LM)

Site Control File Error Codes

-----------------------------

NOTE: These codes are also used as file extensions to rename bad input

files, so they must remain 3 digits due to 8.3 filenames.

710 SC_FILE_CANTREAD                - Can't open/read .ct1

711 SC_FILE_BADLOCALTRANS           - Unknown local transaction only

712 SC_FILE_BADTRANS                - Unknown transaction only

713 SC_FILE_BADFILETYPE             - Unknown file type

714 SC_FILE_BADSITEINFO             - No site info or mismatch site code,

                                      install dir, etc.

715 SC_FILE_NODOMAIN                - No domains in file

716 SC_FILE_BADACCT_NOADDR          - No acct info or no valid addresses

717 SC_FILE_NOSQL                   - No SQL info for smart site

718 SC_FILE_NOCOMPONENT             - No components or no senders

Additional reference words: sms prodsms 1.00 1.10

KBCategory:kbnetwork

KBSubcategory: ntconfig nthowto


Network Client Support for Systems Management Server

Article ID: Q121852

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

When using MS-DOS Network Client version 3.0, included with Windows NT

Server, only inventory capabilities are supported due to a restriction in

the NetBIOS interface on the client. This restriction precludes the use of

the NetBIOS interface for Diagnostics and Help Desk features and should be

corrected in the next release of the networking client.

Using the NWLink protocol with this client causes inventory to return all

0's for the network card ID. This is because the NWLink protocol does not

have NetBIOS turned on by default, which is used to get the network card

ID.

There are also restrictions on the use of the Package Command Manager and

Program Group Controller due to a limited implementation of the WNet and

LAN Man Networking application programming interface (API) when Windows NT

is running with MS-DOS Network Client 3.0. Microsoft recommends using

Windows for Workgroups 3.11 or LAN Manager 2.2 clients at a minimum when

Systems Management Server client support is needed.

KBCategory: kbtool

KBSubcategory: ntutil

Additional reference words: sms wfw wfwg prodsms 1.00 1.10


How to change Your Systems Management Server Site Name

Article ID: Q121854

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Every Systems Management Server Site is given a descriptive text string

during setup. This is used to identify the site to the Administrator. Once

this text is entered during setup, the administrator can no longer change

it through setup or Systems Management Server Administrator. This article

describes how to change this.

Warning: This procedure bypasses all error checking and is unsupported. If

directions are not followed exactly, database corruption can occur.

MORE INFORMATION

================

Below is the step by step procedure.

1. Open the \SMS\SITE.SRV\SITECFG.BOX\SITECTRL.CT0 file using Notepad or

   another text editor.

2. In the BEGIN_SITE_ACCOUNT section on approximately the sixth line find

   your current site name enclosed in angle brackets (<site name>).

3. Change this entry to your new site name, making sure that it's still

   enclosed in angle brackets.

   NOTE: Do not use any of the following characters within the angle

   brackets:

      <>{}"

   These characters can cause the file to be rejected, possibly resulting

   in database corruption which may force you to restore of the Systems

   Management Server database or reinstall the site.

4. Save this file as SITECTRL.CT1 in the same directory you used in Step 1.

5. Allow the Hierarchy and Site Config services to process the file. This

   could take a few minutes to over an hour, depending on your site service

   settings and current Site server load.

6. Refresh Systems Management Server Administrator and you should now see

   your new site name.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntdomain


Systems Management Server Tracing and Log Capabilities

Article ID: Q122055

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Because Microsoft Systems Management Server is based on a

sophisticated set of transactions that are processed throughout the site

hierarchy, it is often difficult to predict the time in which a command

will complete. These commands can range from a package distribution to a

logon server configuration update. Systems Management Server builds in to

each Windows NT service component the ability to write status and

diagnostic information to log files for historical or interactive review.

There are also several client-side log files created by Program Group

Control, AppStart, and so on.

It is strongly recommended that tracing remain active; however, for

performance tuning, you may disable trace logging with Systems Management

Server Service Manager, and activate tracing during diagnostics and

setup/upgrade. This feature is on by default so that any recent problems

will be recorded.

MORE INFORMATION

================

Along with the ability to write log information to a file, Systems

Management Server includes the Server Service Manager (SMSVCMGR.EXE) and

Trace (SMSTRACE.EXE) that you can use to control and display and review

these diagnostic log files.

By default, tracing (the process of writing to the log files) will be

enabled for the Windows NT service components of Systems Management Server

but can easily be deactivated (for performance improvements) with the SMS

Service Manager. Once activated for a particular component, you can use SMS

Trace (run from SITE.SRV\<ARCHITECTURE>.BIN\SMSTRACE.EXE) to open the log

file and monitor it in real time.

Log files are located in the SMS\LOGS directory by default. You can use

Systems Management Server Service Manager to set log file locations and

maximum sizes. Following is a list of Systems Management Server components

and the relevant log files:

Site Config Manager:          SCMAN.LOG

Hierarchy Manager:            HMAN.LOG

Inventory Agent NT:           INVAGENT.LOG

PCM Service:                  PACMAN.LOG

SMS_Executive:                SMSEXEC.LOG

Alerter:                      ALERTER.LOG

Applications Manager:         APPMAN.LOG

Inventory Data Loader:        DATALODR.LOG

Despooler:                    DESPOOL.LOG

Inventory Processor:          INVPROC.LOG

Senders:                      LANSEND.LOG, RASASYNC.LOG, and so on

Maintenance Manager:          MAINTMAN.LOG

Job Scheduler:                SCHED.LOG

Site Reporter:                SITEREPT.LOG

Package Command Manager:      No log file used; see note below.

Program Group Controller:     <WINROOT>\SMSLOG.TXT

AppStart:                     <WINROOT>\SMSLOG.TXT

Information included in a log file usually includes the time of day, error

codes, a description, and identification of the component and thread ID.

Because of the specialization of each component, each log file contains

slightly different text. If you need to see what is happening with a

particular task, and there is insufficient information reported by Systems

Management Server Administrator, you can check the log files to see how

things are progressing.

NOTE: The Package Command Manager does not use a log file; instead, it can

be run with a /debug switch that causes PCM to write diagnostic information

to a special window up to a maximum of 64 kilobytes (K).

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


How to Use Remote Control with TCP/IP

Article ID: Q122057

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

In Microsoft Systems Management Server version 1.0, to control a

remote client that is not on a local subnet using TCP/IP, you may configure

WINS or configure the LMHOSTS file on the Systems Management Server

administrator computer so that it contains the NetBIOS name and IP address

of the remote computer. This article lists and describes the entries of the

LMHOSTS file on both the server and client computers.

MORE INFORMATION

================

In order for Remote Control to work properly, you must configure the

LMHOSTS files on both the server and client computers in the following

format:

NOTE: Letters C, D, E and F must be located on the 16th position after the

opening quotation mark. Quotation marks are not optional.

Server LMHOSTS Entry

--------------------

<IP address><tab>"<client name>  C" (Letter C activates USERTSR)

<IP address><tab>"<client name>  E" (Letter E activates file transfer

                                     options on the server side)

Example:

130.20.37.30     "SMS_Client     C"

130.20.37.30     "SMS_Client     E"

Client LMHOSTS Entry

--------------------

<IP address><tab>"<Server name>  D" (Letter D activates USERTSR)

<IP address><tab>"<Server name>  F" (Letter F activates file transfer

                                     options on the client side)

Example:

130.20.50.31     "SMS_Server     D"

130.20.50.31     "SMS_Server     F"

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntnetserv nttcp ntdomain


Cannot Use Leading Spaces in a String for an Inventory Rule

Article ID: Q122134

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you use a string that contains leading spaces in the Systems

Management Server Administrator Inventory Rules dialog box for a software

inventory rule, the inventory rule string returns in quotation marks with

the leading spaces removed. This prevents the administrator from specifying

a string with leading spaces for an inventory rule.

CAUSE

=====

This is a known situation with Systems Management Server Administrator in

Microsoft Systems Management Server, which removes leading spaces in a

string.

FILETOKN -S <filename> returns 10 byte strings, each offset by 10 bytes

from the previous. It can return several strings at 10 byte offsets with

leading spaces, depending on the file. The Systems Management Server

administrator can erroneously assume that these strings with leading spaces

can be used to uniquely identify the software package. But because SMS

Administrator won't allow leading spaces, these strings cannot be used.

RESOLUTION

==========

When you run  FILETOKN -S <filename>, the results can look like this:

   10 "1234567890"

   20 " 23 56 890"

   30 "  34567890"

   40 "   4567890"

Theoretically, you could specify an inventory rule with the string

"1234567890" at offset 10 or "  4567890" at offset 40. With Systems

Management Server Administrator removing leading spaces, the second example

is wrong, to  use this string you would need to specify the address 40+3=43

with the string "4567890".

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: nthowto

Additional reference words: sms prodsms 1.00 1.10


SMS Network Applications Database Synchronization

Article ID: Q122175

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

When a program group or package is defined for a site in a hierarchy, it is

replicated to all child sites of the site for which it was defined. The

process of replicating the network applications database (NAD) involves

many subprocesses. It is possible that various combinations of parent site

attachments and detachments may make the NAD go out of synch between

originating and current sites.

The RSAPPCTL utility can be used to manage the NAD replication and reset

process when it goes out of synch. You can run RSAPPCTL from the

SITE.SRV\<architecture> directory.

Command Syntax:

   rsappctl {/SELF} {/ALL} {/SITE:sitecode} {/SITESERVER:servername}

   /SELF                   Reset NAD for this site (but not children).

   /ALL                    Reset NAD for all child sites (not self).

   /SITE:sitecode          Reset NAD for the specified child site.

   /SITESERVER:server      This site's site server. Only needed

                           if NADRESET is not being run on the site server.

You can combine /SELF with /ALL to do a total reset of the current site and

any children of the current site.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


SMS Site Reset Recommended Before Upgrade

Article ID: Q122176

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

Microsoft recommends that prior to attempting an upgrade of Systems

Management Server site server software, that you perform a Site Reset from

the SMS Setup program. This is intended to ensure that all service

componants are properly responding to service control commands for stopping

and starting.

SYMPTOMS

========

During an upgrade of the Systems Management Server site server software,

the SMS_Executive service cannot be stopped and reports an error. The

upgrade fails.

One or more of the following symptoms may indicate that this is the

problem:

 - Sometimes after a NET STOP SMS_EXECUTIVE command, Service Control

   Manager responds with "the service cannot be controlled."

 - Control Panel shows SMS_Executive is not running.

 - NET START shows SMS_Executive is running.

 - NET START SMS_EXECUTIVE results in:

      System error 1072 has occurred.

      The specified service has been marked for deletion.

 - There are many new temporary (.TMP) files in the root of the site drive

   that can't be deleted.

WORKAROUND

==========

Shutdown and restart the Windows NT server, do a Systems Management Server

Site Reset, and then attempt to upgrade again. There is no way to stop the

service after it was uninstalled while running, other than a system

shutdown. The reset should clean up service problems. The upgrade should

make sure all the correct files have been replaced and the new settings are

correctly entered.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


Systems Management Server Event Log Codes 0 Through 99

Article ID: Q122177

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article details Systems Management Server event log codes 0 through

99.

Event Log Codes 0 - 99

======================

Code   Description

----   -----------

0      Success.

1      The despooler instruction file is corrupt or has a wrong version

       stamp.

2      X is missing.

3      The component is unable to open registry key.

4      The component is unable to read registry key.

5      Unable to connect to domain.

6      The job has been cancelled, the package won't be installed on any

       servers.

7      The component is unable to create share on server with path.

8      The share name for a sharing job cannot be ADMIN$ share or any

       rootdrive$ share. Hidden shares are supported, they just can't be

       any existing system hidden shares. Please use a share name other

       than X and resend the package.

9      Unable to remove file.

10     The component is unable to delete directory tree.

11     Unable to find the package file. The scheduler at the sending site

       expects the package file to be at this site, however the package is

       either being removed via a remove package job or deleted by some

       user. Have the administrator resend the package to correct this

       problem.

12     Unable to connect to the instruction source.

13     No server is specified in the registry or in the instruction.

14     X encountered a fatal error, and is unable to retry the instruction.

15     Unable to decompress file X to Y, because it's corrupted.

16     The component is unable to do a tree copy of files from X to Y.

17     Install request: Could not obtain a SQL connection.

18     Install request: Unable to obtain destination addresses.

19     Install request: Unable to open outbox (X).

20     Install request: Unable to insert send request into datdabase.

21     Install request: Send request has permanently failed. Total

       retries = X.

22     Install Request: Unable to locate send request (X) in database.

23     Install Request: Unable to reactivate request. Send request

       access mode violation.

24     Install Request: Unable to reactivate request. Cannot change status

       to 'Pending'.

25     Install Request: Unable to obtain transmit status while updating

       request status.

26     Install Request: Unable to obtain status values from job details

       table.

27     Install Request: SQL query failed on table (X).

28     Server Install Job: Could not obtain a SQL connection.

29     Install Request: SQL query failed on table (X).

30     Install Job: Job table failed to update correctly.

31     Install Job: Unable to read Job table.

32     Install Job: Could not generate target machine list.

33     Install Job: Could not generate destination site list.

34     Install Job: Could not generate new request during job activation.

35     Install Job: Could not write to the NT registry.

36     Install Job: No requests found for this job while updating job

       status.

37     Install Job: Request (X) failed to activate.

38     Install Job: Could not locate Package.

39     Install Job: Request failed to reactivate.

40     Install Job: Could not generate instruction file.

41     Install Job: Job detail record missing.

42     Install Job: Unable to create transfer file.

43     Install Job: Could not locate request (X).

44     Install Job: Could not add Job Detail record.

45     Install Job: Could not locate Package.

46     Install Job: Could not retrieve Package Command Manager information.

47     Job Source: Could not get a SQL connection.

48     Job Source: SQL query failed on table (X).

49     Job Source: Directory was empty.

50     Job Source: Was not able to create a new file.

51     Job Source: Directory snapshot failed.

52     Job Source: Job missing from source.

53     Request Source: Unable to obtain a SQL connection.

54     Request Source: SQL query failed.

55     Machine not specified in instruction.

56     Location not specified in instruction.

57     Machine (X) in instruction cannot be found.

58     Location (X) in instruction cannot be found.

59     Cannot open file (X) for instruction.

60     Cannot read file (X) for instruction.

61     Cannot write file (X) for instruction.

62     Machine not specified in instruction for Package Command Manager.

63     Location not specified in instruction for Package Command Manager.

64     Machine (X) in instruction for Package Command Manager cannot be

       found.

65     Location (X) in instruction for Package Command Manager cannot be

       found.

66     Reporting location not specified in instruction from Package

       Command Manager .

67     Reporting location (X) in instruction from Package Command Manager

       cannot be found.

68     Machine not specified in instruction from Package Command Manager.

69     Location not specified in instruction from Package Command Manager.

70     Machine (X) in instruction from Package Command Manager cannot be

       found.

71     Location (X) in instruction from Package Command Manager cannot be

       found.

72     Destination directory for inventory and status (delta-MIF) files not

       specified in system job instruction.

73     Destination directory (X) for inventory and status (delta-MIF) files

       in system job instruction cannot be found.

74     Cannot find package file (X) for system job instruction.

75     Cannot open file (X) for system job instruction.

76     Cannot read file (X) for system job instruction.

77     Cannot execute system job instruction in file (X).

78     Cannot write file (X) for system job instruction. Disk may be full.

79     Site Reporter: Directory for inventory and status files not

       specified.

80     Site Reporter: Cannot find directory (X) for inventory and status

       files.

81     Site Reporter: Job source for inventory and status files not

       specified.

82     Site Reporter: Cannot find job source (X) for inventory and status

       files.

83     Site Reporter: Destination site not specified in inventory or status

       file (X).

84     Site Reporter: Cannot insert system job in job source (X).

85     Directory Monitor: Cannot find directory (X).

86     Directory Monitor: Wait function abandoned due to NT error (X).

87     Directory Monitor: Cannot find site code in delta-MIF file (X).

88     Database Processing: (X).

89     The component is unable to create directory X.

90     Unable to decompress the instruction file X into file Y.

91     The instruction source X is either missing or cannot be located.

92     Machine classes: Could not open file <X>.

93     Machine classes: Memory allocation failure.

94     Machine classes: Varfile error - file invalid.

95     Machine classes: Varfile bad seek error, error number <X>.

96     Machine classes: Varfile general error, error number <X>.

97     Machine classes: Varfile unknown error, error number <X>.

98     Machine classes: File append error.

99     Machine classes: File close error.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Systems Management Server Event Log Codes 100 Through 199

Article ID: Q122178

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article details Systems Management Server event log codes 100 through

199.

Event Log Codes 100 - 199

=========================

Code   Description

----   -----------

100    Machine classes: There is an error in the records of a varfile.

101    Machine classes: Exception <X> occurred for file <Y>.

102    Cannot find the site server for site X.

103    Cannot connect to the registry on site server X in site Y.

104    The component is unable to delete registry key X.

105    The component is unable to create registry key X.

106    Failed to remove package X from Y. Verify the package server is up

       and running and no one is currently using the package.

107    Failed to remove directory X. Verify there is no active process

       access the directory.

108    Failed to install package to X. Verify the package server is up and

       running and has sufficient disk space. The SMS service account must

       exist on the package server and has the same password as the

       siteserver, and the service account must have admin privilege. If

       the package server is a Netware server, verify the volume exists.

109    Failed to install package. There isn't sufficient disk space on

       package server X. Disk space available on that server is Y

       megabytes, space required is Z megabytes.

110    Failed to create directory on server X. Verify the server is up and

       running, The SMS service account must exist on the server and has

       the same password as the site server, and the service account must

       have admin privilege.

111    Failed to create share X on server Y using local path Z. Verify the

       server is up and running. The SMS service account must exist on the

       server and has the same password as the site server, and the service

       account must have admin privilege.

112    Failed to create mac volume X on server Y using local path Z. Verify

       the server is up and running. The SMS service account must exist on

       the server and has the same password as the site server, and the

       service account must have admin privilege.

113    There isn't any NTFS drive on server X, which is needed by the

       despooler to decompress or install the package.

114    Failed to decompress package X to Y. Verify there is enough disk

       space on the destination drive.

115    Failed to store the compressed package as X. Verify there is enough

       disk space on the SMS site installation drive.

116    Failed to perform replication on server X. Please check various

       inbox settings for this server in the site server registry. Please

       also check if this server is on the network. If the server is an

       OS/2 1.3 LanMan server, this could be that the local NT machine has

       already used up the two sessions that allowed to connect to an OS/2

       1.3 server. If the server is a NetWare machine, this could be that

       the NetWare server has run out of user connections.

117    Failed to detect the AppleTalk zone for SFM server X. This means

       SMS_INVENTORY_AGENT_NT on that server hasn't been started or failed

       to find that server's AppleTalk zone. Verify AppleTalk service is

       running on that server.

118    Cannot compile the package rule file X for site Y.

119    Workstation installation MIF file from Package Command Manager has

       an invalid format or is too large (>64 kBytes).

120    Cannot write a JobDetails MIF file for Workstation installation job.

121    Could not read from file: <X>

122    Could not allocate memory.

123    Could not flush machine map.

124    Bad ISV MIF file: <X>

125    Bad MIF file: <X>

126    Could not get local SMS.INI for current machine.

127    Could not open history file in directory: <X>

128    Bad header on Inventory Agent output file: <X>

129    Inventory Agent output file had an incompatible version stamp: <X>

130    Bad trailer on Inventory Agent output file: <X>

131    Unknown ID in Inventory Agent output file: <X>

132    Length of data given in Inventory Agent output file does not match

       expected length: <X>

133    Unknown error in Inventory Agent output file: <X>

134    Could not enumerate ISV MIF files in: <X>

135    Could not enumerate Inventory Agent output files in: <X>

136    Open failed: <X>

137    Could not process inventory for current machine.

138    Unknown group type in history file; unable to delete.

139    Error finding relationship to history in group: <X>

140    Unknown error attempting to find relationship to history: <X>

141    Machine Configuration: Could not access machine map: <X>

142    Machine Configuration: Could not create unique file in: <X>

143    Machine Configuration: Could not open machine map file: <X>

144    Machine Configuration: Could not allocate memory.

145    History: Could not allocate memory.

146    History: Could not open history file: <X>

147    History: Could not get unique file name in: <X>

148    History: Could not add new key to key table.

149    History: Could not find key in key table.

150    History: Could not find history key table in file, deleting file.

151    Could not allocate memory.

152    Could not create unique file in: <X>

153    Could not open file: <X>

154    Could not validate Systems Management Server path on local

       workstation:<X>

155    Could not validate Standalone ISV MIF path: <X>

156    Could not validate Machine ISV MIF path: <X>

157    Could not open history file in: <X>

158    Could not gather inventory on workstation.

159    Could not scan for ISV MIF files on workstation.

160    Bad ISV MIF file: <X>

161    Error reading from file: <X>

162    Could not enumerate ISV MIF files in: <X>

163    Unknown group type in history file; unable to delete.

164    Could not allocate memory.

165    Delta: Could not get unique name: <X>

166    Delta: Could not allocate memory.

167    Delta: Could not open file: <X>

168    Delta: Bad Delta file: <X>

169    Delta: Could not get objects from file: <X>

170    Delta: Variables were NULL: <X>

171    Delta: Could not append record: <X>

172    Delta: Could not init delta file. Too many sharing violations.

173    SHICNT: Could not open or create history file: <X>

174    SHICNT: Could not allocate memory.

175    SHICNT: Length in command history file inconsistent with known

       command history length.

176    SHICNT: Error reading data from command file: <X>

177    Cannot remove package <X> from Y.

178    Cannot set the max use for share X on server Y.

179    Machine classes: Could not initialize the Delta file.

180    A new machine is being entered into the database. Some of the

       identification attributes for the machine being added overlap with

       another machine in the database. Current Machine: <X> Overlapping

       Machine: <Y>

181    A match has been made on a machine being processed. Some of the

       identification attributes for the machine overlap with a separate

       machine in the database. Current Machine: <X> Overlapping Machine:

       <Y>

182    A machine match has been made based on the SMS ID of the machine

       being processed. The machine that matched had some attributes that

       were different. The old machine will be updated to have the

       attributes of the current machine. Current Machine: <X> Old Machine

       (will change): <Y>

183    Machine classes: Several machines were found in the database that

       matched the identification attributes of the machine currently being

       entered in the database. All machines in the database with these

       attributes were deleted and a resync command was sent to the machine

       being added. Identification information: <X>

184    Machine classes: Couldn't delete the list of machines from the

       database.

185    Machine classes: Several machines were found in the database with

       the same SMS ID as the machine currently being entered into the

       database. All machines with the this SMS ID were deleted from the

       database and are sync command was sent to the machine being entered.

       SMS ID: <X>

186    Machine classes: A resync command was sent to the Following machine.

       Site: Domain X SMS ID: Y

187    Machine classes: A MIF contained an attribute with a type different

       from that already defined in the database for the same attribute.

       The MIF was not processed. Group: X Attribute: Y

188    Error reading configuration information in path: <X>

189    Cannot find the Package Command Manager instruction for machine (X)

       to remove.

190    Command not specified in Inventory Agent re-synchronize instruction.

       Re-synchronization will not take place.

191    Invalid command in Inventory Agent re-synchronize instruction or

       corrupted instruction file. Re-synchronization will not take place.

192    Machine not specified in Inventory Agent re-synchronize instruction.

       Re-synchronization will not take place.

193    Domain not specified in Inventory Agent re-synchronize instruction.

       Re-synchronization will not take place.

194    Invalid domain (X) in Inventory Agent re-synchronize instruction.

       Re-synchronization will not take place.

195    Cannot write file for domain (X) Inventory Agent re-synchronize

       instruction. Re-synchronization will not take place.

196    Delta: Could not write; disk full.

197    The registry is not set up properly for the Site Reporter to run.

       Sitecode, site server, or site server domain are missing.

198    Insufficient memory to run the Site Reporter. Close one or more

       other applications and restart.

199    The registry is not set up properly for Inventory Data Loader to

       run.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Systems Management Server Event Log Codes 200 Through 249

Article ID: Q122179

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article details Systems Management Server event log codes 200 through

249.

Event Log Codes 200 - 249

=========================

Code   Description

----   -----------

200    The registry is not set up properly for Inventory Agent to run.

201    The registry is not set up properly for an instruction to execute.

202    Insufficient memory to execute an instruction. Close one or more

       other applications and restart.

203    The registry is not set up properly for a system job instruction to

       execute.

204    Insufficient memory to execute a system job instruction. Close one

       or more other applications and restart.

205    The registry in [X] is not set up properly for the instruction to

       execute.

206    Failed to store the master package from X to Y.

207    Alerter: An alert has been generated.

208    Insufficient memory to configure or watchdog this site. Close one or

       more other applications and restart the Site Configuration Manager.

       Possible NT error: (X)

209    The SMS Identification section in the NT registry (X) is not set up

       correctly for the Site Configuration Manager. For a new site, this

       may be due to the Site Configuration Manager not receiving a site

       control file within the first (Y) minutes. For an existing site,

       this may be due to an invalid or missing SiteCode (3 alphanumeric

       characters) or Install Directory (full DOS pathname not at root of

       drive). Another attempt will be made every (Z) seconds. Possible NT

       error: (N)

210    Cannot find the directory (X) for site control files. The SMS

       installation directory may have been deleted. Another attempt will

       be made every (Y) seconds. Possible NT error: (Z)

211    Error reading site control file (X). This file may be corrupted or

       the data may not be valid. Check to make sure that this site has

       been completely de-installed if this is a new or re-installation.

       The invalid site control file has been renamed to (Y). Include a

       copy of this file with your bug report. Possible NT error: (Z)

212    An error occurred while writing the User Group delta-MIF file for

       this site. This may be due to one or more inactive domains. Ignore

       this error if it occurred during an unsuccessful setup attempt.

       Another attempt to write this file will be made after the next Site

       Properties change or after (X) minutes. Possible NT error: (Y)

213    An error occurred while writing the site control file (X). Verify

       that the disk drive on this server has sufficient free disk space.

       Another attempt to write this file will be made after the next Site

       Properties change or after (Y) minutes. Possible NT error: (Z)

214    An error occurred while creating the system job to send a site

       control file to the parent site (X). The site control file has been

       renamed to (Y). Verify that the disk drive on this server has

       sufficient free diskspace and that the installation of this site

       succeeded. Another attempt will be made after the next Site

       Properties change or after (Y) minutes. Possible NT error: (Z)

215    Cannot find Windows NT server (X) on the network. The server may be

       down (inactive) or the server's domain may be down or not part of

       this SMS site. Component (Y) will be started on the SMS site server.

       Verify the server's status independent of SMS. Verify the spelling

       of the servername in the Site Properties -> Services dialog in the

       Systems Management Server UI. This server must be an NT server in an

       active NT domain that is part of this SMS site. This server must

       either be automatically detected or included in the server list for

       this domain.

216    An error occurred while copying the logon script file(s) (A) to

       server (B) in domain (C). Windows NT directory replication must be

       enabled for server (D) with server (E) as the export server for

       replicating SMS logon script files. Verify server (F) has a SCRIPTS

       directory under the REPL$ share and the SMS service account has

       access privileges to this share and directory. Users' logon script

       paths will not be modified until the logon script files have been

       successfully copied. Possible NT error: (G)

217    An attempt to verify the domain type failed for domain (X). The

       domain controller may be down (inactive). If the domain controller

       for this domain is an NT or LAN Manager server, the NetLogon service

       may not be running. If the domain controller for this domain is a

       LAN Manager or LANServer server, this may be due to the OS/2 session

       limit being exceeded, and if so, the Site Configuration Manager will

       recover from this after one or more sessions to this server are

       dropped. This may also be due to the SMS service account having

       expired for this domain. The domain status is changed to inactive.

       Verify the domain's status independent of SMS. Verify the domain

       type and the spelling of the domain name in the Site Properties ->

       Domains dialog in the Systems Management Server UI. Possible NT

       error: (Y)

218    Cannot find domain (X) on the network to enumerate servers. This may

       be due to the Computer Browser service not running on the SMS site

       server. If this is a NetWare domain, this may be due to the Gateway

       Service for NetWare not running on the SMS site server. If this is

       an NT or LAN Manager domain, this may be due to the Computer Browser

       service not running on any NT server in this domain. If this is a

       LAN Manager domain, you may need to add this domain to the list of

       other domains for the Computer Browser. This is done using the

       Control Panel Network applet -> Computer Browser -> Configure on the

       primary domain controller for the SMS site server's domain. The

       domain status is changed to inactive. Verify the domain's status

       independent of SMS. Possible NT error: (Y)

219    Cannot find NT server (A) on the network for outbox (B). Server (C)

       or the server's domain may be down (inactive) or not part of this

       SMS site. Outbox (D) will be unavailable until the server is up and

       detected during the next watchdogging cycle. Check earlier event

       messages fromthe Site Configuration Manager for this domain and

       server. Verify the server's status independent of SMS. Check the

       spelling of the servername in the Systems Management Server UI.

       This server must be in anactive NT domain that is part of this SMS

       site. Possible NT error: (E)

220    Cannot create a shared directory on server (A) for outbox (B). This

       may be due to the SMS service account having insufficient privileges

       on this server or the server (C) or server's domain (D) being down

       (inactive). Verify that the SMS service account has Administrator or

       Supervisor equivalent access privileges on this server and that the

       account has not expired. Check earlier event messages from the Site

       Configuration Manager for this domain and server. Also verify that

       the drive letter for this outbox exists and this drive has

       sufficient free disk space. Possible NT error: (E)

221    Cannot find server (A) on the network. The server or the server's

       domain (B) may be down (inactive) or the SMS service account may not

       have access privileges to this server. If this is a NetWare domain,

       this may be due to the Gateway Service for NetWare not running on

       the SMS site server. If this is an NT domain, this server must be a

       Windows NT server. If this is a LAN Manager or LAN Server domain,

       this server must be a primary domain controller or backup domain

       controller. The server status is changed to inactive. Verify the

       server's status independent of SMS. Check the spelling of the server

       name in the Site Properties -> Domains dialog in the Systems

       Management Server UI. The SMS service account must have

       Administrator or Supervisor equivalent access privileges on this

       server, an identical password to the SMS site server service

       account, and must not have expired. Possible NT error: (C)

222    Cannot enumerate shares for  server (A) in domain (B). This may be

       due to the Computer Browser service not running on the SMS site

       server. If this is a NetWare domain, this may be due to the Gateway

       Service for NetWare not running on the SMS site server. If this is

       an NT or LAN Manager domain, this may be due to the Computer Browser

       service not running on any NT server in this domain. Possible NT

       error: (C)

223    Cannot create shared directories on server (A) in domain (B) for

       inboxes(C). This may be due to the SMS service account having

       insufficient access privileges to connect to this server, to create

       a directory or share, or to set directory and share access

       permissions. Verify that the SMS service account has Administrator

       or Supervisor equivalent access privileges on this server and has

       not expired. Check if this server has sufficient free disk space.

       Possible NT error: (D)

224    Cannot find a drive or volume with sufficient free disk space on

       server (A) in domain (B). This may be due to the SMS service

       account having insufficient access privileges to determine the

       available drives or volumes for this server. If this is a Netware

       server, this may be due to the server having no available user

       connections at this time. The volume or drive must have a minimum of

       C MB free. This server will be marked inactive. Another attempt to

       install this server will be made after the next Site Properties

       change or during the next watchdog cycle.

225    Cannot install or start component (A) on server (B) in domain (C).

       This may be due to the SMS service account having insufficient

       access privileges to install or start this component on this server.

       This may also be due to one or more missing, incorrectly copied, or

       out-of-date executable files on this server that are required by

       this component. Verify that the SMS service account has not expired.

       This account must be in the Domain Admins global user group for

       domain (D) and have the Logon As Service user right in this domain

       or on this server. Also check for the existence of the system map

       file (E) on the SMS site server. Another attempt to install or start

       this component will be made after the next Site Properties change or

       during the next watchdog cycle. Possible NT error: (F)

226    The parent site code (A) specified in the site control file does not

       match the previous parent site code (B) that is stored in the

       Identification section of the SMS registry. The parent site will now

       change to (C).

227    Cannot find previously detected server (A) on the network. This

       server or the server's domain (B) may be down (inactive). The server

       status is changed to inactive. Verify the server's status

       independent of SMS. Another attempt to detect this server will be

       made after the next Site Properties change or during the next

       watchdog cycle. If this server stays inactive for more than C days,

       it will be removed from the Domains section for domain (D) in the

       SMS registry even though it has not been de-installed. Possible NT

       error: (E)

228    Cannot find a logon server in domain (A) to use as the export server

       for logon script files. There must be at least one active domain

       controller in this domain for SMS to use as the export server for NT

       directory replication. Users'logon script paths will not be modified

       until the logon script files have been successfully copied to an

       export server's REPL$\SCRIPTS directory. Possible NT error: (B)

229    The following user accounts in domain (A) were altered to automate

       SMS logon scripts: (B). This involved changing the Logon Script Path

       for each user account from blank to (C).

230    The following user accounts in domain (A) could not be altered to

       automate SMS logon scripts: (B). This may be due to the SMS service

       account having insufficient access privileges for modifying user

       accounts in this domain. Possible NT error: (C)

231    The system logon scripts for the following servers in domain (A)

       were altered to automatic SMS logon scripts: (B).

232    The system logon scripts for the following servers in domain (A)

       could not be altered to automatic SMS logon scripts: (B). This error

       may be caused by the system logon script files not existing or the

       SMS service account having insufficient access privileges for

       modifying files on these servers. Possible NT error: (C)

233    Cannot create shared directory (A) on server (B) to store executable

       files for SMS component (C). This may be due to the SMS service

       account having insufficient access privileges to connect to this

       server, to create a directory or share, or to set directory and

       share access permissions. Verify that the SMS service account has

       Administrator equivalent access privileges on this server and has

       not expired. Check if this server has sufficient free disk space.

       Possible NT error: (D)

234    Cannot copy the following executable files for SMS component (A) on

       server (B): (C). This may be due to the SMS service account having

       insufficient access privileges to connect to this server or to

       create or write files. This may also be due to the files being

       locked because the component isrunning. Verify that the SMS service

       account has Administrator equivalent access privileges on this

       server and has not expired. Check if this server has sufficient free

       disk space. The Upgrade mode of the Systems Management Server Setup

       UI can be usedto refresh the files on the SMS site server and

       initiate a site shutdown of all components followed by a re-copying

       of all component executable files to all servers. Possible NT error:

       (D)

235    No active servers were found for domain (A). This may be due to all

       servers in this domain being down (inactive) or a Computer Browser

       error enumerating the servers in this domain. The domain status is

       changed to inactive. Verify in a manner independent of SMS that at

       least one server is active. Another attempt to detect servers in

       this domain will be made after the next Site Properties change or

       during the next watchdog cycle. Possible NT error: (B)

236    Cannot install to server (A) in domain (B). The share (C) on this

       server was previously created for SMS site (D). This may be due to

       an attempt to install two sites in domain (E) with at least one not

       having Use Specified Servers for this domain as a Domain Property in

       the Systems Management Server UI. This may also be due to specifying

       this server (F) as part of a domain in two sites or this server

       being previously part of a different SMS site that was not

       successfully de-installed. The status of this server is changed to

       inactive for this site. Possible NT error: (G)

237    Cannot open or successfully read the system map file (A). Check for

       the existence of the system map file (B) on the SMS Site Server.

       Verify that it is identical to the released system map file, or if

       modified, that all changes are syntactically correct. Possible NT

       error: (C)

238    The service account and password has been successfully changed for

       all SMS services. The new service account is (A).

239    The SQLServer account, password, and server name has been

       successfully changed for SMS. The new SQL account for server (A) is

       (B).

240    Cannot change the service account and password for SMS component (A)

       on server (B) in domain (C). This may be due to the new account not

       existing in this domain. Another attempt to change the service

       account will be made after the next Site Properties change or during

       the next watchdog cycle. Possible NT error: (D)

241    Cannot save the next available SMS Unique ID (A) in file (B)

       for this site. This may be due to this file being locked by another

       application. The purpose of saving this ID is to prevent duplicate

       SMS Unique IDs from being generated if this site is re-installed

       with the same site code. This entry can be added by hand to the (C)

       file on the SMS site server by adding this line to the file in the

       [D] section:  =  Possible NT error:  (E)

242    Cannot start site configuration until a site control file is

       received. If this is a new site, this may be due to the user pausing

       the Systems Management Server Setup UI or some other delay in the

       delivery of the site control file. If this is an existing site,

       this may be due to the SMS registry being corrupted. Verify that the

       section in the SMS registry is correct. The master site control file

       (A) in directory (B) can be used to force an update ofthe registry

       by copying this file to a new file with a (C) file entension.

       Possible NT error: (D)

243    Could not get a SQL connection.

244    The SQL connection has been reestablished.

245    A MIF could not be processed and has been moved to file X.

246    Failed to access registry section.

247    Cannot find file X to continue the current operation.

248    Failed to write to file X, verify there is enough disk space on the

       machine and there is no process that locked the file.

249    Cannot open outbox X. Verify the server is up and the outbox

       directory exists.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Systems Management Server Event Log Codes 250 Through 349

Article ID: Q122180

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article details Systems Management Server event log codes 250 through

349.

Event Log Codes 250 - 349

=========================

Code   Description

----   -----------

250    Cannot create new thread. Verify there is enough virtual memory on

       the machine.

251    Cannot connect to site A over LAN. Verify the remote site server B

       is on the LAN and share C is visible and has all the necessary

       permission for the SMS service account. Also verify the network is

       not saturated. Verify you can move large amount of data across the

       network. Win32Error Code = D.

252    Cannot connect to site A over RAS. Verify the remote site server B

       is alive and running RAS Server Serivce, and the phone book entry C

       in the default phone book contains valid information Win32 Error

       Code = D. Check the RAS section in the NT document for detailed

       explanation on the error code.

253    Sender had a successful RAS connection to site A. However it failed

       to connect to share B on server C using the given user name and

       password. Verify the share permission is set up properly. Win32

       Error Code = D

254    Cannot start TP using local LU alias A while establishing a SNA

       connection to site B. The primary return code is C, the secondary

       return code is D. Verify all the SNA setting are correct through the

       SNA Admin.

255    Cannot do a MC_ALLOCATE while establishing a SNA connection to site

       A. The primary return code is B, the secondary return code is C.

       Verify all the SNA setting are correct through the SNA Admin.

256    Cannot find an active receiver at remote site A to confirm the

       connection request. Verify the SNA receiver is running at the remote

       site.

257    The X adddress string is invalid. It's missing the remote server

       name section.

258    The X adddress string is invalid. It's missing the remote share name

       section.

259    The X adddress string is invalid. It's missing the remote gateway

       name section.

260    A Sender is starting for send request

261    Incorrect invocation of a sender.

262    Cannot open status file X.

263    Cannot read status file X.

264    No remote addresses in status file X.

265    Connection to remote site failed after retries exceeded. No more

       remote addresses in status file X.

266    Remote site installation failed with error X.

267    No errors reported from remote site installation.

268    Cannot locate the package file or it is of zero length. File name X.

269    Cannot locate the instruction file or it is of zero length. File

       name X.

270    File X exists.

271    File X exists. It has been renamed.

272    Job X was successfully sent to destination Y.

273    The dispatcher failed to spawn a sender process for send request X.

       The system returned the above error code.

274    No remote address present.

275    The remote address is inavlid. Address: X.

276    Local address missing or invalid.

277    Failed to connect to destination X.

278    Failed to disconnect from remote resource X.

279    Failed to connect to RAS Server. Remote resource X. The error code

       from RAS is reported above.

280    Failed to open file X.

281    Failed to open file X. LU aliases: Y.

282    Failed to close file X.

283    Failed to close file X. LU aliases: Y.

284    File X is not the expected size.

285    Write to file X failed. The sender failed to confirm that the file

       was written to correctly.

286    Failed to flush file X.

287    Failed to flush file X. LU aliases: X.

288    Failed to read file X.

289    Insufficient disk space on X.

290    Insufficient disk space on X. LU aliases: Y.

291    Failed to check the disk space on remote machine X. Possible causes

       are: The remote machine is unavailable. Incorrect access rights to

       the remote machine.

292    Failed to rename remote file from X to Y.

293    Failed to remove file X.

294    Failed to remove file X. LU aliases: Y.

295    Memory allocation failed.

296    Dispatcher starting.

297    SNA Receiver starting.

298    SNA Receiver stopping.

299    RAS Dispatcher cannot get access to the RAS section of the registry.

300    Dispatcher has terminated.

301    Dispatcher has terminated due to an error.

302    Sender has received a message to stop the current transfer.

303    Sender has received a message to cancel the current transfer.

304    Sender has received a message to suspend the current transfer.

305    Failed to establish connection between local LU X and remote LU Y.

306    The SNA communication with the remote site failed. Local LU alias X,

       Remote LU alias Y.

307    The application failed to set a notification event on the above

       directory. The API has returned the error code above.

308    The application failed to create a handle. The API has returned the

       error code above.

309    Incomplete data. Either the destination site or the instruction type

       is missing.

310    Cannot access the registry.

311    Missing in-box path in registry.

312    Failed to construct the instruction file.

313    The package source directory cannot be found.

314    Failed to update the job source.

315    The job handler encountered an error attempting to place the send

       request in the unscheduled outbox. Possible causes are: the server

       holding the Scheduler's unscheduled outbox is not reachable (server

       may be off the network); or there may already be a send request with

       the same ID (A) in the unscheduled outbox (should not happen).

316    The job encountered an error while sending data or performing

       operations relating to the destination site. Possible causes are: X

       addresses to the destination site may be invalid (server or account

       information may be incorrect); the destination site server may not

       be running; or there may be communications or other sending-related

       errors.

317    The job encountered an error while sending a remote cancel

       instruction. The job information has already reached the destination

       site, requiring a cancel instruction to be sent to that destination

       site, informing the site to stop processing the job. Possible causes

       are: addresses to the destination site may be invalid (server or

       account information may be incorrect); the destination site server

       may not be running; or there may be communications or other sending-

       related errors.

318    The job cannot access the specified query (A) and therefore cannot

       generate the list of target workstations for the job. Possible

       causes are: SQL server is not responding; a blank queryname was

       specified; or the query was deleted after the job was created.

319    The job encountered an error trying to process the specified machine

       path (A) and therefore cannot generate the list of target

       workstations for the job. Possible causes are: an invalid site name

       or site code was specified (site groups are not allowed); the PC

       architecture has not been defined yet; or a fatal low-memory

       condition was encountered.

320    The job encountered an error trying to execute a query and there

       forecannot generate the list of target workstations for the job.

       Possible causes are: SQL server is not available; or a fatal low-

       memory condition was encountered.

321    The job encountered an error trying to reach the Job Details table

       and therefore cannot generate the list of target workstations for

       the job. Possible causes are: SQL Server is not started; SQL Server

       logon account is invalid; a named-pipe connection to the server

       running SQLServer cannot be established; or the maximum user

       connections for SQL Server has been reached.

322    The job encountered an error trying to insert a record into the Job

       Details table and therefore cannot generate the list of target

       workstations for the job. Possible causes are: SQL server is not

       available.

323    The job has been failed without performing any actions, because the

       generated list of target workstations was empty. The provided query,

       machine group, or machine path, along with any site limiting,

       resulted in zero machines being targeted. Therefore, the job has

       nothing to do.

324    The job encountered an error trying to generate the list of

       destination sites. Possible causes are: SQL server is not available.

325    The job encountered an error trying to reach the Requests table and

       therefore cannot be activated. Possible causes are: SQL Server is

       not started; SQL Server logon account is invalid; a named-pipe

       connection to the server running SQL Server cannot be established;

       or the maximum user connections for SQL Server has been reached.

326    The job encountered an error trying to insert a record into the

       Requests table and therefore cannot be activated. Possible causes

       are: SQL server is not available.

327    The job encountered an error trying to connect to the registry while

       updating job status. Job status updating will be skipped for this

       cycle.

328    The job encountered an error trying to read the registry while

       updating job status. Job status updating will be skipped for this

       cycle.

329    An error occured while trying to compress the contents of the source

       directory specified for the workstation version of the package.

       Possible causes are:  the source directory specified is invalid or

       cannot be accessed by the compression process;  or, there was

       insufficient disk space to compress the contents of the source

       directory.

330    An error occured while trying to compress the contents of the source

       directory specified for the server version of the package. Possible

       causes are: the source directory specified is invalid or cannot be

       accessed by the compression process; or, there was insufficient disk

       space to compress the contents of the source directory.

331    An error occured while trying to compress the source directory or

       file associated with the job. Possible causes are: the source

       directory or file does not exist orcannot be accessed by the

       compression process; or, there was insufficient disk space to

       compress the contents of the source directory or file.

332    The system cannot find any defined addresses by which this site can

       send to a destination site for the job. Possible causes are: no

       addresses have been defined between this site and the destination

       site; the SMS site server registry (which holds the address list) is

       not active and on the network; or, SMS_SCHEDULER does not have

       sufficient rights to access the SMS site server registry.

333    Cannot read registry on Server X. Check for missing SMS keys in

       registry.

334    Cannot update Site Table for site X. Check Sites table and SQL

       Server.

335    First config job created for site X. %5

336    Cannot read Site Control file for site X from database on SQL

       Server Y. Check SQL Server and Site Control table.

337    Cannot write Site Control file for site X to database on SQL Server

       Y. Check SQL Server and Site Control table.

338    Cannot write Site Control file to the SITE.SRV\SITECFG.BOX. Check

       for directory existence.

339    Site Control file X has bad or unknown type. Check for corrupted

       file.

340    Cannot read the Site Control file X. Check for locked or corrupted

       file.

341    Site X had bad or unknown status value in Sites table. Check SQL

       Tables.

342    Cannot change to working directory X. Check for directory existence.

343    Cannot connect to Job Source [SQL]. Check SQL Server and Jobs table.

344    Cannot insert a job into Job Source [SQL]. Check SQLServer and Jobs

       table.

345    Cannot read Job X from SQL tables. Check SQLServer and Jobs table.

346    Cannot generate a new send request for remote site intallation.

347    No address is available to reach site X. Cannot create a job.

348    Remote site install package created. X files copied to make package.

349    Remote site installation sequence started for site X.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Systems Management Server Event Log Codes 350 Through 400

Article ID: Q122181

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article details Systems Management Server event log codes 350 through

400.

Event Log Codes 350 - 400

=========================

Code   Description

----   -----------

350    New site installation initiated for site X.

351    Could not create send request to install site X.

352    Could not create Site Reconfiguration Minijob for site X.

353    Site reconfiguration for site X initiated.

354    Local site reconfiguration initiated.

355    Remote site reconfiguration job for site X failed due to problems

       creating the minijob.

356    Site Hierarchy Manager is not functional. Unable to make connection

       to SQL Server .

357    Unable to obtain status for Job X for site Y.

358    Received an ACTUAL site control file from site X.

359    Preinstall job for site X has failed.

360    Site Install Job for site X has failed.

361    Site reconfig job for site X has failed.

362    Creation of Minijob to parent site  from site  is failing.

363    Sites table is empty. Cannot do any processing.

364    Forwarding site control file(s) to parent site X.

365    Cannot post site control files to parent site X.

366    Cannot identify this site. No site code is in registry.

367    Attempt to add site X to the Sites table in the database failed.

368    Attempt to add domain X for Site Y to Domains table in database has

       failed.

369    SQL Server Errors =>

370    X is not setup correctly.

371    Unable to create MAC volume X on server Y with path Z.

372    There is not enough free disk space on share A, server B. Available

       diskspace is C MBytes, the package requires D bytes.

373    There is no NTFS drive on server X, which is needed to decompress or

       copy the package.

374    The workstation install job has failed on workstation X in domain Y,

       the description generated by the setup script is Z.

375    The package file is corrupted. It either has a bad internal format

       or failed CRC check. Have the administrator resend the package to

       correct this problem.

376    X caused an exception. Shutting down the SMS Executive.

377    Site X is attempting to produce an illegal site hierarchy.

378    Failed to install SMS_BOOTSTRAP service at the secondary site.

       Possible causes are the service account doesn't have the proper

       rights, the install drive doesn't exist or the server platform is

       incorrect.

379    The SMS root directory X on server Y cannot be an existing directory

       that is not empty. Either delete the directory by hand or choose a

       different directory and redo the secondary site install.

380    An SMS alert has been triggered. Alert:  (X) -- . The hit count for

       the alert was Y.

381    Installation or upgrade of site X has failed. The main site package

       (BOOTSTRP.PK1) and/or the site control package (BOOTSTRP.PK2) have

       disappeared from that site's installation directory, where they had

       been previously stored. Installation or upgrade cannot continue. If

       this was an upgrade, SMS_BOOTSTRAP has triggered a restart of the

       secondary site, attempting to restart the previous version of SMS.

       If this succeeds, it should be possible to retry the upgrade using

       SMS Setup to upgrade the primary site again.

382    Installation or upgrade of site X has failed. The main site package

       (BOOTSTRP.PK1) is invalid, failing internal consistency checks.

       Installation or upgrade cannot continue. If this was an upgrade,

       SMS_BOOTSTRAP has triggered a restart of the secondary site,

       attempting to restart the previous version of SMS. If this succeeds,

       it should be possible to retry the upgrade using SMS Setup to

       upgrade the primary site again. Possible causes are: a transmission

       error during sending.

383    Installation or upgrade of site X has failed. The site control

       package (BOOTSTRP.PK2) is invalid, failing internal consistency

       checks. Installation or upgrade cannot continue. If this was an

       upgrade, SMS_BOOTSTRAP has triggered a restart of the secondary

       site, attempting to restart the previous version of SMS. If this

       succeeds, it should be possible to retry the upgrade using SMS Setup

       to upgrade the primary site again. Possible causes are: a

       transmission error during sending.

384    Installation or upgrade of site X has failed. SMS_BOOTSTRAP detected

       insufficient disk space to decompress the main site package

       (BOOTSTRP.PK1) or the site control package (BOOTSTRP.PK2).

       Installation or upgrade cannot continue. If this was an upgrade,

       SMS_BOOTSTRAP has triggered a restart of the secondary site,

       attempting to restart the previous version of SMS. If this

       succeeds, it should be possible to retry the upgrade using SMS Setup

       to upgrade the primary site again. Possible causes are: low disk

       space on the secondary site server.

385    Installation or upgrade of site X has failed. The main site package

       has failed during decompression. Installation or upgrade cannot

       continue. If this was an upgrade, the secondary site may now contain

       a mixture of files from the previous and new versions and should be

       considered unstable. SMS_BOOTSTRAP has triggered a restart of the

       secondary site, attempting to start the "mixed" version of SMS. If

       this succeeds, it should be possible to retry the upgrade using SMS

       Setup to upgrade the primary site again.

386    Installation or upgrade of site X has failed. The site control

       package has failed during decompression. Installation or upgrade

       cannot continue. If this is an upgrade, SMS_BOOTSTRAP has triggered

       a restart of the secondary site, attempting to start the new version

       of SMS using the old site control file. If this succeeds, it should

       be possible to retry the upgrade using SMS Setup to upgrade the

       primary site again.

387    Installation or upgrade of site X has failed. After it was

       decompressed, the main site package did not included a master system

       map (SYSTEM.MAP). This file should have been in the install

       directory. Installation or upgrade cannot continue. If this is an

       upgrade, SMS_BOOTSTRAP has triggered a restart of the secondary

       site, attempting to start the new version of SMS without the system

       map. If this succeeds, it should be possible to retry the upgrade

       using SMS Setup to upgrade the primary site again.

388    Installation or upgrade of site  has failed. SMS_BOOTSTRAP has run

       for more than 48 hours at the secondary site without the site

       successfully starting. Installation or upgrade will not continue.

       If this was an upgrade, SMS_BOOTSTRAP has triggered a restart of the

       secondary site, attempting to restart the previous version of SMS.

       If this succeeds, it should be possible to retry the upgrade using

       SMS Setup to upgrade the primary site again.

389    Cannot enumerate users for domain (X). Possible NT error: (Y)

390    Cannot enumerate user groups for domain (X). If this is a NetWare

       domain, this may be due to the Gateway Service for NetWare not

       running on the SMS site server. Possible NT error: (Y)

391    The package includes Macintosh as one its supported platforms.

       However none of the package servers are able to support Macintosh

       packages. Please make sure Service for Macintosh is running on at

       least one of the package servers.

392    Drive X on server Y is not an NTFS drive, which is required for a

       successful secondary site install. Please select an NTFS drive and

       retry the secondary site install.

393    Failed to decompress the package on server X, the required space is

       MBytes, the drive with most free space only has Y MBytes free.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Foreign NAD Items Remain After Child Detaches

Article ID: Q122201

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When a child site detaches from a parent site, any packages or program

groups defined at the parent site exist and are preserved on the child

site.

WORKAROUND

==========

After a child site detaches from a parent, you may want to remove the

previous parent site's network applications database (NAD) from the child.

Removal of the parent's NAD does not automatically occur because of the

potentially dramatic effect it could have on client machines (program

groups and program items being removed) even though access to these items

may still exist.

To initiate a transaction in the Systems Management Server Applications

Manager, use the following procedure, run the NADRESET.BAT file in the

PSSTOOLS directory on the CD. This file performs the following steps:

 - Creates a 10000000.NAD directory in <SMSROOT>\SITE.SRV\SITECFG.BOX.

 - Creates a TRANSLOG.CLR file in the 10000000.NAD directory.

 - Creates an ALL.RST file in the 10000000.NAD directory.

NOTE: 10000000.NAD is used only because it is unlikely that a directory

with the same name exists. Any name can be used with the NAD extension.

The next polling interval for the Applications Manager removes foreign NAD

items. There will be a period of time before the changes are propagated to

the MAINCFG.BOX\APPCTL.SRC\DATABASE directory. Following this processing,

the files created in the list above are automatically removed by the

Applications Manager.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntdomain

Additional reference words: sms prodsms 1.00 1.10


DEC Turbo Port Addresses Appear Reported Incorrectly

Article ID: Q122324

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

Microsoft Systems Management Server appears to incorrectly report the

actual port address for DEC Turbo network cards.

CAUSE

=====

DEC Turbo DE20x NICs support only a primary or secondary I/O port address.

Because of this, the DEC Turbo MAC driver needs only to configure the

drivers I/O port Registry entry for 0x1 or 0x2.

Systems Management Server reads the Registry entries for NIC drivers when

it collects hardware inventory. Because of the special configuration of DEC

Turbo NIC Registry entries, Systems Management Server reports the NIC I/O

port addresses as 0x1 or 0x2.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

DEC Turbo network cards are manufactured by Digital Equipment Corporation,

a vendor independent of Microsoft; we make no warranty, implied or

otherwise, regarding this product's performance or reliability.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntdriver ntinterop

Additional reference words: sms adapter prodsms 1.00 1.10


Problems Running SMS w/Non-English Versions of Windows NT

Article ID: Q122383

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you use Microsoft Systems Management Server version 1.0 with a

non-English version of Windows NT, one or both of the following

problems may occur:

 - Site Config Manager cannot set any directory permissions.

 - Despooler fails on any package because the directory permissions cannot

   be set.

WORKAROUND

==========

To allow SMS to work with non-English versions of Windows NT Server, the

following procedure is recommended in User Manager:

1. Duplicate the non-English local Administrators group to "Administrators"

   in English.

2. Duplicate the non-English local Guests group as the "Guests" group in

   English.

3. Duplicate the non-English local Users group as the "Users" group in

   English.

4. Duplicate the non-English local Users group as the "Everyone" group in

   English and add the global Domain Guests group to it.

5. Restart Windows NT.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versionw 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: nthowto ntconfig

Additional reference words: sms prodsms 1.00 1.10 umd


Enabling Help Desk Options for MS-DOS Clients

Article ID: Q122399

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Help Desk Options for MS-DOS clients are disabled by default. This article

discusses proper methods to enable Help Desk Options for an MS-DOS Remote

client.

MORE INFORMATION

================

Help Desk Options can be enabled by an MS-DOS client using the -v option of

USERTSR and USERIPX, or by modifying the SMS.INI on the client. Help Desk

Options enabled using the -v option of USERTSR and USERIPX (USERIPX is used

only with Novell IPX clients) are not saved, so the next reboot results in

selected options being disabled again. Help Desk Options enabled by

modifying the SMS.INI are permanent.

Method 1: Using -v Option of USERTSR and USERIPX

------------------------------------------------

To enable options using the -v command of USERTSR or USERIPX:

1. Make sure USERTSR or USERIPX has already been loaded in the CLIENT.BAT

   file because the -v options are not available until USERTSR or USERIPX

   has already been loaded.

2. Run USERTSR or USERIPX with a -v option for every Help Desk Option you

   would like to enable. Available options are:

      VIEW - Allows Remote Control of the client

      FILEXFER - Allows File Transfer to/from the client

      EXECUTE - Allows Remote Execution of commands on the client

      REBOOT - Allows Remote Reboot of the client

      Example:

      USERTSR -vVIEW -vREBOOT -vEXECUTE

   NOTE: To disable a Help Desk Option, enter a -v option preceded by NO.

   For example:

      USERTSR -vNOVIEW -vNOREBOOT -vNOEXECUTE

Method 2: Modifying SMS.INI File

--------------------------------

To enable options in the SMS.INI:

1. Change the properties of the SMS.INI file from read-only, hidden, and

   system using the following MS-DOS command:

      attrib c:\sms.ini -r -h -s

2. Open the SMS.INI file in Notepad and change the entries in the Sight

   section from "No" to "Yes" (without the quotation marks):

      [Sight]

      Allow Takeover= <No | Yes>

      Allow Reboot= <No | Yes>

      Allow File Transfer= <No | Yes>

      Allow Remote Execute= <No | Yes>

3. Save the changes and set the properties of the SMS.INI to read-only,

   hidden, and system using the following MS-DOS command:

      attrib c:\sms.ini +r +h +s

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain


Using SMS to Share Document Files with PGC

Article ID: Q122400

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Microsoft Systems Management Server version 1.0 was not designed to

share documents that were associated with Systems Management Server shared

applications. For example, by current design, a Systems Management Server

shared version of Microsoft Word (MSWord) cannot open a Systems Management

Server shared document. The following error message

usually appears in this situation:

   Unable to open file <filename>.

This happens whenever a drive letter is required. With Windows NT systems,

using the Runs With UNC Name attribute allows the document to load

properly.

MORE INFORMATION

================

Any Systems Management Server shared program item requires the Appstart

utility (APPSTART) to be ran. If a shared program item has a command line

like SHAREME.DOC, and Requires Drive Letter is specified, Systems

Management Server is unable to open the document file.

This is because APPSTART is ran twice during the process; first to launch

SHAREME.DOC, and second to launch MSWord. APPSTART then quits the first

instance of itself and continues. This removes the first environment and

the associated drive letter assigned to the SHAREME.DOC path.

For example, APPSTART assigns a driver letter <G:>, and runs

G:\SHAREME.DOC. Windows then associates the *.DOC file with MSWord and

attempts to launch it. If a Systems Management Server version of MSWord is

installed on the system, Windows then launches APPSTART a second time to

start the shared version of MSWord. APPSTART detects that it is already

running and shuts down the first instance, removing the drive connection to

SHAREME.DOC. APPSTART then connects a new drive letter <H:> for MSWord and

runs the command line H:\WINWORD.EXE G:\SHAREME.DOC. Because drive G has

been disconnected by APPSTART, MSWord generates an error message that the

file could not be opened.

A partial workaround is to configure the shared document with the Runs With

UNC Name attribute, and distribute to Windows NT clients only. Like the

above scenario, the second instance of APPSTART quits the first instance,

removing the drive location. However, Windows NT allows universal naming

convention (UNC) network path names, and when MSWord runs, the command line

is H:\WINWORD \\<SMS Server>\SHAREME.DOC. This forces Windows NT to open a

new UNC connection to the SHAREME.DOC.

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: nthowto


SMS Installation Incomplete with Missing Admin Drive Share

Article ID: Q122988

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you install Microsoft Systems Management Server on a drive that

has the Administrator share deleted, Systems Management Server installs a

site that has most subdirectories missing, and Setup does not report any

errors. This results in an unusable Systems Management Server site.

CAUSE

=====

Systems Management Server Setup and the Systems Management Server services

require that the Administrative drive shares (such as C$) exist on a server

before Systems Management Server is installed. These shares are installed

by default by LAN Manager and Windows NT.

Systems Management Server Setup begins installation and creates part of the

directory structure on the target drive. Systems Management Server then

starts the SMS_SITE_CONFIG_MANAGER service which completes the

installation. The service attempts to look for the UNC name \\<server

name>\<drive>$ to complete the installation. If this share doesn't exist,

an error will be reported in the SCMAN.LOG file but the site does not

complete the installation.

WORKAROUND

==========

The drive administrative shares will be recreated the next time you reboot

of the system or you can manually recreate the shares. In order to recover

from the damaged Systems Management Server installation, use Systems

Management Server Setup to remove the site and then reinstall it from the

beginning.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntsetup

Additional reference words: sms prodsms 1.00 1.10


How Set Up SMS to a Remote SQL Server

Article ID: Q123212

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The following procedures will guide you through setting up a primary site

server on a remote SQL Server.

MORE INFORMATION

================

Installing SQL Server

---------------------

1. Install SQL Server on the Windows NT domain server. Follow SQL Server

   documentation.

   NOTE: All device names and passwords are case-sensitive.

2. Start SQL Administrator to create new devices for the remote Systems

   Management Server server.

3. Connect to the SQL Server server using the correct login name and

   password.

4. Choose the Devices icon.

5. From the Manage menu, choose Devices.

6. Choose Create.

7. Enter a logical name. SQL Administrator will generate a physical name

   with a *.DAT extension.

8. Select database for the type and use the size you think is correct for

   your site. The more computers to be inventoried, the larger the database

   should be. Use 5 KB to 10 KB per computer.

9. Choose OK.

10. Repeat steps 4 through 8 for LOG device creation changing the *.DAT

    file extensions to *.LOG. Do not change the device number for either

    the DB or the LOG device creation.

11. Do not create a new database. The Systems Management Server Setup

    program creates the Systems Management Server databases dynamically and

    attach the devices.

Installing Systems Management Server

------------------------------------

1. Create a user account for the Systems Management Server Service Account.

   This account must be a member of either the Administrators local group

   or the Trusted Domains Administrators group. Ensure that this user can

   log on as a service.

   If the SQL database is located on a non-trusted domain, ensure that the

   user account you have created in your domain has the same username and

   password as the remote SQL Server.

   NOTE: If this procedure is not done properly, the following error

   message may appear:

      Hierarchy Manager is not responding to instructions.

2. Install Systems Management Server.

3. When asked about SQL Server, enter the computer name of the remote SQL

   Server server.

4. Fill out the rest of the screen until you get to the database name,

   device, and log device. Enter the device names that you chose on the

   remote SQL Server server. Systems Management Server Setup creates the

   database dynamically in order to attach to the manually-created devices.

5. Choose OK and proceed with the rest of the Systems Management Server

   installation.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


Requirements of a SMS Network Monitor Agent

Article ID: Q123213

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

Microsoft Network Monitor is a component of Systems Management Server that

allows network administrators to detect and troubleshoot problems on the

network.

A Network Monitor Agent enables a client computer to be used by a

remote installation of Network Monitor to capture network statistics.

One of the requirements of a Network Monitor Agent is that it must run

on a Windows NT computer in order to remotely capture network statistics.

This process cannot be accomplished on any other client computer such

as a Windows for Workgroups version 3.11 computer. A Windows for

Workgroups computer can only monitor locally.

Additional reference words: sms wfw wfwg prodsms 1.00 1.10

KBCategory: kbnetwork

KBSubcategory: ntnetserv


DumpSend: Send Request File Formats

Article ID: Q123221

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article describes how to use the DumpSend utility, explains the output

generated, and shows the different record types and their meanings within

the Systems Management Server system.

THE DUMPSEND UTILITY

====================

The DumpSend utility is accessed with the DUMPSEND command. It displays the

binary Systems Management Server send request file in text format for

review. It has the following syntax:

   DUMPSEND [/P] [send request filename, *.SRS, *.SRQ]

These files reside in the \SMS\SITE.SRV\SENDER.BOX\REQUEST\<outbox>

directories and can have either a "*.SRQ" (not processed yet) or "*.SRS"

(processed but not completed) extension.

A Sender monitors its associated outbox directory for the existence of a

send request file. When this file is seen by the Sender, it parses the

instructions and attempts to perform the operations requested. Some site to

site communication problems can be resolved by using DumpSend to determine

the contents of these files.

A send request file is a variable length file composed of a series of

records. This file contains, at a minimum, the INFO, STATUS, ADDRESS, and

INSTRUCTION records.

NOTE: Some record types are not parsed by DumpSend. The information in

these record types is usually not needed for trouble-shooting.

SEND REQUEST RECORD TYPES

=========================

Following is a list of the various Send Request record types and their

structures listed in the order that DumpSend displays them:

Send Request RECORD (INFO, Record type 3)

-----------------------------------------

Priority:      SMS Job priority; 1 high, 2 medium, 3 low

Dest Site:     SMS Site code; 3 character

Job name:      SMS Job ID; 8 characters

Job request:   Unique send request ID; 7 characters

Outbox:        UNC path to outbox directory

Sender/Scheduler RECORD (STATUS, Record type 15)

------------------------------------------------

Sender status:              Contains one of the following status flags:

                               SREQ_STATUS_NONE

                               SREQ_STATUS_STARTED

                               SREQ_STATUS_CONNECTING

                               SREQ_STATUS_SENDING

                               SREQ_STATUS_ERROR

                               SREQ_STATUS_INVALID

                               SREQ_STATUS_CANCELLED

                               SREQ_STATUS_SUSPENDED

                               SREQ_STATUS_OK

First sender started at:    Date/Time of first send attempt

Sender started at:          Date/Time of last send attempt

Sender ended at:            Date/Time of when last send attempt stopped

Sender gate heartbeat at:   Date/Time interval for next attempt

Scheduler to restart at:    Date/Time of next send attempt

Total bytes to send:        Total bytes to send, including package file

Bytes left to send:         Total bytes left to send

Sync point is:              Total confirmed bytes sent and acknowledged

File type is:               0 Sender only, 1 *.INS, 2 *.PKG

Number of connects:         Number of connection attempts

Sender ID:                  ID of sender working on send request

CANCEL RECORD (Record type 4)

-----------------------------

Cancel Status:   Indicates if Send Request has been canceled.

ACTION CODE RECORD (Record type 14)

-----------------------------------

Code:   This code is set by the Sender after a send failure. The Scheduler

        service processes this code: 0 do nothing, 1 retry, 2 delete send

        request.

ADDRESS RECORD (Record type 5, multiple records allowed)

--------------------------------------------------------

Address:   Contains the destination \\<SMS Server>\SMS_SITE share and the

           encrypted account password to access this share.

PACKAGE FILE RECORD (Record type 7)

-----------------------------------

File:   The universal naming convention (UNC) name of the package file to

        send. The package file contains a compressed copy of the original

        package which is to be sent to the despooler at the destination

        site.

INSTRUCTION FILE RECORD (Record type 8)

---------------------------------------

File:   The UNC name of the instruction file to send. The instruction file

        contains the despooler instructions for the package.

Other types of Sender records exist that DumpSend does not parse out at

this time. Some of these are listed below:

TRANSMISSION STATUS (Record type 1)

-----------------------------------

Transmission status, errors etc., between sites.

TRANSMISSION INFORMATION (Record type 2)

----------------------------------------

Transmission statistics.

CANCEL (Record type 4)

----------------------

Cancel mode.

BOOTSTRAP (Record type 13)

--------------------------

Contains information necessary to start the bootstrap process for

installing a secondary Systems Management Server Site.

SENDACTION (Record type 17)

---------------------------

This record contains information that is specific to the individual types

of Senders.

ROUTING (Record type 18)

------------------------

This record contains routing information but is not implemented for Systems

Management Server version 1.0.

SAMPLE DUMPSEND OUTPUT

======================

Below is a sample command line and the subsequent output:

   d:\sms\site.srv\sender.box\requests\lan_defa.000>dumpsend 1_2zybpc.srs

   SMS DumpSend v1.0 - Dump Sender files

   Copyright 1994 by Microsoft Corp., All rights reserved

   SEND REQUEST DATA RECORD

      Length:       300

      Priority:     2

      Dest Site:    CSL

      Job:          BPC00434

      Job request:  _2ZYBPC

      Outbox:       \\CNS-SMS\SMS_SHRD\site.srv\sender.box\requests

                    \LAN_DEFA.000

   Sender/scheduler RECORD

      Length:       80

   ==============================================

      Sender status:              SREQ_STATUS_OK

      First sender started at:    (not set)

      Sender started at:          Mon, Nov 21 1994 12:45

      Sender ended at:            Mon, Nov 21 1994 12:45

      Sender gate heartbeat at:   Mon, Nov 21 1994 12:45

      Scheduler to restart at:    Mon, Nov 21 1994 12:45

      Total bytes to send:        1596

      Bytes left to send:         0

      Sync Point is:              504

      File type is:               0 (No file)

      Number of connects:         0

      Sender ID:

   ============= End of Dump ==============

   CANCEL RECORD

      Length:   4

      Mode:     Not cancelled

   ACTION CODE RECORD

      Length:   4

      Code:     0

   ADDRESS RECORD

      Length:    181

      Address:   {}{\\VERMONT\SMS_SITE

                 2DDEAF90293488DDD7427DB90B5AEB891C48F9

                 0CF52F68C273D919D3A338EC39B641AF2D2AFADD

                 9C493B13ABA1DED992959DDEA4A9ADAAFF67B25

                 E1DB3B75A584CD80F1F198907AE5D3544D39C9C}

   PACKAGE FILE RECORD

      Length:   59

      File:     \\CNS-SMS\SMS_SHRD\site.srv\sender.box

                \tosend\BPC00434.P00

   INSTRUCTION FILE RECORD

      Length:   59

      File:     \\CNS-SMS\SMS_SHRD\site.srv\sender.box\tosend\BPC00434.I00

   UNKNOWN RECORD TYPE 18

      Length:   544

   UNKNOWN RECORD TYPE 17

      Length:   61

KBCategory: kbnetwork

KBSubcategory: nthowto

Additional reference words: sms prodsms 1.00 1.10


Checklist for Enabling SMS in Logon Scripts

Article ID: Q123318

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

This article provides a checklist of what must be accomplished before

Systems Management Server will install itself in the logon scripts

for a Microsoft network domain (Windows NT or LAN Manager):

1. Configure and enable the Directory Replicator service for the domain

   being managed by Systems Management Server. Systems Management Server

   looks for a REPL$ share on the domain controller (DC). If it doesn't

   exist, the Site Configuration Manager will not be able to copy the

   proper Systems Management Server logon support files to the

   \EXPORT\SCRIPTS directory.

2. Using Systems Management Server Administrator, configure the Systems

   Management Server Site properties as follows:

   a. In the Clients dialog box, select Automatically Configure Workstation

      Logon Scripts.

   b. In the Domains dialog box, select Use All Detected Servers for each

      domain that you want logon scripts enabled.

   NOTE: At this point, SMS has been properly configured. It will then

   configure the user logon scripts for each domain to include the

   SMSLS.BAT entry, and copy the proper SMS support files to the REPL$

   share during the next Site Configuration Manager watchdog cycle. This

   occurs by default, every 24 hours but can be forced immediately by using

   one of the two methods listed in Step 3.

3. To force the watchdog cycle to occur immediately, use one of the

   following steps:

    - Toggle the SMS Site property for Logon Scripts, changing it from its

      current state to the other state. This will toggle the site control

      file line "PROPERTY <Logon Scripts><><><1>" to 1 or 0. Site

      Configuration Manager will read this line and immediately configure

      the Logon Scripts appropriately. For example, if the Site Property,

      Automatically Configure Workstation Logon Scripts, in the Clients

      dialog box, is clear, selecting it will change the flag from 0 to 1.

      This would then force Site Configuration Manager to configure logon

      scripts when it next reads the SITECTRL.CT1 file.

    - Use the SENDCODE utility. It is located on the SMS CD in the PSSTOOLS

      directory. At the SMS Site server, run Command Prompt and type in the

      following command line:

         sendcode sms_site_config_manager 196

      This will force Site Configuration Manager to perform its watchdog

      cycle immediately and configure the SMS logon scripts for all users

      in the domains that were enabled in Step 2.

KBCategory: kbnetwork

KBSubcategory: nthowto ntutil

Additional reference words: sms prodsms 1.00 1.10


Adding a Pure LAN Manager Domain to SMS

Article ID: Q123369

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

Due to the way the Windows NT Computer Browser service manages LAN

Manager/LAN Server domains in its browse list, the Site Configuration

Manager may fail to enumerate a LAN Manager/LAN Server-only domain when

adding a LAN Manager/LAN Server domain to a Systems Management Server

site. It is possible to correct this by modifying the configuration of the

Computer Browser service on the site server domain primary domain

controller (PDC).

On the site server domain PDC, the Computer Browser service must be

specifically configured to include the LAN Manager/LAN Server domain. To do

this, use the following procedure:

1. In Control Panel, choose the Network icon.

2. In the Network Settings dialog box, select Computer Browser and choose

   Configure.

3. For Other Domain, type the name of the LAN Manager/LAN Server domain and

choose Add. Choose OK.

This procedure will cause the Computer Browser service for the domain to

track needed information on the LAN Manager/LAN Server domain, allowing SMS

to successfully configure the new domain. This is not specific to SMS and

may also be needed for simple domain and server browsing from within File

Manager on a network with both Windows NT domains and pure LAN Manager/LAN

Server domains.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


PCMDUMP and Package Command Manager Instruction Files

Article ID: Q123499

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

This article describes how to use the PCMDMP utility, explains the output

generated, and shows how to interpret the information within the Systems

Management Server system.

MORE INFORMATION

================

When the client's Package Command Manager (PCM) polls a logon server during

its designated interval, it will look in the \\<logon

server>\SMS_SHR\PCMINS.BOX directory for a file name that has the same SMS

ID as itself. When the file is located, PCM will then parse this file and

determine what actions need to be taken, if any.

PCMDUMP displays binary PCM instruction files in text format for review.

These files reside in the \SMS\LOGON.SRV\PCMINS.BOX directories, named with

the unique SMS ID of the destination system, appended with a .INS

extension.

Some package installation problems can be resolved by examining the

contents of the clients PCM instruction file. The instruction file can

contain multiple records, one for each package to install. Below is a

description of the record structure:

SiteID:             Three character SMS site code.

RequestID:          A unique package distribution ID.

PackageID:          Identifies actual package to distribute.

JobID:              ID of job used to distribute this package.

Install Flag:       0-1   Install regardless of network speed.

                    2     Do not install over a slow network link.

Install By Date:    Package will become mandatory after this date and time.

Install By Full:    0   Optional Install.

                    1   Mandatory Install.

Display Date:       Make available for installation after this date.

Display Full:       Display this package in PCM.

Expiration Date:    Package expires after this date.

Expiration Full:    0   Never expires.

                    1   Expires after expiration date.

User Input Flags:   0   Doesn't require user input.

                    1   Require user input.

Operating System:   Bit mask of which operating system to install on.

                    Supported operating systems and bit masks:

                       WIN16         0x00000001

                       WIN32_X86     0x00000002

                       WIN32_MIPS    0x00000004

                       WIN32_ALPHA   0x00000008

                       DOS5          0x00000010

                       DOS6          0x00000020

                       MACINTOSH     0x00000040

Disk Usage:         Not used.

Run Command:        Command line to be run.

WCL Name:           Descriptive text, displayed in PCM under Command Name.

Server(s):          The full universal naming convention (UNC) path to

                    available package directories, and server types. Server

                    types:

                       UNKNOWN    1

                       WINNT3     2

                       LANMAN1    3

                       LANMAN2    4

                       NETWARE2   5

                       NETWARE3   6

                       NETWARE4   7

Package Name:       Name of package.

Comments:           Text comments that are included with the package.

Domain Name:        Not used.

Reserved:           Internal information used by SMS.

Below is an example of PCMDUMP output. Note that there are two extra items

at the top of the PCMDUMP output that are not part of the normal record

structure. The first item, reported only once, is the filename that PCMDUMP

is parsing. The second item, repeated for every record, is the version of

the record. "Beta 455" translates to "version 6" which is the correct

version for SMS 1.0.

   D:\SMS\LOGON.SRV\PCMINS.BOX>PCMDUMP MDM00005.INS

   PCM Instruction File Dump Utility v1.0

   Copyright 1993, 1994 Microsoft Corporation

   File Name       : mdm00005.ins

   PCM Version     : Beta 455

   SiteID          : BPC

   RequestID       : BPC001M

   PackageID       : BPC0000A

   JobID           : BPC000AA

   Install Flag    : 0

   Install By Date : 00/00/00 00:00:00

   Install By Full : 0

   Display Date    : 09/21/94 17:56:00

   Display Full    : 1

   Expiration Date : 03/07/95 17:56:00

   Expiration Full : 1

   User Input Flags: 0

   Operating System: 15

   Disk Usage      :

   Run Command     : acmewkst.exe smsproxy\complete.stf /I:C

   WCL Name        : Complete

   Server(s)       : \\CNS-SMS\SMS_PKGD\BPC0000A\ Type: 2

                     Zone: \\CNS-SMS\SMS_PKGD\BPC0000A\

                   : \\CNSAPPS1\SMS_PKGD\BPC0000A\ Type: 2

   Package Name    : Microsoft Office Professional 4

   Comments        : Microsoft Office Professional 4.3

   Domain Name     :

   Reserved        : 00 E6 F8 77 60 82 F9 77 FF FF FF FF 94 FF 03 00 FE 5F

                     40 00 00 00 05 00 08 00 00 00 0F 00 00 00

   PCM Version     : Beta 455

   SiteID          : BPC

   RequestID       : GBL00B9

   PackageID       : GBL00015

   JobID           : GBL0015B

   Install Flag    : 0

   Install By Date : 00/00/00 00:00:00

   Install By Full : 0

   Display Date    : 09/24/94 07:00:00

   Display Full    : 1

   Expiration Date : 11/31/94 07:00:00

   Expiration Full : 1

   User Input Flags: 0

   Operating System: 51

   Disk Usage      :

   Run Command     : audit.bat

   WCL Name        : Find Microsoft Software

   Server(s)       : \\CNS-SMS\SMS_PKGD\GBL00015\ Type: 2

                     Zone: \\CNS-SMS\SMS_PKGD\GBL00015\

                   : \\CNSAPPS1\SMS_PKGD\GBL00015\ Type: 2

   Package Name    : MS Software Audit (16 Packages)

   Comments        : This package will search your hard disk drives looking

                     for Microsoft software. It will report only which

                     Microsoft programs you have installed on this

                     computer. This will be used to offer you software

                     upgrades as they become available.

   Domain Name     :

   Reserved        : 00 E6 F8 77 60 82 F9 77 FF FF FF FF 94 FF 03 00 FE 5F

                     40 00 00 00 05 00 08 00 00 00 0F 00 00 00

   PCM Version     : Beta 455

   SiteID          : BPC

   RequestID       : BPC003F

   PackageID       : BPC00010

   JobID           : BPC00112

   Install Flag    : 0

   Install By Date : 00/00/00 00:00:00

   Install By Full : 0

   Display Date    : 09/25/94 13:14:00

   Display Full    : 1

   Expiration Date : 03/11/95 13:14:00

   Expiration Full : 1

   User Input Flags: 1

   Operating System: 64

   Disk Usage      :

   Run Command     : "Flight Simulator Program"

   WCL Name        : Install Flight Simulator on your system

   Server(s)       : \\CNS-SMS\SMS_PKGD\BPC00010\ Type: 2

                     Zone: \\CNS-SMS\SMS_PKGD\BPC00010\

                   : \\CNSAPPS1\SMS_PKGD\BPC00010\ Type: 2

   Package Name    : MS Flight Simulator

   Comments        : This is for Macintosh Only

   Domain Name     :

   Reserved        : 00 E6 F8 77 60 82 F9 77 FF FF FF FF 94 FF 03 00 FE 5F

                     40 00 00 00 05 00 08 00 00 00 0F 00 00 00

   PCM Version     : Beta 455

   SiteID          : BPC

   RequestID       : BPC005Q

   PackageID       : BPC00012

   JobID           : BPC001F9

   Install Flag    : 0

   Install By Date : 11/01/94 23:59:00

   Install By Full : 1

   Display Date    : 09/27/94 18:37:00

   Display Full    : 1

   Expiration Date : 03/13/95 18:37:00

   Expiration Full : 1

   User Input Flags: 0

   Operating System: 1

   Disk Usage      :

   Run Command     : patch.exe

   WCL Name        : Patch of NW Redirector

   Server(s)       : \\CNS-SMS\SMS_PKGD\BPC00012\ Type: 2

                     Zone: \\CNS-SMS\SMS_PKGD\BPC00012\

                   : \\CNSAPPS1\SMS_PKGD\BPC00012\ Type: 2

   Package Name    : WFW VREDIR.386 Patch

   Comments        : Patch Utility for new WFW Redirector

   Domain Name     :

   Reserved        : 00 E6 F8 77 60 82 F9 77 FF FF FF FF 94 FF 03 00 FE 5F

                     40 00 00 00 05 00 08 00 00 00 0F 00 00 00

KBCategory: kbtool

KBSubcategory: nthowto ntutil

Additional reference words: sms prodsms 1.00 1.10


Orphan Machine Inventory, Ghost Sites, and Domains

Article ID: Q123878

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you follow the process for adding or removing a domain or site from a

Systems Management Server Primary Site, you may see warnings

indicating that sites, addresses, or machines are inconsistent with the

database.

CAUSE

=====

The following situations can cause these messages:

 - A client machine is moved from one primary site database to

   another primary site database. When this happens the "losing"

   site database is not informed. This constitutes an "orphan"

   machine, and since the possibility exists that the entire

   domain was moved to a new site, a warning may be issued. If

   you do not want the machine movement, you (as the administrator),

   can increase the FalseLogonThreshold parameter in the registry.

   Movement from a secondary site to a parent site does not cause

   a problem because the existing machine inventory is updated with

   a new site code/domain name.

 - A child site detaches or is otherwise removed (secondary site)

   from the current site. When this happens the machine inventory

   is left behind. This is similar to the following situation.

 - One or more of the current site's domains are removed using

   the Site Properties <Domains> dialog. When this happens the machine

   inventory is left behind. Because the machine inventory is keyed to the

   Site/Domain combination, a warning appears when this combination is no

   longer valid.

 - Sites exist in the database which are not addressable (no

   sender address has been created). Also, when a site detaches, the

   parent's address to the child is automatically removed, but the

   inventory remains.

RESOLUTION

==========

To correct the database and prevent these message pop-ups, use a query

to bring up a list of candidate machines to be manually deleted. The

query dialog can be used to specify a particular site code, domain

name, and so forth. In the case of site address messages, an address will

need to be created, or the ghost site can be removed with the PREINST

/DELSITE command (see the Admin documentation for the Site Hierarchy

Manager command-line syntax).

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

versions 1.0 and 1.1. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


SMS: ViewNAD and the Network Applications Database (NAD)

Article ID: Q124083

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

ViewNAD provides a text based graphical display of the current Systems

Management Server Network Applications Database (NAD) for review.

This article describes how to use the ViewNAD utility.

MORE INFORMATION

================

VIEWNAD.EXE    Dumps the NAD database for review

Environment:   32 bit Windows NT

Usage:         VIEWNAD

Execute VIEWNAD.EXE from the directory:

   \\<logon server>\SMS\LOGON.SRV\APPCTRL.BOX\DATABASE

ViewNAD provides a text based graphical display of the current Network

Applications Database for review. This database consists of *.HGF (groups)

and *.HAF (applications) files. These files are parsed by ViewNAD and are

then displayed.

The NAD database resides on each SMS logon server in the

..\LOGON.SRV\APPCTRL.BOX\DATABASE directory. The *.HAF files contain the

applications available and the *.HGF files contain information on what

global user groups have access to these applications.

An SMS client uses the Program Group Control (PGC) utility to read these

databases and update the users desktop based on the information in the

files.

This is accomplished by using a LAN Manager API to enumerate all global

user groups that the current user belongs to in the currently logged on

domain. PGC will then compare the list generated with the user groups

listed in the NAD files and update the clients desktop to match the NAD

list of applications that are associated with these user groups.

There are three sections to the ViewNAD output.

The first section lists what groups the currently logged on user of ViewNAD

belongs to.

The second section contains a list of the NAD objects. The first line

contains the return code 1 or 0 for success/failure and the size of the

buffer holding the objects. It then lists all the NAD objects in the

database. The first three characters are the site code of the originally

created package.

The third section contains the NAD program item information. Each program

group is listed with its associated program items. Below is the record

format.

Program Group:   <Internal Database Unique ID>

  Group:         Name of program group

  Users:         A list of global user groups that have been granted access

                 to this program group

  <SMS Program Item Unique ID>

  Registry:      Name of the clients registry key for this program item

  Description:   Name of the program item

  Command:       Command line executable file name

  Servers:       UNC names of the SMS distribution servers available.

  Drive:         Type of redirection required (drive mode)

                    If not listed then runs with UNC name

                    <"?">: Requires a drive letter

                    <letter>: Requires this specific drive letter

  Platform:      Bit mask of supported platforms. Currently this data is

                 invalid. ViewNAD parses this data incorrectly.

Below is an example of a ViewNAD output of an SMS site's NAD database:

   INTERACTIVE

   LOCAL

   Department 8954

   psscnsred-se

   Administrators

   Everyone

   Domain Users

   Get Objects Return Code 1 Size 45

   BPC00001

   BPC00002

   BPC00003

   BPC00004

   GBL00003

   Program Group ======= BPC00001 ==========

     Group          MS Office

     Users          psscnsred-mgr;psscnsred-se

     ÃÄ BPC00007

     ³  Registry    msoffpro+autoconv:msapps

     ³  Description Graph AutoConvert

     ³  Command     msgraph5\autoconv.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0000C

     ³  Registry    msoffpro+graflink

     ³  Description GraphicsLink

     ³  Command     graflink.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0000A

     ³  Registry    msoffpro+wrkgadm

     ³  Description MS Access Workgroup Administrator

     ³  Command     wrkgadm.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0000D

     ³  Registry    msoffpro+mplayer

     ³  Description Media Player

     ³  Command     mplayer.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00009

     ³  Registry    msoffpro+msaccess

     ³  Description Microsoft Access

     ³  Command     msaccess.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00004

     ³  Registry    msoffpro+excel

     ³  Description Microsoft Excel

     ³  Command     excel.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00001

     ³  Registry    msoffpro+msoffice

     ³  Description Microsoft Office

     ³  Command     msoffice.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00006

     ³  Registry    msoffpro+powerpnt

     ³  Description Microsoft PowerPoint

     ³  Command     powerpnt.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00005

     ³  Registry    msoffpro+msquery:msapps

     ³  Description Microsoft Query

     ³  Command     msquery\msquery.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00002

     ³  Registry    msoffpro+winword

     ³  Description Microsoft Word

     ³  Command     winword.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0000B

     ³  Registry    msoffpro+ofreadme

     ³  Description Office Readme Help

     ³  Command     ofreadme.hlp

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0000E

     ³  Registry    msoffpro+preview

     ³  Description PowerPoint

     ³  Command     preview.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00008

     ³  Registry    msoffpro+pptview

     ³  Description PowerPoint Viewer

     ³  Command     pptview.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00003

     ³  Registry    msoffpro+macrode

     ³  Description Word Dialog Editor

     ³  Command     macrode.exe

     ³  Servers     \\CNS-SMS\ofc43_sh\;\\CNSSUP2\ofc43_sh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0000F

     ³  Registry    MSAPPS

     ³  Description MSAPPS Shared Components

     ³  Command     <no command for applets>

     ³  Servers     \\CNS-SMS\msappssh\;\\CNSSUP2\msappssh\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

   Program Group ======= BPC00002 ==========

     Group          CNS Documents

     Users          psscnsred-mgr;psscnsred-se

     ÃÄ BPC0001D

     ³  Registry    oct94hcl.hlp

     ³  Description NT 3.5 October HCL

     ³  Command     miscinfo\oct94hcl.hlp

     ³  Servers     \\CNS-SMS\cns-docs\;\\CNSAPPS1\cns-docs\;\\CNSSUP2\cns-

                    docs\

     ³  Drive       ?

     ³  Platform    556A8556A9556AA556AB

     ÃÄ BPC00014

     ³  Registry    SP2help

     ³  Description NT Service Pack 2

     ³  Command     SP2-3.1\fixlist.hlp

     ³  Servers     \\CNS-SMS\cns-docs\;\\CNSAPPS1\cns-docs\;\\CNSSUP2\cns-

                    docs\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC00015

     ³  Registry    NTSP2a

     ³  Description NT Service Pack 2a

     ³  Command     SP2a-3.1\fixlist.hlp

     ³  Servers     \\CNS-SMS\cns-docs\;\\CNSAPPS1\cns-docs\;\\CNSSUP2\cns-

                    docs\

     ³  Drive       ?

     ³  Platform    556A8556A9556AA556AB

     ÃÄ BPC00016

     ³  Registry    NTSP2b

     ³  Description NT Service Pack 2b

     ³  Command     SP2b-3.1\FIXLIST.HLP

     ³  Servers     \\CNS-SMS\cns-docs\;\\CNSAPPS1\cns-docs\;\\CNSSUP2\cns-

                    docs\

     ³  Drive       ?

     ³  Platform    51EA851EA951EAA51EAB

     ÃÄ BPC0002D

     ³  Registry    BPC0002D

     ³  Description NT Service Pack 3

     ³  Command     SP3-3.1\FIXLIST.HLP

     ³  Servers     \\CNS-SMS\cns-docs\;\\CNSAPPS1\cns-docs\;\\CNSSUP2\cns-

                    docs\

     ³  Platform    555C0555C1555C2555C3

Additional reference words: sms prodsms 1.00 1.10

KBCategory: kbnetwork kbusage

KBSubcategory: nthowto


How to Remove Systems Management Server Clients

Article ID: Q124361

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

This article explains how a Systems Management Server administrator

can remove SMS clients from an SMS site.

MORE INFORMATION

================

To remove an SMS client, run the appropriate Client Setup application with

the /R switch. This is documented in Appendix B of the SMS "Administrator's

Guide." You must run Client Setup twice because it has to stop all SMS

components before the files can be removed. You can do this by running

SMSLS.BAT from the logon script or command prompt, or by running Client

Setup directly from the proper ..\SMS_SHR\<processor>.BIN directory for the

SMS client platform.

You can also run DEINSTAL from the SMS logon server SMS_SHR share. All site

SMS logon servers have DEINSTAL.BAT and DEINSTAL.CND files in the SMS_SHR

share. These files, when run from a SMS client, determine the operating

system that is being used and run the correct version of Client Setup with

the /R switch (for example, CLI_NT /R). This configures the client to

remove itself from the SMS site the next time Client Setup is run.

Additional reference words: sms prodsms 1.00 1.10 uninstall deinstall

deinstallation

KBCategory: kbnetwork

KBSubcategory: ntinfo


SMS Shared Version of Works 3.0 Displays OLE Error on Startup

Article ID: Q124429

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

After configuring and distributing Microsoft Works 3.0 as a Systems

Management Server shared application, an OLE registration error message

appears when you attempt to start Works. After choosing OK, Works runs

normally with no further errors.

CAUSE

=====

OLE applications are supposed to update their Registry entries on startup

to reflect the actual locations from which they run. Works is reporting an

error if these settings are as expected. In this instance, Works objects to

the SMS proxy applications file specification in its OLE Registry entries.

This has no effect on how OLE and the MSAPPS proxies work as the actual

path is resolved when an MSAPPs program is executed. The message is a

warning and not an indication that Works is improperly configured.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management Server

version 1.0. This problem has been corrected in Systems Management Server

version 1.1.

KBCategory: kbinterop kbbug1.00 kbfix1.10

KBSubcategory: nt16ap

Additional reference words: sms prodsms 1.00 1.10


Information on the SMSLOG.TXT File

Article ID: Q124430

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SMSLOG.TXT is created by APPSTART and SMSETUP to log all errors by these

applications. It can be found on your Systems Management Server

client, in your <WINROOT> directory. If it does not exist then APPSTART

will create it. SMSLOG.TXT will help you determine why an application will

not start, or why an application will not install using SMS. It can be

viewed with a simple text editor.

Example

-------

SMSLOG.TXT

[12/06/94 16:21:23] Program Group Control ==> An Application specific error

                                              occurred: SMSSETUP

- msworks: MSAPPS server list is empty. SMS package has not been

           successfully distributed.

[12/06/94 16:21:31] Program Group Control Start ==> 'Microsoft Works' has

                                                    not been successfully

                                                    configured.

[12/06/94 16:41:11] Program Group Control ==> An Application specific error

                                              occurred: SMSSETUP

- msworks: MSAPPS server list is empty. SMS package has not been

           successfully distributed.

[12/06/94 16:41:20] Program Group Control Start ==> 'Microsoft Works' has

                                                    not been successfully

                                                    configured.

[12/14/94 14:50:29] Program Group Control ==> The application

                                              msworks+msworks exists in the

                                              database, but this user does

                                              not have permission for it.

Additional reference words: sms 1.00 1.10 PRODSMS

KBCategory: kbusage

KBSubcategory: nthowto


Automatically Starting Shared Applications Under SMS

Article ID: Q124800

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Running Systems Management Server client component from the Program Manager

startup group is not supported. This article explains how to configure an

Systems Management Server client to start Systems Management Server shared

applications when Windows is started.

NOTE: The procedure described in this article is for informational use only

and is not supported by Microsoft.

You cannot run Systems Management Server client components from the Startup

group, because during an upgrade of the client, the SMSSVR component must

be able to overwrite program files. If the files are running, they cannot

be replaced. SMSRUN is assumed to be the single responsible component for

starting the Systems Management Server client applications. It is designed

this way to ensure that if upgrade is needed, it can skip loading the

applications and upgrade them.

MORE INFORMATION

================

For Systems Management Server to start a shared application, Program Group

Controller (PGC) must be running first. Since PGC requires time to

initialize, any Systems Management Server shared applications that are put

in the Startup Group usually fail to start. Shared applications are started

by APPSTART which is dependent on APPCTL<xx>.EXE (where <xx> is 16 or 32).

If APPSTART determines that APPCTL<xx>.EXE is not running, it fails to

start any applications.

When an SMS-configured Windows client is started, the LOAD= line, in the

WIN.INI file or the Windows NT Registry, starts the Systems Management

Server utility SMSRUN<xx>.EXE (where <xx> is 16 or 32). One of

SMSRUN<xx>.EXE's duties is to start APPCTL<xx>.EXE. This is done when

SMSRUN<xx>.EXE parses and executes the instructions in the

\MS\SMS\BIN\SMSRUN<xx>.INI (where <xx> is 16 or 32) file. This file tells

SMSRUN<xx>.EXE what to do and in what order.

By inserting a new line at the end of the [startup] section of the

SMSRUN<xx>.INI file, an Systems Management Server client can have

SMSRUN<xx>.EXE start other applications. To start a shared Systems

Management Server application, insert a line that contains APPSTART and the

Registry entry for that application. This should be a copy of the command

line for the program item in Program Manager. This will have SMSRUN<xx>.EXE

start PGC and allow it to initialize completely. After PGC initializes,

APPSTART will then be able to start an Systems Management Server shared

application.

NOTE: The Systems Management Server system itself may occasionally, using

CLI_<os>.EXE (where <os> is OS2, DOS, or Windows NT), modify this file

based on changes in the Systems Management Server site properties. If this

happens, you will need to reinsert any changes you made

to the SMSRUN<xx>.INI file.

EXAMPLE

=======

The following is a sample SMSRUN16.INI file that will start a shared

version of Microsoft Excel:

[SMS Client]

Package Command Manager=D:\MS\SMS\bin\pcmwin16.exe

Program Group Control=D:\MS\SMS\bin\appctl16.exe

Remote Control=D:\MS\SMS\bin\wuser.exe

Help Desk Options=D:\MS\SMS\bin\editini.exe

MIF Entry=D:\MS\SMS\bin\mifwin.exe

SMS Client Help=D:\MS\SMS\bin\sm16.hlp

[startup]

load=D:\MS\SMS\bin\pcmwin16.exe

load=D:\MS\SMS\bin\appctl16.exe

load=D:\MS\SMS\bin\mifwin.exe /SMSLS

load=APPSTART.EXE msoffpro+excel

KBCategory: kbnetwork kbenv

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 1.10 sms run program office auto

start


Connecting to a Remote Network Monitor Agent across a Router

Article ID: Q124837

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Network Monitor has the ability to capture traffic on another subnet by

connecting to a system that is running the remote AGENT software on that

subnet. The (Network Monitor) Agent software is shipped with Windows NT

Workstation and Windows NT Server. In Network Monitor, choosing Networks

from the Capture menu displays "remote" as one of the options. Provide the

AGENT's Computer Name (with or without "\\") to connect to it.

For Network Monitor to connect to a Remote Agent across a router, the

Remote Agent's computer name needs to be resolved. If the name cannot be

resolved, you get the following error.

   Failure connecting to <computer name of Agent>

MORE INFORMATION

================

The Remote Agent registers a NetBIOS name which is 16 characters long. It

consists of the computer name followed by 0xBE (extended characters).

So a machine named "HITME" would be "HITME\0xBE\0xBE\0xBE..."

Proceed with the following to connect to the agent across a router.

1. Ensure that the Manager and the Remote Agent systems have a routable

   protocol such as TCP/IP or NWLINK installed.

2. Install the Network Monitor Agent software on the remote computer.

3. Start the Network Monitor Agent Service either from the command line

   using the command NET START NMAGENT or from the Control Panel Services

   applet choosing Start with the Network Monitor Agent service selected.

4. If TCP/IP is the protocol that is used, then there are two ways to

   resolve a NetBIOS name to an IP address. If both the management station

   and the remote agent are using WINS (Microsoft Windows Internet Naming

   Service) then the name will be resolved via WINS and WINS locates the

   Agent. If not, then the LMHOSTS file on the management station must

   contain a special entry for the remote agent.

   If TCP/IP is used and WINS is not available, add the Agent's name in the

   LMHOSTS file. Non-printing (extended) characters can be added by using

   \0xnn format where nn represents the ASCII code for the character.

   Following are some examples from an LMHOSTS file.

   130.1.2.3  "MYAGENT\0xBE\0xBE\0xBE\0xBE\0xBE\0xBE\0xBE\0xBE\0xBE"   #PRE

   130.2.3.4  "REMOTEAGENT\0xBE\0xBE\0xBE\0xBE\0xBE"                   #PRE

   130.3.4.5  "SEATTLESERVER\0xBE\0xBE\0xBE"                           #PRE

   NOTE: Capital letters must be used for the agent name, the agent name

   must consist of 16 characters surrounded by quotation marks, and #PRE

   must end each entry.

6. The NBTSTAT command can be used to flush and reload the LMHOSTS cache

   after modifying the LMHOSTS file. To reload the cache, type "nbtstat -

   R". To view the cache, type "nbtstat -c".

   Once the cache has been updated, it should be possible to connect to the

   remote agent.

7. If NWLINK protocol is used, NameQuery should succeed because most

   routers are configured to forward broadcasts (packet type 20).

Additional reference words: sms prodsms 1.00 1.10 Bloodhound Netmon BH

KBCategory: kbnetwork

KBSubcategory: nthowto


NICs That Work with Network Monitor

Article ID: Q124838

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

The following network interface cards (NICs), or network adapters, have

been verified to work with Network Monitor. Microsoft has not tested every

computer and/or device in all possible configurations.

For updates to this list refer to the latest Hardware Compatibility List

for Windows NT, which is in Library 1 of the WINNT (GO WINNT) forum on

CompuServe[R] Information Services.

The following network adapters have been tested on the indicated platforms.

X86  MIPS  ALPHA  Network Adapter

----------------------------------------------------------------------

X     X      X    3Com[R] 3C503 EtherLink II[R] (Coax & TP)

X     X      X    3Com 3C503/16 EtherLink[R] II/16 (Coax & P)

X     X           3Com 3C507 EtherLink 16 (Coax & TP)

X     X      X    3Com 3C509 EtherLink III Parallel Tasking

                     Adapter - ISA (Coax, TP and Combo)

X                 3Com 3C523 EtherLink/MC (Coax & TP)

X                 3Com 3C529 EtherLink III Parallel Tasking

                     Adapter - MCA (Coax & TP)

X     X      X    3Com 3C579 EtherLink III Parallel Tasking

                     Adapter - EISA (Coax & TP)

X                 3Com 3C770 FDDILink-F for Optical, UTP & STP[1, 106, 107]

X                 COMPAQ NetFlex-2 ENET-TR Controller

X                 COMPAQ NetFlex-2 TR Controller

X                 COMPAQ NetFlex-2 DualPort ENET Controller

X            X    DEC DE201 EtherWORKS Turbo/TP

X                 Madge Smart 16/4 EISA Ringnode [1]

      X           National Semiconductor DP83932 (Sonic) Motherboard

                     Ethernet Controller on MIPS ARC/R4000 systems

X     X      X    Novell/Eagle Technology NE2000

X     X      X    Novell/Eagle Technology NE3200

X                 Thomas-Conrad TC4046 MCA Token Ring Adapter [1]

X                 Ungermann-Bass NIUps/EOTP

X                 Xircom Corporate Series CreditCard Ethernet

                     Adapter [1]

X                 Xircom Pocket Ethernet III Adapter [1, 112, 113, 114]

Technical Notes

---------------

   1   This device requires a driver from the \DRVLIB directory on

       the Windows NT CD-ROM, or the Windows NT Driver Library.

  106  This adapter is not supported on the Compaq ProSignia 500 and

       DeskPro M series computers..

  107  FDDI tested only.

  112  Not compatible with IBM Thinkpad 700.

  113  Non-bi-directional parallel ported machines may suffer

       performance degradation when the driver for this adapter

       is installed.

  114  The Toshiba 4700CS and 4800CT are not supported in Bi-directional

       mode with this adapter.

The Windows NT Driver Library is provided on the Windows NT CD-ROM in the

DRVLIB directory, as well as several locations for electronic transmission.

KBCategory: kbnetwork kbhw

KBSubcategory: nthw

Additional reference words: sms prodsms 1.00 1.10 1.10 Bloodhound Netmon


Err Msg: ...the Package Requires an NTFS Drive to Install...

Article ID: Q124959

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

A shared application package fails to be distributed to a NetWare server.

The DESPOOL.LOG file shows the following error:

   Server SMSDIST is not a Windows NT machine and the package requires an

   NTFS drive to install to, we'll skip this server.

CAUSE

=====

This problem occurs if the package source directory is on an NTFS partition

and has been shared as a Macintosh volume through Services for Macintosh.

If a long filename (LFN) is detected by the Systems Management Server

Scheduler service, while it compresses the package source directory, it

includes an attribute noting this package requires an NTFS partition in the

instruction file. When the SMS Despooler receives the package, it sees the

indication that the package requires an NTFS partition. Since there is no

NTFS partition on the NetWare server, it fails to install the package.

WORKAROUND

==========

Use Windows NT File Manager to remove the Macintosh volume from the SMS

package source directory or remove any long filenames from the package

source directory tree. Then resend and redistribute the package.

KBCategory: kbnetwork

KBSubcategory: ntmac ntfilesys ntinterop

Additional reference words: sms sfm prodsms 1.00 1.10


Why SMS Creates Macintosh Volumes for Shared Applications

Article ID: Q125016

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

When distributing a Systems Management Server shared application

package to an SMS Windows NT distribution server that is also running

Services for Macintosh, a Macintosh volume is created for the new share

with the same name as the Windows NT share. This occurs even though SMS has

no attributes for the shared package designating that the package supports

Macintoshes.

MORE INFORMATION

================

SMS can be used to distribute anything to a shared network directory, not

just shared applications for PC platforms. Because Macintoshes are a

supported platform, SMS creates a Macintosh Volume on any SMS Windows NT

distribution server that is also running Services for Macintosh.

This was designed so SMS can be used to distribute applications and data

files for Macintoshes even though SMS itself has no Program Group Control

application for the Macintosh platform. This allows SMS administrators to

support multiple platforms with one distribution point without creating

multiple packages and jobs.

Additional reference words: sms prodsms 1.00 1.10 SFM Mac Apple

KBCategory: kbnetwork

KBSubcategory: ntinfo ntinterop ntmac


Using the SMS Tracer Utility

Article ID: Q125452

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The Microsoft Systems Management Server allows you to trace the

actions performed by the SMS services. When tracing is enabled, each

service makes log entries for actions that it performs or errors that it

receives in a log file. The log files are ASCII text and can be viewed with

a text editor. However, SMS includes a Tracer utility that parses these log

files and presents them in a clearer, more user-friendly manner than plain

text viewing. Tracer also allows interactive viewing of the SMS log files

as the services are writing to them.

MORE INFORMATION

================

There are currently two versions of this utility, TRACER.EXE and

SMSTRACE.EXE

TRACER.EXE is a command line console-mode utility that reads changes made

to a text file in real time. This file is located the PSSTOOL\<arch>

directory on the SMS CD-ROM.

   Usage: tracer <path to one of the SMS log files>

SMSTRACE.EXE is a graphical user interface (GUI) multiple document

interface (MDI) version and is included in the SITE.SRV\<arch>.BIN

directory.

SMSTRACE.EXE allows you to customize the display by selecting options such

as columns, filtering, and ignore new lines. You can also Cut and Paste and

Print from SMSTRACE. SMSTRACE.EXE also allows viewing of several log files

simultaneously.

To install SMSTRACE as an icon in the SMS group:

1. Open the Systems Management Server group windows.

2. From the Program Manager File menu, select New.

3. Choose New Program Item. For the Command Line, enter:

      <drive>:\sms\site.srv\<arch>.BIN\SMSTRACE.EXE

   For the working directory, enter:

      <drive>:\sms\site.srv\<arch>.BIN

The SMS services log files are all located in the SMS\LOGS directory except

for the Site Configuration Manager log file SCMAN.LOG and the Bootstrap log

file BOOT.LOG.

The following is a list of the log files and the names of the component

that writes to them:

SMS Alerter                   ALERTER.LOG

Applications Manager          APPMAN.LOG

Bootstrap                     BOOT.LOG (in SMS root directory of Secondary

                                        Site Servers)

Inventory Dataloader          DATALODR.LOG

Despooler                     DESPOOL.LOG

Site Hierarchy Manager        HMAN.LOG

Inventory Agent               INVAGENT.LOG

Inventory Processor           INVPROC.LOG

LAN Sender                    LANSEND.LOG

RAS Sender                    RASSEND.LOG

RAS Sender (asynchronous)     RASSYNC.LOG

RAS Sender (ISDN)             RASISDN.LOG

RAS Sender (X.25)             RASX25.LOG

SNA Sender                    SNASEND.LOG

SNA Sender (Batch)            SNABATCH.LOG

SNA Sender (Interactive)      SNAINTER.LOG

SNA Receiver                  SNARECV.LOG

Maintenance Manager           MAINTMAN.LOG

Package Command Manager       PACMAN.LOG

SMS Scheduler                 SCHED.LOG

Site Configuration Manager    SCMAN.LOG (in root directory of SMS drive)

Site Reporter                 SITEREP.LOG

SMS Executive                 SMSEXEC.LOG

SMS Administrator             UI.LOG

For further information on tracing SMS services, please refer to the SMS

"System Guide," Appendix J.

Additional reference words: sms prodsms 3.50 1.0 tshoot troubleshooting

KBCategory: kbnetwork

KBSubcategory: nthowto ntutil


Windows NT Account Requirements for SMS Site to Site Com.

Article ID: Q125453

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

A destination site account is required when you create a Systems Management

Server site address. This article explains what destination site

account rights are required.

MORE INFORMATION

================

When one SMS site needs to communicate with another, it does so by writing

files to the destination site's SMS_SITE share DESPOOL.BOX\RECIEVE sub-

directory. The account used to write to this share must have at least

CHANGE rights to this share and directory. For NetWare and other network

operating systems (NOSs), CHANGE rights equates to CREATE/DELETE and

READ/WRITE.

Cross site addressing can be setup with connection accounts that do not

have administrator rights on the destination system. This helps eliminate

security concerns when using administrative accounts or configuring trust

relationships.

To accomplish this, at each site, create an address that contains the full

domain\username for the account created at the destination site. (This does

not require a trust relationship.) This allows the LAN_SENDER to do the

equivalent of a NET USE \\<server>\SMS_SITE /USER:domain\username command

when connecting to another site.

For example, given the following two sites:

Site:         BPC              VMT

Server:       \\CNSSMS         \\VEMONT

Domain:       PSS-BP           VERMDOMAIN

User account: PSS-BP\SMSSITE   VERMDOMAIN\SMSCONN

At the BPC site, create the address for the VMT site that contains the

VERMDOMAIN\SMSCONN account. At the VMT site, create an address for the BPC

site with the PSS-BP\SMSSITE account.

KBCategory: kbnetwork

KBSubcategory: nthowto ntdomain ntconfig

Additional reference words: sms prodsms 1.00 1.10


SMS Service Account Requirements for Different Configurations

Article ID: Q125454

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The services running on a Systems Management Server site require

various administrator-type rights on all site server systems maintained by

SMS. This article describes what rights are required for the supported

configurations.

MORE INFORMATION

================

The SMS service account requires administrative rights on each SMS

maintained server. SMS creates new shares and directories on each installed

server in order to populate them with files.

On Windows NT and OS/2 servers, SMS installs and starts the Inventory Agent

service. On Windows NT servers, SMS also installs the Package Command

Manager. To install these services, the SMS Windows NT service account must

have the right to logon as a service at each Windows NT server.

For a single Windows NT domain SMS site, the SMS service account must be at

least a member of the Local Administrators group and have right to logon as

a service. If OS/2 servers are added to the NT domain, the SMS service

account must be in the Global Administrators group

If an OS/2 domain is added to an existing SMS site, create an identical SMS

user account in the Administrators group on the OS/2 domain (with the same

password). This is necessary because OS/2 does not understand the concept

of Local groups.

If a NetWare domain is added, each NetWare server must have a supervisor-

equivalent user account identical to the Windows NT SMS account.

If you add a NT domain to an existing site, create a one way trust

relationship from the new domain to the domain that contains the SMS

service account. Once the trust relationship is active, add the SMS service

account to the Local Administrators group in the new domain and give the

account the right to Logon As A Service. Make sure that you use the full

<trusted domain>\<username> syntax. This ensures that the proper domain

validates the account through the trust relationship.

When connecting sites together in a hierarchy, no administrative rights are

not required, and you don't have to create a trust relationship between the

sites. The connection address for the respective sites must include the

<destination domain>\<username> of the other site, and the account must

have Change access to the SMS_SITE share.

KBCategory: kbnetwork

KBSubcategory: ntinfo ntdomain ntinterop

Additional reference words: sms prodsms 1.00 1.10


SMS Administrator Unable To Retrieve Machine List

Article ID: Q125487

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

After dumping the Systems Management Server database and transaction

log to a dump device and then restoring it to a different database and log

device, either on the same SQL Server or a different one, the SMS

Administrator cannot retrieve the list of machines in a domain and the

following errors appear in the Data Loader log file, DATALODR.LOG:

   CMachine::FindMachine - Searching for matching Identification group info

   CMachine::FindMachine - Query Execution failed

These errors also appear in the Hierarchy Manager log file, HMAN.LOG:

   {818} ERROR SQL: General SQL Server error:

                    Check messages from the SQL Server.

   {825} INFO SQL: Can't allocate space for object 'Syslogs' in database

                  'xxx' because the 'logsegment' segment is full. If you

                  ran out of space in Syslogs, dump the transaction log.

                  Otherwise, use ALTER DATABASE or sp_extendsegment to

                  increase the size of the segment.

   (where xxx is the SMS database name)

NOTE: Error 825 above is the same as the SQL Error 1105 which is discussed

in Chapter 2 (Error Messages) on pages 36-40 of the "Microsoft SQL Server

Troubleshooting Guide."

CAUSE

=====

These errors occur because the Transaction Log for the SMS Database is full

and SQL Server can no longer log transactions to it. When SMS originally

created the database it enables the Trunc. Log on Chkpt. option. When the

database is dumped and then restored to a new device, that option is not

set by default, therefore the Transaction Log is never truncated and fills

up after a while.

RESOLUTION

==========

1. Dump the Transaction log by doing the following:

   a. Create a Dump Device. See pp. 23-25, 'Using Devices' section of the

      "Microsoft SQL Administrator User's Guide" for instructions on

      creating devices.

   b. Dump the Transaction log with the No Log option. See pp. 77-79,

      'Backup and Recovery' section of the "Microsoft SQL Administrator

      User's Guide" for instructions on dumping a transaction log.

2. Set the option Trunc. Log on Chkpt. for the SMS database. See pp. 36,

   37, 'Using Databases' section of the "Microsoft SQL Administrator User's

   Guide" for instructions on setting database options.

For further information on managing the Transaction Log please see

Chapter 4, 'Transaction Log Management' of the "Microsoft SQL Server

Troubleshooting Guide."

Additional reference words: sms 1.00 1.10 prodsms SMS_HIERARCHY_MANAGER

SMS_INVENTORY_DATA_LOADER

KBCategory: kbenv kberrmsg

KBSubcategory: ntconfig ntinterop


Creating the SMS Administrator Log File UI.LOG

Article ID: Q125668

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

SMS Administrator can log its activities to a log file (a process known as

tracing). By default, tracing is turned on for SMS Administrator, but the

log file does not get created until SQL Server tracing is turned on.

MORE INFORMATION

================

To turn on SQL Server tracing:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT or Microsoft SMS to

correct them. Microsoft cannot guarantee that any problems resulting from

the use of Registry Editor can be solved. Use this tool at your own risk.

1. Start Registry Editor (REGEDT32.EXE) and select the HKEY_LOCAL_MACHINE

   subtree.

2. Go to the following subkey:

      \SOFTWARE\MICROSOFT\SMS\TRACING

3. From the parameter list, select SqlEnabled.

4. From the Edit menu, choose DWORD.

5. In the Data field, change the value from 0 to 1 and then choose OK.

6. To verify that tracing is enabled for the SMS Administrator User

   Interface, go to the following HKEY_LOCAL_MACHINE key:

      \SOFTWARE\MICROSOFT\SMS\TRACING\SMS_USER_INTERFACE

   The parameter Enabled should be set to 1.

7. Exit and restart SMS Administrator (SMS.EXE).

A UI.LOG file is created in the SMS\LOGS directory. The log file can be

viewed using SMS Tracer (SMSTRACE.EXE). For more information on using SMS

Tracer, query on the following words here in the Microsoft Knowledge Base:

   tracer

KBCategory: kbnetwork

KBSubcategory: ntconfig ntutil

Additional reference words: sms prodsms 1.00 1.10


SMS Server Selection Using Appstart

Article ID: Q125931

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

You can run shared applications from Systems Management Server

version 1.0 by using the Appstart program to select an appropriate

application server. There are three ways Appstart locates a server (in

order):

 - Existing Share

 - Existing Server

 - Random

Existing Share

--------------

If an existing connection to a needed share exists, Appstart piggy-backs or

reuses the existing share connection. Appstart assumes that a previous

attempt to connect was made, and, during that attempt, these same rules

were followed. This is done to maximize load balancing on the initial

connection, and minimize the total number of distinct connections a client

makes.

Existing Server

---------------

If there is already a session established with the server providing the

desired share and a connection to the share does not already exist,

Appstart connects to this server and share. Quite often a local connection

will exist to the SMS Windows NT logon server (and SMS_SHR) that

authenticated the logon. For this reason, the majority of Appstart requests

will go to a Windows NT (or LAN Manager) domain controller local to the

client computer.

Random

------

If no shares or servers are connected that have the desired resources,

Appstart will randomly pick from the list in the network accounts database

(NAD).

Random selection is rarely performed after either the existing share or

server methods have been used. They are oriented to the local subnet, while

the random method acts as a safety net. The random selection will most

likely be made on the local subnet, but it cannot be guaranteed in SMS

version 1.0. That is why the existing share and server methods are

attempted first. To ensure a local connection, you can add a NET USE

command to a local distribution server in the logon script. Then you

guarantee a session because Appstart will always check for an existing

server before choosing randomly.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: sms prodsms 1.00 1.10


LMSCRIPT.PIF and the SMSLS logon script

Article ID: Q126159

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

The SMSLS logon script stop responding (hangs) when used with some Windows

3.1 and Windows for Workgroups 3.1 or 3.11 configurations.

CAUSE

=====

When a Windows system logs on to a network, LMSCRIPT.EXE is run on the

client to parse and run the logon script. Under some Windows

configurations, applications run from the logon script can cause

LMSCRIPT.EXE to hang. This problem usually occurs due to a timing problem

with the background and foreground processes.

Since LMSCRIPT.EXE is an MS-DOS-based program, a LMSCRIPT.PIF file is used

to describe it's required environment. Other drivers or processes running

under Windows can take processor cycles away from LMSCRIPT.EXE. This can

hang the LMSCRIPT process or cause applications that are running within the

logon script to fail.

RESOLUTION

==========

You may be able to reduce or eliminate this problem by modifying the

\WINDOWS\SYSTEM\LMSCRIPT.PIF file or by creating a batch file:

Modifying LMSCRIPT.PIF

----------------------

1. Run PIF Editor (PIFEDIT.EXE) and open \WINDOWS\SYSTEM\LMSCRIPT.PIF.

2. Ensure the Execution Background check box is selected. It should be by

   default.

3. Select the Execution Exclusive check box.

4. Save your changes and quit PIF editor.

If this does not resolve the problem, modify the process priorities:

1. Run PIF Editor (PIFEDIT.EXE) and open \WINDOWS\SYSTEM\LMSCRIPT.PIF.

2. Choose Advanced, and then increase the Background Priority and

   Foreground Priority values.

3. Save your changes and quit PIF editor.

Creating Batch File

-------------------

Create a batch file called NTLOGON.BAT with the following entries:

   Net Time

   Net Use <network drive>: \\<ServerName>\<SMS Share>

   <network drive>:

   SMSLS.BAT  (SMSLS logon script)

   <local drive C>:

KBCategory: kbnetwork

KBSubcategory: nthowto

Additional reference words: sms prodsms 1.00 1.10 wfw wfwg program

information

file


Different Language Site Reporting Not Supported in SMS

Article ID: Q126351

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

You cannot report from one site to another using different language

versions of Systems Management Server version 1.0. For example, a

German SMS site cannot report to a parent French SMS site.

CAUSE

=====

Language strings are localized and cannot be accurately converted by the

receiving site. Converting the language strings (used in packages,

comments, events, etc.) requires single-byte to multi-byte conversion.

WORKAROUND

==========

To work around this problem, configure the site hierarchies as follows:

1. Use the same language version of SMS.

2. Configure the code-page and country settings to appropriate languages.

NOTE: In this situation, all needed event codes, error codes, etc.,

required by the system, are presented in a consistent way without any

conversion.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management

Server versions 1.0 and 1.1. We are researching this problem and will post

new information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig ntdomain

Additional reference words: sms prodsms 1.00 1.10 hierarchy


Troubleshooting SMS Inventory Collection Problems

Article ID: Q126642

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

This article describes several SMS inventory collection problems, and what

you can do to resolve them.

MORE INFORMATION

================

The Client Hangs when you Run Inventory Agent

---------------------------------------------

1. See if you have a C:\SMSSAFE.TMP file. This file lists each test that

   was run. The last test listed indicates what test hung the client.

   Inventory Agent deletes this file if it completes normally.

2. Set the SMSLS=1 environment variable. This turns on the SMSLS.BAT file's

   VERBOSE mode to help you determine where the Inventory Agent hung the

   client. VERBOSE mode echoes all output to the screen.

3. Once you determine where the Inventory Agent is hanging, remove or

   reconfigure the suspect component and re-run the inventory again. Once

   the problem has been narrowed down to a particular configuration, report

   the results to Microsoft Product Support Services (PSS).

You Run Inventory Agent On a New Client But The Inventory Doesn't Show Up

In The Database

-------------------------------------------------------------------------

1. Look at the CurrentLogonServer entry in the hidden C:\SMS.INI file to

   determine what logon server SMS is reporting the inventory to.

2. For MS-DOS, Windows, Windows for Workgroups, and Windows NT clients,

   check the \\<logon server>\SMS_SHR\INVENTRY.BOX directory for a .RAW

   file generated by the client. For Macintosh and OS/2 clients, check the

   \\<logon server>\SMS_SHR\ISVMIF.BOX directory for a *.MIF file. If

   multiple files exist, look for one with a recent time stamp. Display the

   text contents of the file and look for a SMS ID that matches the SMS

   Unique ID entry in the C:\SMS.INI file. Confirm that the Inventory Agent

   did write this file.

   NOTE: The .RAW file has a binary header and a text detail area. The .MIF

   file is a text file.

3. If the .RAW or .MIF file does not exist, check for a permission or

   connection problem. The client's Inventory Agent may not be able to

   connect and write to this location.

   If this file does exist then Inventory Agent is working properly. See

   the next section to determine if one of the SMS Site services is

   suspect.

Inventory Agent Runs Normally On The Client But The Hardware Inventory Is

Not Updated

-------------------------------------------------------------------------

1. Confirm that the hardware inventory collection interval has expired for

   the client. Check the current LastHardwareScan value in the SMS.INI

   file, add the inventory collection interval configured for the SMS site,

   and compare the resulting date against the clients current system clock

   date. SMS uses this procedure to determine when it needs to collect

   hardware or software inventory.

   For more information on the inventory process, see Appendix C of the

   "SMS Administrator's Guide."

2. The SMS Maintenance Manager service is responsible for collecting the

   *.RAW and *.MIF files from the logon servers and transferring them to

   the SMS Site server. These files are put in the

   \SMS\SITE.SRV\INVENTRY.BOX or ISVMIF.BOX directory, depending on the

   client type. If the files do not arrive during the Maintenance Manager

   watchdog cycle, check the \SMS\LOGS\MAINTMAN.LOG file for errors that

   occurred while attempting to connect to the logon server or transferring

   files to the site server.

3. After these files reach the Site server, the SMS Inventory Data

   Processor service processes them and placing the output in the

   \SMS\SITE.SRV\DATALOAD.BOX\DELTAMIF.COL directory. If the files are not

   removed from the source directories or do not appear in the destination

   directory, check the \SMS\LOGS\INVPROC.LOG file for errors.

4. After the output is written to the ..\DELTAMIF.COL directory, the SMS

   Inventory Data Loader copies the data in these files to the SQL

   database. If the files are not removed from this directory, or do the

   data does not appear in the SQL Database, check the

   \SMS\LOGS\DATALODR.LOG file for errors.

5. Use the SMS Services Manager to stop the SMS services while you

   troubleshoot this problem. After you examine a file at one point in the

   process, start the service that will process that file. This allows you

   (the administrator) time to look at the file before it is deleted, and

   the results get sent to the next point in the system.

6. Log file entries report both the SMS event id and the Windows NT

   error code. Convert the Windows NT error code to text using ERROR32 to

   determine what the actual error is.

   ERROR32 can be copied from the \PSSTOOLS directory on the SMS CD.

Inventory In The Database Is Corrupt Or Incorrect

-------------------------------------------------

1. Run Inventory Agent  on the client and check the .RAW or .MIF file

   (at the locations mentioned above) generated by the client. Compare the

   inventory reported with the known configuration of the client. If the

   .RAW or .MIF file is correct on the logon server, check the file again

   after it is moved to the site server, and again after the SMS Inventory

   Processor has created the delta .MIF in the ..\DELTAMIF.COL directory.

2. If corruption occurs in the .RAW or .MIF file on the logon server, it is

   usually caused by the Inventory Agent. If this happens, enable the

   Inventory Agent verbose mode and watch the output to determine where the

   problem occurs.

3. If the .RAW or .MIF files on the SMS Site server are corrupted, check

   the associated service log files for error or warning messages. These

   may indicate network or file system problems that are causing the

   corruption. The SMS Data Loader service does not usually parse the MIF

   file and put the file in the DATALODR.BOX\BADMIFS directory for the

   administrator to review.

Software Inventory Is Not Collected Or Updated

----------------------------------------------

1. Confirm that the software inventory collection interval has expired. Use

   the same procedure as above ("Inventory Agent Runs Normally On The

   Client But The Hardware Inventory Is Not Updated," step number one) but

   use the value in LastSoftwareScan to confirm the software collection

   interval.

2. Confirm that a compiled software package rules file (PKG_16.CFG) exists

   on the logon servers. This file specifies what software inventory is

   supposed to be collected from the SMS client by Inventory Agent. Check

   Appendix C of the "SMS Administrator's Guide" for details on how

   PKG_16.CFG is created and placed on the logon servers.

3. Check the PACKAGE.RUL file and confirm that it has the proper software

   package rules. This file is compiled to create the PKG_16.CFG file.

   Refer to Appendix C for the location.

4. Check the resulting .RAW or .MIF file created by the Inventory Agent.

   Software inventory and collected files are appended to the end of the

   hardware inventory section.

5. Carefully check your Software Package inventory rule properties

   (created using SMS Administrator. Many software inventory problems

   occur due to a bad rules configuration.

Machine Inventory Appears To Change And Contains Entries From Another

System

---------------------------------------------------------------------

This problem usually occurs when two clients have mistakenly been

configured with the same SMS ID. Check the machine name, logon name, or

other unique identifier. If these change, you should be able to track down

which machines have the same SMS ID.

To correct this problem, delete the SMS.INI file from one of the systems

and run SMSLS.BAT again on that system. This assigns a new SMS ID to the

affected system a creates a new entry in the SQL database. If this problem

occurs on several systems, check all the \\<logon server>\SMS_SHR\SMSID

directories for the site and confirm that the current .UID file contains a

unique ID to be assigned to the next new SMS client configured by the

system.

KBCategory: kbtshoot

KBSubcategory: nthowto

Additional reference words: sms prodsms 1.00 1.10 trouble shoot trouble-

shoot

tshoot shooting


Troubleshooting SMS Workstation Package Installations

Article ID: Q126644

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

This article describes several SMS workstation package problems, and what

you can do to resolve them.

MORE INFORMATION

================

The Workstation Package Has Been Created And Distributed With No Errors

But The Item Never Shows Up In The Pending Folder Of The Destination

Systems Package Command Manager

-----------------------------------------------------------------------

1. Check the package workstation properties and confirm that the Supported

   Platforms pick list has the destination systems platform selected. Using

   SMS Administrator, check the PC Properties for the destination system

   and confirm that SMS has the correct platform type listed for the target

   system.

2. Get the CurrentLogonServer location and the Unique SMS ID from the

   hidden C:\SMS.INI file. Using these, check the

   \\<logonserver>\SMS_SHR\PCMINS.BOX directory for a file with the name

   <Unique SMS ID>.INS. If this file does not exist, the instruction file

   for this system is missing from that logon server. The SMS Maintenance

   Manager is responsible for placing these files on the logon servers.

   Check the \SMS\LOGS\MAINTMAN.LOG file for errors that may have occurred

   when this file was replicated from the Site server to the logon server.

   Check Appendix C of the "SMS Administrator's Guide" for details.

3. If the <SMS ID>.INS file exists on the logon server, use PCMDUMP to

   display it's contents. Careful examination of the Display Date and

   Expiration Date fields may indicated why the package has not been

   displayed on the destination system.

   For more information on using PCMDUMP to display the contents of an .INS

   file, see Knowledge Base article Q123499.

   PCMDUMP can be copied from the \PSSTOOLS directory on the SMS CD.

Mandatory Package Does Not Execute On Time Or Does Not Execute At All

---------------------------------------------------------------------

1. Use PCMDUMP to check the value of the Install By Date field. Compare

   this date/time stamp with the destination system current date/time

   The system time must be on or after the Install By Date before PCM will

   run the package.

2. If the package is supposed to run unattended on a Windows NT system that

   has no user logged on locally, ensure that the follow conditions are

   met:

    - The package must not use console I/O. This means that nothing can

      print to the screen or require keyboard or mouse input. The PCMSVC

      service is responsible for executing System Background installation

      tasks and has no access to the local console for I/O. Any console I/O

      in this type of package will fail.

    - Confirm that both Automated Command Line and System (Background) Task

      are selected in the package's workstation properties.

    - Confirm that PCM service user account for the Windows NT client has

      sufficient rights to execute the job on the system. On a Windows NT

      system in a secure environment, it is possible keep the PCM

      service from accessing particular directories or other Windows NT

      system objects, causing the installation to fail.

The Package Fails To Execute Properly Or Does Not Execute At All

-----------------------------------------------------------------

1. Ensure that the package source directory and the package command line

   have been configured correctly:

   a. Ensure that the command line points to a valid executable.

   b. Ensure all directory path references are relative to the package

      source directory and are not absolute directory references. For

      example, to execute SETUP.EXE in the INSTALL directory of a package,

      use a relative path in the command line (INSTALL\SETUP.EXE). Do not

      use an absolute directory path reference

      (\\SMSSVR\D$\PACKAGE1\INSTALL\SETUP.EXE).

2. Manually run the package command line using PCMDUMP to determine what

   distribution servers contain the package. Connect to one of the listed

   server shares and change to the directory listed for the package. Run

   the packages command line from this directory. Look for errors that

   reference incorrect paths or missing files.

3. Confirm that the package directory contains a mirrored image of the

   original source directory specified when the package was created. Except

   for the top level directory name, both directory trees should be

   identical. If they are not, check the DESPOOL.LOG file for any errors

   that may have occurred while the directory structure was being created

   on the distribution server.

4. If the distribution directory does not exist on the servers, check the

   \SMS\LOGS\DESPOOL.LOG file on the SMS Site server for errors referring

   to the creation and file population of this directory.

The Package Instruction Files Never Arrive Or Never Get Updated In The

<Logon Server>\Sms_Shr\Pcmins.Box Directory

----------------------------------------------------------------------

1. Check the SMS Site server \SMS\SITE.SRV\MAINCFG.BOX\PCMDOM.BOX\<clients

   domain>\ directory. Confirm that an instruction file exists for the

   client and that it has been updated since the package was distributed.

   Use PCMDUMP if you are unsure of the status or contents of this file.

2. If this file exists and has been updated, check the

   \SMS\LOGS\MAINTMAN.LOG file for any errors that may have been logged

   when SMS attempted to transfer this file to the logon servers. The SMS

   Maintenance Manager will replicate these files at a regular watchdog

   interval. Use the log file to confirm that this watchdog cycle has

   actually taken place and that the logon server in question was one of

   its targets.

3. If this file does not exist, or has not been updated with the current

   package, check the DESPOOL.LOG file for any error referring to the

   creation or distribution of instruction files.

KBCategory: kbtshoot

KBSubcategory: nthowto

Additional reference words: sms prodsms 1.00 1.10 trouble shoot trouble-

shoot

tshoot

shooting


SMS Unique ID (SMSID) Allocation

Article ID: Q127052

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Every client in a Microsoft Systems Management Server site has a

unique identification called an SMSID. This is derived from the Unique

ID (UID) file on a logon server. SMS Server performs several functions

to ensure uniqueness within the site and across sites. This article

discusses these functions in detail.

MORE INFORMATION

================

SMS Server performs the following functions to ensure uniqueness within the

site and across sites:

 - To ensure uniqueness (in the event of a site de-installation), the last

   UID range is saved from the Registry by SMS Server Setup and placed into

   the site server's SMS.INI file. If a site is reinstalled later, this

   range is restored to the Registry, thus the site does not allocate any

   duplicate SMSIDs. If the SMS.INI is removed from the site server

   following de-installation, each client should be de-installed and

   reinstalled.

 - It is possible to reinstall the site and assure no duplicate SMSIDs

   are allocated. As the last allocated UID range is stored in the

   Registry, the Administrator, in lieu of de-installing and reinstalling

   client computers, can place a sufficiently high value into the Registry

   to assure duplicate SMSIDs are not issued. The Registry entry is stored

   as a REG_SZ type in the following key:

      HKEY_LOCAL_MACHINE

       \SOFTWARE

        \Microsoft

         \SMS

          \Components

           \SMS_MAINTENANCE_MANAGER

            \Next SMS Unique ID

 - Assuming the site is installed, normal processing begins. In creating

   the actual UID file, the SMSID is managed in several parts. The first

   three characters are always the site code of the creating site. The next

   two characters represent the UID range and allows each logon server to

   own a range of SMSIDs to allocate to clients. No two logon servers will

   have the same range. The last three characters are sequentially

   incremented each time an SMSID is allocated by a client. The numeric

   range of the SMSID is expanded by including the A to Z characters as

   extensions of 0 to 9 range. This provides 36 values instead of just 10,

   and allows for the following maximum capacities:

    - Unique site codes: 36^3 =     46,656

    - Unique logon server ranges:

      - Assuming not more than 44,065 clients per logon server:

           36^2 =   1,296

      - Assuming more than 44,065 clients per logon server is more

        complicated because each doubling of 44,065 SMSIDs per server

        reduces the available ranges by half.

      Unique SMSIDs per logon server (depends on number of logon servers

      because values between the two bounds of 1 and 1,296 vary the number

      of available ranges which can be allocated upon the expiration of a

      prior range):

      - Assuming a single logon server: 36^5 =       60,466,176

      - Assuming 1,296 logon servers:   36^4 =        1,679,616

    - Unique SMSIDs (per site):   36^5 =       60,466,176

    - Unique SMSIDs (total):      36^8 =   78,364,164,096

 - When each new client attempts to allocate an SMSID, it takes the current

   name of the UID file as its own SMSID and attempts to increment the name

   of the UID file to the next value. Each client does this in turn (it is

   not controlled by the site server). Only the allocation of new ranges is

   managed by the site server. When a sharing violation or other errors

   occur, the client will retry 30 times, and indicate a # character on the

   screen for each retry. The UID file is maintained in a single location,

   SMS_SHR\SMSID\<next_smsid>.UID.

 - The Maintenance Manager compares each logon server's UID range to

   evaluate if a new range needs to be issued. If the current value of the

   SMSID exceeds "*****Y00" (44,065 SMSIDs), then a new range is allocated

   to the logon server. This is a rather proactive threshold (2,591 SMSIDs

   early), intended to make sure the range never actually expires even when

   Maintenance Manager is set for the slow response setting in site

   properties. This provides room for 44,065 computers per range, and will

   have a minor effect on the architectural limitations described above.

 - If a computer moves from one site to another by virtue of three

   successive logons to a new site's domain, then the original SMSID for

   the client is used by the new site database. This is by design. The

   SMSID should not be altered once it is allocated. The

   de-install/reinstall procedure should be used when a SMSID change is

   desired on a client.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 1.10 sms


Installing SMS Client to Drive Other Than Most Free Disk Space

Article ID: Q127072

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

By default, Microsoft Systems Management Server 1.0 client software

is installed on the drive with the most amount of free disk space. This

article discusses the steps necessary to allow SMS client software (Windows

NT, MS-DOS, and OS/2) to be installed on a drive other than the drive with

the most free disk space.

MORE INFORMATION

================

For Windows NT and MS-DOS Clients

---------------------------------

1. Make a backup copy of the SMSLS.BAT file.

2. Use a text editor such as Notepad to modify the SMSLS.BAT file.

   For login scripts and manual execution of SMSLS.BAT, find the

   following and add the appropriate switches according to the

   syntax below.

   Login Scripts:

      CLI_DOS.EXE -pa:/<another drive>:

      CLI_NT.EXE -pa:/<another drive>:

   Manual Execution of SMSLS.BAT:

      CLI_DOS /<another drive>:

      CLI_NT /<another drive>:

For OS/2 Clients

----------------

1. Make a backup copy of the SMSLS.CMD file.

2. Use a text editor such as Notepad to modify the SMSLS.CMD file.

   For login scripts and manual execution of SMSLS.CMD, find the

   following and add the appropriate switches according to the

   syntax below.

   Login Scripts:

      CLI_OS2.EXE -pa:/<another drive>:

   Manual Execution of SMSLS.CMD:

      CLI_OS2 /<another drive>:

NOTE: If the above additions are not made to the SMSLS.BAT or SMSLS.CMD

file, only manual execution of the file works.

KBCategory: kbnetwork

KBSubcategory: nthowto ntsetup

Additional reference words: prodsms 1.00 1.10 sms


Systems Management Server: Error 5016 When Running INVMac

Article ID: Q127929

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

-------------------------------------------------------------------------

SYMPTOMS

========

When you run INVMac (Inventory Agent program for Macintosh client

computers) for Microsoft Systems Management Server version 1.0, the

following error message appears:

   Error 5016 in file shicsetting.cp

CAUSE

=====

This error occurs when INVMac on the Macintosh client computer is not able

to find the server.

RESOLUTION

==========

To correct this problem:

1. Ensure the information in the [AppleServers] section of the SMS.INI

   file on the Macintosh client computer is correct as follows:

      [AppleServers]

      CurrentLogonServer=<zone>@<server name>

      Server1=<zone>@<server name>

2. Ensure that the DOMAIN.INI file contains the correct server information.

   If the SMS.INI file does not exist and the DOMAIN.INI file is located in

   Microsoft SMS system folder, then the Macintosh client computer was

   installed before the server updated the DOMAIN.INI file.

3. If a Macintosh client computer is not using Microsoft authentication,

   ensure that the properties of the SMS_SHR Macintosh volume allows Guest

   access. To do this, select "View/Modify Volumes" from the MacFile menu

   of the Windows NT File Manager. Select SMS_SHR and choose Properties.

   Ensure that the "Guest can use this volume" option is selected.

4. Ensure that the SMS Server is operational.

5. Ensure the network is operational.

6. Reset the Macintosh network connection in the Network Control Panel of

   the Macintosh client computer.

7. Ensure that the SMS Logon Server is running Services for Macintosh.

KBCategory: kbnetwork

KBSubcategory: ntconfig ntdomain

Additional reference words: prodsms 1.00 1.10 sfm mac SMS sms "No Server"

System


Unrecognizable Characters Displayed Using Remote Control

Article ID: Q127949

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

-------------------------------------------------------------------------

SYMPTOMS

========

When you take remote control of a client computer from Help Desk in

Microsoft Systems Management Server version 1.0, unrecognizable

characters are displayed when you start a third-party 3270 terminal

emulation program for Windows.

CAUSE

=====

This problem occurs when a font used on the client computer is not

available in the Windows NT system.

RESOLUTION

==========

To correct this problem, use a different font that is available on the

Windows NT system or install the same font in Windows NT.

The third-party product discussed here is manufactured by a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

KBCategory: kb3rdparty

KBSubcategory: nt16ap

Additional reference words: prodsms 1.00 1.10 sms


Err Msg: Remote Control Agent Cannot Load IDIS_IPX.DLL

Article ID: Q128927

-------------------------------------------------------------------------

The information in this article applies to:

- Microsoft Systems Management Server versions 1.0 and 1.1

-------------------------------------------------------------------------

SYMPTOMS

========

When you start Remote Control on a NetWare client running Windows version

3.x in Microsoft Systems Management Server version 1.0, the following error

message appears:

   Remote Control Agent cannot load idis_ipx.dll

CAUSE

=====

This problem occurs if one or all of the following files are not present

in the NetWare client computer:

   NWNETAPI.DLL

   NWCALLS.DLL

   NWIPXSPX.DLL

These files are included with the NetWare client software and are available

in the Novell public forum on CompuServe. If you install and run a NetWare

client in MS-DOS, the three files above are not required. NWCALLS.DLL and

NWIPXSPX.DLL are installed for NetWare clients running Windows version 3.x.

RESOLUTION

==========

To correct this problem, install the NWNETAPI.DLL file on the NetWare

client.

To allow Microsoft Systems Management Server to install the file, place the

file in the SITE.SRV\MAINCFG.BOX\CLIENT.SRC\X86.BIN directory on the site

server. The Maintenance Manager will replicate the file to all NetWare

logon servers. The file will be installed to the MS\SMS\BIN directory on

all NetWare clients when users run Client Setup (either manually or through

their login script).

The NetWare products discussed here are manufactured by Novell, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

KBCategory: kb3rdparty kbinterop

KBSubcategory: ntconfig

Additional reference words: 1.00 1.10 sms prodsms


Functional Description of SMSWORK

Article ID: Q129602

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Systems Management Server uses SMSWORK to do any work that was queued by

Systems Management Server before the computer was rebooted. This allows

Systems Management Server to execute a program before anything else has

been started. This is usually done to reconfigure an operating system

during an upgrade, but could be used for anything that needs to be

accomplished during start up.

MORE INFORMATION

================

SMSWORK is run from CLIENT.BAT, which is called from the AUTOEXEC.BAT file

(as setup by Systems Management Server during the SMS configuration

process). SMSWORK looks in the C:\SMS.INI file for the PendingWork key and

executes any command found there. Once this command is executed, the line

is cleared so the command is not executed the next time the system is

started.

SMS 1.0a Release Notes on SMSWORK

---------------------------------

SMS uses a program called SMSWORK.EXE to queue work to be done after a

system reboot. SMSWORK is used to do any general work that cannot be done

at the time a command is executing, for instance the Operating System Setup

Encapsulation programs use SMSWORK to remove or replace files and

directories at reboot time.

SMSWORK.EXE looks in the SMS.INI file for the section [SMS Work] and the

key PendingWork. The key value is a single command line or a series of

comma-delimited command-lines, for example:

PendingWork=Echo Please wait while SMS removes an SMS created temp

directory, DEL c:\SMSTMP SMSWORK is invoked by CLIENT.BAT on MS DOS,

Windows, and OS/2 SMS clients. On Windows NT computers SMSRUN32 performs

these functions.

KBCategory: kbnetwork

KBSubcategory: ntgeneral

Additional reference words: prodsms sms 1.00 1.10


Using Systems Management Server Remote Control over a RAS Server

Article ID: Q129603

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you use Systems Management Server to remotely control a client through

a Windows NT Remote Access Service (RAS) server, this error message

appears:

   Unable to locate <computer name>

where <computer name> is the computer name of the remote client.

CAUSE

=====

Systems Management Server cannot access the remote client because the RAS

Service is not configured to allow listens to be posted for all NetBIOS

names.

By default, the RAS Service will only allow NCB.LISTENs to be posted for

Server and Messenger service NetBIOS names. These names consist of the 15

character NetBIOS computer name with a 16th character that is ASCII 0x00

for Server, or 0x03 for Messenger. This allows most file and print services

to operate and reduces the resource requirements for the RAS service.

When the Systems Management Server Remote Control client software is

initialized during startup, it posts NCB.LISTENs that have the NetBIOS

computer name and the following values for the 16th character:

   Hex    ASCII   Description

   ----   -----   --------------------------------------

   0x43   C       SMS Administrators Remote Control Tool

   0x44   D       SMS Clients Remote Control

   0x45   E       SMS Clients Remote Chat

   0x46   F       SMS Clients Remote Transfer

When the Systems Management Server Administrators Tool attempts to remotely

control a client, it first broadcasts a NetBIOS Name Query against the

client with the NetBIOS name formatted as described above.

For the RAS Server to forward the NetBIOS Name Query to the client, it must

post each of these NetBIOS names. Otherwise, the client cannot respond and

the Administrators Tool fails to find the client.

RESOLUTION

==========

The RAS server needs to be configured to allow all NCB.LISTENs to be posted

before remote control will work properly.

To do this, use the registry editor to modify the RAS NetBIOSGateway

Parameter.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of

Registry Editor can be solved. Use this tool at your own risk.

Go to the following key in the HKEY_LOCAL_MACHINE subtree:

   SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters\NetBIOSGateway

Change the value of RemoteListen from 1 to 2.

This will enable RAS to post NCB.LISTENs for all NetBIOS names. Once this

is done, stop and restart the RAS Services for the change to take effect.

For more information, see Appendix C of the Windows NT Server "Remote

Access Service" or Knowledge Base articles Q97599, Q99145, and Q110315.

Additional reference words: prodsms 1.00 1.10 sms

KBCategory: kbenv kberrmsg

KBSubcategory: nthowto ntras ntnetserv


Changing From Auto to Manual Logon Scripts In SMS

Article ID: Q130184

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SYMPTOMS

========

When you use Systems Management Server to automatically configure user

logon scripts, and then disable the feature and set up scripts manually,

the Site Config Manager removes it's script files from the primary domain

controller's REPL$\SCRIPTS directory.

CAUSE

=====

Site Config Manager records on a domain basis if it has previously modified

logon scripts at any time, even if the auto-script feature is currently

disabled.

WORKAROUND

==========

To work around this problem, modify the registry:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of

Registry Editor can be solved. Use this tool at your own risk.

1. Run Registry Editor (REGEDT32.EXE).

2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

      \SOFTWARE\Microsoft\SMS\Sites\<sitecode>\Domains\<domain>\Role

3. The setting for Role is based on a bit mask of the following:

      ENUMERATED      = 0x0001  Servers are enumerated

      SERVERLIST      = 0x0002  Servers from user list

      SCRIPTSMODIFIED = 0x0004  User/system logon scripts have been

                                modified

   Role is likely 5 (enumerated + modified). If you change it to 1, it will

   appear to Site Config Manager as though it had never touched logon

   scripts. If you switched to Use Specified Servers, the value will be 6.

   You can change it to 2 to obtain the same effect.

   NOTE: When you switch to Use Specified Servers, NetWare "domains" do not

   require auto-detect as a prerequisite to automatically configuring logon

   scripts. If you have NetWare domains, the needed script files could get

   removed. Consequently, changing the domain role value is a better

   solution.

STATUS

======

Microsoft has confirmed this to be a problem in Systems Management

Server versions 1.0 and 1.1. We are researching this problem and will post

new information in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug1.00 kbbug1.10

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 1.10 sms configuration


SMS: Automating Installations of Windows for Workgroups 3.11

Article ID: Q130682

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

In the current release of Systems Management Server, you must hand-tailor

the Windows for Workgroups setup script file (SETUP.SHH) for each type of

network card and protocol configuration used on network clients. A separate

SETUP.SHH has to be created for each configuration.

To ensure that the correct setup script file is used, the administrator

must first query for all computers with a specified network card configured

a specific way (common I/O address, IRQ setting, memory window location)

and copy these computers to a machine group. The package must be created

and the file SETUP.SHH must be replaced on each distribution server in

order for the automated setup routine to configure Windows for Workgroups

correctly on the target computers. Computers with net card configurations

that do not meet the general standards used within an organization cannot

be upgraded easily.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms 1.00 1.10 sms


Manual Installation of INVWIN32 on Windows NT Workstation

Article ID: Q130937

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

The administrator of an Systems Management Server managed network may want

to install the inventory agent service for Windows NT on Windows NT

Workstations. Systems Management Server does not provide a means to do

this, and it is not a supported feature at this time. The following steps

may be used to accomplish this. They are provided as is and are not

supported by Microsoft.

MORE INFORMATION

================

1. On Windows NT Workstation, create an SMS\HELPER.SRV\X86.BIN directory.

   This directory name is arbitrary, but it helps to be consistent with the

   currently supported methodology for domain controllers running the

   inventory agent service. The X86.BIN directory should be named

   appropriately for the proper architecture (X86.BIN, ALPHA.BIN,

   MIPS.BIN.)

2. From the appropriate directory on an existing Systems Management Server

   logon server, copy the INVWIN32.EXE program file into the directory

   created in step 1 above.

3. From the PSSTOOLS directory on the Systems Management Server

   distribution CD, run INSTSRV.EXE. Install the service using this tool,

   answering the following questions as presented by the tool:

    - Service Name

    - User account

    - Password

    - Machine name

    - Path

    - Start Mode

4. Each time the service is started, it must include an argument containing

   the path to the logon server it will report inventory to. This is in the

   format of "/L:\\<SMSLogonServer>\SMS_SHR\" and may need to be "escaped"

   in some cases. For example, using the SMS Service Manager, the argument

   must look like /L:\\\\<SMSLogonServer>\\SMS_SHR\\. Option 4 in INSTSRV

   can be used to start the service, Control Panel <Services>, in addition

   to the Systems Management Server Service Manager.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms sms 1.00 1.10


Inventory Update Reporting Interval

Article ID: Q130940

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

When an inventory agent produces an inventory, the Site Server checks for

changes and only pass through inventory data when a four-day timeout

occurs, unless the changes are found outside the Identification Group and

Workstation Status Group.

MORE INFORMATION

================

This can result in a machine inventory that only has changed attributes for

Last Hardware Scan or Last Software Scan (indicating a routine scan time

and no changes to the actual inventory). However, this inventory will not

be posted to the database for four days.

This is by design and is intended to minimize the number of delta MIF

transactions. A delta MIF is normally generated by the Inventory

Processor each time it processes a machine inventory. It compares the last

time a delta was forwarded to Inventory Dataloader to its four-day timer,

and may block redundant deltas. For this reason, even if machine name,

domain name, or any other item contained in the Workstation Status or

Identification groups have changed, it takes four days for these changes to

posted in the database (assuming a logon/inventory is made each day.)

A machine may not appear to have its Last Hardware Scan or Last Software

Scan times up to date with the last time an inventory was actually taken.

If you want greater accuracy, and are willing to accept increased system

overhead, modify the following registry entry:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components

      \SMS_INVENTORY_PROCESSOR\Inventory Update Reporting Interval (Days).

The default is 4 days, the minimum value is 1 day.

KBCategory: kbnetwork

KBSubcategory: ntconfig nthowto ntdomain

Additional reference words: prodsms sms 1.00 1.10 4-day


How to Change the SQL Login ID for the SMS Database

Article ID: Q130941

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

System Management Server uses a SQL Login Id to manage the its database on

a SQL Server. Systems Management Server uses the SQL Server System

Administrator (SA) account by default. The following procedure outlines how

to change the SQL Login Id.

MORE INFORMATION

================

1. Use the SQL Server Administrator Utility to login to the SQL Server

   containing the Systems Management Server database. Login with an SA

   account.

2. Open up the System Logins Window. If the Login Id you intend to use

   already exits on the SQL server proceed with Step 5.

3. Choose Manage/Add Login...

4. Specify the Login ID and password in the appropriate fields and choose

   OK.

5. Open the Query Window.

6. In the Query Window, type the following information:

      use SMS

      go

      sp_changedbowner "login id", true

      go

7. Execute the Query.

8. Run the System Management Server setup utility on the Primary Site

   Server.

9. Choose continue, then choose Operations.

10. Choose SMS Database.

11. Change the Login ID and password.

12. Choose OK.

The Setup program will restart the Systems Management Server services. Once

this has completed the setup program can be exited.

NOTE: The Login ID that you give to Systems Management Server should not be

a user of the database prior to executing Step 6. If the Login ID is a user

of the database, drop the Login ID from the database before proceeding with

Step 6.

Additional reference words: prodsms 1.00 1.10 sms loginid login_id

KBCategory: kbnetwork

KBSubcategory: nthowto


How To Speed Site Property Changes

Article ID: Q131010

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Depending on the Site Server's service response settings, the services

involved in changing a site's properties may sit idle for an extended

period of time waiting for their polling interval to expire. If

proposed site property changes exist, their implementation can be

expedited, rather than waiting up to 30 minutes for them to be imposed.

MORE INFORMATION

================

Proposed site properties are written to the SQL database for the site,

and there they wait for the Hierarchy Manager service to extract them

to a .CT1 file for hand-off to the Site Config Manager. Because the

Hierarchy Manager bases its interaction for reads from the database

on a polling interval, the service can be stopped and restarted in

order to force it to check the database for changes.

Once it has pulled the changes from the database, it writes them to a *.CT1

file and the Site Config Manager immediately wakes up (upon detecting the

new *.CT1 file) and implement the changes.

Finally, Site Config Manager writes a new *.CT2 file containing

confirmation of the proposed changes and this file is handed off to the

Hierarchy Manager. Hierarchy Manager then updates the database, making the

proposed site properties, actual site properties.

NOTE: Use of the unsupported SENDCODE.EXE utility to wake up the Site

Config Manager will do nothing until there is a valid *.CT1 file

containing the proposed changes. Stopping and starting the Hierarchy

Manager is the proper way to jump-start the process.

KBCategory: kbnetwork

KBSubcategory: nthowto ntdomain

Additional reference words: prodsms sms 1.00 1.10


Propagating MIF Entry Forms (XNF files) to SMS Clients

Article ID: Q131614

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

----------------------------------------------------------------------

SUMMARY

=======

Appendix G of the Systems Management Server Administrators Guide discusses

the customizing of computer inventory and the method to deliver

the custom MIF forms to the Systems Management Server clients. This article

outlines an alternate method to achieve this. The alternate method has the

additional benefit of automatically downloading the new forms for all new

clients when added to the Systems Management Server site.

NOTE: If you run Systems Management Server Setup and add components or

upgrade your site after you following the procedure below, the files you

modified (CLI_*.TXT) will be replaced with the original versions.

Therefore, this method is not supported by Microsoft for Systems Management

Server version 1.0. If you decide to use the method below, Microsoft

recommends that you make backup copies of the CLI_*.TXT files you modify.

MORE INFORMATION

================

The steps described below are similar to the documented method in the

Systems Management Server Administrators guide. The main difference is

the modification of the CL_*.txt file (where * indicates the client

operating system). The change specifies which files should be downloaded to

the client computers. You should specify the new forms you have created in

this file.

The remainder of this article will reference the CLI_WIN.TXT for purposes

of demonstration. If you are using other client operating systems with

Systems Management Server, follow the steps below to modify the appropriate

copylist file for each operating system platform.

1. Create the new form.

   Follow the steps outlined in Appendix G for Customizing the Computer

   Inventory and Creating forms. Save the new forms in the

   \SITE.SRV\MAINCFG.BOX\CLIENT.SRC\<platform> (where <platform>

   is all platforms currently installed  [for example, X86.BIN]). Forms

   saved in this location will automatically be copied to the logon

   servers.

   NOTE: All forms should be saved with the .XNF filename extension.

2. Modify CL_WIN.TXT.

   Modify the \SITE.SRV\MAINCFG.BOX\CLIENT.SRC\CL_WIN.TXT file to include

   the new form(s) you have created. You can add the appropriate lines to

   this file in one of several locations. However, Microsoft recommends

   you add the lines in the STANDARD NETWORK FILES section. This file will

   automatically be replicated to all logon servers.

3. Create a package to update clients.

   Write a batch file to connect to the \SMS_SHR share on a logon server

   and run CLI_DOS.EXE /U from the appropriate platform subdirectory.

   This will prepare the client to be updated at the next logon and the

   specified XNF files to be downloaded to the client where they will

   be available to the MIF Entry utility.

   Sample batch file:

     C:

     net use t: \\smsserver\sms_shr

     t:

     cd x86.bin

     cli_dos /u

     c:

     net use t: /d

4. Distribute CLI_WIN.TXT to clients.

   Deliver the above batch file to the client machines where the new forms

   should be available. When the job is executed on the client, the above

   batch file will prepare the client for update at the next logon. This

   file will also be delivered to all new Systems Management Server clients

   and will result in the automatic installation of the desired XNF forms.

KBCategory: kbnetwork

KBSubcategory: nthowto

Additional reference words: 1.00 1.10 sms prodsms


Sample SMSVIEW Reports and Queries Not Included in SMS

Article ID: Q131699

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Systems Management Server versions 1.0 and 1.1

-------------------------------------------------------------------------

Page 665 of the Systems Management Server 1.0 Administrator's Guide

incorrectly states the following:

   SMS provides sample reports and queries for use with Microsoft Word

   for Windows version 6.0, Microsoft Excel version 5.0, and Microsoft

   Access version 2.0

The Systems Management Server 1.0 compact disc does not include the sample

reports and queries.

KBCategory: kbdocerr

KBSubcategory: ntdocerr

Additional reference words: prodsms 1.00 1.10 sms


How to Obtain SMSKB.HLP

Article ID: None

The Microsoft Systems Management Server Knowledge Base help file is

periodically updated. You can obtain the updated file from:

 - The Microsoft Software Library (MSL) on CompuServe (GO MSL).

   Search for SMSKB.HLP.

 - The Microsoft anonymous FTP server (ftp.microsoft.com).

 - The Microsoft Download Service (MSDL) at (206) 936-6735.

 - The BackOffice area on the Microsoft Network (MSN).

Microsoft Systems Management Server Knowledge Base articles are

also available on the Microsoft World Wide Web site

(http://www.microsoft.com) and are included on the Microsoft

TechNet CD (distributed monthly).