Category Archives: Exchange Online

Lync Room System (LRS) Setup with Hybrid Exchange Online Deployment

I’ve found a number of articles that discuss setting up Lync Room System (LRS) with Exchange and Lync On-Premise and with Exchange Online but none that dealt with a Hybrid Exchange deployment.  Below are the steps I used to get LRS configured with Skype for Business Online and Exchange Online with a Hybrid deployment.  For more information on Lync Room System, check on the following link…

https://blogs.technet.microsoft.com/lync/2013/02/19/the-lync-room-system-lrs/

Create Room Mailbox in Office 365

  1. Connect to Exchange Online via PowerShell
  2. To create the Room Mailbox, run “New-Mailbox -room -name “Skype Room Test” -RoomMailboxPassword (ConvertTo-SecureString ‘Password’ -AsPlainText -Force) -EnableRoomMailboxAccount $true”
  3. To configure the required calendar processing, run “Set-CalendarProcessing “Skype Room Test”  -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -DeleteSubject $false”
  4. Log into the Office 365 Portal.  Click on Active Users and find the Skype Room Test.
  5. Change the accounts Email Address / UPN to be “skyperoomtest@domain.com” (where domain.com is your primary UPN suffix).
  6. Assign both a license for Both Exchange and Skype for Business to the account

Create Remote Mailbox On-Premise

  1. Log into the Exchange Admin Center on-premise
  2. Click on Recipients –> Mailboxes
  3. Click on the drop down next to the + sign and select “Office 365 mailbox”
  4. Enter the appropriate account information
  5. Open the new account in AD Users and Computers and verify that the UPN and the primary Mail value match what you set in Office 365
  6. Force or wait for a directory synchronization to run
  7. Verify that the account in the Office 365 Portal shows as “Synced” versus “Cloud”

Enable Lync Room Account

  1. Connect to Skype for Business via PowerShell
  2. Determine an existing accounts Registrar Pool by running “Get-CSOnlineUser user@domain.com | FL Name,RegistrarPool”
  3. To enable LRS, run “Enable-CsMeetingRoom –Identity skyperoomtest@domain.com -SipAddressType EmailAddress –RegistrarPool pool.infra.lync.com” where “pool.infra.lync.com” is the RegistrarPool value determined in Step 2
Advertisements

New Azure AD PowerShell Module and Windows Server 2008 R2

A new version of the Azure Active Directory Module for PowerShell was released in mid September 2014.  You can find the link to it here…

http://aka.ms/aadposh

That’s great except if you are trying to install it on Windows Server 2008 R2.  If you read the link it looks like all you need is the version of .NET and PowerShell that comes with Windows 2008 R2 (3.51 and 2.0 respectively).

When you install the updated version of the AAD Module for PowerShell on a vanilla machine and launch it though you are greeted with this message…

AAD

That doesn’t look good!  I could never find any official support article but I found a couple of hints that it needed PowerShell 3.0.  So I installed Windows Management Framework 3.0 on my system and tested again and it worked.  You can download it here…

http://www.microsoft.com/en-us/download/details.aspx?id=34595

Note, if you are installing this on a production server, make sure you aren’t running any of the unsupported products listed under the System Requirements section.

Hope this helps!

Migrating Public Folders to Exchange 2013 / Exchange Online After Coexistence

If you are migrating from Exchange 2007/2010 to either Exchange 2013 or Exchange Online and your customer has Public Folders chances are you followed the following document from Microsoft for setting up coexistence with legacy Public Folders…

http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx

Now you’ve completed moving mailboxes to Exchange 2013 (or Exchange Online) and you want to migrate Public Folders to the new system so you follow one of the following articles…

http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx

Life is good.  You run the command…

Set-Mailbox -Identity <Test User> -DefaultPublicFolderMailbox <Public Folder Mailbox Identity>

…against a test mailbox and successfully access Public Folders.  You think you are all set and run…

Get-Mailbox -PublicFolder | Set-Mailbox -PublicFolder -IsExcludedFromServingHierarchy $false

…but, then to your shock, nobody else can get to the recently migrate Public Folders.

The problem is caused by when you setup legacy coexistence.  As part of this process you ran the command…

Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1

Your Exchange Organization still thinks it should direct Public Folder traffic to a remote Organization.  To fix this, run the following command…

Set-OrganizationConfig -PublicFoldersEnabled Local

It will take awhile to take effect but, once it does, you should see the DefaultPublicFolderMailbox automatically change for your mailboxes.  To check run the following command…

Get-Mailbox | FT Alias,DefaultPublicFolderMailbox

Office 365 PowerShell–The Two-Headed Monster

One of the best features in Office 365 is the ability to manage it via PowerShell.  However, currently there are two separate PowerShell interfaces into Office 365 depending on what you’re trying to do.  If you want to manage settings under the main Portal (think AD stuff) you connect via a PowerShell 1.0 interface requiring you to load tools on your local workstation.  If you want to manage things under Exchange Online you utilize PowerShell remoting which requires you to have nothing installed on your local system other than PowerShell 2.0.  Here’s the specifics for each method…

 

Portal PowerShell Administration

Prerequisites

  • Windows 7 or Windows Server 2008 R2
  • Windows PowerShell and the .NET Framework 3.5.1 enabled

Software to Install

  • Microsoft Online Services Sign-In Assistant – 32bit  64bit
  • Microsoft Online Services Module for PowerShell – 32bit  64bit

Connecting to the Microsoft Online Services Portal

  1. Click on Start > All Programs > Microsoft Online Services > Microsoft Online Services Module for PowerShell
  2. Run “Connect-MsolService”
  3. When prompted enter the credentials of an administrator account
  4. To get a list of all available commands run “Get-Command –Module MSOnline”

For a complete list of all commands and usage click on the following link…

http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh125002.aspx

 

Exchange Online PowerShell Administration

Prerequisites

  • Windows 7 or Windows Server 2008 R2 – No Additional Software Necessary
  • Windows XP SP3, Vista SP1, Server 2003 SP2, Server 2008 SP1 – See Below

Software to Install

Connecting to Exchange Online

  1. Click on Start > All Programs > Accessories > Windows PowerShell > Windows PowerShell
  2. The first time run “Set-ExecutionPolicy RemoteSigned”
  3. Run “$LiveCred = Get-Credential”
  4. When prompted enter the credentials of an administrator account
  5. Run “$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection”
  6. Run “Import-PSSession $Session”
  7. To get a list of all commands run “Get-Command –Module tmp*”

For a complete list of all commands and usage click on the following link…

http://help.outlook.com/en-us/140/dd575549.aspx