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.
Staff directories are a very common request for Intranets. Oddly SharePoint doesn't have a feature called Staff Directories but it contains many bits and pieces that can help build one.
i.e People Search, Custom user properties, My sites, People and Groups page.
There are also out of the box solutions that you can purchase from http://www.bamboosolutions.com such as http://store.bamboosolutions.com/p-41-user-directory-web-part-release-14.aspx
Or you can write code such as http://blogs.syrinx.com/blogs/sharepoint/archive/2007/10/05/sharepoint-2007-face-book-web-part.aspx
This article is to demonstrate how far we can go with just out of the box configuration trying various methods.
Method 1 - Using the User Information List
################### Read this First ################################
Before you try this at home, please note that this solution is very limited. I am making notes as I attempt various methods and these articles are my findings not neccesarily the best solutions.
A better solution is found in part 2 of this article - http://blog.sharepointsydney.com.au/post/Creating-a-staff-Directory-in-SharePoint-Part-2-People-Search.aspx
Pros of this method
Very easy to set up
- Does a good basic job
- Some decent styles and info available OOTB
- Can't create own styles
- Content doesn't synch with SharePoint Profiles (This may be fixable with Bamboo Solutions User Sync)
- As users are removed from SharePoint they still remain in this list (This may be fixable with Bamboo Solutions User Sync)
- Can't edit the page that results appear on. E.G Can't add web parts.
- Can't search for users. Can only group by SharePoint groups.
- When users update their details in MySites it takes a while for the UIL to reflect the changes. This is because syncing is done by a Timer Job called "Profile Synchronization" which runs by default once an hour.
More info: http://sharepointsherpa.com/2008/01/31/employee-directory-using-user-information-list-in-sharepoint-2007/
As part of the experiment I will use the Personalization Site Template
to create a dedicated Staff Directory site for no particular reason
other than I want to see what this site template does.
So here is what the new site looks like. It is just a normal site but it contains a couple of filters preloaded on the page. It also applies a link to this area directly to the creators mysites section.
Now let's go to the People and Groups page and see what our options are.
In this image you can see that I have actually jumped a few steps ahead.
Really all that I have done is created a few groups - Sales, Marketing etc. Under Settings -> 'Edit Group Quick Launch' you can define which groups to show in the Quick Launch on the left.
In our example the client would like to be able to browse by department so we can either create groups to represent each department or perhaps these departments already exist if you are using AD.
Next notice in the top right dropdown that we have created a new view called Staff Directory. You could create as many views as you like perhaps even filtering by location. Or alternatively instead of using the groups in quick launch you could use the views to filter by dept instead.
Note: For some reason list settings option only appears from the top level site which is where you go to create custom views.
Here is where we start the limitations of this approach. You can create a new view but the properties that are displayed in that view seem to be limited to these.
Not sure at this point if you can add more. This may not be a huge limitation as all we areally want this view fo ris to display some basic info about the users and if they want more they can really click through to the user MySite page.
The other bit of customisation for this view is that you can select different styles for displaying the info.
I'm trying to find if you can create your own styles but can't find any info.
You can open any of the views of the UIL from SharePoint Designer by opening the root site but the only options available appear to be the same as you get from the browser view.
On thing I noticed is that a ListViewWebPart is used to display the info but can't find any info on editing styles for LVWP either.
At this point this solution is not looking flexible enough for me so I am abandoning it and moving onto trying the People Search instead in part 2 of this artilce.
For anyone who has ever had to edit content in Sharepoint and asked themselves why is it so hard to insert an image, this is for you.
By default to insert an image into a wiki or blog for example, you have to do something like upload images to a Sharepoint picture library and link to image by copying and pasting a URL to the Image.
Does Microsoft know what year this is?
Anyway there is a Solution but it requires a little effort. The telerik MOSS editor which also comes in free lite version.
See - http://www.telerik.com/products/sharepoint/radeditor.aspx
Uing the RAD editor you can browse to image folders directly while editing content and create folders for storing images on the fly.
A few gotchas to watch:
Make sure you follow the installation instructions that come with the download package as the online instructions seem to be out of date.
You need to have either AJAX or .Net 3.5 installed on the server.
You dont need to edit the masterpages as the instructions say you do.
To modfiy properties of the editor you need to modify the ListConfigFile.xml located in
/Program Files/Common Files/Microsoft Shared/web server extensions/wpresources/RadEditorSharePoint/184.108.40.206__1f131a624888eeed/Resources/
(ListConfig as opposed to Config.xml as most content is kept in Lists. Lists, Wikis, Blogs, etc. are Sharepoint Lists)