Link to home
Start Free TrialLog in
Avatar of Ninja2k4
Ninja2k4

asked on

SCP bypass for Outlook 2010 (Office 365 staged migration)

Hi, currently performing a staged migration in which we have Exchange 2010 and are running a 10 user test pilot. Office 365 is all working fine, I can login to webmail and send and receive email fine (we are using target address redirection). I can set the client up manually on outlook 2010 and again it also works fine.

The issue is I can't seem to bypass the SCP so that it automatically sets the clients up. I've tried the registry entry's to try bypass this but it doesn't work. If I go into ADSI.edit and remove the SCP from there, then it sets the client up fine, but unfortunately I can't remove this for good. Autodiscover cname is pointing to autodiscover.outlook.com

Anyone got any other ideas at all ?
Avatar of Ninja2k4
Ninja2k4

ASKER

Weird thing I have noticed though, If I re-direct IIS autodiscover directory to - http://autodiscover.cim.co.uk then it sets the account up, but an on site account then takes ages to configure itself.
Avatar of Vasil Michev (MVP)
The CNAME needs to point to your on-prem endpoint when in hybrid. But that shouldnt be the issue here, if I remember correctly your problem was that it didnt return the redirect.

Regardless of which method the client is getting the xml with (even the SCP), the server *should* return the redirect. In your case, it looked like you were getting the xml for a normal mailbox, not MEU. Can you test it with a 'normal' mail-enabled user, not something that was moved to EO?
Not doing a hybrid migration, doing a staged one.

With a normal user, it just picks up the SCP and first point of autodiscovery and that is it.

If I remove the SCP, then the redirect gets picked up,  but then setting up an internal on site mailbox takes forever. Unfortunately this is a customer we have taken over and it's a bit of a mess.

Just making sure their autodiscovery is correct as they were using a self signed cert which has now been changed for a 3rd party one.
OK, so you have the SCP pointing to on-prem, and you have the CNAME pointing to EO? The only logical explanation I can think of is that the mailbox on-prem still exists (i.e. NOT converted to MEU as described in Step 6 here: http://technet.microsoft.com/en-us/library/jj874018(v=exchg.150).aspx). In this case, on a domain joined machine it will always return the local autodiscover WITHOUT the redirect. Outside of the network (or if you disable SCP so it progresses until the CNAME lookup) it will return the EO autodiscover info, which is what you want (but there will be no redirect).

Are you actually seeing the REDIRECT in the response, or you simply mean that it gives you the info from the correct server (EO)? It doesnt make sense to not see the redirect when using the SCP but see it with the CNAME, if anything it should be the other way around. Here's what the redirect should look like:

<Action>redirectAddr</Action>
  <RedirectAddr>user@contoso.mail.onmicrosoft.com</RedirectAddr>

Open in new window



Btw if you have mailboxes both in the cloud and on-prem using the same namespace, autodiscover needs to point to the on-prem server. Converting the mailboxes to MEU and having their targetaddress populated correctly will make sure they get the correct autodiscover info.
ASKER CERTIFIED SOLUTION
Avatar of Ninja2k4
Ninja2k4

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Self fix.