| Author |
Topic  |
|
wobble_wobble
Honorable But Hopeless Addict
    
Ireland
4517 Posts
Status: offline |
Posted - 12/02/2012 : 5:20:45 PM
|
That's not good. Talk to your MS Account manager... |
Joe
After everything that has happened during the month of Jan 07, I do believe that pigs fly backwards!
http://whatismyv6.com/ |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 12/05/2012 : 01:51:01 AM
|
| Finally got contacted by someone who at least has access to people who seem to have a clue. We got it working by manually adding an extra SMTP address to the special federation account. Why this didn't happen automatically they can't explain. They have agreed that the documentation for hybrid configuration is a godawful mess and they are working on cleaning it all up. Half of the things they've done aren't even documented anywhere official. Makes me glad we aren't considering putting anything other than archives in the cloud currently - I'd hate to actually have to deal with mailflow. Also, according to them, it's perfectly normal for it to take hours for archives to provision once you create them in EMC. That's a fail right there. |
-Wes |
 |
|
|
JSCLMEDAVE
Administrator
    
USA
6116 Posts
Status: offline |
Posted - 12/05/2012 : 08:47:02 AM
|
sigh........
I have nothing, just, sigh.......
Glad you got it sorted. |
Tim-
“This too shall pass" |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 12/08/2012 : 4:10:22 PM
|
| Sort of sorted :-) It's only working with one smtp domain, but at least I was able to get the same rep immediately for the new case to try and make it work with others... |
-Wes |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 12/08/2012 : 10:21:58 PM
|
| Latest hiccup - trying to move an existing onprem archive mailbox (and only the archive) to the cloud results in an error squawking about not having a matching UM policy on the cloud side (which of course we do not have, since we are trying to use the cloud for nothing more than archive storage). They are trying to see if there is some kind of workaround to force the mailbox move through, or if we'll have to approach it another way. Side note: the number of moving bits and pieces to this whole thing is pretty ridiculous, and all the undocumented updates and hotfixes are really piling up! |
-Wes |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 12/08/2012 : 10:37:50 PM
|
| The rep is thinking that the engineer who wrote the remote mailbox move logic didn't conceive of the hybrid/archive scenario when it was written (we are able to create new archives for um-enabled users, just not move existing ones). |
-Wes |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 12/09/2012 : 10:11:35 PM
|
So to work around this issue, even if you're just moving an archive mailbox as we are, you have to create a dummy UM dial plan on the cloud side, and then run:
Set-UMMailboxPolicy -Identity "Cloud Default Policy" -SourceForestPolicyNames "On-Premise Policy"
Also make sure that the cloud dial plan matches the number of extension digits and URI type of the onprem policy or the move will fail.
Another gem: the move mailbox process is often unstable and they had me update the web.config on all CAS servers: 1. Set below "length" and sizes to 8MB (8388608), as below. The default value is 1MB (1048576). 2. Update reader quotas too. <binding name="MRSProxyHttpsBinding"> <reliableSession /> <textMessageEncoding> <readerQuotas maxDepth="256" maxStringContentLength="8388608" maxArrayLength="8388608" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> </textMessageEncoding> <httpsTransport authenticationScheme="Negotiate" maxReceivedMessageSize="8388608" /> </binding> <binding name="MRSProxyWSSecurityBinding"> <reliableSession /> <textMessageEncoding> <readerQuotas maxDepth="256" maxStringContentLength="8388608" maxArrayLength="8388608" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> </textMessageEncoding> <httpsTransport authenticationScheme="Anonymous" maxReceivedMessageSize="8388608" />
|
-Wes |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 12/09/2012 : 10:12:30 PM
|
Finally, SSO will not properly work with Outlook 2010 (causes an extra popup) without this hotfix which is not pushed by Microsoft Update: http://support.microsoft.com/kb/2687351
I was afraid to ask about Outlook 2007. Outlook 2013 seems to work properly. |
-Wes |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 03/23/2013 : 8:55:31 PM
|
| On top of all the earlier nightmares, turns out you can't just use o365 for mailboxes (archives in our case) - you HAVE to configure mailflow (which contradicts what multiple support reps told me previously) or risk people using FOPE not being able to get mail to you. Fail. Also, they are going to be upgrading tenants from v14 to v15 (exchange 2013 compatible) on some random schedule and the best they can give is "it will be complete some time in 2013." Ridiculous - as if there haven't been enough delays wrt Exchange 2013. So at this point we are moving the archives out of the cloud (the cheap storage simply isn't worth the incredible headache this has been) and back on-prem. Less costly to just buy more storage than to have to waste so much time while losing flexibility. |
-Wes |
 |
|
|
Jazzy
Administrator
    
Netherlands
1932 Posts
Status: offline |
Posted - 03/25/2013 : 07:18:14 AM
|
I think you're very negative, Wes. I'm sorry to hear that Exchange Online did not meet your expectations, but I don't think you can blame 'the cloud' for everything. For instance, the requirement for a full hybrid Deployment is clearly stated in the requirements: http://technet.microsoft.com/en-us/library/hh529915(v=exchg.141).aspx The delay between configuring the mailbox and the provisioning of the archive in the cloud is also mentioned in the documentation: http://technet.microsoft.com/en-us/library/dd979791(v=exchg.141).aspx And regarding the update to 'wave 15' every Office 365 org will receive a notice several weeks before the actual upgrade. Customers can choose to delay the upgrade twice. Also this information is not hidden but can even be found with a simple search on 'Office 365 upgrade', first result is this: http://community.office365.com/en-us/wikis/office_365_service_updates/default.aspx
I'm not saying you have no reason to complain and support can be terrible, I'm just trying to add some balance in the discussion. Although the cloud is certainly not mature, with the right mindset it can bring huge benefits. And when I read your experiences I wonder if the mindset is right to go to the cloud, you're probably better of with everything under your own control. |
Jetze Mellema
Exchange specialist Former MVP (2005-2012) My blog: http://jetzemellema.blogspot.com (Dutch) My company: http://www.imara-ict.nl/ |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 03/25/2013 : 11:48:58 AM
|
Definitely - let me be clear that I am referring specifically to the hybrid setup. Have plenty if clients on pure o365 and am extremely happy with it. But the hybrid config is poorly documented (half of what support has given me as far as commandlets are not documented anywhere, and even the reps had the hunt around for days in some cases to find the proper internal documentation). Nowhere was it stated that mail flow was required - even multiple reps told me it was not!
So yes my support experience has been extremely negative and that is coming through in my posts, and that does not bother me one bit. I do not see it as slamming the cloud in general, or even o365 in general, but this aspect of microsofts services has a LOT to improve and a ton of my time has been wasted by an extremely inefficient and uneducated support structure. Overall while I have no qualms about referring orgs of almost any size to pure o365, I would strongly caution against hybrid configs to all but the largest orgs with dedicated exchange admins and no concerns about losing control of their upgrade schedules to MS. |
-Wes |
 |
|
Topic  |
|