CPolydorou.Exchange v2.8.1

Hi, its Chris and I have updates on my Microsoft Exchange module to share!

A new function is added to version 2.8.1, named "Copy-RecipientAddress". This function copies proxy addresses from one object to another. This is a very common scenario when synchronizing recipients between directories since ambiguous objects may be created.

Usually, a mail contact is created by the synchronization service that has the smtp address of an existing recipient. Removing the contact will resolve the issue - provided that the object coming from the remote organization will be joined on the next synchronization operation, but if the contact has been available on the GAL for a while, users may have sent messages to this contact. If this is the case, outlook keeps a copy of the Legacy-Exchange-DN address of the contact in it's cache and when the user will try to send a message to the contact you've removed, the message will not be delivered.

Enter Copy-RecipientAddress! If you copy the addresses (including X400 and X500) from the contact to be removed to the object that will remain, you will not face the above issue.

Let's take a look at an example of the command.

Here's our test mailbox and the addresses assigned to it:


And this will be the object causing the ambiguous address:


After we've resolved the issue on the system that created or updated the contact instead of joining it, we will copy the addresses of the contact to the mailbox:


As shown in the verbose output, the SMTP address "test.mailbox@lab.local" was not copied since it already existed, the SMTP address "test.contact@lab.local" has been copied and the Legacy-Exchange-DN address has been added as a X500 address. Now that the addresses are copied, we can remove the contact causing the issue!

Since the addresses of the objects are stored in Active Directory, you may have to wait a bit for the changes to take effect due to replication.

Have fun!

Popular posts from this blog

Domain Controller Machine Password Reset

Image
On my lab environment, I've configured two Active Directory sites since most enterprises have offices in more that one places. My lab however is not running 24/7 and the domain controllers in the second site are rarely turned on in order to save resources. This leads to issues with the Active Directory replication such as the "The target principal name is incorrect" error when I execute:  repadmin /syncall /AdeP. To remedy the issue, we have to reset the machine password of the domain controller that has been offline. First off, we are going to stop and disable the Kerberos Key Distribution Center (kdc) service on the problematic domain controller, in our case DC4. There may be some tickets in the cache so we should also clear them using klist purge Now it's time to change the machine password of the domain controller using the command netdom resetpwd /s:dc3 /ud:lab\administrator /pd:* Replace the "lab\administrator" with an account on your...
Keep reading

Managing Active Directory User Certificates using PowerShell

I first came across user certificates when I was working with email certificates a few years ago and I have to admit that I had trouble updating the certificates on the objects! Most organizations have a Microsoft Active Directory Certification Authority that issues the certificates used internally. When a certificate is issued to a user, the Microsoft Certificate Service saves the public key in Active Directory. The userCertificate attribute is a multi-valued attribute that contains the DER-encoded X509v3 certificates issued to the user. Although we rarely need to pay attention to this attribute, there are cases where we have to update it. To make things easier, I've written PowerShell functions to Get, Remove, Import and Export the certificates on that field. To get the list of certificates for an object, use the Get-ActiveDirectoryObjectCertificate function: PS C:\> Get-ActiveDirectoryObjectCertificate -UserPrincipalName cpolydorou@lab.local DistinguishedName  ...
Keep reading

Configuring a Certificate on Exchange Receive Connector

Today's article is about configuring Exchange receive connectors with specific certificates. Out of the box, Exchange uses self signed certificates to provide TLS secured mail flow. This will definitely be an issue if you expose the SMTP protocol to client computers since they won't trust the certificate. In this article we are going to configure a certificate that was issued by a third part authority to the Client Frontend receive connector. We'll start with getting the thumbprint of the certificate using the Get-ExchangeCertificate cmdlet: [PS] C:\> Get-ExchangeCertificate Thumbprint                               Subject ----------                               ------- 241B864DC82C664FECBA18B8D54987AAFB65B4C2 CN=*.lab.com, ... D4D210886B34E690191A1F008C78FDD0E7325DD4 CN=Exchange2013A 960171662EB26116...
Keep reading