Our Windows 2008 SBS Server with Exchange 2007 was working just fine until we installed a recent batch of updates, and suddenly all the clients were getting the pop-up.
I did what glenknight suggested and the pop-ups have immediately gone away.
This will get the users off our back so that we can schedule the upgrade to MS Exchange 2007 SP2, with better preparation.
you all guys are facing issue with exchange 2007. Well here is an upgraded version problem. Exchange 2010 with Winxp and Office 2007 has the same issue. Its the problem with outlook 2007.The password doesnt get saved.I installed outlook 2010 on the same machine its gone.In win7 with outlook 2007 thr is no prb. Win xp with outlok 2007 has isue.believe me :)
here is a possible solution. worked for me on windows 7, outlook 2010, exchange 2010.
in the control panel there is the credential manager, go into the credential manager and update each set of credentials to be the user in question, even if the username appears right, type the passwords again.
in my case, i had a reference to the administrator account which outlook kept asking my user to provide. changed that to his account and all was fine.
I know some folks may have found these posts via Google as did I. I found like most that most suggested solutions did not work. The reason I have found is that there are several areas that need to be corrected before this problem goes away.
scenario: MS-Outlook 2010, Windows 7 (logged into domain), Exchange Server 2007
1. in the workstations user accounts area, REMOVE any references to outlook accounts 2. In the servers IIS manager, check the authentication under Autodiscover. (under sites->sbs web applications->autodiscover) Windows Authentication should be the only one enabled. 3. Have the correct autodiscover parameter defined. In the Exchange server powershell (example: Set-ClientAccessServer -Identity internal-server-name.internal-domain -AutoDiscoverServiceInternalUri https://autodiscover-hostname.domain/Autodiscover/Autodiscover.xml)
Be sure to restart the web publishing service after you make your changes in IIS.
If you do all of the above you should find your problem magically disappears. I found these out through much pain and toil so hopefully you will find that this works for you as well.
I know some folks may have found these posts via Google as did I. I found like most that most suggested solutions did not work. The reason I have found is that there are several areas that need to be corrected before this problem goes away.
scenario: MS-Outlook 2010, Server 2008, Windows 7 (logged into domain), Exchange Server 2007
1. in the workstations user accounts area, REMOVE any references to outlook accounts
2. In the servers IIS manager, check the authentication under Autodiscover. (under sites->web applications->autodiscover) Windows Authentication should be the only one enabled.
Be sure to restart the web publishing service after you make your changes in IIS.
If you do all of the above you should find your problem magically disappears. I found these out through much pain and toil so hopefully you will find that this works for you as well.
< Message edited by smartguyus -- 25.Jan.2012 2:47:46 PM >
pretty sure IIS has nothing to do with it unless the client is connecting using RPC over HTTP. if its just a local direct connection to the server, then IIS will not be in your way.