Transitioning to Exchange Server 2013: Should you make the hop from 2003 or 2010?

TrainSignal always has great information available.  This will help you to make a decision on implementing Exchange 2013.

Transitioning to Exchange Server 2013: Should you make the hop from 2003 or 2010?

by Todd Nelson


Connect to Office 365 with PowerShell

Using Windows Azure Active Directory Module for Windows PowerShell, enter the following commands to connect to Office 365 with PowerShell.

This command will provide the window to allow you to enter your Office 365 credentials … $cred=Get-Credential

In the login pop-up, enter your Office 365 administrator credentials to proceed.

Next, enter this command to create a new cloud-based PowerShell session with your Office 365 credentials … $s=New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $cred -Authentication Basic -AllowRedirection

This command brings that cloud-based PowerShell session to the local computer … $importresults=Import-PSSession $s

Good luck.

Reference(s): Connect Windows PowerShell to the Service

by Todd Nelson

On-Premise Public Folder Migration to Public Folders in Exchange Online

Earlier this week, I spoke with Office 365 support regarding on-premise public folder migrations to the new version of O365.  Based on what the engineer provided to me, the following is an “officially” supported migration path for migrating public folders in Exchange on-premise to public folders in Exchange Online.  Of course, there is no publicly accessible documentation for this procedure but I have tested these steps (in a lab environment) and it does work.  It is definitely not elegant though.


– Identify/record which on-premise public folders need to be migrated

– Identify/record permissions of each on-premise public folder

– Create Public Folder mailbox in EAC of Exchange Online (or via PowerShell)

– Create public folders with same structure as that on-premise and assign permissions (NOTE: This task can be performed via EAC, PowerShell or Outlook)

– Export on-premise public folders to PST file via Outlook

– Connect to Exchange Online mailbox via Outlook client to access public folders

– Import public folder PST into Exchange Online public folder structure


– Public Folders are not accessible or visible via Outlook Web App (OWA) in Exchange Online

– Public Folders mailboxes are limited to 25GB total size

– Additional Public Folder mailboxes seem to do nothing of value in Exchange Online

– Public Folder mailboxes do not require a license


– You must use Outlook 2007 or later to access public folders in Exchange Online

Best of luck.

Reference(s): Public Folders in Exchange Online, Set Up Public Folders in a New Organization, New Feature – Public Folders in Office 365 Preview

by Todd Nelson

Email Forwarding in Office 365

Working with a customer the other day, I discovered they had a need to forward emails from an on-premise reporting system to a vendor using a customer supplied email address.  So, email to will need to be forwarded to  The setup is similar to that with on-premise Exchange.

There are some articles I found that state forwarding can be set up without a mailbox in Office 365 by instead using an External Contact.  Through testing the steps in these articles, I was unable to reproduce a contact that forwards email.  An external contact works for using as a contact to email to from the address list but does not work as a forwarder.  To configure forwarding, a mailbox is required.

To setup email forwarding in Office 365, we will first need to…

  • Identify which Office 365 account needs to have email forwarded to another SMTP address
  • Assign the account a license (or convert the mailbox to a shared mailbox and then remove the license)

Now we can assign a forwarding address via O365 OWA or PowerShell.

Via OWA signed in as a O365 admin…

  • Click on Home
  • Select Options under Outlook
  • On the “toolbar”, click the Manage Myself drop-down to select Another Account
  • Choose the mailbox you want to set up and click OK
  • You are now in the Options of the mailbox you chose
  • Click on Connected Accounts
  • Scroll to the bottom of the page until you see the Forwarding section
  • Enter the email (SMTP) address that all messages bound for this mailbox will be forwarded to (NOTE: Remember to select or deselect to keep a copy of the forwarded message)
  • Click Start Forwarding to complete the setting
  • To reverse (or disable) this setting, clear the email address field and click Stop Forwarding

Via PowerShell…

  • Connect to Office 365 with PowerShell
  • To enable forwarding for a mailbox and keep a copy of the forwarded message, enter the following command …
    • Set-Mailbox -Identity MailboxAlias -DeliverToMailboxAndForward $true -ForwardingSMTPAddress
  • To disable forwarding for a mailbox, enter this command …
    • Set-Mailbox -Identity MailboxAlias -DeliverToMailboxAndForward $false -ForwardingSMTPAddress $null
  • To enable forwarding for a mailbox but not keep a copy of the message, enter the following command …
    • Set-Mailbox -Identity MailboxAlias -DeliverToMailboxAndForward $false -ForwardingSMTPAddress


by Todd Nelson

SharePoint Online Error Access Denied When Accessing Team Site

Are your users receiving “Error: Access Denied” when accessing the SharePoint Online Team Site?

Here is how to resolve it…

Log into the Office 365 portal as the global admin.

Access the Team Site

Click the Site Actions drop down (top left corner of the page) and select Site Settings

Under the Users and Permissions click on People and Groups

Click the New drop down and select Add Users

In the Select Users section, enter the name of a user that has been assigned a SharePoint Online license and click the Check Name icon.

Once the name is validated, click OKNOTE: If the name does not validate, it is potentially because the account has not been assigned a SharePoint Online license.

The new user appears in the Team Site Members page.  At this point, the user will now be able to access the Team Site.


by Todd Nelson

Change the Product Key for Windows Server 2012

I was working with a customer the other day who was having difficulty in getting their Windows 2012 servers activated.  Come to find out the product key was entered incorrectly during the OS installation.  However, they couldn’t figure out how to change it.  It is fairly simple once you understand that the method of changing the product key is no longer GUI-based like it was with Windows 2008.

To make the change, open an elevated PowerShell console…

Enter the following command to remove the existing product key:  slmgr -upk

Once you have your new (or correct) product key, the following command will install it:  slmgr -ipk <New Product Key>

Good luck.


by Todd Nelson