XADM: Performance Optimizer Values Change Depending on NT Login

 Last reviewed: November 5, 1997
Article ID: Q163572
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

The initial values for the Microsoft Exchange Performance Optimizer are read from the following Windows NT registry key: 

   HKEY_CURRENT_USER\Software\Microsoft\PerWiz\Question States
Because this is part of the HKEY_CURRENT_USER tree, the value will be dependent upon the Windows NT login.

These setting are display settings and do not reflect the actual performance enhancement settings that have been made to the registry from running the Performance Optimizer.

MORE INFORMATION

To understan this problem, let's use the following example:

User A logs into the Windows NT Server and runs the Microsoft Exchange Performance Optimizer and changes the Estimated # of users to 101-250.

User B logs into the Windows NT Server and runs the Microsoft Exchange Performance Optimizer. The Estimated # of users does not reflect the change that user A made.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug4.00 XADM buglist
Version : 4.0
Platform : winnt
Issue type : kbbug

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: November 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.