Office 365 migration & ADSL2+

I'd also check the ADSL connection and see if theres anything you can do to help the connection speed.
I had 12 people in a neighbouring office using google apps, and they swamped their ADSL2+ connection in the UK. OK so they where a advertsing agency moing big photoshop files about in Apps but still.
Would 4G be a help and drop this to the firewall rather than ADSL2+.

Hi,
We have about 30 mailboxes and are looking to migrate to Office 365 from Exchange 2007.
Server spec: Dell PowerEdge T110, 16GB.
The main reason why we would like to migrate to office 365 is that the server needs major hardware upgrades as disks are not configured in RAID and this will require hardware maintenance in a long term as well but also we want to use higher version of Exchange server.
If only Exchange online is used not other features such as sharepoint and skype, would it be reliable to move to office 365 and continue to use it over ADSL2+ line? (12Mbit download, 1Mbit upload) Or would this affect current Internet speed?
This topic first appeared in the Spiceworks Community

Similar Messages

Office 365 Migration Challenges

Hi everyone,
Currently, I am evaluating the various challenges or Concern that need to be taken care at the time of Office 365 migration.
For example if I have to migrate Nintex workflow from SharePoint on-premise to SharePoint Online, Whether It is possible or not? If possible then whether it can be easily migrated or there need to do some work around it to achieve that?
Office 365 (Sharepoint Online) Integration with K2 workflow, Salesforce CRM, Biztalk, Business Objects (BO), etc. ?
Office 365 (Sharepoint Online) Connection to External Data i.e. Business Connectivity Services (BCS), etc. ?
Also, Migration is not limited to only SharePoint Online. It can be Exchange Online, Lync Online, Single sign-on etc.
Can any one please assist me. It would be helpful for me.

Would mail continue to flow unimpeded?
Do I have to change my inbound/outbound connectors to the Partner option from On-prem?
The hybrid connectors in EOP should not impact messages sourced or destined to the Internet.
Going forward if my on-prem exchange becomes unavailable (through outage, uninstallation, normal update restarts) would that affect the mail-flow?
Assuming there are no on-premises mailboxes or applications leveraging the hybrid server, there should not be an interruption.
Would it be safe to remove the inbound/outbound connectors?
Yes however I would start by disabling and leaving in-place.
Would I uncheck the Hybrid-Deployment box in WaaD (DirSync) and maintain directory synchronization?
As long as you're using DirSync, your on-premises AD is still authoritative for objects in the cloud. This means if you want add a proxy address for a user, you add it in AD and it syncs to Office 365. You will still want the write-back enabled.
I would also plan to keep an on-premises Exchange server around for management purposes.
ADFS has not been implemented yet but I would like to eventually. Should I be take that into consideration with any of these questions?
Should not come impact any decisions here.
Joseph Palarchio http://www.itworkedinthelab.com

Office 365 Migration, Hybrid to Online Only

This is my first Office 365 migration. I took over the project that was partially started by my predecessor who left abruptly.
Current status of the project is moving along. I have all of the mailboxes in 365. My concerns are related to redirecting mail flow. Currently DNS records point to our on-prem. If I were to redirect DNS to 365 (ourdomain-com.mail.protection.outlook.com)
Would mail continue to flow unimpeded?
Do I have to change my inbound/outbound connectors to the Partner option from On-prem?
Going forward if my on-prem exchange becomes unavailable (through outage, uninstallation, normal update restarts) would that affect the mail-flow?
We will be removing our on-prem exchange server permanently once mail is flowing correctly. After this,
would it be safe to remove the inbound/outbound connectors?
Would I uncheck the Hybrid-Deployment box in WaaD (DirSync) and maintain directory synchronization?
ADFS has not been implemented yet but I would like to eventually. Should I be take that into consideration with any of these questions?
Thank you for your advice and patience on this one. Its a new situation that I was dumped into and I've learned a lot from technet guides and pluralsight classes but nothing beats bouncing questions of others who have done it before though.

Would mail continue to flow unimpeded?
Do I have to change my inbound/outbound connectors to the Partner option from On-prem?
The hybrid connectors in EOP should not impact messages sourced or destined to the Internet.
Going forward if my on-prem exchange becomes unavailable (through outage, uninstallation, normal update restarts) would that affect the mail-flow?
Assuming there are no on-premises mailboxes or applications leveraging the hybrid server, there should not be an interruption.
Would it be safe to remove the inbound/outbound connectors?
Yes however I would start by disabling and leaving in-place.
Would I uncheck the Hybrid-Deployment box in WaaD (DirSync) and maintain directory synchronization?
As long as you're using DirSync, your on-premises AD is still authoritative for objects in the cloud. This means if you want add a proxy address for a user, you add it in AD and it syncs to Office 365. You will still want the write-back enabled.
I would also plan to keep an on-premises Exchange server around for management purposes.
ADFS has not been implemented yet but I would like to eventually. Should I be take that into consideration with any of these questions?
Should not come impact any decisions here.
Joseph Palarchio http://www.itworkedinthelab.com

Exchange 2007 Decommissioning, post Office 365 migration

Hello,
We have four Exchange 2007 servers in four different sites, single AD. All four Exchange servers are CAS, Mailbox, Hub, secondary domain controllers. We have migrated to Office 365 successfully, and would like to remove the Exchange 2007 servers.
I have stopped the Exchange services on all four for at least a week and tested Office 365 mail flow with no issues. My questions are:
1) Can I expect to simply uninstall Exchange 2007 from each server, one by one, without a negative impact to Active Directory?
2) Should/can the many Mailbox Databases be deleted prior to uninstalling Exchange 2007? Not all mailboxes had to be migrated to Office 365, and they contain data that we no longer need.
If there is a 'safe' method to remove Exchange in a multi-site setup, I would prefer to try that before having to dig through ADSIedit.
Thank you in advance.

Hi Chase,
here's an
official guide for uninstalling Exchange 2007. Please also note the other documents in the same library directory (see navigation pane to the left).
Cheers,
Fred
There's no place like 127.0.0.1

Exchange 2007 with pop3 downloader to office 365 migration

Hi,
i would like to migrate my exchange server (exchange 2007) to office 365,
presently i am downloading mails from a online mail service to exchange 2007 through a pop3 downloader and i am distributing this mails locally ( around 20 mail box)
how do i migrate my exchange mails to office 365, is there any automated way to do the same
requesting your valuable suggestions
Regards
Ratheesh
Ratheesh

Hi,
The partially complete in the migration report means there are some items have been skipped due to some reasons. If you check the skipped items, you will see the value is not 0 like other users with status as complete. Usually, this value is not high(1 or
2 in most circumstances) which means only limited items have been skipped.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2010 to office 365 migration lab

I am looking out for free migration lab if any available online from Microsoft or any vendor related to migrate from exchange 2010 to office 365 . Please suggest ?
Aditya Mediratta

Hi,
Unfortunately, there’s no related lab for use.
We can Microsoft Exchange Server Deployment Assistant to generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios. For your reference:
https://technet.microsoft.com/en-us/office/dn756393.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Decommissioning Exchange 2003 after Office 365 Migration

Hello,
My company recently migrated from Exchange 2003 to Office 365 and are working on decommissioning our on-premises Exchange 2003 server. We believe everything is ready to go, however this Microsoft article: http://help.outlook.com/en-us/140/ff959224.aspx#nextsteps has
a big Caution box warning of "unintended consequences" and recommending I contact Microsoft Support:
I've tried my Office 365 support options, but they only tell me that Exchange 2003 is no longer supported and they can't help me, despite the fact that I'm trying to remove it, not maintain it. So
I'm allowed to pay for a new service, but shouldn't expect assistance in safely moving from my old service...
Regardless, they directed me here, so I was hoping someone might be able to advise about what these "unintended consequences" actually are so I can feel fully prepared to decommission.
Thanks in Advance,
Jim

Hi,
After you’ve verified that all e-mail is being routed directly to the cloud-based mailboxes, completed the migration, and no longer need to maintain your on-premises e-mail organization or don’t plan on implementing a single sign-on solution, you can uninstall
Exchange from your servers and remove your on-premises Exchange organization. For more information, see the following:
How to Uninstall Exchange Server 2003
http://technet.microsoft.com/en-us/library/bb125110(EXCHG.65).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migration from Lotus Note / Domino to Microsoft office 365

Core functionality has been agreed to be tested which include:
- Provisioning of user account (create, delete, amend)
- Authentication
- Data Migration and
- Usability.
The Background of the project is the migration of data from Lotus note/Domino to Microsoft Office 365.
A: How would we go about testing the product?
B: What are the main features to look out for in order to achieve test coverage in this type of project?

For migrating Lotus Notes (NSF files) & Domino Server Mailboxes in Office 365 accounts use only a Good-Quality Lotus Notes to Office 365 migration application. The product executes Bulk migrations with high-speed and data security. Perform migration
of emails, contacts (mailing lists), calendars and task (to-do lists) completely into Office 365.
Get Product Overview at:
http://www.export-notes.com/lotus-domino-to-office365.html
(Facility to Migrate Lotus Notes as well as Domino Server Mailboxes)

How to migrate Outlook configuration to Office 365

As we plan our migration to Office365/Exchange Online, I am getting asked questions about the user Outlook profiles. We have users that make extensive use of categories, folder views, rules, etc. In addition, we have a custom Outlook toolbar that is part
of our default image. Can anyone tell me if these items get migrated using the standard Office 365 migration wizard? If they don't is there a way to migrate or export/import this information?
Thanks!
Joe

Hi,
According to your description, I want know the configuration of Outlook after migrate Exchange 2010 to Exchange Online.
If I misunderstand your concern, please do not hesitate to let me know.
Mailbox database will be moved to Office 365, also the mailbox content. The Outlook client can use SCP and DNS record get autodiscover service, then connect to Exchange server and auto-configure Outlook profile. However, dumpster content and old message
missing after migrate to Office 365, please refer to below link and work it out:
https://support.microsoft.com/en-us/kb/2603594?wa=wsignin1.0
For POP3 and IMAP account, and they may not remain the copy in Exchange server, we need to import .pst file to Exchange server. For your reference:
https://technet.microsoft.com/en-us/library/hh781035%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
As client side, we can just move .pst file to new computer, then import to Outlook:
https://support.office.com/en-ca/article/Import-Outlook-items-from-an-Outlook-Data-File-pst-431a8e9a-f99f-4d5f-ae48-ded54b3440ac
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Google Postini outbound configuration with Office 365

Hi all,
My company is currently looking into Office 365 migration. Currently we have Exchaneg 2010 on-premise with Google Postini services for mail security and e-discovery. We are routing all inbound and outbound e-mail trough the Postini-service for archiving
and compliancy reasons.
Inbound is quite easy to set up with the mail connectors in office365, but for outbound Postini requires the IP-adresses of the sending mail servers. Obviously this is constanly changing because of the cloud-based nature of Office 365, but there is no other
way of defining the outbound mailservers for my domain. So my question is as how to cirumvent this or how to define the IP-adresses used by the Office 365/EOP service for sending mail.
Any thoughts on this would be appreciated!

Have you looked up the IP addresses for your <domain>.onmicrosoft.com MX record, using a tool like
http://www.mxtoolbox.com? You are correct that they may change, though. Additionally, I don't know how Postini will handle reinjection to Office 365 - I've read that it's not supported.

Can you merge two user accounts on macbook? my wife has created a user on her new macbook , then inadvertently created a second one when using the migration tool. 1st ac has her office 365 install, yet 2nd has her itunes database, docs and contacts.

Can you merge two user accounts on a macbook? my wife has created a new user on her new macbook air then, inadvertently, created a second one when using the migration tool. 1st a/c has her office 365 install, while 2nd has her itunes database, docs and contacts. What is the best way forward to get everything into the one account? Not sure if the office 365 will allow another installation into the second account, otherwise would just do that and delete the first, if that is possible?

There is no merge but you can move data from one account to another via the Shared folder. Data is copied from Shared. Watch your free space when copying. These are large files. Do one at a time if you are on a small drive. After making copy, delete from other users before you start next copy.
Office365 installs in the main Applications folder and is available for all users on the computer. Activation is tied to the drive not the User.

Error during the migration of Lync 2013 onpremise user to Office 365 Lync

Hi,
I am trying to migrate a Lync 2013 onpremise user to Office 365 Lync in a Hybrid environment.
I am connecting to the Lync server from my machine with the following commands
$lyncOptions = New-PSSessionOption -SkipRevocationCheck -SkipCACheck -SkipCNCheck
$lync = New-PSSession -ConnectionUri https://lyncserver/ocspowershell -SessionOption $lyncOptions -Authentication NegotiateWithImplicitCredential
Import-PSSession $lync
In the next step I am trying to migrate the user to the Office 365 Lync:
Move-CsUser -Identity "username" -Target 'sipfed.online.lync.com' -HostedMigrationOverrideUrl 'https://admin1e.online.lync.com/HostedMigration/hostedmigrationservice.svc'
After that I get a warning message due to to migration to a previous version which I accept.
WARNING: Moving a user from the current version to an earlier version (or to a service version) can cause data loss.
Confirm
Move-CsUser
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
Then I am getting the following error message:
Can not load Live Id module. Make sure correct version of Live Id Sign-in assistant is installed.
    + CategoryInfo          : NotSpecified: (:) [Move-CsUser], CommonAuthException
    + FullyQualifiedErrorId : Microsoft.Rtc.Admin.Authentication.CommonAuthException,Microsoft.Rtc.Management.AD.Cmdle
   ts.MoveOcsUserCmdlet
    + PSComputerName        : lyncserver
Tried to Google it but found nothing.
As far as I can see it is complaining about the Live ID Sign-in assistant, which is installed (the 64bit version) on my computer but not on the remote server. Does it need to be installed on the server as well?
Thanks for the answers in advance.
Regards,
Akos
Akos_DB

This error related to reporting services, you need to verify that reporting services is installed on these instances.
Secondly, you didn't need to create this instance manually then setup monitoring role. delete this instance from shared storage and try again to setup rule using different instance name and it will create automatic on shared storage.
You can also refer below link
http://windowspbx.blogspot.com/2012/07/aaa-donotpost-install-lync-standard.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Summary Report after migrating to Office 365

Hi all,
I just successfully performed a cutover migration off a SBS 2011 Server.
Admins are missing the Daily/Weekly Status report email generated by SBS. The report still goes to the on-premises mailbox. I also unticked the users from the list and created new emails as "external" recipients but did not work.
The DNS is authoritative for contoso.local. I don't know how to create a MX record for contoso.com within that zone.
I think it may be an attribute in AD that needs to be changed.
Could you guys provide help with this?
Regards,
Frank

Hi Frank,
On current situation, please refer to following thread and check if can help you.
Change
email address of SBSMonAcct on SBS 2011
Meanwhile, please refer to the “Completion of the Migration”
section in following article.
Step-By-Step:
Migrating from Exchange 2007 to Office 365
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Error in migrating SharePoint 2010 list fields to Office 365 list [CSOM]

Hi,
I am trying to migrate a SharePoint 2010 list to Office 365. I created a new ListCreationInfo for a new list in O365. But when i am to trying add fields from SP2010 list, its giving me an error after list.update() -
A duplicate field name "fa564e0f-0c70-4ab9-b863-0177e6ddd247" was found.
if (!l.Hidden)
ListCreationInformation creationInfo = new ListCreationInformation();
creationInfo.Title = l.Title;
creationInfo.TemplateType = l.BaseTemplate;
List list = web.Lists.Add(creationInfo);
//Fields in the list
ctxOnPrem.Load(l.Fields);
ctxOnPrem.ExecuteQuery();
foreach (Field f in l.Fields)
list.Fields.AddFieldAsXml(f.SchemaXml, true, AddFieldOptions.DefaultValue); list.Update();
Note- l is the SharePoint 2010 List.

Answer given on StackExchange -
http://sharepoint.stackexchange.com/questions/128875/error-in-migrating-sharepoint-2010-list-fields-to-office-365-list-csom/129015#129015
Thanks,
Thomas

Office 365 migration & ADSL2+

Similar Messages

Maybe you are looking for