Advertisement
Hi all,<\/p>\n
I’ve got about 150 users on 5 RDS servers and most of them are working fine however we’ve been getting about 2 or 3 a day whereby their Outlooks that have been working fine and then suddenly close and then won’t open again and come up with the “cannot open the set of folders” error. If we close and re-open Outlook we get the same error but also even if we delete the profile and re-create it we then get errors saying “outlook cannot log on, Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable”. or it gives us the prompt to setup a new profile but then fails saying “something went wrong” and then the options to Change Account settings etc<\/p>\n
We know the connection is there as it’s an RDS and others are on it and working fine and we have AD Sync with their email addresses as the UPN so when we try to create a new profile it picks up the correct details.<\/p>\n
We were in Hybrid mode so now we have email going into our on prem spam filter and then direct to Office 365 (not that i think that’s the issue) and i’ve nulled the SCP lookup record on the On Prem Exchange 2016 server, amended the local and external DNS to point autodiscover to Office 365<\/p>\n
We have found that on some of these if we log them off and then onto another RDS that it resolves itself but some don’t and so we’ve had to get them to use OWA for the interim but then found that it works fine the next day or for the one’s it WAS working for then it’s stopped maybe later that day or a couple of days down the road.<\/p>\n
I’ve ran SARA as advised on another post (that i can no longer find so apologies if whoever helped me on there thinks I’ve ignored them and just started a new post) but that comes back with no errors.<\/p>\n
I’ve tried adding the root domain lookup exclusion in a users registry also but this hasn’t worked either.<\/p>\n
I’ve just tried the Connectivity Analyzer and i haven’t used it for a few years and there are a lot more options on there but i couldn’t find just an “office 365 test” so i’ve tried the single sign on but it says that my domain isn’t a federate domain so not sure if this is part of the issue or something i can ignore ?<\/p>\n
Either way it’s a sporadic issue that seems to be related i guess to some sort of lookup either for the domain or the users creds/mailbox etc but i cannot figure out where.<\/p>\n
Any ideas would be great.<\/p>\n
Thanks<\/p>","upvoteCount":1,"answerCount":6,"datePublished":"2022-01-06T12:49:44.000Z","author":{"@type":"Person","name":"spiceuser-xw374","url":"https://community.spiceworks.com/u/spiceuser-xw374"},"suggestedAnswer":[{"@type":"Answer","text":"
Hi all,<\/p>\n
I’ve got about 150 users on 5 RDS servers and most of them are working fine however we’ve been getting about 2 or 3 a day whereby their Outlooks that have been working fine and then suddenly close and then won’t open again and come up with the “cannot open the set of folders” error. If we close and re-open Outlook we get the same error but also even if we delete the profile and re-create it we then get errors saying “outlook cannot log on, Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable”. or it gives us the prompt to setup a new profile but then fails saying “something went wrong” and then the options to Change Account settings etc<\/p>\n
We know the connection is there as it’s an RDS and others are on it and working fine and we have AD Sync with their email addresses as the UPN so when we try to create a new profile it picks up the correct details.<\/p>\n
We were in Hybrid mode so now we have email going into our on prem spam filter and then direct to Office 365 (not that i think that’s the issue) and i’ve nulled the SCP lookup record on the On Prem Exchange 2016 server, amended the local and external DNS to point autodiscover to Office 365<\/p>\n
We have found that on some of these if we log them off and then onto another RDS that it resolves itself but some don’t and so we’ve had to get them to use OWA for the interim but then found that it works fine the next day or for the one’s it WAS working for then it’s stopped maybe later that day or a couple of days down the road.<\/p>\n
I’ve ran SARA as advised on another post (that i can no longer find so apologies if whoever helped me on there thinks I’ve ignored them and just started a new post) but that comes back with no errors.<\/p>\n
I’ve tried adding the root domain lookup exclusion in a users registry also but this hasn’t worked either.<\/p>\n
I’ve just tried the Connectivity Analyzer and i haven’t used it for a few years and there are a lot more options on there but i couldn’t find just an “office 365 test” so i’ve tried the single sign on but it says that my domain isn’t a federate domain so not sure if this is part of the issue or something i can ignore ?<\/p>\n
Either way it’s a sporadic issue that seems to be related i guess to some sort of lookup either for the domain or the users creds/mailbox etc but i cannot figure out where.<\/p>\n
Any ideas would be great.<\/p>\n
Thanks<\/p>","upvoteCount":1,"datePublished":"2022-01-06T12:49:44.000Z","url":"https://community.spiceworks.com/t/outlook-federation-issue/821322/1","author":{"@type":"Person","name":"spiceuser-xw374","url":"https://community.spiceworks.com/u/spiceuser-xw374"}},{"@type":"Answer","text":"
Just as an additional note that another user i’ve tried to fix is now getting “The set of folders cannot be opened. Microsoft Exchange is currently busy” ? Not sure if this helps but also didn’t know if it’s worth me adjusting the internal and external autodiscover url on the on prem exchange to point to Office 365 (even though i’ve nulled the scp) ?<\/p>","upvoteCount":0,"datePublished":"2022-01-06T13:05:36.000Z","url":"https://community.spiceworks.com/t/outlook-federation-issue/821322/2","author":{"@type":"Person","name":"spiceuser-nxrk7","url":"https://community.spiceworks.com/u/spiceuser-nxrk7"}},{"@type":"Answer","text":"
When you say AD Sync, hopefully you mean Azure AD Connect? AAD Sync is now legacy. Moreover, although Connect is set to auto-update by default, it might not be working and is at least worth looking into, e.g. what version of the tool is installed. For anyone still on Sync, you’d have to perform a swing migration as a direct in-place upgrade isn’t supported – see below:<\/p>\n