AAD Connect Upgrade error - Microsoft.Online.Deployment.PowerShell.PowerShell InvocationException: An error occurred while executing the 'Get-MsolUser' command

An interesting issue occurred tonight during the upgrade of AAD Connect from 1.1.380 to the latest version.  Of course, time was of the essence, so an error immediately after the Credential prompt caused quite a bit of angst, and seemed impossible to work around. Unfortunately searching thru the install log under the C:\Program Data\AADConnect directory…

0

AAD Connect Event IDs

This is by no means a complete list, but it should get you started monitoring your AAD Connect Server…   Informational Events   AAD Connect Engine 904 – Scheduler related informational events There are a good number of 904 Informational events related to Scheduler starting, Scheduler settings changing, Purging AAD Connect Operations Run history, scheduler…

0

SKU and Service Plan ID values

This is by no means a complete list, it’s only what I’ve been able to collect so far, however here are a list of SKU ID and Service Plan ID values.    This may help you with errors returned, or cases where a service plan or SKU ID are provided and not the friendly plan name……

0

DN value in AAD Sync AAD Connect - the NEW format

DirSync \ FIM used to use the Immutable ID value in the Azure connector space, making it somewhat straightforward to search for objects in the Azure CS using the ImmutableID (either copied from MSOL powershell or from the onprem AD ObjectGUID value converted to a Base64 string), however in AAD Sync and AAD Connect the…

4

Powershell, The Clipboard, and re-living the past ...

One of my favorite Powershell features is the ability to export the output of pretty much anything to the clipboard using | clip I've found that piping to clip is much easier than trying to export output to a TXT or CSV file, then finding and opening the file… For those of you who are…

2

IMCEAEX non-delivery report

When migrating from on-prem Exchange to Office 365, it's best to treat it like any other cross-forest move and populate each object's LegacyExchangeDN value as an X500 address, otherwise you'll get NDR errors replying to old messages or calendar entries once mailboxes start moving. When receiving IMCEAEX NDRs, you can use the contents of the…

0

msExchRemoteRecipientType

When dealing with attributes synced to O365 via FIM \ DirSync \ AAD Sync, you will frequently encounter the msExchRemoteRecipient type attribute, previously empty in on-prem Exchange (only msExchRecipientTypeDetails and msExchRecipientDisplayType had values) the msExchRemoteRecipientType will have the following values depending on the object type and how the mailbox and archive were enabled \ moved…

5

What is this .... (FYDIBOHF23SPDLT)

You may notice that the Legacy Exchange DN value in onprem AD typically contains something like : ou=External (FYDIBOHF23SPDLT)/cn=Recipients Just in case you were curious, the FYDIBOHF23SPDLT value is a constant, it’s basically the phrase EXCHANGE12ROCKS…  the letters are all alpha-shifted one character. It’s changed for each version of Exchange over the years.

0

Provisioning Remote Object Types in Exchange Online

Many times, once a customer has migrated from Exchange on-premises to Exchange Online, they want to completely decommission ALL on-premises Exchange servers.  The issue this presents is that on-prem AD is authoritative for all objects, and then synced to Azure using AAD Sync. There are 2 options – You can maintain a single Exchange server…

0

Migrating OnPrem DLs to Cloud DLs

If you find that you need to migrate an onprem DL into a cloud DL, you can use the script below…. <# .SYNOPSIS        This command converts a Federated DL to a Cloud-only DL   .DESCRIPTION     This command accepts the DISPLAY NAME of a on-prem DL that has been synchronized to Azure and appears…

0