Outlook requiring password after exchange reboot

exchangeexchange-2010outlookpassword

We recently moved from Exchange 2003 to 2010, and have noticed a quirk that is annoying us.

If our exchange server (single server) goes down, ie it gets rebooted, or client loses connectivity (or for example a reboot is done overnight and the users computer is on at the time) they will be prompted to login, and will have to use the full domain\username notation in their username field in order to login again. Either that or reboot outlook.

Its not a big deal, but lots of inexperienced users are confused by this, and some dont realise they need to do something and thus their outlook sits there without receiving emails until they finally notice.

This used to be seamless, what do I have to do to get that back again?

Best Answer

This is because the Outlook account settings were configured with "Outlook Anywhere" turned on. You can turn it off, if you do not want it.

So that when exchange is rebooted, it will loose connection and restore it once it is back online, and it will not try to connect via https - Outlook Anywhere.

I normally advice my user to restart outlook. If they enter their credential, it will change their connection to exchange from native connection via lan to HTTPS.

Related Solutions

Outlook Prompting for password from Exchange server in domain environment

Check to see if the clients are configured to use Outlook Anywhere

Email accounts > Change > More settings... > Connection

If they're connection via Outlook Anywhere it will always ask for credentials. You can run a netstat -n to see if you have any 443 connections to your CAS server as well.

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

Best Answer

Related Solutions

Outlook Prompting for password from Exchange server in domain environment

Ssh – How to automate SSH login with password

Related Topic