Exchange Team Blog - All Comments

re: Released: Exchange Server 2013 RTM Cumulative Update 1

John M. Rode — Fri, 24 May 2013 14:01:44 GMT

I am wondering when CU2 is going to come out that will actually stabilize mail flow. Like many many many others - I have had to set the Hub Transport Service to restart ( which it does about every 4 to 6 hrs a day, every day). Today mail flow on the SMTP receive connector just decided to up and quit. after 2 reboots it began working again - but the point is - first a foremost Exchange Servers should be able to Send And Receive Mail - Second - Internal Domain Clients should be able to connect. Third and last - External OWA / Phone / And RPC. This new version - when something breaks - everything breaks. In the past at least I NEVER had to worry about the First TWO Primary functions.

By the Way config was Exchange 2003 - migrated to 2010 - Migrated to 2013 on a Server 2012 box with 12GB Ram Virtualized on Xenserver 6.5

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

Brian Day [MSFT] — Fri, 24 May 2013 00:47:09 GMT

@Sai Thanks, but truth be told there is a lot of work from a lot of folks that go into a post like this. The real king of CAS, who likes to wear shorts a lot, had a big hand in it. :)

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

Sai Prasad — Thu, 23 May 2013 23:04:16 GMT

Brian, I have internal OA setup, but do you mind recommending me go out and play XBox One.

Kidding apart, Great article and you are the best CAS out there.

re: Use Exchange Web Services and PowerShell to Discover and Remove Direct Booking Settings

Petri X — Thu, 23 May 2013 22:37:34 GMT

Big thanks to you all! This is so big help for us!

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

Brian Day [MSFT] — Thu, 23 May 2013 21:29:29 GMT

@DirtyGoat, when I was a couple years old I was once knocked down by a goat at a county fair. Are you one of his descendants? If so, tell him I'm now big enough to head butt him back. This TechNet article will eventually contain all of the steps necessary for OA in a coexistence world. They aren't in it yet, but we're working on an update. technet.microsoft.com/.../bb123741(v=exchg.150).aspx

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

Greg Taylor [msft] — Thu, 23 May 2013 21:22:04 GMT

Yes DirtyGoat, you need OA enabled everywhere to allow connections from 2013 to be proxied.

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

DirtyGoat — Thu, 23 May 2013 21:04:43 GMT

@Brian, does the OA requirement on all legacy CAS servers hold true for CAS servers in a separate (non-internet facing) AD site?

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

Fred Chamanara — Thu, 23 May 2013 20:22:08 GMT

Great Article Brian :-)

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

steve siyavaya — Thu, 23 May 2013 19:49:06 GMT

Great article Brian!

re: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

Brian Day [MSFT] — Thu, 23 May 2013 19:08:16 GMT

@Frank, that suggestion is invalid when coexisting with Exchange Server 2013. It is a requirement to enable OA on all legacy CAS when Exchange Server 2013 and 2010 coexist and OA connectivity to the legacy servers is required.