Outlook / Exchange Online launch issue
-
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@travisdh1 said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
Re: Outlook 2016 Cannot Open Because of Set of Folders
Forking... Yay, I just ran into a WTF issue as well with Outlook. User 1 works fine. Outlook 2016, using O365 Essentials licensing. User 2 is on the same PC and can connect the client via IMAP, but not Exchange. Throws this lovely error. Tried a reinstall, Office removal tool, no avail.
Dumb questions from me time. Same domain?
Yep, PC is on the domain, email address shows correct domain. Verified the user has a mailbox and proper licensing.
Is Autodiscover setup properly?
Actually, it looks like it is autodiscover. Autodiscover passed by running a connectivity test externally. But after installing a Microsoft analyzer on the user's workstation, it failed and said that https://companywebsite.com/autodiscover/autodiscover.xml is interfering. No idea currently who is hosting their company site (already checked their registrar). I'll have to talk to their marketing individual tomorrow.
-
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@travisdh1 said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
Re: Outlook 2016 Cannot Open Because of Set of Folders
Forking... Yay, I just ran into a WTF issue as well with Outlook. User 1 works fine. Outlook 2016, using O365 Essentials licensing. User 2 is on the same PC and can connect the client via IMAP, but not Exchange. Throws this lovely error. Tried a reinstall, Office removal tool, no avail.
Dumb questions from me time. Same domain?
Yep, PC is on the domain, email address shows correct domain. Verified the user has a mailbox and proper licensing.
Is Autodiscover setup properly?
Resolved. HKEY_CURRENT_USER > Software > Microsoft > Office > 15.0 > Outlook > Autodiscover . Within Autodiscover add a DWORD (32 bit Value) with the name ExcludeHttpsRootDomain and set the value to 1.
I am not alone... https://community.spiceworks.com/topic/795327-weird-autodiscover-issue
-
@bbigford said in Outlook / Exchange Online launch issue:
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@travisdh1 said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
Re: Outlook 2016 Cannot Open Because of Set of Folders
Forking... Yay, I just ran into a WTF issue as well with Outlook. User 1 works fine. Outlook 2016, using O365 Essentials licensing. User 2 is on the same PC and can connect the client via IMAP, but not Exchange. Throws this lovely error. Tried a reinstall, Office removal tool, no avail.
Dumb questions from me time. Same domain?
Yep, PC is on the domain, email address shows correct domain. Verified the user has a mailbox and proper licensing.
Is Autodiscover setup properly?
Resolved. HKEY_CURRENT_USER > Software > Microsoft > Office > 15.0 > Outlook > Autodiscover . Within Autodiscover add a DWORD (32 bit Value) with the name ExcludeHttpsRootDomain and set the value to 1.
I am not alone... https://community.spiceworks.com/topic/795327-weird-autodiscover-issue
Yeah, I have done this before an the Exclude SCP too.
-
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@travisdh1 said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
Re: Outlook 2016 Cannot Open Because of Set of Folders
Forking... Yay, I just ran into a WTF issue as well with Outlook. User 1 works fine. Outlook 2016, using O365 Essentials licensing. User 2 is on the same PC and can connect the client via IMAP, but not Exchange. Throws this lovely error. Tried a reinstall, Office removal tool, no avail.
Dumb questions from me time. Same domain?
Yep, PC is on the domain, email address shows correct domain. Verified the user has a mailbox and proper licensing.
Is Autodiscover setup properly?
Resolved. HKEY_CURRENT_USER > Software > Microsoft > Office > 15.0 > Outlook > Autodiscover . Within Autodiscover add a DWORD (32 bit Value) with the name ExcludeHttpsRootDomain and set the value to 1.
I am not alone... https://community.spiceworks.com/topic/795327-weird-autodiscover-issue
Yeah, I have done this before an the Exclude SCP too.
What does SCP mean in regards to Exchange? I only know it as Secure Copy Protocol.
-
@bbigford said in Outlook / Exchange Online launch issue:
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@travisdh1 said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
Re: Outlook 2016 Cannot Open Because of Set of Folders
Forking... Yay, I just ran into a WTF issue as well with Outlook. User 1 works fine. Outlook 2016, using O365 Essentials licensing. User 2 is on the same PC and can connect the client via IMAP, but not Exchange. Throws this lovely error. Tried a reinstall, Office removal tool, no avail.
Dumb questions from me time. Same domain?
Yep, PC is on the domain, email address shows correct domain. Verified the user has a mailbox and proper licensing.
Is Autodiscover setup properly?
Resolved. HKEY_CURRENT_USER > Software > Microsoft > Office > 15.0 > Outlook > Autodiscover . Within Autodiscover add a DWORD (32 bit Value) with the name ExcludeHttpsRootDomain and set the value to 1.
I am not alone... https://community.spiceworks.com/topic/795327-weird-autodiscover-issue
Yeah, I have done this before an the Exclude SCP too.
What does SCP mean in regards to Exchange? I only know it as Secure Copy Protocol.
Service Control Point
http://jetzemellema.blogspot.com/2015/10/how-to-remove-exchange-autodiscover-scp.html?m=1 -
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@dbeato said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
@travisdh1 said in Outlook / Exchange Online launch issue:
@bbigford said in Outlook / Exchange Online launch issue:
Re: Outlook 2016 Cannot Open Because of Set of Folders
Forking... Yay, I just ran into a WTF issue as well with Outlook. User 1 works fine. Outlook 2016, using O365 Essentials licensing. User 2 is on the same PC and can connect the client via IMAP, but not Exchange. Throws this lovely error. Tried a reinstall, Office removal tool, no avail.
Dumb questions from me time. Same domain?
Yep, PC is on the domain, email address shows correct domain. Verified the user has a mailbox and proper licensing.
Is Autodiscover setup properly?
Resolved. HKEY_CURRENT_USER > Software > Microsoft > Office > 15.0 > Outlook > Autodiscover . Within Autodiscover add a DWORD (32 bit Value) with the name ExcludeHttpsRootDomain and set the value to 1.
I am not alone... https://community.spiceworks.com/topic/795327-weird-autodiscover-issue
Yeah, I have done this before an the Exclude SCP too.
What does SCP mean in regards to Exchange? I only know it as Secure Copy Protocol.
Service Control Point
http://jetzemellema.blogspot.com/2015/10/how-to-remove-exchange-autodiscover-scp.html?m=1Ah, right. I had forgotten about that.
-
We had to do some weird voodoo to get our Autodiscover to work in a hybrid scenario.
-
@brrabill said in Outlook / Exchange Online launch issue:
We had to do some weird voodoo to get our Autodiscover to work in a hybrid scenario.
I honestly can't remember what I had to do the one time I did a hybrid setup, as it's been about 3 years. What did you have to do?
-
@bbigford said in Outlook / Exchange Online launch issue:
@brrabill said in Outlook / Exchange Online launch issue:
We had to do some weird voodoo to get our Autodiscover to work in a hybrid scenario.
I honestly can't remember what I had to do the one time I did a hybrid setup, as it's been about 3 years. What did you have to do?
I create a folder on the local hard drive stipulating what servers to look to.
I also create registry entries to force Outlook to use the local file first.
-
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover]
"OURDOMAIN.com"="C:\autodiscover\autodiscover.xml"
"ExcludeScpLookup"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeHttpsAutodiscoverDomain"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeSrvLookup"=dword:00000001
"ExcludeSrvRecord"=dword:00000001
"PreferLocalXML"=dword:00000001