Frankly this is absurd. There must be a consistent solution to this problem. Not one that works depending on the configuration, or, in my case doesn't.
If anyone has suggestions for making these passwords stick other than the ones presented here:
http://systembash.com/content/outlook-20032007-wont-save-hosted-exchange-password/
Or any of the ones suggested in the archived Technet article, I'd appreciate hearing about them. In my case we're trying to connect clients to an Exchange 2010 server using Outlook 2007, 2010 running XP Pro and Windows 7.
I have ran into this problem with a few of my clients and we managed to get it to work.
ตอบลบHere is what we did to get passwords to stick:
This method will not require ANY registry modifications.
When hosting a client our server name never matches the domain we are hosting thus you get a login prompt every time you connect to outlook.
--For example our Proxy host is mailhost.domain.net and the server name is exch1.domainX.com. So in order to get the passwords to stick you have to save the passwords for both domains, the proxy and the server, so you will need to go under credential management (Windows 7) or user settings (XP) and set the two entries. You can use the * to specify all servers on that domain like the following:
--*.domain.net
--*.domainX.com
Fill in the proper user names and passwords and next time they open outlook it will just let them in. The reason this works is when the PC looks to use a stored UserID and password it looks at the domain. So if the domains don’t match it will fail on one of the authentication attempts.
Though this worked for us I do NOT recommend it for security reasons. I prefer the user to enter a password when they open outlook. Bothers me that some people don’t think about getting there laptops stolen and all their info wide open for people to take.
Let me know if it works for you.
I think I understand the frustration. I know it may sound like a simple thing, there is actually quite a few components in place that sort of complicate this. The issue isn't Hosted Exchange specific. It is a combination of RPC over HTTP or Outlook Anywhere (which that itself is quite a component like you have SSL and IIS and RPC Proxy involved here and IIS serves as the first authentication and then the authentication to Exchange server itself), non-domain joined machine and authentication mechanism. Well, it happens that such configurations happen to be what the Hosted environment clients are using. To add to the complexity a bit, different versions of Outlook and Windows may behave differently under different circumstances. For example, older version of Outlook may need NTLM for this to work and if you go through some proxy server that may block this, then it may not work.
ตอบลบUsing the Credential Manager as mentioned by ScoNetExch should work but at the same time, you should make sure that it is NTLM enabled at the server side too. Try that and see if it works. If not, try sending a note to the Outlook IT Pro forum and see and let them know that you are using the configurations above whcih is Outlook Anywhere from the internet + a non-domain joined computer.