{"id":175,"date":"2014-11-28T04:33:54","date_gmt":"2014-11-28T04:33:54","guid":{"rendered":"http:\/\/www.torontohelpdesk.ca\/blog\/?p=175"},"modified":"2014-12-29T14:34:10","modified_gmt":"2014-12-29T14:34:10","slug":"office-365-migration-from-sbs-outlook-defaults-to-server","status":"publish","type":"post","link":"http:\/\/www.torontohelpdesk.ca\/blog\/office-365-migration-from-sbs-outlook-defaults-to-server\/","title":{"rendered":"Office 365 Migration from SBS &#8211; Outlook defaults to server"},"content":{"rendered":"<p><strong>Problem:<\/strong><\/p>\n<p>You&#8217;ve setup all the A, CNAME, MX records etc. for your migration of email to Office 365 from SBS 2008 or 2011. Every time you try adding the account, it defaults to the existing server.<\/p>\n<p><strong>Solution:<\/strong><\/p>\n<p>Autodiscover is configured to pull info off the server and not Microsoft. Unfortunately, I don&#8217;t know where I get this document so I can&#8217;t credit anyone for it. Be sure that I didn&#8217;t discover this:<\/p>\n<p>While editing the Service Connection Point in Active Directory Sites and Services does work, it\u2019s probably not the \u201capproved\u201d way to do things.<\/p>\n<p><em>The support manager recommended that I instead use the Exchange Management Shell to entirely remove the Autodiscover Virtual Directory using Remove-AutodiscoverVirtualDirectory. Here\u2019s how I did that:<\/em><\/p>\n<ol>\n<li><em>Open an elevated command prompt and backup the IIS configuration (explained here):<br \/>\n<\/em><em>%windir%\\system32\\inetsrv\\appcmd.exe add backup \u201cBefore Removing Autodiscover\u201d<\/em><\/li>\n<li><em>Open an <strong>elevated<\/strong> Exchange Management Shell and retrieve the current Autodiscover virtual directory:<br \/>\n<\/em><em>Get-AutodiscoverVirtualDirectory | fl Name, Server, InternaUrl, Identity<\/em><\/li>\n<\/ol>\n<p><em>Copy the Identity value to the clipboard<\/em><\/p>\n<ol start=\"3\">\n<li><em>In the Exchange Management Shell, remove the autodiscover virtual directory:<br \/>\n<\/em><em>Remove-AutodiscoverVirtualDirectory \u2013Identity \u201c&lt;identity value retrieved above&gt;\u201d<\/em><\/li>\n<\/ol>\n<p><em>You will have to confirm by typing a \u201cY\u201d.<\/em><\/p>\n<ol start=\"4\">\n<li><em>Check that the autodiscover virtual directory is gone:<br \/>\n<\/em><em>Get-AutodiscoverVirtualDirectory | fl Name, Server, InternaUrl, Identity<\/em><\/li>\n<\/ol>\n<p><em>This should now return nothing.<\/em><\/p>\n<ol start=\"5\">\n<li><em>Now, with Outlook running on the desktop, hold the<strong> Ctrl<\/strong> button, right-click on the Outlook icon in the system tray, and select <strong>Test E-mail AutoConfiguration<\/strong>. Enter your email address and password and click the <strong>Test<\/strong> The results should come back from Office 365 server.<\/em><\/li>\n<\/ol>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Problem: You&#8217;ve setup all the A, CNAME, MX records etc. for your migration of email to Office 365 from SBS 2008 or 2011. Every time you try adding the account, it defaults to the existing server. Solution: Autodiscover is configured <a class=\"more-link\" href=\"http:\/\/www.torontohelpdesk.ca\/blog\/office-365-migration-from-sbs-outlook-defaults-to-server\/\">Continue reading <span class=\"screen-reader-text\">  Office 365 Migration from SBS &#8211; Outlook defaults to server<\/span><span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,5,64,18,24],"tags":[98,99,47],"class_list":["post-175","post","type-post","status-publish","format-standard","hentry","category-exchange","category-office","category-office-365","category-sbs-2008","category-sbs-2011","tag-migration","tag-office-365","tag-sbs"],"_links":{"self":[{"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/comments?post=175"}],"version-history":[{"count":2,"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/175\/revisions"}],"predecessor-version":[{"id":183,"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/175\/revisions\/183"}],"wp:attachment":[{"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/media?parent=175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/categories?post=175"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/tags?post=175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}