timb551
asked on
Adding a Custom Attribute to AD for use in a hub transport email signature.
Hi
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?
thanks
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?
thanks
ASKER
Yes I have called it %%CustomAttribute1%%
Extract from rule
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html;charset =utf-8"><s tyle type="text/css">body,td,th ,p{font-fa mily: Tahoma, Geneva, sans-serif;font-size:11px; max-width: 600px}a{co lor: inherit;}.d{font-size:10px ;color:#99 9;}</style ></head><b ody><p>Kin d Regards,</p><br/><p><stron g>%%displa yName%%</s trong> %%CustomAttribute1%%<br/>% %title%%</ p><br/><ta ble width="600" cellspacing="0" cellpadding="0"><tr><td style="border-right:solid 2px #797979;" width="200" rowspan="10">
Extract from rule
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html;charset
darn.
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
or
Get-Mailbox -ResultSize Unlimited | Where-Object {$_.CustomAttribute1 -eq “LLC”}
i think both should work
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
or
Get-Mailbox -ResultSize Unlimited | Where-Object {$_.CustomAttribute1 -eq “LLC”}
i think both should work
ASKER
Ran the first one and got
[PS] C:\Windows\system32>get-ma ilbox -RecipientFilter {CustomAttribute1 -eq "DOCTOR"}
A positional parameter cannot be found that accepts argument 'CustomAttribute1 -eq "DOCTOR"'.
+ CategoryInfo : InvalidArgument: (:) [Get-Mailbox], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFoun d,Get-Mail box
Ran the second one and it just went to a new blank line
[PS] C:\Windows\system32>get-ma
A positional parameter cannot be found that accepts argument 'CustomAttribute1 -eq "DOCTOR"'.
+ CategoryInfo : InvalidArgument: (:) [Get-Mailbox], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFoun
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
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
ASKER
It thinks about it for a while but then just goes to the next line.
Untitled-1.jpg
Untitled-1.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
CustomAttribute1 :
CustomAttribute10 :
CustomAttribute11 :
CustomAttribute12 :
CustomAttribute13 :
CustomAttribute14 :
CustomAttribute15 :
CustomAttribute2 :
CustomAttribute3 :
CustomAttribute4 :
CustomAttribute5 :
CustomAttribute6 :
CustomAttribute7 :
CustomAttribute8 :
Curious why it isnt propegated?
CustomAttribute10 :
CustomAttribute11 :
CustomAttribute12 :
CustomAttribute13 :
CustomAttribute14 :
CustomAttribute15 :
CustomAttribute2 :
CustomAttribute3 :
CustomAttribute4 :
CustomAttribute5 :
CustomAttribute6 :
CustomAttribute7 :
CustomAttribute8 :
Curious why it isnt propegated?
ASKER
I have figured it out.
Sorry its OF (operator fault)
I was putting in the details incorrectly into AD. Its called ExtensionAttribute1 not customattribute1
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
just to keep people on there toes
ASKER
Ridiculous behavior from Microsoft :)
%%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