Outlook doesn't save passwords on hosted Exchange
-
2010년 7월 9일 금요일 오후 4:48
This seems to be a huge issue judging from the chatter on the Internet and this archived thread on Technet:
http://social.technet.microsoft.com/Forums/en/office2010/thread/cd38f3f2-892f-470c-b52e-17b8beeb275e?prof=required
I've tried just about every solution proposed in the above article, as well as a few on my own (including editing the registry). In my eyes this is a Microsoft problem that should have been solved by now. It seems there are a dozen "solutions" depending on what variation of OS and Outlook you're running, and whether your PC is joined to a domain.
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.
모든 응답
-
2010년 7월 9일 금요일 오후 5:54
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.
- 답변으로 제안됨 Kip NgMicrosoft Employee, Editor 2010년 7월 10일 토요일 오전 6:28
- 답변으로 표시됨 Kip NgMicrosoft Employee, Editor 2010년 7월 12일 월요일 오후 5:54
-
2010년 7월 10일 토요일 오전 6:28답변자
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.
Kip
Regards, Kip Ng - http://blogs.technet.com/b/provtest/ -
2010년 7월 12일 월요일 오후 3:11
Thank you to both Brandon and Kip. Brandon's suggestion worked. Once again it's the simple solutions that often end solve the complex problems. It's curious I had such a difficult time finding an answer to this. Even my host didn't have an answer other than to try that Outlook Autologin script (which didn't work for me).
Thanks again. Problem solved!
-
2010년 7월 28일 수요일 오후 12:20Brandon, I seem to recall reading some time ago that the issue of remembering passwords has more to do with the operating system version than Outlook. More specifically, Windows "Home" editions vs. business class. This seems to be true in our environment. Here's our configuration: - We use hosted Exchange 2007. (So I have no control over server settings.) - All users but me use Outlook 2007. I'm testing/using Outlook 2010 on Windows Vista (32) Home Premium and I receive the password prompt whenever I Open Outlook. - All employees work from their home office. - We are not using a domain with any of these computers. All of our Windows business class users (whether Vista Business or XP Prof.) are not prompted for password entry whereas all of our Windows Home Premium users are prompted. Have you found this to be the case with your clients? However, I'd like to give your solution a try. As stated above I'm running Windows Home Premium and Outlook 2010. I need a bit more instruction on configuring environment. Can you provide more details on where and how to set this up? Thanks... Steve
-
2010년 7월 28일 수요일 오후 3:40
It should be the same configuration from above for the Home editions. I'll setup a test in VM today and give it a try with a XP Home edition and see what I find. But in vista and 7 you can go to control Panel -> Credential Manager and save the needed credentials. The settings are the same for both Home and Pro of Vista and most Versions of 7; I dont think Home Basic can do save them. If you run into any problems let me know.
Thanks,
Brandon Fulton
MCITP: Exchange 2007/2010
Brandon Fulton Systems Engineer -
2010년 8월 10일 화요일 오전 7:40If you are using outlook 2010 try this solution, i just tried it and it worked for my work exchange account. http://www.msoutlook.info/question/481
-
2010년 8월 13일 금요일 오전 3:55Hi Brandon, I tried your method and it did work on my computer - however I am connecting remotely to another user at a different company and it didn't work on their computer. Hosted Exchange, MS Outlook 2010, Windows XP Pro, SP3. Not on a domain, using a local administrator account. Any advice?
-
2010년 9월 1일 수요일 오후 10:04
Interesting. I've tested this with our pilot and it is the solution. Our hosted exchange environment has however an internal domainname. This means that we will need to ask our customers to also trust that domainname - which is unknown to them (that, and the hosted domainname and the external domainname). And that all with a * setting. That really isn't very professional.
I've tried adding a UPN name (the external domainname) to the internal AD. But that doesn't seem to work.
Why? And is there another workaround, so we can still hide the internal domain name? -
2010년 11월 10일 수요일 오전 11:37
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 am using a hosted excahge server with www.apps4rent.com andcrom teh credential manager i did the following:- load credential manager
- Add a windows credential (upper right portion of the screen)
- server field = "*.hostallapps.com" no quotes
- filled in user name and password fields
- do the same steps above but for "*.hostallapps.net"
- closed credential manager
- opened outlook and it was all done and working
**note**
windows 7, x86 with outlook 2010
these instruction are so the next poor guy can find how to add a credential manually as it took me awhile to find that "add windows credential" link. As of Nov 10, 2010 this works.
-
2011년 1월 4일 화요일 오전 10:20
This is the only way I've been able to get password prompting to go away. Actually you only have to manually enter the *.contoso.local credentials. Having this pre-loaded will allow the user to click on 'remember my password' and have it actually save the password. Perhaps if we had rigged it so that the internal and external FQDNs matched.
This is a step backwards for us. On the 2003 server password prompting seemed solved. Also, having to tell a user to go into credentials and do this is a support nightmare. We can't do it 'for them' because we don't want to know their passwords. Not to mention when the password changes.
As a possible work-around - has anyone front-ended (or scripted) a way to make the entry in credentials manager so at least we could give people an 'update my saved password' icon.
-
2011년 1월 10일 월요일 오후 10:15
Hello John,
Thanks very much. Works perfectly!!!! I was convinced there should be an answer. Finaly I found your solution over here!
Regards Marc from the Netherlands.
-
2011년 1월 10일 월요일 오후 10:20
OK so the command line to run on the client to add the credentials for the local domain:
cmdkey /add:*.contoso.local /user:testuser@contoso.com /pass:password
-
2011년 5월 30일 월요일 오후 1:16
-
2011년 6월 17일 금요일 오전 6:39
Tried all solutions here but no help. My config:
Windows 7, Outlook 2010, windows in local domain: mydomain.local. In outlook I have one profile. It uses hosted Exchange and my e-mail account is xxx.xxx@domain1.com. Now I recently added two e-mail accounts into the same profile. They both use MS Exchange Online. First one is xxx@domain2.com and second zzz@domain2.com
My problem is, that every time I start Outlook it will ask credentials for xxx@domain2.com and zzz@domain2.com. Outlook/Windows does remember the user name for both but not the passwords.
I have tried to store them and also used Win Control Panel tool Credential Manager to wipe out the stored ones and entered manually new ones there. No help. Outlook is still asking passwords everytime.
My guess is that this is not a Windows based issue but a problem in Outlook. Seems a lot of people are strugling with similar issue. Hope above information helps Outlook guys to solve the problem.
Note: I had even more twisted problem earlier: when I started Outlook it asked twice credentials for xxx@domain2.com. I found out that the credentials for xxx@domain2.com was stored twice in Credential Manager: once under Windows Credentials and second time in Generic Credentials. Removing xxx@domain2.com entry from Generic Credentials solved this problem, now I "only" need to give password once when starting Outlook.
-
2011년 6월 24일 금요일 오전 9:32Hi John,
I couldn't get this to work for me. Would you mind offering a little more guidance for my setup?
Win vista
Outlook 2010
I freelance so have access to various clients exchange email accounts.
I have 4 exchange accounts in Outlook 2010 and one Hotmail account. Two of the exchange accounts are with the same exchange hosting company but for different clients of mine, one is with the same hosting company but is my own hosted exchange account, and the last is with a client of mine who manage their exchange internally. .
When I open outlook, I have to enter the login password for all 4 of them so I tried you fix but just couldn't get it to work and I think it's due to not knowing 100% what the server name is and what the domain name is.
Where is the best place to find these?
Many thanks,
Chris
-
2011년 7월 18일 월요일 오후 7:28I found a very simple solution to this problem. Go to your C drive and right click on Users. Select Properties and uncheck the Read-only checkbox. Press Apply. This solved my Outlook password problem and a problem I was having with IE 9.
- 답변으로 제안됨 KenDen2 2011년 7월 18일 월요일 오후 7:28
- 답변으로 제안 취소됨 Spiderkingbeemer 2011년 7월 19일 화요일 오전 1:24
-
2011년 7월 19일 화요일 오전 1:26KenDen2: I don't recommend your solution, though it may have worked for you. The better solution here is to add proper credentials to credential manager as proposed Brandon above. The solution you describe is problematic from a security standpoint.
-
2011년 8월 20일 토요일 오후 8:45
I'm trying to use Hosted Exchange from Apps4Rent as well. I'm using XP Pro SP3 and Outlook 2003. Everything is updated. Using NTLM Authentication.
Although they all seem to be exactly the same place, I have tried:
- control userpasswords2
- control keymgr.dll
- Manage my network passwords.
In Stored User Names and Passowrds I have tried:
- *.hostallapps.com
- *.hostallapps.net
- EXMBX01.apps4rent.com
- EXMBX01.apps4rent.net
- EXMBX01.apps4rent.info.com
- EXMBX01.apps4rent.info.net
- EXMBX01.hostallapps.com
- EXMBX01.hostallapps.net
I think I have tried them alone, in pairs, and all together. None of this worked or even behaved differently.
I still get asked for the Username and Password. I enter that and check the box to remember the password, exit Outlook, verifyt that it is closed using Task Manager, then I repeat it again (strange, but as instructed), try it again, and still get asked for the Username and Password. The Username is there, but the Password is still required.
Ultimately, I get it to login with the Username and Password I supply, so I think my other Mail settings are correct.
I tried the OutlookAutologin.exe. That works, but I end up getting an Error 0x8994010F error. I suspect this is going to cause me more difficulty down the line and I'd really like to just learn how to get XP/Outlook to remember the password and be done with it.
What am I missing?
-
2011년 8월 21일 일요일 오후 4:26
I don't see *.apps4rent.com in your list. Have you tried this?
What is the primary domain name of the server(s) you're authenticating against? (app4rent.com? hostallapps.com?). Whatever those domains are you need create a wildcard entry in key manager or credential manager for those servers. Also, clear all other entries for the primary domain names before creating the wildcard entries. You only need one entry for each primary domain name.
- 답변으로 제안됨 Jundan WuAdministrator 2011년 8월 21일 일요일 오후 4:50
-
2011년 8월 22일 월요일 오후 12:23
I'm new to this, so I just do what the host site tells me to do -- to begin with. After that it is a steep learning curve.
The host sites's instructions at http://www.apps4rent.com/support/kb/article/000213 included the "EXMBX01." Surmizing from Spiderkingbeemer's note, I guess that EXMBX01 is the primary domain name of the server(s).
In my case, making entries for both *.apps4rent.com and *.apps4rent.net worked as Spiderkingbeemer's response suggested. THANK YOU Brandon and Spiderkingbeemer !!!
I wish that apps4rent would simply have provided the comprehensive answer, but they just provide a tailored version of the help at http://support.microsoft.com/kb/820281. This site and a couple of others were onto the need for saving passwords to two places. The wildcard "*." seems to be a key because my use of EXMBX01.apps4rent.com with concurrent use of EXMBX01.apps4rent.net did not work.
The purpose of the rest of this note is to provide the suite of information consistent with this solution particular case in the hope that others can adapt it to their parallel situation. Additionally, I'd appreciate knowing what other things the wild card may be satisfying.
The mail account settings include:
- Microsoft Exchange Server -- EXMBX01.apps4rent.net
- User Name -- XXX@XXX.apps4rent.info
- URL for proxy server -- webmail.apps4rent.com
- Principle for proxy server -- msstd:webmail.apps4rent.com
- Authentication is NTLM Authentication
- Let me know if there is another piece missing and I'll provide it.
Thanks to all for providing what seems to be a solid solution. The only residual trouble I seem to have is that I get the following error when I do a Send/Recieve. Task 'Microsoft Exchange Server' reported error (0x8004010F) : 'The operation failed. An object could not be found.'
Any ideas?
-
2011년 8월 30일 화요일 오후 5:15
After dealing with the same issue and applying all kinds of "possible solutions" we tried the following: On the Exchange IIS manager, open the SSL settings for autodiscover; we found that users were require to use SSL but the Ignore client's request was checked; we changed to Accept and restarted IIS. No more password pop-ups (we are using outlook versions 2003, 2007 and 2010 across the organization). Happy users for the last two days...
RC- 답변으로 제안됨 scarboni888 2012년 8월 11일 토요일 오후 1:37
-
2011년 10월 6일 목요일 오전 8:25
Hi, Please help me on authentication issue.
the outlook version varies 2003, 2007 & 2010 users to users and os (xp / vista / 7)
Exchange - 2010 standard
all 3 version facing issue. The same users able to login to OWA, but when login to outlook, this authentication issue comes.
The password is not being accepted. Then i checked the settings and in under connection i saw it was in BASIC, which i changed to NTLM, then restart outlook and it started to work.
But when outlook is restarted again same problem of authentication.
Note: we have 2 domain and this issue coming for only one domain users. the other domain users didnt have any of the mentioned problem of authentication
Tks & rgds. Narayanan -
2011년 10월 6일 목요일 오전 9:22nope.. did that, still asking.. help me pleaseeeeeeeeee..
Tks & rgds. Narayanan -
2011년 12월 29일 목요일 오전 12:35
Same here.
I am using Go Daddy's Hosted Exchange...
mail.ex2.secureserver.net
*.ex2.secureserver.net
*.mail.ex2.secureserver.net
Please help
-
2012년 4월 12일 목요일 오후 7:07
I am using the same platforms: Exchange 2010 with Outlook 2007/2010 and Windows XP/7.
It is a nuisance now. Any updates on it?
-
2012년 5월 10일 목요일 오후 8:26
Worked for me.
RPC over HTTP
Windows XP
Outlook 2010
Thanks
Elgin Green
-
2012년 8월 11일 토요일 오후 1:45
After dealing with the same issue and applying all kinds of "possible solutions" we tried the following: On the Exchange IIS manager, open the SSL settings for autodiscover; we found that users were require to use SSL but the Ignore client's request was checked; we changed to Accept and restarted IIS. No more password pop-ups (we are using outlook versions 2003, 2007 and 2010 across the organization). Happy users for the last two days...
RC
This worked for me with a new installation of Exchange 2010 and so far three client scenarios:
1) Outlook 2007 on a non-domain Vista Home Basic machine
2) Outlook 2003 on a domain-enabled off-site Windows XP Pro machine
3) Outlook 2010 on a domain-connected Windows 7 Pro machine
Using NTLM authentication and a certificate which uses a completely different external domain name than the internal NT domain name.
I was lucky enough to try this solution first before making any other of the myriad proposed changes so know that it was this and this only that solved the problem.

