Administrator BPOS to Office 365 Transition Tools & Utillities

Posted on



As BPOS administrators start their journey towards transitioning into Office 365, many Administrators with a medium to large/complex need tools to help them understand whether the following are ready for this Transition:

  • Desktops
  • Network
  • Applications
  • Operating Systems
  • Internet Explorer browser
  • Office applications (Office 2007 & 2010) | Lync, Outlook, Live Meeting, etc.

The following information will help these administrators in understanding the current state of the above variables and help them get ready for the BPOS to Office 365 Transition:

  1. The Desktop Readiness Tool is a “Run from the web” end-user application and not a pre-requisite for transition.  In most cases, an enterprise level customer will not use it, or only use it to spot check some PCs.  Details here:
  2. The Desktop Application Setup Tool, however, performs updates and installs that are required and must be run on any PC that will access Office365.  Enterprises will most likely perform the “manual” process described here:
  3. Deployment Readiness Tool that is designed for enterprise level transition readiness assessment.  Details here:

Password Changes continue to be the overwhelming majority of day one issues.  All BPOS administrators MUST make sure that each of their BPOS users and administrators change their password at least once before the Transition.  This password change is synchronized into Office 365, so when the Transition is complete and users login to Office 365, they can use their BPOS credentials (username and password) to login.  Without this password, again facilitated by changing in BPOS, Office 365 administrators must do a password reset in the new Office 365 Portal in order to get users into the new Office 365 services.

Users with Sync’d Passwords

Here is a PowerShell cmdlet to export a list of user info into a CSV file which you can then open in Excel as “comma delimited”

Fields of particular interest are PasswordExpirationDate, PasswordLastSetDate, LastSignedInDate

Use the newest “Microsoft Online Services Migration Tools”

Version:               1.0.1453.123       Date Published:                3/28/2012 (or later)

  • Get-MSOnlineUser -Enabled -sourcedetail full -ResultSize 25000 | export-csv “users.txt”

Additional Administrator PowerShell Scripts:

Find All Users Who Have Not Changed Passwords Since 12/1/2011 and Change Password to “P@ssw0rd1” and Force to Change at Next Logon

  • $Cred = Get-Credentials [enter your BPOS Administrator account credentials]
  • Get-MSOnlineUser -Credential $Cred -enabled | where {$_.PasswordLastSetDate –lt “12/1/2011”} | FL Identity
  • Get-MSOnlineUser -Credential $Cred -enabled | where {$_.PasswordLastSetDate –lt “12/1/2011”} | Set-MSOnlineUserPassword -Password “P@ssw0rd1” –Credential $Cred –ChangePasswordOnNextLogon $true

Note – The above will query the BPOS Microsoft Online Directory Services (MSODS) for users who have NOT changed their password since December 1st, 2011. Anyone in this PowerShell (in-memory) list will then be piped to the Set-MSOnlineUserPassword and change these users passwords to “P@ssw0rd1” and instruct MSODS to force the user to change their password during their next login. Of course you will need to tell these users that their password has changed to P@ssw0rd1, as they will need this to change their password!

Note – If you want to run the following, it will give you the list, and then you can run the full command to set the password for these users. This way you will have a list of people that you need to contact with their new password:


  • $Cred = Get-Credentials [enter your BPOS Administrator account credentials]

 Note – In order to use the above updated Get-MSOnlineUser cmdlets you must upgrade your BPOS Mail Migration machine to use the latest Migration Tool. If you have downloaded and attempted toupdate/upgrade your older Migration Tool application, you may find errors when issuing the Get-MSOnlineUser command. Please refer to the following post, which explains how to resolve this issue:

Whatcha thinkin?

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s