Typing Full Path and Filename Causes Inventory Rule to Fail

Last reviewed: April 23, 1997
Article ID: Q135088

The information in this article applies to:
  • Microsoft Systems Management Server versions 1.0, 1.1 and 1.2

SYMPTOMS

If you add an inventory rule for a package in the Systems Management Server Administrator File Properties dialog box and type the full path to the file and the filename, the following symptoms occur:

  • The inventory agent is unable to find the file.
  • If you add a property such as Checksum to the rule, you cannot obtain the value for that property.

CAUSE

The rule parser requires that you type only the filename without the full path to the file.

WORKAROUND

To work around this problem, type the filename without the path to the file.

To retrieve the value of a property for the rule, choose the Browse button to find the file (instead of typing the filename).

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1 and 1.2. We are researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodsms sms software invdos package.rul
Keywords : kbbug1.00 kbbug1.10 kbbug1.20 kbnetwork ntutil smsconfig smsinv
Version : 1.0 1.1 1.2
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND 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 FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.