Adding a Custom Attribute to AD for use in a hub transport email signature.


I have created a HTML sig for one of my customers and added it to the exchange as a transport rule and it works perfectly assing names, telephone numbers etc.

The only issue i have is that they want to further items adding which arent a normal section in ad.  I understand you can use CustomAttributes1-15 to do additional items.

I have gone through the process of adding a customattribute call CustomAttribute1 of which will contain their qualifications (such as LLP) but it is not appearing in my html sig.

Any ideas?

timb551IT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

how have you called the custom attribute

%%CustomAttribute1%% would be the right way of doing it

if you post up the transport rule and the HTML Sig to go with it that would help
timb551IT ManagerAuthor Commented:
Yes I have called it %%CustomAttribute1%%

Extract from rule

<html lang="en"><head><meta http-equiv="Content-Type" content="text/html;charset=utf-8"><style type="text/css">body,td,th,p{font-family: Tahoma, Geneva, sans-serif;font-size:11px;max-width:600px}a{color: inherit;}.d{font-size:10px;color:#999;}</style></head><body><p>Kind Regards,</p><br/><p><strong>%%displayName%%</strong> %%CustomAttribute1%%<br/>%%title%%</p><br/><table width="600" cellspacing="0" cellpadding="0"><tr><td style="border-right:solid 2px #797979;" width="200" rowspan="10">

can you trying running Get-  cmdlet to see if its able to read them properly

i.e. get-mailbox -RecipientFilter { CustomAttribute1 -eq "LLp"} and see if you get them coming back


Get-Mailbox -ResultSize Unlimited | Where-Object {$_.CustomAttribute1 -eq “LLC”}

i think both should work
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

timb551IT ManagerAuthor Commented:
Ran the first one and got

[PS] C:\Windows\system32>get-mailbox -RecipientFilter {CustomAttribute1 -eq "DOCTOR"}
A positional parameter cannot be found that accepts argument 'CustomAttribute1 -eq "DOCTOR"'.
    + CategoryInfo          : InvalidArgument: (:) [Get-Mailbox], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Get-Mailbox

Ran the second one and it just went to a new blank line
do you get >> 
or does it just hang on a blank line

I have just added something into custom attribute1 and searched with this

Get-Mailbox -ResultSize Unlimited | Where-Object {$_.CustomAttribute1 -eq "MSc"}

took 20-30s but came back with 1 result
timb551IT ManagerAuthor Commented:
It thinks about it for a while but then just goes to the next line.
what happens when you do this

get-mailbox -identity "username" | fl  
for username put in someone who has the attribute set

this should return a lot info on the mailbox and if Excahgne can see the attribute properly you will see it in the list

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
timb551IT ManagerAuthor Commented:
CustomAttribute1                       :
CustomAttribute10                      :
CustomAttribute11                      :
CustomAttribute12                      :
CustomAttribute13                      :
CustomAttribute14                      :
CustomAttribute15                      :
CustomAttribute2                       :
CustomAttribute3                       :
CustomAttribute4                       :
CustomAttribute5                       :
CustomAttribute6                       :
CustomAttribute7                       :
CustomAttribute8                       :

Curious why it isnt propegated?
timb551IT ManagerAuthor Commented:
I have figured it out.

Sorry its OF (operator fault)

I was putting in the details incorrectly into AD.  Its called ExtensionAttribute1 not customattribute1
the name changed at somepoint, they were CustomAttributes and changed to extetntion

just to keep people on there toes
timb551IT ManagerAuthor Commented:
Ridiculous behavior from Microsoft :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.