*this appears to be outdated but perhaps helpful still*Īfter several attempts of trying to configure Outlook using the wizard - I decided to configure Outlook manually. Now, with Outlook running on a desktop, hold the Ctrlīutton, right-click on the Outlook icon in the system tray, and select Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl,ĥ. Check that the autodiscover virtual directory is gone: You will have to confirm by typing a “Y”.Ĥ. Remove-AutodiscoverVirtualDirectory –Identity In the Exchange Management Shell, remove the autodiscover virtual
>Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl,Ĭopy the Identity value to the clipboard.ģ. The current autodiscover virtual directory: Open an elevated Exchange Management Shell and retrieve %windir%\system32\inetsrv\appcmd.exe add backup "Before RemovingĢ. Open an elevated command prompt and back up the IIS configuration Shell to entirely remove the Autodiscover Virtual Directory using Remove-AutodiscoverVirtualDirectory. The support manager recommended that I instead use the Exchange Management Services does work, it’s probably not the “approved” way to do things. While editing the Service Connection Point in Active Directory Sites and Getting Outlook to Autodiscover Office 365 So the solution is still to send the email to an account outside your domain,īut you can use your custom subdomain on Office 365:
I had removed thatĪlias but was able to re-add it through the Online Exchange mailboxĬonfiguration screen, under E-Mail Options. If my primary email Office 365 lets me as well. The support manager reminded me that Office 365 offers an email alias in the Updated suggestions to the problems identified in the first version of this article. You're probably already fine there, but just in case, it wouldn't hurt to verify.Īfter working with a very helpful Microsoft Support manager, here are some Pay special attention to MX, TXT, SRV, CNAME records. This has been driving us crazy ever since they migrated us to Office 365.Īlso verify all your DNS records have been added per MS intstuctions in your Office365 admin site. If anyone has had this issue and knows the fix, please let me know. This issue probably happens in about 5% of our users. It is a big deal when these are billable employees with 4 gig mailboxes and a large amount of time is being wasted. MS acts like it is not big deal to just create a new profile. We have even deleted accounts and created a new account with a new address and still had the issue. MS support answer is always to do a repair which never works, and then when that fails they say to create a new profile, which also never works. We never had this when we had our in house Exchange or BPOS. Used Auto Discover, all DNS entries were correct. We used the setup option that installs MS Online Services Sign-in Assistant. When we went from BPOS to Office 365 everything was done the way it was suppose to be done. As you can imagine this is extremely annoying.
Some have to enter it five times and then do a captcha.
EXCHANGE CLIENT ACCESS SERVER NAME OFFICE 365 PASSWORD
The remember password box is checked but they still get prompted. We continue to have an issue with our Office 365 email in the Outlook 2007 client where some users are continually prompted for a password.
0 kommentar(er)
