So imagine a situation where you have Office 365 and you synchronise your on premise Active Directory with Office 365 via DirSync or Windows Azure Active Directory Sync Tool to give its full name. One day an employee comes to you and informs you of their name change which you duly change in your on premise active directory and either wait for a sync to occur or trigger on manually. Then you find out that the users logon name in Office 365 hasn't changed so they are still logging in with their old logon name or worse they cannot access their mailbox. ...continue reading "Changing a user’s logon name in Office 365"

This is a quick guide on using PowerShell to assign Office 365 licenses to existing users that you have previously created. I've used this in environments where I have created large numbers of users in Office 365 using PowerShell as described in this post and then needed to assign licenses to those users so they can use their Office 365 mailboxes etc. ...continue reading "Licensing new Office 365 users"


In this scenario I have a Exchange 2013 Hybrid environment with Office 365 and 99% of the users have mailboxes in Office 365.

Creating a mailbox for an existing Active Directory user isn't possible through the Exchange GUI using the Exchange Admin Console (EAC) and must be done through PowerShell, here is how its done. ...continue reading "Creating an Office 365 mailbox for an existing Active Directory user"

I have been recently working on an Office 365 project with a client which involved implementing single sign-on using ADFS. During the pilot phase I encountered a strange issue where some users when trying to sign into their mailbox via ADFS it would not log them in and just refresh the page, it was like it accepted their login credentials but then didn't redirect them back to the OWA page where they should be going to. ...continue reading "ADFS 2012 R2 login fails for some users"

There has been a number of occasions when I have seen this error occurring on servers running DirSync, the error is this one:

Event ID:      6313
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FIMSync

The server encountered an unexpected error creating performance counters for management agent "Active Directory MA".

Performance counters will not be available for this management agent.

The solution is a relatively simply one:

  1. Delete this registry key first:
  2. Next from an elevated command prompt run:
    unlodctr.exe FIMSynchronizationService
  3. Then run from the same elevated command prompt:
    lodctr.exe "C:Program FilesWindows Azure Active Directory SyncSYNCBUSSynchronization ServiceBinmmsperf.ini"

After these steps restart the service FIMSynchronizationService and you should be all sorted. This has worked for me numerous times

I was spending some time going through Exchange PowerShell cmdlets to create an Admin Role with the least permissions required for an account for the System Center Configuration Manager Exchange Connector when I stumbled across this excellent script. It was hard to find so I am putting it out there for others in the hope it gets more exposure




If you are using a Federated domain with your Office 365 there may be occasions when you would want to convert your domain back to a Standard or Managed domain type. The two reasons for doing this I can think of are: ...continue reading "Office 365 converting domain from Federated to standard"

I recently had the pleasure of assisting a client with their decommissioning of their Exchange 2003 environment as they wanted to move to Office 365 in the cloud rather than upgrading to an on-premise Exchange 2010 environment. This came down purely to cost as for 15 mailboxes in Office 365 is a lot less than the cost of a new server and Exchange 2010 licensing.

Anyway although I was initially asked only for some general advice and assistance because the client wanted to do it themselves, it soon became clear I was going to end up pretty much doing it for them. ...continue reading "Migrating Exchange 2003 to Office 365"