The following walk through will go through the process of upgrading the MyProfile Site Collection from 2010 to 2013 allowing you users use the newsfeed tab at the top in 2013 allowing them to see a consistent view.

My recommendation would be to upgrade this site collection first as it will be used a lot by users and is a key element of the new navigation of Office 365 with Sites, Newsfeed and SkyDrive.

If you are the site collection administrator you will be shown a red bar at the top of the page allowing you upgrade now or later

Here is my current profile site collection

Having clicked Start now you will be taken to a ‘Prepare for takeoff!’ screen allowing you to request a demo upgrade.  This will take a day or two but will allow you as the administrator to see what the experience will look like.

Having clicked the Upgrade this Site Collection it will ask you whether you are sure or not

And then its the waiting game to upgrade.  You can still cancel it but once the upgrade has got a certain point, you won’t be able to cancel it.

When it has finished it will refresh and give you a small report on the upgrade process.

By clicking on the newsfeed tab you will then be taken to the new 2013 looks and feel My Profile/Newsfeed Site Collection

This article is part of a series of articles on the upgrade process for Office 365 to wave 15

• Part 1: Email Notifications
• Part 2: Addressing Issues
• Part 3: Postponing the upgrade process
• Part 4: Upgrading SharePoint Online
• Part 5: Upgrading My Profile Site Collection <—This Post

http://community.office365.com/en-us/blogs/office_365_technical_blog/archive/2013/05/03/upgrading-to-the-new-sharepoint-online.aspx

This article is part of a series of articles on the upgrade process for Office 365 to wave 15

• Part 1: Email Notifications
• Part 2: Addressing Issues
• Part 3: Postponing the upgrade process
• Part 4: Upgrading SharePoint Online <—This Post
• Part 5: Upgrading My Profile Site Collection

At the bottom of the email you get about your 4 week notice, you will get P.S. saying you can postpone it.

To postpone it you need to log into your Office 365 portal site at http://portal.microsoftonline.com with Global Administrator rights where you will be presented with the following at the top of the page.

Click on Service update options to start the postponement.

You are now presented with a bit of information telling you that you don’t have to worry about anything when the upgrade happens and that there will be no service interruption.

The second part allows you to postpone the upgrade process.  This might be for 30, 60 or 90 days depending on your tenancy.

Click on Postpone upgrade if you want to and it will tell you that you can only postpone it once.

This article is part of a series of articles on the upgrade process for Office 365 to wave 15

• Part 1: Email Notifications
• Part 2: Addressing Issues
• Part 3: Postponing the upgrade process  <—This Post
• Part 4: Upgrading SharePoint Online
• Part 5: Upgrading My Profile Site Collection

If we want to be able to log into Office 365 with our domain name such as @bfcnetworks.com we need to have this set in our users Active Directory UserPrincipalName attribute.

Over the years, many people have configured their domain FQDN to something like bfc.local rather than use their external domain name.

As we look more into cloud services and Windows Azure Active Directory we see that the requirement to use DirSync and your own domain name (rather than bfcnetworks.onmicrosoft.com) requires local Active Directory changes.  The process below will show you how to add an additional domain and then a PowerShell command to get all users using the bfc.local UserPrincipalName and change it to @bfcnetworks.com

Part 1: Add FQDN to Active Directory

Log onto your Active Directory Domain Controller and open Active Directory Trusts and Domains.  Right click on  Active Directory Domain and Trusts which will open the below property box and type the domain name you want to use in Windows Azure Active Directory

Part 2: PowerShell command to change UserPrincipalName

There are 2 section to this single line of PowerShell.  The first is that it will get all the users that has @bfc.local in their UserPrincipalName.  The second section will then set search users UserPrincipalName to their SAMAccountName + @bfcnetworks.com

get-aduser -filter {UserPrincipalName -lie “*@bfc.local”} | foreach {set-aduser -identity $_.SAMAccountName -UserPrincipalName ($_.SAMAccountName + “@bfcnetworks.com”)}

You may want to schedule this to run over 3 hours just before your DirSync runs to ensure all your users do have the right FQDN in their UserPrincipalName before being synced with Windows Azure Active Directory & Office 365

The email is customised to your tenancy where Microsoft have evaluated your connectivity and how you use it and will let you know of changes required.

Some of the notifications are standard to Office 365 such as the new logon page but others are related to your clients, servers (ADFS/DirSync) and Office 365 tenancy.

Its important that you do read the Microsfot Office 365 wikis about Office 365 and the updates required.  You can get the information from this post

http://www.bfcnetworks.com/blogs/alexpearce/office-365-system-requirements-and-admin-tasks-wiki/

Here are a few examples I have received – if you have some that are missing please share so the community can see what is coming

Standard/Common Notifications

Other Important Issues

This article is part of a series of articles on the upgrade process for Office 365 to wave 15

• Part 1: Email Notifications
• Part 2: Addressing Issues <—This Post
• Part 3: Postponing the upgrade process
• Part 4: Upgrading SharePoint Online
• Part 5: Upgrading My Profile Site Collection

But what do those emails looks like, so you know what to look out for in your inbox.

Marketing Email

The first email that comes is more of a marketing email to let you know that you are getting upgraded.  The important links in this email is the link to the service upgrade centre.  There you will be able to watch a video on what to new experience will look like, how the upgrade will work, how to postpone the upgrade and select some test users to test with early upgrade.  Please do watch the email

4 Weeks Notice

The second email to look out for is entitled: Service Alert: New features are coming to your Office 365 service soon  which will arrive about 4 weeks before your upgrade.

During the next 3 weeks you will be able to postpone your upgrade and you need to look out for the PS at the bottom of this email for this information.  It will state a date which is your last chance to postpone it by.

The Learn More link goes to the same link as the Marketing email.

1 Week Notice

The next email and last for this blog post (Titled: Service Alert: Your Office 365 service upgrade is scheduled for your date)arrives around 1 week before the upgrade.  When you receive this it will be too late to postpone your upgrade as Microsoft would have scheduled you in for the next 7 days.

The Tell Your Users link goes to a webpage which gives you an example email template to send to your users about the upgrade

http://community.office365.com/en-us/wikis/office_365_service_updates/service-upgrade-notification-template.aspx

A big thanks to Mark Stokes for some of the content of this post

This article is part of a series of articles on the upgrade process for Office 365 to wave 15

• Part 1: Email Notifications <—This Post
• Part 2: Addressing Issues
• Part 3: Postponing the upgrade process
• Part 4: Upgrading SharePoint Online
• Part 5: Upgrading My Profile Site Collection

Its important to note that these PowerShell commands are not the normal PowerShell commands you get for on-premise SharePoint and they are here to manage creating and managing site collection as well as gather information about your tenancy.

You can download the powershell commands from here

Here are a few powershell commands that you might find useful.

Import SharePoint Online Module

Import-Module Microsoft.Online.SharePoint.Powershell

Use this cmdlet to add the commands for SHarePoint Online management shell

Connection to SharePoint Online

We are first going to set the URL of the SharePoint Online Admin site and then log in.

Note we only have powershell for the admin portal so you have to connect to the –admin.sharepoint.com URL.

$spourl = “https://contoso-admin.sharepoint.com”

connect-sposervice -url $spourl

List all Site Collections

get-sposite

Get current storage of site collection

First we are going to get the Site Collection and request the information the current storage usage.

$spositecollection = get-sposite https://contoso.sharepoint.com

$spositecollection.StorageUsageCurrent

Average out Storage Quota to all Site Collections

This last command is a little bit more complicated.

We are going to get the storage quota for the tenancy and then divide that by the number of site collections we have an implement it to each site.  This command can take a while to run as it will run on each site collection, confirm and then move onto the next one.

#Gets the number of sites

$getnumberofsites = Get-SPOSite

$numbersofsites = $getnumberofsites.count

#get the storage quota for your tenancy

$gettenancy = Get-SPOTenant

$storagequota = $gettenancy.StorageQuota

#set average

$average = $storagequota / $numbersofsites

This will now set each site collection to the average of the tenancy storage quota.  It will error if the average is over 100GB as this is the highest it can be.

This year I’ll be talking about Office 365 and some of the deployment scenarios we have been through at BFC Networks including an 80,000 deployment with Office 365 with the 2010 wave technologies as well what’s new in 2013 and how things have changed for us as we gear up from deployment to over 800,000 users.

For those who are education establishment such as schools, colleges or universities there is a 20% discount code which is educationevo2013.  Register here: http://www.sharepointevolutionconference.com/

I look forward to seeing you are the conference and also in my session on the Wednesday.

The announcement which included the release of the new Office 365 Home Premium (now available) has set a date of the 27th February for the new wave available to business.  Exisiting customers will have to wait for the upgrade but if you are thinking of going cloud, save yourself of an upgrade and wait for that date.

We will also be announcing our new product/service for Office 365 for education running on the 2013 platform around this date, stay tuned

I decided to talk about the differences as I know there are many companies still planning to deploy SharePoint 2010 and all of a sudden 2013 is now here but there are a few things that we can do now in 2010 that will help us and that is what this session was all about.

Thanks to those who came and listened