We got to this point as the site has a very slow internet connection, multiple remote offices connecting to the central exchange server, and on advise from someone within Office support, we setup dirsync, and the plane was to allow the users to get access to their Office 365 account, get Office installed, and export their mailbnoxes to PST, then, over time, once this was done, point mx records to o365 and then we were told that we could disable the on premise.
This is not going to work, having had to use ADSI edit frequently during the moveover, I dont want ot have to use it consistantly. Would it be easier to disable Dirsync, Decomission on premise, and then just manage them seperately, and or look at another method to manage user accounts and Office 365 mailboxes? On 30 June 2015 at 17:18, Michael B. Smith <[email protected]> wrote: > Honestly, I’m not quite sure how you got to this point. I mean, I read > your description, but that’s not the way we recommend you do things. > > > > I’m not sure how to easily recover from this. If I were you, I’d probably > fire an email to Michael van Horenbeeck and/or Steve Goodman. They are also > Exchange MVPs, but they focus on hybrid situations. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Graeme Carstairs > *Sent:* Tuesday, June 30, 2015 11:57 AM > *To:* [email protected] > *Subject:* Re: [Exchange] Migration to Office 365 removing on premise > server > > > > Ok thanks, > > > > so as the users have e-mail mailboxes on cloud and on premise (on premise > no longer being used) forgive my stupididty but is there away for changing > them from On premise mailbox to just mailenabled, so we can get rid of the > on premise mailboxes? > > > > Thanks > > > > > > On 30 June 2015 at 15:38, Michael B. Smith <[email protected]> wrote: > > In general, we recommend you leave your last server on-premises. But if > you feel you must: > > > > https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx > > > > > http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Graeme Carstairs > *Sent:* Tuesday, June 30, 2015 5:27 AM > *To:* [email protected] > *Subject:* [Exchange] Migration to Office 365 removing on premise server > > > > Hi There, > > > > We are in the middle of an Office 365 migration from On Premise Exchange > 2010 > > > > What we have done is > > > > 1. Setup O365 for the domains needed. > > 2. setup Azure AD Dirsync to sync AD domain to Office 365. > > 3. Disabled on premises mailoxes for users so that when they are assigned > the o365 licernse it creates a mailbox in the cloud) > > 4. renabled on premise mailbox to allow users to continue working. > > 5. once all users were able to access O365 mailbox and had backed up their > e-mail to pst we then changed DNS to point to Office 265 > > 6. all users are now using their cloud mailbox and mail flow is working > correctly > > > > We now need to remove the on premise server, but when we disable a mailbox > (as part prep for the uninstallation of Exchnage on prmise) the dirsync > replicates that the user has lost all Exchnage properties and they loose > e-mail addresses etc. So we have to renable on premise mailbox to recreate > their Exchnage attributes for dirsync to replicate. > > > > My question is > > > > How do I remove the on premise exchange, whilst retaining all Exchange AD > attributes. > > > > TIA > > > > Graeme > > > > > > -- > > Good news everyone, you have just received an e-mail from me! > > > > > > -- > > Good news everyone, you have just received an e-mail from me! > -- Good news everyone, you have just received an e-mail from me!
