GAL and Generational Qualifier Attribute

Question

Hi,
I have added a generational qualifier to Active Directory using
set-ADObject -identity 'CN=Sean Kelly,OU=Calgary,OU=RJC Users,DC=rjc,DC=local' -Replace @{generationQualifier='A+'}
Checking to make sure it is in there I used:
Get-ADUser skelly -Properties * | Select * > $env:userprofile\Desktop\Attributes.txt
Then in Exchange Management Console I update the offline address book.
In Outlook I download the latest version of the GAL.
My problem is that I don't get this attribute to show up when I click on my name in the Global Address list. What am I missing? Does the Display Name not show a generational qualifier by default? How do I get this field to show up as an extension to the
users name? 

Answer 1

Hi,
According to your description, I know that you have run a script to add an attribute on GAL however this attribute doesn't show up in OAB. Please correct me if there is any misunderstanding.
First I suggest double check the script is right. Sorry for the lack of knowledge on Script. I suggest asking Script Center to double confirm the Script so that we can get more professional suggestions. For your conveniece:
http://technet.microsoft.com/en-us/scriptcenter/dd742246.aspx
If my understanding is correct, I suggest double check whether the new attribute shows up in GAL. Please also using OWA to double check whether the new attribute exists.
Sometimes it needs time to sync data between DCs (if you have multiple DCs).
If the new attribute exists in OWA, it seems an issue on the Outlook client side or OAB side.
Outlook client side:
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
OAB side:
OAB files generate from MBX server, then distribute to CAS server via File Distribution service and download to Outlook client side.
Please follow following steps to narrow down this issue.
1. Following are the locations that .lzx files in CAS server and MBX server:
CAS server
C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB
MBX server
C:\Program Files\Micorosft\Exchange Server\V14\ExchangeOAB
Please verify whether the .lzx files update to the latest.
1. If the .lzx files in MBX server not update to the latest. It should be an issue on the OAB generation side.
2.
If the .lzx files in MBX server is latest, but CAS server not. It should be a distribution issue.
Please run Get-OabVirtualDirectory command in EMS to verify whether at least one OAB VD exist in the org. If not, please create a new one.
Please make sure whether any setup for Web Distribution. Selecting the “Enabling an Offline Address Book for Web Distribution” checkbox.
Please force restart File Distribution services to distribute OAB files manually.
3. If the .lzx files in MBX server and CAS server are all update to the latest. It should be the connectivity between CAS server and Client issue.
Please verify the network.
Please check DNS, MX, etc. configuration.
Please run “Test E-mail AutoConfiguration” to check the AutoDiscover details.
Please make sure the OAB URLs are correct.
If the OAB URLs are incorrect, please using following command to re-set them:Set-OABVirtualDirectory
-Identity "ServerFQDN\OAB (Default Web Site)" -ExternalUrl https://www.contoso.com/OAB -InternalUrl
https://mail.contoso.com/OAB
Please checking the App log and finding solutions from Microsoft Technet articles or KB, according to the Event ID.
If it still not working after performing the methods above unfortunately, please trying to re-build OAB Virtual Directory.
Article for reference:Remove,
Re-Create, and Reconnect an Offline Address Book Virtual Directoryhttp://technet.microsoft.com/en-us/library/bb123595(v=exchg.141).aspx 
Thanks
Mavis
Mavis Huang
TechNet Community Support