CNAME Autodiscover already exists

ตอบทั้งหมด

• 27 ตุลาคม 2554 15:53

   

   
  

  0

  You need to update at point of change or a bit before to allow for DNS propagation for straight/cut over migrations

  Co-existence situations are different see below *

  This is from microsoft

  Create or update your autodiscover CNAME DNS record; for example: autodiscover.<your domain> CNAME autodiscover.outlook.com. If your domain is contoso.com, then the DNS record would be “autodiscover.contoso.com CNAME autodiscover.outlook.com”. For more information, see Enable Outlook to Connect.

  http://www.microsoft.com/online/help/en-us/helphowto/8939e90a-59dc-4f0f-aec0-19a899c0af75.htm

  * If you already have an autodiscover DNS record for your current on-premises Exchange environment, then you do not need to set up another autodiscover record, as long as each BPOS mailbox has a corresponding mail-enabled account on the on-premises Exchange server.

  ---

  Spudney
   
• 1 พฤศจิกายน 2554 22:21

   

   
  

  0

  If it is not a co-existence setup with an on-premise Exchange environment, but a transition from BPOS to Office 365, will changing the autodiscover CNAME before the transition cause any issues? I haven't been able to pinpoint if there's any document from Microsoft specifying what results to expect from changing the autodiscover CNAME in preparation for transition. I can only guess that it would break current free/busy and Out of Office capabilities, etc, with current BPOS users in Outlook as I haven't seen otherwise.

  Currently the autodiscover CNAME on the domain is pointing to autodiscoverredirect-red001.mail.microsoftonline.com

  
  

  • แก้ไขโดย sethgi 1 พฤศจิกายน 2554 22:34
  •  
   
• 22 พฤศจิกายน 2554 23:46

   

   
  

  0

  Hi Sethgi, I would NOT change the Autodiscover CNAME record until your Transition is complete.  Autodiscover serves a few features, such as directing Outlook clients where to connect based on their email address (i.e. user@contoso.com --> Look for Autodiscover.contoso.com --> take results and connect to endpoint, authenticate and connect!

  So most people wait on their CNAME change over as this can affect Outlook clients when attempting to create Outlook Profiles and connect.  It is also seen when Outlook is looking for Messaging Web Services, like Free/Busy, Ofline Address Book (OAB) and other services.  SO I would not change your AutoD CNAME record until after you have Transitioned.

   

  HTH

  ---

  Ryan J. Phillips
   
• 22 พฤศจิกายน 2554 23:53

   

   
  

  0

  While I agree with Ryan's recommendation, it's the exact opposite of what Microsoft is telling us to do.  The "Perform tasks before transition" section of http://www.microsoft.com/online/help/en-us/helphowto/8939e90a-59dc-4f0f-aec0-19a899c0af75.htm instructs us to Update DNS settings in step 4.

  ---

  James Mayes Nims & Associates IT Consultants www.nimsassociates.com

  • เสนอเป็นคำตอบโดย Daniel Trautman 13 ธันวาคม 2554 3:27
  •  
   
• 13 ธันวาคม 2554 3:27

   

   
  

  0
  The reason for changing the AutoDiscover record pre-tranisition is that users with the Sign-in client for BPOS have their AutoDiscover registry keys changed to specifically point to BPOS instead of using your DNS record.  It is safe to do so prior to the transition.

  ---

  If it wasn't difficult, it wouldn't be fun, but why's it got to be this much fun.

  • เสนอเป็นคำตอบโดย Daniel Trautman 13 ธันวาคม 2554 3:27
  •  
   
• 5 มกราคม 2555 19:27

   

   
  

  0

  I changed our autoD CNAME and it was NOT safe.  Users began receiving login prompts to the new service, which, because they hadnt yet changed their passwords would fail continually and thus raised a slew of problem reports about Outlook being unavailable.  Changing the CNAME back made the authentication popups go away.

   

  We will disregard Microsoft's instructions to change it before hand and wait for the actual cutover...

   
• 10 มกราคม 2555 17:24

   

   
  

  0

  I changed our autoD CNAME and it was NOT safe.  Users began receiving login prompts to the new service, which, because they hadnt yet changed their passwords would fail continually and thus raised a slew of problem reports about Outlook being unavailable.  Changing the CNAME back made the authentication popups go away.

   

  We will disregard Microsoft's instructions to change it before hand and wait for the actual cutover...

  Microsoft's handling of this transition has been about as subtle as the Gestapo!  If you are a hosted exchange only client their instructions have been misleading at best and flat out wrong in many cases as the above clearly illustrates!  Good Luck all!  Here's hoping my users still have email on Monday!
  
  I would definitely NOT change DNS settings until the transition has been completed and don't forget to update MX records as well.  Fortunately the days are (mostly) long gone where DNS changes really did take 72 hours to propagate, so you should see the changes take effect within a couple of hours.

   
• 13 มกราคม 2555 20:01

   

   
  

  2
  I'm not sure what you are talking about, I have done several transititons over the last few months and Microsoft has been spot on. If I did have a question their support was always quick to respond and very helpful. As far as changing any DNS records I think anyone in the admin role knows you do not do this until the actual cutover which is always on a weekend. My actual transition started last night and that is when I changed my DNS records for exchange and Lync and I have had no issues so far.