For many people using hosted Exchange services, password saving problems could plague you. That is mainly because Outlook doesn’t like it if the Exchange server’s domain doesn’t match your domain.

Fortunately there is a way around this, because by the default way it is set up, you would have to enter your password every time you open up Outlook.

First step is to change the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Change lmcompatibilitylevel to “2″

Here is the meanings of these numbers (source):

0 - Clients use LM and NTLM authentication, but they never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
1 - Clients use LM and NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
2 - Clients use only NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controller accepts LM, NTLM, and NTLMv2 authentication.
3 - Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
4 - Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM authentication responses, but it accepts NTLM and NTLMv2.
5 - Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM and NTLM authentication responses, but it accepts NTLMv2.

I’ve uploaded a registry file which will automatically make the change here.

You then need to access the advanced user dialog properties (see my previous article on this if you do not see a tab in Control Panel -> Users & Accounts dialog). Click “Manage Passwords” and then add a new entry. This entry should be the Exchange server’s real name - the name that pops up in your password prompt windows. In my example, in is MAILXXX.mail.lan.

Finally, make sure that the Exchange server’s local name, MAILXXX.mail.lan, is in your hosts file. For most Windows XP folks, this is C:\WINDOWS\system32\drivers\etc\hosts.

The format is:

69.x.x.x MAILXXX.mail.lan

where the real accessible IP address is the first part, and the real Exchange server name is the section part. This allows your PC to locate the “Real” Exchange server name over the internet, even though it is not a real exchange server’s hostname on the internet.

Updated on 8/26/2008 with corrected information!

Window’s simple shutdown command works well, but has some major drawbacks. The major one is that it will only schedule a reboot up to 10 minutes into the future (600 seconds). Linux’s shutdown command makes this easy, just issue the command ’shutdown -r +60′ for example to reboot an hour in the future.

No such luck in Windows, you need to download a separate program to do this. It is a sysinternals program, you might remember sysinternals from such utilies like FileMon and ProcessMonitor.

The program we use for this is called PsTools and more specifically the file psshutdown.exe.

[Download PsTools here]

Place psshutdown.exe into a directory for future use, for this example we will use c:\tools\.

Easiest Method:

Type the following command into the command prompt:
c:\tools\psshutdown.exe -r -f -c -t 02:00 /accepteula

PSshutdown will respond with:

PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems
Copyright (C) 1999-2006 Mark Russinovich
Sysinternals - www.sysinternals.com

Local system is scheduled to reboot in 15:08:00.

If all goes will, Windows will reboot at 2:00am, or your specified time. This command will start a system service with the psstools scheduling program, PSSDNSVC.EXE.

Alternate Method:

Then open a command prompt and type the following command:

at 2:00am c:\tools\psshutdown.exe -r -f -c -t 10 /accepteula

This will result in:

Added a new job with ID = 1

You can verify this task has been added by looking at the Scheduled Tasks - the job name will be At1 if you haven’t scheduled any other tasks via the command line.