Hi,
I was wondering what would happen if we re-ran the sync after migrating the users and mail.
We have already migrated once and have the users set up with all their previous emails. But we want to retrive emails sent during the DNS changes (any emails which had not be synced for various reasons).
Will the sync just update the accounts with emaisl that are not there or will it totally re sync every piece of mail?
Thanks
We are in the process of removing Exchange 2007 from our SBS 2008 box since we are now on office 365 for all our email services. Though I do have a few questions regarding best practices for mail enabled distro lists. We currently have a number of mail enabled distribution lists in our Active Directory which are updated to office 365 via directory sync, right now to update those DL's we just use our Active Directory on our SBS to make these changes.
I am assuming after we remove our on premise Exchange 2007, is the above stated the best practice procedure to update future DL's that orginiated from our our onpremise AD, or do I need to remove all these mail enabled DL's in AD, let directory sync update O365, then recreate them in the O365 ECP??
In addition, new mailboxes can't be added to these DL's, we still have to add these users in the DL via on premise AD is that correct??
I just want to make sure all mail enabled DL's that are coming from our Active Directory will still be working, even after we remove the onpremise Exchange 2007 server.
Thanks in advance,
DC
Hello:
I've been trying to figure out the right way to move forward on this - here's my current scenario:
The last part of our migration is to migrate our email. With only 30 mailboxes, I'm guessing it'll be pretty quick, so a hybrid-deployment seems like overkill.
So I found this article (http://community.office365.com/en-us/wikis/exchange/835.aspx) on doing an Exchange cutover migration with ADFS, but it's all from the perspective of setting up ADFS post-migration. Is there a way to migrate email with an existing ADFS/SSO configuration? From what I read, I need to:
Add the tenant.onmicrosoft.com proxyAddress/SMTP address to each user
Turn off DirSync
Do the cutover migration
Convert users to MEUs post-migration
re-run DirSync
Does that sound accurate? Is that scenario something I can expect to work?
thanks
Is Exchange SP2 OWA supported with ADFS? We need this to make hybrid sign-on to OWA universal.
I've found the following but it appears there is no official documentation from MS.
We are preparing to move a large batch of domains (1000+) onto Exchange online from our on-premise IMAP servers. In order to fully automate this process we need to figure out the value of the Exchange online MX records (the ones with the .mail.eo.outlook.com. suffix).
I have the value in the portal but since we are dealing with a large batch of domains this is not sufficient. It looks like the value of this MX record is derived from the domain name, but sometimes additional letter combinations are added to the domain, so we cannot guess with 100% what the record value will be.
Is there a Commandlet available that allows me to fetch the correct MX record value from Exchange online?
Many thanks,
Tom
I started a staged migration and migrated one user's mailbox, but after testing I have decided cutover is the way to go for my situation. However I cannot get the option to run a cutover when I try to create a new migration batch. How do I get to choose cutover migration?
Active Directory syncronization was enabled and DirSync was installed on-premises. I have since disabled syncronization, but I have not removed DirSync.
Hi Team,
We have just taken on a project ( large to me ) to move 170 users from a single on premises Exchange 2003 Server to Host 365 Exchange Plan 1.
A quick background into the local domain.
2 Windows 2003 DC servers
1 Windows 2003 with Exchange 2003 Server ( 190 Mailboxes)
Mails boxes sizes range from 100mb to some very large 15gb mailboxes.
Total Exchange Database is around 65gb
The site has a nice large 100mb internet line
The end goal is to 100% remove the old Exchange 2003 Server by removing it from the domain.
So my steps are :
Set-up server with SSL cert for RPC to work correctly.
Delete any unwanted email accounts.
Setup a new 365 console and add the domain name
Setup a cut-over migration job, i understand this will then connect to my local exchange server and start syncing all the email, then every 24 hours it will upload the changes.
My questions come at this point. While it is syncing in the background my job is to dial into 130 computers and install the pre-reqs, and hopefully add the new Mail Profile if possible, please note that I said ADD a profile as the computers are still being used by the users and the Original profile still connects the local exchange server. I imagine this is going to take at least a month to get round to all the computers and complete the works.
So questions are :
1, does the above sound right ? is it the correct way ?
2. can i create a autodiscover record NOW so it makes my Outlook Profile easier to create?
3. If no to autodiscover record, how would i create the Outlook Profiles
4. I have set the completion date for a few months, planing to do the mx change on a friday night so it has the weekend, is it ok to leave the Migration Plan running after i have changed the mx record to point to 365 for a few days to ensure it uploads all the email?
5, Once the email migration job has be finished and deleted, I'd like to be able to manage the user base from my Active Directory on my Windows 2003 Server, is this possible ?
6. Some users have PST files, what's the easiest method of importing?
The end goal is on the Monday we go live when users boot up there pc's and launch Outlook they simply select the new profile that was set-up in advance, I understand that the mail will only now start to download the cached folder but I dont see any other method here, is this correct ?
As you can see, I'm trying to make this migration smooth as possible, can anyone see any flaws or better options for me.
Please feel free to comment, good or bad..
Thank all.
One of my coworkers recently migrated our business to office365 for email service only, no online office apps, from exchange 2007. We did not deploy a hybrid install, just let Microsoft pull the mailboxes from our old server. We have been running well for several weeks with few issues. For the last few days, however, when first opening outlook in the morning, everyone in the organization had been getting a security certificate error referencing our old exchange server. It says the certificate is trusted, the data is valid but the name is invalid. Clicking proceed lets up continue but it's getting annoying. I have tried installing the certificate but it still keeps popping up. The client is Outlook 2007 SP3.
Robert Olson
Hi:
This has been driving me crazy the past few hours. Here's my configuration:
-Exchange 2010 SP2 on-prem w/ ADFS & DirSync
-Hybrid Config wizard completed
-MX records pointing to on-prem
-Hybrid config set to route all mail through on-prem exch server
-Single mailbox moved to O365
I can send mail from this address successfully, to both internal and external recipients.
When an internal address attempts to send me mail, they get a 550.
When an external address attempts to send me mail, there is no immediate NDR, but inspecting the on-prem exchange server logs, when the on-prem server attempts to send the mail to the tenant.mail.onmicrosoft.com address (the cloud mailbox), it fails.
Any suggestions?
LS,
when I create a new migration batch and then start this batch there are 0 users migrated. (status Synced)
But when I started this migration 2 weeks ago, there were 8 users migrated.
What is happening here?
Grz,
Wilco
Hi all
Id be most greatful if someone could shed some light on this predicament I find myself in...
I have a client that has an O365 tenant that is in use with approx 500 US users for Exchange & Sharepoint online.
They are now wanting to do a cutover migration of their UK users (approx 60) from Exchange 2007 to Exchange online.
Now.... the cutover process is fairly straight forward and I have no real issues with the process, they are not worried about seperate credentials (so no ADFS) and they are already running Dirsync with the US forest (i.e. cannot set up for UK forest as they are two difference domains).
They have already provisioned online user ID's for their UK users to access sharepoint online (in the format name@tenant.onmicrosoft.com)
So....
My question is, when the cutover migration provisions the online mailbox, can I get it to provision agains the associated online user id (i.e. by way of SMTP matching?) or not? If so, how?
Do I have to let the cutover migration create new users id's? or will it match against the alias?
If anyone knows the answers to this Id be most greatful .
Thanks
John
We want to delegate permissions for mailbox moves from the on-premise Exchange 2010 environment to Office 365, to specific users. Each user is an administrator for a specific OU in local AD.
I've created a management scope for the collection of online mailboxes based on attributes, and added the roles for the set-mailbox and remove-mailbox permissions, as stated in http://help.outlook.com/en-US/140/ff852814.aspx
But now I want to add the permission to move mailboxes, but even after adding the role "move mailboxes", the user is still unable to move a mailbox, the error presented in the "New Remote Mailbox Move"-wizard at the Target Delivery Domain selection states that the Get-RemoteDomain cmdlet cannot be found.
Which permission am I missing here, and how do I add this specific permission to the Role Group?
Hello,
We are building a hybrid setup with 1000 users online and 1000 users on premise.
We have done a good pre study and there are business reasons not to run the on premise users in Office 365.
We have two sites (layer 3 separated, no stretched vlan and/or Vmware srm)
For redundancy (in case primary site goes down) we still want to have DAG and redundant ADFS and hybrid servers.
We know that DAG, and ADFS is possible. For hybrid we can have more servers (when they are in one site) but how about two sites.
Is this possible?
Kind regards,
John Bruijntjes
After DirSync has been installed on-premises, is Cutover Migration still possible?
Backstory:
I installed DirSync and enabled AD Syncronization. All the user accounts were imported to Office365. I ran a staged migration batch successfully on one user mailbox.
After seeing how Staged Migration works, I decided I would rather perform a Cutover Migration. I deleted all the AD users from Office365, and attempted to create a new Migration Batch. I still get prompted for a CSV file every time I try to create a new batch, which indicates a Staged Migration batch is getting created.
I read in another thread that once DirSync is installed, a Cutover Migration is no longer possible. If I uninstall DirSync, will I then be able to successfully create a Cutover Migration batch?
We are planning a staged migration from Exchange 2003 to O365/Exchange Online.
Is it possible to have multiple concurrent migration batches running at the same time, to maximize throughput?
The 'Migration Performance' paper at http://technet.microsoft.com/en-us/library/jj204570.aspx suggests that it should be possible, in the section that says:
"For migration tools that use RPC over HTTP, it’s a common practice to increase migration throughput by adding more migration servers and using multiple Office 365 administrative user accounts. This practice can gain data injection parallelism and achieve higher data throughput, because each administrative user is subject to Office 365 user throttling. We have received reports that many enterprise customers had to setup more than forty migration servers to obtain 20-30 GB/hour of migration throughput."
With this in mind, we set up two Exchange Front End Servers, using two different O365 admin accounts and attempted to start two migration batches at once. But the second batch just queued itself up until the first batch had completed.
Are we missing something? Or are concurrent batches not possible with the built-in Microsoft migration tools?
From the information I found online, I believe that PST Capture is capable of handling up to three concurrent uploads; however, it seems I'm only able to upload one PST at a time. I've tried approaching this two different ways: 1) more than one PST in a given import; and 2) more than one cloud import list importing at the same time. Using either approach, yields the same result...one PST begins importing and the others remain in queue. Does anyone know who to properly configure PST Capture and/or Office 365 to allow concurrent PST uploads?
Hi All,
I have a customer who is looking to move to 365. They currently have an on premise Exchange 2007 server. They have 55 users with some mailboxes up to 11GB. They have a total mail store of about 110GB and a further 100GB of PST files.
They would like to do a staged migrations because of the size of the data that they need to move to the cloud. They have a 10mb internet connection and this amount of data won’t go up in a weekend.
If I understand it right and they look at a staged migration the MS online directory tool needs to be installed but then this can’t be un-installed later and they would need to keep it along with the Exchange 2007 server to managed the 365 environment. Can someone confirm?
If they choose to go for a hybrid approach an Exchange 2010 would need to be installed and again it would need to be left in place at the end of the migration? Can someone confirm? Would this be the best option to perform a staged migration?
Thanks for any help.
Jeremy
Hi,
After we upgrade edu@live to Office 365 we are not receiving any mails on our domain configured with Office 365. Meanwhile we are able to send mails to internal and external users, as well as we are receiving mails from internal users.
External users are getting this message:
bh=5P7hiF4cpdxdmb+z93SjUnkAHuQznwo2rFZPgMUR3qs=;
b=Bqn8itth0mEB88aRE4aXPtCczMoHd880Qn4X7yfqAuOCR3H+kodpL2OIGNfQJTZAVq
Sg+0Ach62J2/+hmMJ6k+mQn5mVbj+09P8o0oFu//vlWPuuEmxIcbSUDgBVqcFmUh5myT
PwFrrl12t2eFpSKmlWteUcPYza7S8RZIM3YVcTFkptFbhPAZ0bhg5AN0HPm+Q6rS8EMb
6xr6kgQF7xdCTd+OJ1xgIbzaozw2/UnCBxGLUV6dH3CxhKlsFxFyyuPfcYTXSAves24p
jwEYDRLDPESm1HOL3UOVkvn8v+kE9/gpqgLfoLUkdfUyu0B+uDBMy+VSME2ou2JaswIX
IaQQ==
MIME-Version: 1.0
Received: by 10.58.162.130 with SMTP id ya2mr8612338veb.2.1349931539755; Wed,
10 Oct 2012 21:58:59 -0700 (PDT)
Received: by 10.220.21.202 with HTTP; Wed, 10 Oct 2012 21:58:59 -0700 (PDT)
In-Reply-To: <CAA6F6D662EA8F4687CFE300093092311CF47BC7@HKNPRD0410MB363.apcprd04.prod.outlook.com>
References: <CAA6F6D662EA8F4687CFE300093092311CF47BBA@HKNPRD0410MB363.apcprd04.prod.outlook.com>
<CAA6F6D662EA8F4687CFE300093092311CF47BC7@HKNPRD0410MB363.apcprd04.prod.outlook.com>
Date: Thu, 11 Oct 2012 10:28:59 +0530
Message-ID: <CAPqH7nLV5LyPNDJxit8sBqXGv=BfH011XW8MyP5aMg0nJhrXUg@mail.gmail.com>
Subject: Re: FW: Test
Content-Type: multipart/alternative; boundary=047d7b6766dce5f44a04cbc16df0
> ------------------------------
> *From:* Vaibhav Kulshreshtha
> *Sent:* 11 October 2012 10:26:25
> *To:* Vaibhav Kulshreshtha
> *Subject:* Test
>
> Test
>
I am not very good at email settings and moving things around. I will try to explain my situation as thoroughly and detailed as possible as I am in need of some help. I have a domain @brandmgtgrp.com that I bought from a third party seller. It is hosted by Enom. I am trying to switch from my current POP/SMTP email program to an exchange online hosted email so that I can sync my email with my iPhone. I really need someone to walk me through the steps. I have purchased a license for this email and my domain has already been verified so I believe I've gotten that much done already.