Thomas Ashworth

Office 365 Script: Append additional proxy address to existing cloud identity

Thomas Ashworth — Thu, 28 Jun 2012 23:31:00 GMT

What more can be said other than the title? Enjoy… :)

Read the help information for details on how to execute the script.

Get-help .\SetMailbox_AppendAdditionalProxyAddress_FromCSV.ps1 -full

A copy of the script can be downloaded by clicking on the link below.

Office 365 Script: Create cloud identities by referencing a CSV file

Thomas Ashworth — Thu, 28 Jun 2012 21:48:00 GMT

It’s easy to think in terms of enterprise deployments and come up with solutions to fit those scenarios. Then, low and behold, a day comes along when you have a need to provision users without using DirSync! It’s doubtful that most of us would want to create users manually. So, if you fall into this scenario and have a need to scriptomatically create users, then feel free to use this script as a way to provision your one’s, ten’s, hundred’s, or whatever number of users as cloud identities (not federated identities). Once the identities are provisioned, you will still need to assign licenses to them and distribute passwords. Fortunately, this script will save the automatically generated passwords to a file for easy reference later when you are ready to distribute them to your user population.

Read the help information for details on how to execute the script.

Get-help .\ NewMsolUser_FromCSV.ps1 -full

A copy of the script can be downloaded by clicking on the link below.

Office 365 Script: Count total user, group, and contact objects in on-premises Active Directory forest in preparation for deploying DirSync

Thomas Ashworth — Fri, 13 Apr 2012 15:21:00 GMT

So, you are preparing to deploy the Directory Synchronization tool for Office 365 and are looking for a PowerShell script that will count all of the users, groups, and contacts in the on-premises Active Directory. First, I should point out that the Deployment Readiness Tool that is available for download from the Office 365 community site will count the objects plus perform additional useful checks. If, however, you still want a PowerShell script that is dedicated to only counting objects, then look no further. This script does not require additional software to run (other than PowerShell). It does, however, require read-only access to the on-premises Active Directory. The results of the script will be displayed to the PowerShell console as well as saved to a CSV file. Enjoy…

A copy of the script can be downloaded by clicking the link below.

Office 365 Script: Get Office 365 tenant SKU/license usage information

Thomas Ashworth — Wed, 11 Apr 2012 22:53:00 GMT

So, you already know how to get license usage information from the Microsoft Online Portal, but now you are looking for a way to accomplish the same thing via PowerShell. Perhaps you are working on a little bit of automation to create a CSV report of usage information that you can send to yourself or team. The following script should be helpful as it will get the license usage information and dump it to a CSV file along with displaying the same results to the PowerShell console. In order for the script to work, you will need to download and install the Microsoft Online Services Module for Windows PowerShell.

Read the help information for details on how to execute the script.

Get-help .\GetMsolTenantSkuUsage.ps1 -full

A copy of the script can be downloaded by clicking on the link below.

Office 365 Script: Get an Office 365 user statistics report

Thomas Ashworth — Wed, 11 Apr 2012 22:39:00 GMT

Need a way to report mailbox statistics and/or mobile device usage information (plus a few other things) to your various business groups or subsidiaries? Or, perhaps you want to verify that users have been assigned the correct license? Use the following script to generate a little report – or big report if you have several thousands of users. In order for the script to work, you will need to download and install the Microsoft Online Services Module for Windows PowerShell. Keep in mind that the script can take a while to run across the internet against Office 365 if you have several thousands of users.

Read the help information for details on how to execute the script.

Get-help .\GetMsolUserReport.ps1 -full

A copy of the script can be downloaded by clicking on the link below.

UPDATED 09/07/2012

- fixed a couple of typo's resulting from the previous update

UPDATED 08/17/2012

- fixed an issue where the script would throw an error about variable optimization when run using PowerShell v3 pre-release.

UPDATED 05/07/2012

- fixed an issue where department, company, and manager attribute values were not being saved to the file. Thanks for pointing this out!

Office 365 Script: Assign Office 365 licenses

Thomas Ashworth — Wed, 11 Apr 2012 22:03:00 GMT

So, you have some users that are now using Office 365, and you need to assign licenses to those users. The following script will enable you to license the users by referencing a CSV file, by identifying all unlicensed users, or by identifying only those users that need license reconciliation. If you have migrated some users, but not all, then you may want to use the option to license only those that require license reconciliation so that you do not assign a license to everyone. If, however, you want to license everyone at once (that does not already have a license), then you may want to use the option to license all unlicensed users. In order for the script to work, you will need to download and install the Microsoft Online Services Module for Windows PowerShell.

Read the help information for details on how to execute the script.

Get-help .\SetMsolUserLicense_AddLicense.ps1 -full

A copy of the script can be downloaded by clicking on the link below.

Office 365 Script: Get Office 365 Account Sku ID’s and Service Plan Names

Thomas Ashworth — Wed, 11 Apr 2012 21:46:00 GMT

Preparing to assign Office 365 licenses to users, but want to disable certain plans associated with the license sku id? Well, before you can do that, you need to know the names of the service plans. Use the following script to get the account sku id’s for a tenant and the corresponding service plan names.

Read the help information for details on how to execute the script.

Get-help .\GetAccountSkuIdsAndServicePlanNames.ps1 -full

A copy of the script can be downloaded by clicking on the link below.

Connect to Office 365 via Remote PowerShell

Thomas Ashworth — Wed, 11 Apr 2012 21:28:00 GMT

First, I should point out that there are a couple of ways of connecting to Office 365. One option involves using the Microsoft Online Service Module for Windows PowerShell cmdlet named Connect-MsolService. This option will connect you to the Office 365 PowerShell web service so that you can execute any of the cmdlets that are included in the MSOnline module.

Another option involves establishing a remote PowerShell connection to Exchange Online for the purpose of remotely executing native Exchange cmdlets against Office 365. This is the option that I describe as follows.

Try creating a function and adding it to your PowerShell profile so that you can quickly execute the function from any open PowerShell session when you need it. Start by creating a PowerShell profile if you do not already have one. The following one liner will create an empty PowerShell profile.

PS> New-item $profile –itemtype file –force

Next open the profile file in Notepad. This step is easily performed from PowerShell using the following command.

PS> notepad $profile

Copy and paste the following function into the profile, save the file, and restart PowerShell (or reload the profile).

Function Connect-ExchangeOnline

{

[CmdletBinding()]

param

(

[Parameter(Mandatory = $False)]

[System.Management.Automation.PsCredential]$Credential = $Host.UI.PromptForCredential("Enter MSOL Admin Credential",

"Enter the username and password of an MSOnline Administrator account.",

"",

"userCreds"),

[Parameter(Mandatory = $False)]

[System.Uri]$Uri = "https://ps.outlook.com/powershell/"

)

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $Uri -Credential $Credential -Authentication "Basic" -AllowRedirection

Import-PSSession $session -AllowClobber

Return $session

}

Now, when you need to connect to Office 365 to run Exchange cmdlets, you can simply type “Connect-ExchangeOnline” directly at the PowerShell prompt just as if you were launching a cmdlet. It is no longer necessary to try to remember where you stored that script or text file that contains the lines of code used to establish the connection - the code/function is readily available upon demand at your fingertips every time you launch PowerShell.