How to Logoff Users on a Remote Server from the CLI

This is some thing that can only be achieved through privileged access to the server you login to perform the task.

To Query for users on the Server

>QUSER [username | sessionname | sessionid] [/SERVER:servername] [/MODE] [/FLOW] [/CONNECT] [/COUNTER]

• username: Identifies the session with user username.
• sessionname: Identifies the session named sessionname.
• sessionid: Identifies the session with ID sessionid.
• /SERVER:servername: The server to be queried (default: current).
• /MODE: Display current line settings.
• /FLOW: Display current flow control settings.
• /CONNECT: Display current connect settings.
• /COUNTER: Display current TSs counters information.

This command will work for almost all the new Windows distributions. For windows XP, an Enviromental Variable needs to be added. However the path could be temporarily set by the below, before executing the above command.

>SET PATH = C:\Windows\System32\DLLCache

To Logoff a user from the server

>LOGOFF [sessionname | sessionid] [/SERVER:servername] [/V]

• sessionname: The name of the session.
• sessionid: The ID of the session.
• /SERVER:servername: Specifies the TS (default is current).
• /V: Displays info about the actions performed.

How to mount Exchange 2000/2003 database when E00.log is missing

You may get the below Error message when trying to mount the mail store: "An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724". Also you may note the Event IDs 9518 & 455 in your Application logs.

Solution

1. Stop all Exchange related services on your server.
2. Backup your log files that are usually located on x:\Program Files\exchsrvr\MDBDATA\Exxxxxxx.Log to a temporary folder.
3. Delete all *.log files in the x:\Program Files\exchsrvr\MDBDATA except for e00.chk, res1.log and res2.log
4. Start all exchange related services.
5. Mount the mail store.

If the above does not work, it could be due to a corrupted database. You could probably find a solution for it through the below link

http://www.msexchange.org/tutorials/exchange-isinteg-eseutil.html