Service Pack Support Tools Documentation

Info Gatherer (SMS20info.exe)

Use the Info Gatherer tool to automatically collect comprehensive information about your SMS site and your SMS site server, which can be provided to the Microsoft System Management Server team when needed.

Administrators might want to review detailed configuration information about their SMS site from the Backup/Recovery Task Information, because this tool does not provide information about systems other than the primary or secondary site server.

Note: SMS 2.0 Info Gatherer stops and restarts Microsoft Windows Management Instrumentation (WMI) on the site server. In most cases, this will not interfere with your testing. If you are investigating a problem that requires WMI to continue running, do not use this tool.

SMS 2.0 Info Gatherer collects information about your SMS 2.0 site and site server by doing the following:

Info Gatherer

Processors: i386 and Alpha
Operating Systems: Windows NT 4.0 and Windows 2000

File Required for Info Gatherer

The following file is required to run Info Gatherer:

SMS20info.exe

Using Info Gatherer (SMS20info.exe)

To start Info Gatherer:

LOGON POINT UPDATE TOOL (KickLSM.exe)

Use the Logon Point Update Tool to manually initiate a logon server manager update cycle, without waiting for the normal scheduled cycle.

Processors: i386 and Alpha
Operating Systems: Windows NT 4.0 Server and Windows 2000

NT INFO TOOL (SrvInfo.exe)

Use the NT Info tool to display various types of information about a computer running Windows NT, such as available disk space and partition types. An example of the data this tool displays is included at the end of this section. You can use the NT Info tool on a remote computer. NT Info is not supported for Alpha platforms that run Windows NT 3.51.

Processors: i386 and Alpha, when running Windows NT 4.0, i386 only when running Windows NT 3.51
Operating Systems: Windows NT 3.51 on i386 only, and Windows NT 4.0

QUERY EXTRACT TOOL (SMSextract.xls or SMSextract.mdb)

Use the Query Extract tool to run the same SMS queries that are found in Queries in the SMS Administrator console. This tool has two varieties, Microsoft® Excel files and a Microsoft Access file. All files are functionally equivalent.

Processors: i386
Operating Systems: Windows NT 4.0, Windows 95, Windows 98, and Windows 2000

SERVER ENUMERATOR TOOL (Svrenum.exe)

Server Enumerator lists all domain controllers in the domain, to which the server belongs. This is the same list of domain controllers targeted by NT Logon Server Manager when configuring logon points. Therefore, the tool might be useful during troubleshooting to help determine why SMS might not be updating particular domain controllers.

Output from Server Enumerator includes:

Processors: i386 and Alpha
Operating Systems: Windows NT 4.0 Server and Windows 2000 Server

SITE UTILITIES TOOL (Preinst.exe)

Preinst passes commands to Hierarchy Manager while Hierarchy Manager is running. Use this tool to diagnose problems in a site, repair a site, or stop all SMS services at a site. For example, suppose that you incorrectly removed an SMS site by removing a child site from its parent site without detaching it first. You can use Preinst to bypass the SMS Administrator console and delete the incorrectly removed site from the parent site database.

Note: Because a secondary site does not have its own database, use only the /stopsite command-line option when using this tool at a secondary site. Because you cannot use the /syncparent command-line option at a secondary site, you can stop and start SMS_EXECUTIVE instead. This will force the current site control file to be forwarded to the parent site.

Processors: i386 and Alpha Operating Systems: Windows NT 4.0

/deinstall:Secondary_Site_Code
Removes the specified secondary site from a site hierarchy. If you want to remove a secondary site from a site hierarchy, first try to remove it by using the SMS Administrator console; if that fails, then use Preinst /deinstall.

/deljob:Site_Code
Deletes all jobs, or commands, that are targeted to the specified site.

/delsite:{Removed_Child_Site_Code, Parent_Site_Code}
Deletes incorrectly removed child sites from the parent site's site database (the braces are required). Use this option if you removed a site before you detached it from its parent. This transaction propagates up the site hierarchy to all parent sites of the current site.

/dump
Writes site control images for all sites to the SMS\Site.srv\Sitecfg.box directory. (An image is a binary representation of the site control file, which is stored in the SMS site database. The dumped site control file image is a sum of the base image plus the pending delta images.) After dumping a site control file image with Preinst, the file name will be in the format SMS_Site_Code.scf.

/stopsite
Initiates a shutdown cycle for SMS Site Component Manager, which partially resets the site. When this shutdown cycle is run, some SMS services on a site server and its remote site systems are stopped. These services are flagged for re-installation. As a result of this shutdown cycle, some passwords will be automatically changed when the services are re-installed.

/syncchild:Site_Code
Synchronizes a child site with the parent site. Site_Code is the child site to synchronize. Syncchild simulates a child site attachment so all the components at the current site get triggered by a site attach notification for the specified child site, thereby updating the child site. For example, Collection Evaluator will send all collection information to the child site, and package definitions will be sent to the child site.

/syncparent
Forces all site control images in the site database to simultaneously propagate up to the parent site of the current site. This propagation includes the site control images of all subsites stored in the site database of the current site. Use this option when sites are out of synchronization due to time lags or other failures. Because secondary sites have no site database for Preinst to operate on, stop and start SMS_EXECUTIVE to force the current site control image to be forwarded to the parent site.

/upgrade:Secondary_Site_Code
Upgrades a secondary site. Use this option to upgrade failed sites if a global upgrade fails to upgrade all secondary sites.

Top of page

Client Maintenance Tools

Installation

To install the APM Spy tool, copy APMSpy.exe to the ..\MS\SMS\Core\Bin directory on the client. The APM Spy tool uses CliBase.dll and CliLog.dll, which are located in this directory.

File Required for APM Spy

APMSpy.exe

APM Spy Syntax

apmspy

Installation

You must install and run the Client Cleaner tool on the client. To install Client Cleaner, copy the required files to the desired location. All required files must reside in the same directory.

Files Required for Client Cleaner

20CliCln.bat
Hammer.exe
Kill.exe
SetEvnt.exe

Client Cleaner Syntax

20clicln.bat [/SCRUB]

/SCRUB
Causes the SMSCFG.INI file to be deleted from the directory indicated by %SMS_LOCAL_DIR%. This is a more thorough cleanup since the smscfg.ini file may contain the previous SMS identifier used by the client.

Installation

To install the Client Travel Mode tool, copy the required files to the desired location. If the tool will be used through a login script, it should be copied down to the client one time only through the script and then run locally to reduce unneeded network traffic.

Required Files for Client Travel Mode Tool

CliTravl.exe

ChkTravl.bat

Client Travel Mode Tool Syntax

CliTravl [/TRAVEL=ON | /TRAVEL=OFF] [/PROMPT=ON | /PROMPT=OFF]

By specifying no arguments, it returns a DOS errorlevel of 1 if travel mode is active, 0 if it's not active.

Installation

You must install and run the Client Utilities tool on the client. To install Client Utilities, copy the required file to the desired location.

File Required for Client Utilities

Cliutils.exe

Client Utilities Syntax

CliUtils command parameter_list

/kickcomponent_name
Initiates the Start Cycle event for the specified client component.

/startcomponent_name
Initiates the Start event for the specified client component.

/stopcomponent_name
Initiates the Stop event for the specified client component.

/sched schedule_string
Decodes the Schedule List string.

/appreg
Registers an application that the client launchers will start. After this command is issued, the Client Utilities tool prompts the user to enter information about how the application should be registered. To use this command-line option, you must understand the client launchers.

Installation

To install the Process Viewer 95 tool, copy the required files to the desired location.

Required File for Process Viewer 95

PView95.exe

Process Viewer 95 Syntax

pview95

Installation

To install the Zap tool, copy the required file to the desired location.

File Required for Zap

Zap.exe

Zap Syntax

zap filename

filename
The path of the file to be deleted.

Top of page

Database Maintenance Tools

Files Required for Delete Client MIF

DelMIF.dll
DelMIF.exe

Delete Client MIF Syntax

delmifSMSID [output_directory]

delmif@SMSID_file [output_directory]

SMSID
The SMS ID of the client that will be deleted.

SMSID_file
A file containing several SMS IDs that will be deleted, one per line. All characters after the first space on a line are ignored.

An easy way to create SMSID_file is to run a query in SMS Administrator console, select the applicable computers, and paste the SMS IDs into a Microsoft Notepad file. (The SMS ID is the first column in the query output.)

output_directory
The directory where the Delete MIF file is written. The defaults are the LastLogonServerPath and ISVMIFCollectionPoint, which are found in C:\SMS.ini. The output directory can be on any logon server in Logon.srv\ISVMIF.box or on the site server in Site.srv\ISVMIF.box. (The Site.srv directory provides a slightly faster response.) You must specify an output directory.

Using Delete Client MIF

The following command creates a Delete MIF file for the client with the SMS ID ABC00012:

delmif ABC00012

The following command creates a Delete MIF file for the client with the SMS ID ABC00345 and writes the Delete MIF file to D:\mydirectory:

delmif ABC00345 d:\mydirectory\

The following command creates a Delete MIF file for each client with an SMS ID listed in Del.dat:

delmif @del.dat

Delete Client MIF with a SQL Server Trigger

SQL Server Trigger allows you to delete clients by using either SMS Administrator console or Dbclean.exe and to generate Delete MIF files automatically. These Delete MIF files will flow up the hierarchy as any other Management Information Format (MIF) file does. (These MIF files are processed by the current site before they are sent up the hierarchy, which can decrease performance on the current site server.)

To run Delete Client MIF with a SQL Server Trigger, run the following two commands from ISQL/W or a Query window in Enterprise Manager. You can copy and paste these two command groups into the SQL Query window.

Modifying the EXEC line to include an output directory (for example, exec master..xp_delmif @smsid, "D:\SMS\Site.srv\ISVMIF.box\") is strongly recommended. You must be logged on with sa access to create extended stored procedures. (For more information, see the next section, "Limitations of Using Delete Client MIF with a SQL Server Trigger.")

From the Master database:

sp_addextendedproc 'xp_delmif', 'delmif.dll'

From the SMS site database:

create trigger delmachine
on Machines
FOR DELETE
AS
DECLARE @smsid varchar(255)
DECLARE tIDs CURSOR FOR
select SMSID0
from MachineDataHistoryTable m (index = dwMachineID_idx),
Identification_SPEC i, deleted d
where i.datakey = m.SpecificKey and
GroupKey = 1 and
m.ArchitectureKey = 5 and
m.dwMachineID = d.dwMachineID
open tIDs
FETCH NEXT
FROM tIDs
INTO @smsid
WHILE (@@fetch_status <> -1)
BEGIN
exec master..xp_delmif @smsid
FETCH NEXT
FROM tIDs
INTO @smsid
end
close tIDs
deallocate tIDs

Limitations of Using Delete Client MIF with a SQL Server Trigger

The SQL Server trigger method works best when the instance of SQL Server containing the SMS site database is on either the site server or an SMS logon server. Using an instance of SQL Server that contains the SMS site database on a stand-alone server creates a problem.

By default, SQL Server runs under the local system account, which is a special Windows NT account that has full administrative access to the local computer but has no network access. Where, then, can the program write the MIF file? (On site servers and SMS logon servers, there is a directory on the local computer to which the process can write.) There are at least two possible solutions:

Delete Client MIF Performance Issue

There might be a performance problem if many computers are deleted at once.

Access to DelMIF.dll

When you use the SQL Server trigger, make sure the SQL Server process has access to DelMIF.dll. Place this file either in the same directory as SQL Server or somewhere in the path.

Installation

To install the Duplicate Data Key Checker tool, copy the required file to the desired location.

File Required for Duplicate Data Key Checker

DatDupck.exe

Duplicate Data Key Checker Syntax

datdupcksql_server_name sql_login sql_password sms_database
- or -
datdupck (You will be prompted to enter the parameters)

Using Data Key Checker

When you attach sites to one another, it is possible for information in the SMS site database to be duplicated incorrectly. Symptoms of this can be apparent in data that is stored as COMMON rather than SPECIFIC according to the Desktop Management Task Force (DMTF) specifications. Examples of this would be in the PC_BIOS or Disk data, although any COMMON storage might be affected. Symptoms might be displayed as a duplicate drive C or no drive A for certain systems. Other symptoms might exhibit themselves as well, but this depends on the state of the child and parent databases before the site attachment.

For more information, see Microsoft Knowledge Base Article Q168565.

DUPLICATE DATA KEY CLEANER TOOL (DatDupcl.exe)

Use the Duplicate Data Key Cleaner tool to remove duplicate data key inventory from the database.

The Duplicate Data Key Cleaner requires that the SMS SQL server be running Microsoft SQL Server 6.5 SP3 or later. This tool should be run from a computer with the SMS Administrator console installed and functioning properly to ensure that all required DLL files are available. Additionally, The SMS site database should be in single user mode to ensure that no users or SMS services are accessing the database at the time Duplicate Data Key Cleaner runs. All SMS services should be stopped and no SMS Administrator console should be running against the SMS site database while this tool runs.

Warning: The Duplicate Data Key Cleaner tool modifies the SMS site database.

Before Using the Duplicate Data Key Cleaner

Before using the Duplicate Data Key Cleaner tool, first execute these DBCC commands from ISQL/W or Microsoft SQL Enterprise Manager:

Refer to Microsoft SQL Server Books Online (Administrators Companion, Troubleshooting Overview, Examining the Error Log and DBCC Output) and verify that there are no errors. If any errors are returned, do not run the Duplicate Data Key Cleaner; contact Microsoft Product Support. If no errors are returned, perform a dump of the SMS site database and then proceed.

Depending on the number of duplicate data key entries, this tool can delete a large amount of information from your SMS site database. It is necessary to delete this information to clean the duplicate data keys or the information will be reported by hardware and software inventory at the next inventory interval. Because this tool can delete a large amount of information, you must ensure that your SMS log size and TEMPDB size are sufficient. Guidelines for these are:

TEMPDB - SMS Site Database Size * .25

SMS log size - SMS Site Database Size * .35

Processors: i386 and Alpha
Operating Systems: Windows NT with the SMS Administrator console installed.

Installation

To install the Duplicate Data Key Cleaner tool, copy the required file to the desired location.

File Required for Duplicate Data Key Cleaner

DatDupcl.exe

Duplicate Data Key Cleaner Syntax

datdupclsql_server_namesql_loginsql_passwordsms_database

Using Duplicate Data Key Cleaner

When you attach sites to one another, it is possible for information in the SMS site database to be duplicated incorrectly. Symptoms of this can manifest in data that is stored as COMMON rather than SPECIFIC according to the Desktop Management Task Force (DMTF) specifications. Examples of this would be in the PC_BIOS or Disk data, although any COMMON storage might be affected. Symptoms might be displayed as a duplicate drive C or no drive A for certain systems. Other symptoms might exhibit themselves as well, but this depends on the state of the child and parent databases before the site attachment.

For more information, see Microsoft Knowledge Base Article Q168565.

Files Required for Duplicate SMS ID Cleaner

12DupCln.exe
Output file

Duplicate SMS ID Cleaner Syntax

12dupclnoutput_file

output_file
The file containing the duplicate SMS IDs (either SMSiddup.log or Shortdup.txt)

Using Duplicate SMS ID Cleaner

Before you use the Duplicate ID Cleaner tool, verify that the cause of SMS ID duplication has been corrected. You must also delete the computer from the SMS site database, otherwise the site database might become corrupted.

For 32-bit clients, you can run the Duplicate ID Cleaner tool from the logon script. This tool must be run before SMSls.bat is called. Be sure to use the START/WAIT command to avoid file locking errors. The following is a sample script entry:

START/WAIT %0\..\12DUPCLN Shortdup.txt

The Duplicate ID Cleaner tool compares the client SMS ID to the SMS IDs contained in the specified output file (either SMSiddup.log or Shortdup.txt). If a match is found, this tool renames the SMS.ini file on the client to SMS.dup. The SMSls.bat file will then assign a new SMS.ini file to the client, thus assigning a unique SMS ID to the client.

In addition to renaming the SMS.ini file on the client, the Duplicate ID Cleaner tool also places a file, Dup.tst, on the client as a flag. This file is placed in the root system directory. Each time this tool is run from the logon script, it will first check for this flag file. If it finds this file, the tool exits, thereby speeding up the logon process for the client.

The specified output file (either Shortdup.txt or SMSiddup.log) must reside in the same directory as this tool (12DupCln.exe). For efficient execution, place these files in the NETLOGON share and replicate them to all of your logon servers.

For both 16-bit clients and 32-bit clients, you can use SMS 1.2 Package Command Manager (PCM) to distribute this tool to clients. If you choose this option, be sure you force the client to log off the network and then log on as soon as possible in order to receive a new client ID.

Installation

To install the Duplicate SMS ID Locator tool, copy the required file to the desired location.

File Required for Duplicate SMS ID Locator

SMSIDDup.exe

Duplicate SMS ID Locator Syntax

smsiddupsql_server_namesql_loginsql_passwordsms_database
- or -
smsiddup (You will be prompted to enter the necessary parameters)

Note: If sql_password is null, use double quotes for the password field:

smsiddup sql_server_namesql_login""sms_database

Using Duplicate SMS ID Locator

In SMS, it is possible to have two different types of duplicate SMS IDs. With the first type, two or more computers share the same SMS ID, but the data for each of these computers is stored in a separate data table. SMS Database Manager will locate this type of duplication. Querying on duplicate SMS IDs in the SMS Administrator console will probably produce multiple records which fit this scenario.

However, the second type of duplicate SMS ID is much more difficult to locate. This is because two or more computers that share the same SMS ID also share the same data table. The SMS Database Manager will not locate this type of duplication. You must use the Duplicate SMS ID Locator tool to find these duplicates.

When a different computer using the same SM SID is inserted into the database, SMS will move the "old" computer data into the historical computer data table. In this case, SMS is not aware that there is more than one computer using the SMS ID. Querying on the SMS ID in the SMS Administrator console produces one record. Viewing the history for the Identification group in this record shows that the computer name changes frequently. However, the computer name does not actually change - multiple computers report using different names.

This second type of SMS ID duplication is usually the result of having a "cloned" SMS.ini file present (an imaged installation of a computer is performed with a pre-existing SMS.ini in the image). This second type of duplication can cause the SMS Dataloader to process computer MIF files very slowly or to hang. These duplicates can also lead to database corruption.

To assist in cleaning up this second type of duplicate SMS ID, the Duplicate SMS ID Locator tool produces a report containing the SMS ID, sitecode, computer name, domain, and the last hardware-scan time for each of these duplicates. These computers should be deleted from the SMS site database and their SMS.ini files should be deleted. After the computers are deleted from the database and their SMS.ini files are deleted, they can be re-inventoried and assigned a new SMS ID. When history and unused common/specific records are removed from the database, remnants of these duplicate SMS IDs are removed.

The SMS.ini file on the client must also be deleted to eliminate the duplicate SMS IDs. If the SMS.ini files on these clients are not deleted, and the computers are merely deleted from the SMS site database, they will show up again in the database after the next inventory and the cleanup process will need to be repeated. You can delete the SMS.ini file manually, or you can use the Duplicate SMS ID Cleaner tool to automatically delete the file when the client logs on to the network. If you use the SMS ID Cleaner tool to automatically delete the SMS.ini file on the client, you might want to use the Duplicate SMS ID Parser tool to optimize the output file from the Duplicate SMS ID Locator tool. This will reduce the amount of time required to match clients logging on to the network with clients listed in the output file.

File Required for Duplicate SMS ID Parser

12DupCnv.exe

Duplicate SMS ID Parser Syntax

12dupcnv

Using Duplicate SMS ID Parser

The Duplicate SMS ID Parser tool requires the output file from the Duplicate SMS ID Locator tool. This output file, SMSiddup.log, must reside in the same directory as the Duplicate SMS ID Parser tool. This tool places the parsed output file, Shortdup.txt, in this same directory, where it can be used by the Duplicate SMS ID Cleaner tool.

Files Required for QDF Writer and Reader

WriteQDF.exe

QDF Writer and Reader Syntax

writeqdfserver account password database {QDF | query_ID}
[/import | /export] /?

server
The computer running the instance of SQL Server that contains database.

account
The account used to access database.

password
The password for account. If the password is blank or contains spaces, it must have quotation marks around it, for example, "Password".

database
The name of the database containing the query information.

QDF
A QDF that is read into SMS.

query_ID
A query ID for which to write a QDF.

/import
Specifies that a QDF is being read.

/export
Specifies that a QDF is being written, which is the default behavior.

/?
Provides a usage statement.

Installation

To install the Status and Configuration Reporter tool, copy the required file to the desired location.

File Required for Status and Configuration Reporter

ChkSMS.sql

Status and Configuration Reporter Syntax

To run ChkSMS.sql, open it in an ISQL/w command window and run it. Additional directions are in the ChkSMS.sql file.

Top of page

Log File, Schedule File, and Error Code Tools

Installation

To install the Dump Error Message tool, copy the required file to the desired location.

File Required for Dump Error Message

Error32.exe

Dump Error Message Syntax

error32 code[:code][source_name | message_DLL][insertion_string[...]][*]

code
Specifies either a decimal error code for a Windows NT error or an event code for an application or system source, such as SMS. The error code is assumed to be a Win32 error unless source_name or message_DLL is specified.

:code
Specifies another code to form a range - for example, 3:11 specifies codes from 3 to 11, inclusive.

source_name
Specifies an application or system name registered for the Windows NT Event Log. You cannot use this option with message_DLL.

message_DLL
Specifies a full or partial path to a Windows NT event log message DLL file (such as Netmsg.dll). You cannot use this parameter with source_name.

insertion_string
Specifies one or more strings to be inserted into the displayed message.

*
Displays messages for all matching languages and matching severities.

Using Dump Error Message

The following command returns Error Code 2 message text, which is taken from the system message table:

error322 The system cannot find the file specified.

The following command returns Error Code 5 message text:

error325 Access is denied.

Installation

To install the Dump Schedule Data tool, copy the required file to the desired location.

File Required for Dump Scheduler Data

DumpSend.exe

Dump Scheduler Data Syntax

dumpsend instruction_filename

file_name
The name of the Scheduler file to view data from.

Using Dump Send Request Data

The .srq files are located in the following directory (where LAN is the type of sender):

\SMS\Inboxes\Schedule.box\Outboxes\LAN

For example, you can use the following command:

dumpsend x:\SMS\Inboxes\Schedule.box\Outboxes\LAN\2_01skro.srq

Installation

To install the NAL Logging tool, copy the two required registry files to the desired computer. Run the desired registry file to either turn NAL logging on or off.

Files Required for NAL Logging

Turn_on_nal_logging.reg
Turn_off_nal_logging.reg

NAL Logging Syntax

turn_on_nal_logging | turn_off_nal_logging

Read Schedule

To install the Read Schedule tool, copy the required file to the desired location.

File Required for Read Schedule

ReadSche.exe

Syntax

readsche.exeschedule_string

schedule_string
The schedule token string.

C:\SMS\Logs\SiteToSite.log

Top of page

Discovery and Inventory Tools

Using Client Component MOF File

You must add the Client Component MOF File (SMSClient.mof) to the SMS_Def.mof file. To do this, copy the contents of the SMSClient.mof file and append the contents to the end of the SMS_Def.mof file. You can also perform this task by typing a command, like the following, at a command-line:

copy /a SMS_Def.mof + SMSClient.mof SMS_Def_New.mof

After appending SMSClient.mof to SMS_Def.mof, use the MOF Compiler tool (MofComp.exe) to verify that the resulting MOF file will compile. The MOF Compiler tool is installed automatically with SMS 2.0. For a list of command-line options, run the following command at a command line: mofcomp /?

However, the MOF Compiler tool is also part of the Windows Management Instrumentation (WMI) Platform SDK. For more information about compiling MOF files, see the WMI SDK documentation.

After compiling the new MOF file, rename the original SMS_Def.mof to SMS_Def.old and rename new MOF file (SMS_Def_New.mof) to SMS_Def.mof. SMS will automatically replicate the changes to all clients.

Note: Each time you upgrade SMS, the SMS_Def.mof file is replaced. Therefore, you should keep a backup copy of your appended SMS_Def.mof file. Also, if you want to use the MOF Manager tool to edit the new SMS_Def.mof file, you must use the version located on the Systems Management Server 2.0 SP1 compact disc in the following directory: Support\Reskit\Bin\i386\MOFMan. Previous versions of the MOF Manager tool cannot open the SMS_Def.mof file after the contents of the SMSClient.mof file have been appended.

File Required for Client Component MOF File

SMSClient.mof

Installation

To install the Dump Discovery Data tool, copy the required files and place them in the following client directory:

SMS\Core\bin

File Required for Dump Discovery Data

DiscDump.exe

Dump Discovery Data Syntax

discdump

Installation

To install the Inventory Synchronizer tool, copy InvSync.exe to the \SMS\Bin\i386 directory on the SMS site server and verify that the other required files reside in the directory.

Files Required for Inventory Synchronizer

BaseObj.dll
BaseSQL.dll
Basesvr.dll
BaseUtil.dll
InvSync.exe
SMSPerf.dll

Inventory Synchronizer Syntax

invsync [hw | sw] client_NetBios

hw
Sends a hardware inventory resynchronization request to the specified client.

sw
Sends a software inventory resynchronization request to the specified client.

client_NetBios
The NetBios name of the client that the request is sent to.

Using Inventory Synchronizer

The following syntax sends a hardware inventory resynchronization request to the specified Windows NT client:

invsync hw SMSNTCLI8

The following syntax sends a software inventory resynchronization request to the specified Windows 95 client:

invsync sw SMSWIN95CLI

File Required for MIF Checker

MIFCheck.exe

MIF Checker Syntax

mifcheck [/dump] file

/dump
Displays the MIF file in a readable format. If you run MIF Checker without specifying the /dump option, the MIF files are checked for syntax errors only.

file
The name of the MIF file.

Using MIF Checker

When you run the MIF Checker tool, the tool reports only one error at a time. Therefore, you must rerun MIF Checker after correcting each error, to verify that each error is resolved.

Using MOF Manager

MOF Manager is used to edit the SMS_def.mof file only. If you use MOF Manager to try to open any other MOF file using MOF Manager, you will receive an error message. Before you edit the SMS_def.mof file, make a backup copy of this file and place it in another location.

To edit SMS_def.mof

For detailed information about using the MOF Manager tool to edit the SMS_def.mof file, see Chapter 10, "Customizing Hardware Inventory," in the Microsoft Systems Management Server 2.0 Resource Guide.

Installation

To install the Software Inventory Viewer tool, copy the required file to the desired location.

File Required for Software Inventory Viewer

SInvView.exe

Software Inventory Viewer Syntax

sinvviewfilename

filename
The name of the file (.sic, .sid, or Sinv.his)

Top of page

Software Distribution Tools

Installation

To install the Advertisement Information tool, copy the required file to the desired location.

File Required for Advertisement Information

AdvInfo.exe

Advertisement Information Syntax

advinfo [package_file | offer_file]

package_file
The full path name of the package file (.pkg).

offer_file
The full path of the advertised program offer file (.ofr).

Using Advertisement Information

The following are directories that normally contain package files and offer files:

SMS\Inboxes\Offerinf.box\

SMS\Inboxes\Pkginfo.box\