XADM: Determining Which Windows NT Account Is the Service Accoun

 Last reviewed: February 23, 1998
Article ID: Q180013
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0, 5.0, and 5.5

SUMMARY

This article describes how to determine which Windows NT account was chosen as the Exchange service account during setup.

MORE INFORMATION

If the Exchange Server computer is running:

  1. Start the Exchange Administrator program.

  2. Expand the Site container and select the Configuration container.

  3. From the file menu, click Properties.

  4. Click the Service Account Password tab. The “Account name” box will display the service account information.

If the Exchange Server computer is down, you will not be able to start the Exchange Administrator program to find the Windows account. Therefore, you will need to perform the following steps:

Note: This is for viewing the information only; changing this value is not supported.

  1. Start the Microsoft Windows NT registry editor (Regedt32.exe).

  2. Select the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

  3. Click MSExchangeSA.

The ObjectName value in the right pane of the window gives the domain name and the Windows NT account name of the Exchange service account. 
Keywords          : XADM
Version           : WINDOWS:4.0,5.0,5.5
Platform          : WINDOWS
Issue type        : kbhowto

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

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