Managing Recipient Addresses using CPolydorou.Exchange

Managing the a recipient's addresses can be a time consuming process since it involves the multi value Active Directory attribute "proxyAddresses". This can be tricky when using PowerShell, especially for the less experienced administrator.

Since I have also wasted a lot of time on this, I decided to make things easier and write a few functions to update the proxy addresses of objects.

Getting
To get the proxy addresses of an object, simply use the Get-RecipientAddress function with the identity of the recipient.

[PS] C:\>Get-RecipientAddress -Identity cpolydorou@lab.com

Identity                               Type Address              Primary
--------                               ---- -------              -------
LAB.local/LAB/Users/Christos Polydorou sip  cpolydorou@lab.local
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou@lab.local False
LAB.local/LAB/Users/Christos Polydorou SMTP cpolydorou@lab.com   True

[PS] C:\>

Adding
The New-RecipientAddress cmdlet will add a proxy address to an object:

[PS] C:\> New-RecipientAddress -Identity cpolydorou@lab.com `
                               -Type SMTP `
                               -Address cpolydorou2@lab.local `
                               -Confirm:$false
[PS] C:\>Get-RecipientAddress -Identity cpolydorou@lab.com

Identity                               Type Address               Primary
--------                               ---- -------               -------
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou2@lab.local False
LAB.local/LAB/Users/Christos Polydorou sip  cpolydorou@lab.local
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou@lab.local  False
LAB.local/LAB/Users/Christos Polydorou SMTP cpolydorou@lab.com    True

[PS] C:\>

The "-Primary" switch will add the address as the primary one:

[PS] [PS] C:\>New-RecipientAddress -Identity cpolydorou@lab.com `
                                   -Type SMTP `
                                   -Address cpolydorou3@lab.local `
                                   -Primary `
                                   -Confirm:$ false
[PS] C:\>Get-RecipientAddress -Identity cpolydorou@lab.com

Identity                               Type Address               Primary
--------                               ---- -------               -------
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou@lab.com    False
LAB.local/LAB/Users/Christos Polydorou SMTP cpolydorou3@lab.local True
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou2@lab.local False
LAB.local/LAB/Users/Christos Polydorou sip  cpolydorou@lab.local
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou@lab.local  False

[PS] C:\>

Removing
Removing a proxy address is a lot easier using the Remove-RecipientAddress. This function will remove a proxy address from an object (removing the cpolydorou2@lab.local address):

[PS] C:\>Remove-RecipientAddress -Identity cpolydorou@lab.com `
                                 -Address cpolydorou2@lab.local `
                                 -Type SMTP `
                                 -Confirm:$false
[PS] C:\>Get-RecipientAddress -Identity cpolydorou@lab.com

Identity                               Type Address               Primary
--------                               ---- -------               -------
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou@lab.com    False
LAB.local/LAB/Users/Christos Polydorou SMTP cpolydorou3@lab.local True
LAB.local/LAB/Users/Christos Polydorou sip  cpolydorou@lab.local
LAB.local/LAB/Users/Christos Polydorou smtp cpolydorou@lab.local  False

[PS] C:\>

The above functions update the proxyAddresses field on Active Directory, thus some time may be required in order for the change to be visible and take effect.

The above functions are included in my Exchange module that is published on PowerShell Gallery.

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