3
votes
Accepted
Local DNS after Office 365 migration
Outlook, uses "Autodiscover" to find out where the user mailbox is, as long as you have Exchange server running in your network, the users will always be pointed to that server before anything.
There ...
- 3,789
2
votes
Migrated SBS 2003 to SBS 2011 and my Outlook clients didn't get the new server name
Like Twisty stated, your Outlook clients need to be told what to do.
Exchange 2003 would tell your clients where their new home is. But because you pulled the old server, they cannot get those ...
- 21
2
votes
Accepted
Post Exchange Setup Issues - Can't connect
Microsoft Office/Outlook 2003 support only "MAPI over RPC" while Microsoft Exchange 2016 only supports "MAPI over http". According to the Microsoft documentation here MS Outlook 2010 (with KB ...
- 2,838
1
vote
Accepted
Migrated SBS 2003 to SBS 2011 and my Outlook clients didn't get the new server name
I hate answering my own question.
As so often with Microsoft server software, I'm not totally certain how I solved the problem, but I didn't have to delete profiles, not did the details autofill.
I ...
- 91
1
vote
Migrated SBS 2003 to SBS 2011 and my Outlook clients didn't get the new server name
When migrating from Exchange on SBS 2003 to 2011, you must leave the old Exchange server running until all instances of Outlook have been started and had the chance to update their settings. Only then ...
- 3,010
1
vote
What is the cause of FAST I/O DISALLOWED errors? (Causing Outlook to open attachments really slowly)
at http://forum.sysinternals.com/what-is-fast-io-disallowed_topic23154.html is says:
It's benign but the explanation is a bit long.
Basically, for a few
I/O operations there are two ways that a ...
- 111
Only top scored, non community-wiki answers of a minimum length are eligible