I am in the middle of doing my second email migration to Office 365. Originally I migrated our 9 accounts from Google Apps and this time I am upgrading from Office 365 P3 plan to the E3 plan. See plans here - http://office.microsoft.com/en-au/business/compare-office-365-for-business-plans-FX102918419.aspx
With both migrations I am using MigrationWiz - https://www.migrationwiz.com
Before doing anything you should carefully read the instructions provided my Migrationwiz. In our case with an Office 365 to Office 365 migration the instructions are here - https://migrationwiz.zendesk.com/entries/20358091-How-do-I-perform-an-Office-365-to-Office-365-migration-keeping-the-same-domain-name-
Please Note: That the only reason we need to do this is because we are still on the old version (2010) of O365. In June they would have upgraded our system to 2013 versions and we wouldn't need to transfer our mail manually when going form a P3 to E3 plan.
This tool makes the migration a breeze. You simply:
- create a connector between your old mail system and the new one (You will need to be an admin on both systems)
- Specify the mailboxes to copy across and start copying
- Very easy to use
- The support is great and very responsive
- It does multiple passes of the mail so that if during transfer more mail comes in, it will be picked up on the next pass
Things to watch
- Don’t use your main email address as the connector admin account. If using O365, use the onmicrosoft accounts they provide. These email addresses are unique to each account so when you transfer the MX records across you can still keep transferring in the background.
- Large accounts can be slow to transfer. In the screen shot above you can see that we have 2 15 gig accounts that will probably take a week to transfer. If set up properly though you can start using your new account straight away as it copies newer mail first.
Next I’ll be looking at transferring content from our internal SharePoint to Office 365.
If you need any help with your Office 365 migration, contact us at firstname.lastname@example.org and we will be glad to help.
Slipstream MOSS 3.0 Service Pack 1
At the time this article was written, Microsoft has only released a version of the MOSS 3.0 installer package without integrating the already available MOSS 3.0 SP1. When you attempt to install MOSS 3.0 using the installer package on the Windows Server 2008, you will get an error from the Program Compatibility Assistant stating that a service pack is required in order to install WSS 3.0. To circumvent this, we need to slipstream the SP1 bits into the MOSS 3.0 installer files. Basically, this involves extracting the SP1 EXE files into the Upgrades folder of the MOSS 3.0 installer files. Then, running the MOSS 3.0 installation should work.
Matt Hester has compiled information on this issue and come out with a very helpful screencast which takes the user through a step-by-step process of slipstreaming SP1 into the installation. Before beginning this video, make sure you have a local copy of the MOSS 3.0 installation files as we will need to add files to the Upgrades folder. The screencast can be found here:
Error Using SharePoint Products and Technologies Configuration Wizard
After installing MOSS 3.0, you should be taken to the SharePoint Products and Technologies Configuration Wizard. After specifying the Database Server, Database Name, Database Account, and Database Password, you may encounter an error stating “Internet Information Service is not installed. You must have Internet Information Service installed in order to use the Sharepoint Products and Technologies Configuration Wizard.” If you receive this error, read the following two sections.
If you used the Add Roles Wizard to install IIS 7.0 (as we did in Matt Hester’s How To), we were given the default installation containing a minimum set of role services. We will need additional IIS 7.0 role services, such as IIS6 Metabase which provides a legacy interface to applications requiring IIS 6 backward compatibility.
Install Additional Features
We can use the following script to install available feature packages, namely IIS-Metabase. Running the following script will give us the full IIS 7.0 installation, which installs all available feature packages. If there are feature packages you do not need, you should change the script to install only the packages you require.
By default, you do not have Administrative privileges if you're logged on as a user (other than the built-in Administrator account) even if this user was added to the local Administrators group on the machine (this is a new security feature in Windows Server®2008 with-IIS 7.0, called LUA).
Make sure to either log-on as the built-in Administrator account, or explicitly invoke applications as the built-in Administrator as needed, using the "runas" cmd-line tool. For example, to launch notepad.exe you could run this command: "runas /user:administrator notepad.exe".
You will be prompted for the password of the Administrator account. It is useful to have a cmd-box shell that is already elevated, by running "runas /user:administrator cmd.exe".
Every application you run from that cmd-box will be elevated as well, and you will not need to use the "runas" syntax from that cmd-box.