I' m trying to take benifit of Custom attribute1 in Exchange 2007 by populating it with Employee Number and make it searchable in Microsoft Outlook.Users would like to find a specific employee by typing the employee number in the "To:" fieldin Outlook and Hit Check Names Button... But it doesn't seem to work for me, there's no results returned in outlook...Any idea ?

Not sure if this can be done. Normally Attributes are used to create filters(based on the value) . Check name button is like Directory look up which resolves the name based on the AD attributes. Probabaly you might need to look for any other attribute which can take care of this.Raj

On Sun, 13-Dec-09 03:41:07 GMT, hamdim wrote:>I' m trying to take benifit of Custom attribute1 in Exchange 2007 by populating it with Employee Number and make it searchable in Microsoft Outlook. Users would like to find a specific employee by typing the employee number in the "To:" field in Outlook and Hit Check Names Button... But it doesn't seem to work for me, there's no results returned in outlook... Any idea ? Why not put the information into the "Alias" (mailNickname) property?It seems to be the way it's being used.---heisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

I' m trying to take benefit of Custom attribute1 in Exchange 2007 by populating it with Employee Number and make it searchable in Microsoft Outlook.Users would like to find a specific employee by typing the employee number in the "To:" fieldin Outlook and Hit Check Names Button... But it doesn't seem to work for me, there's no results returned in outlook...Any idea ? You can do this by updating the schema to allow Ambiguous Name Resolution (Automatic Name Resolution). First register the chema snap-in (if you haven't done so):C:\WINDOWS\SYSTEM32\REGSVR32 SCHMMGMT.DLLLaunch the MMC and add the Active Directory Schema. In attributes drill down to extensionAttribute1. Make sure these three properties are marked: Index this attribute in the Active Directory, Ambiguous Name Resolution, Replicate this attribute to the Global Catalog. And after some minutes ... give replication within a site between 5 and 15 minutes:This works with Outlook and OWA, also with Outlook Express, if you configure the client to check names in the Active directory before it sends messages. And -- just tested it -- with Entourage 2003 for Mac, WSE and Mac OS X Snow Leopard Mail.Harnessing the power of Ambiguous Name Resolution (ANR)http://www.msexchange.org/articles/Ambiguous-Name-Resolution.html Tony Redmond, Exchange 2007 (which I happened to be reading right now -- still incredible good)http://books.google.com/books?id=W3hhKK7rKnYC&pg=PT108&lpg=PT108&dq=Updating+the+schema+to+allow+Ambiguous+Name+Resolution&source=bl&ots=6IyYrzUB4-&sig=45QEkxGHFGGPKmCUoFd4_MUAxok&hl=no&ei=TnclS6_YF4Pp-Aapq5jHBg&sa=X&oi=book_result&ct=result&resnum=1&ved=0CAgQ6AEwAA#v=onepage&q=Updating%20the%20schema%20to%20allow%20Ambiguous%20Name%20Resolution&f=false MCTS: Messaging | MCSE: S+M | Small Business Specialist

Hi,Solution provided by Jon-Alfred is working perfectly , I just enabled options " Index this attribute in the Active Directory" and "Ambiguous Name Resolution"."Replicate this attribute to the Global Catalog" option was already enabled.The result appears immediatly in OWA and working fine , but with Microsoft Outlook 2007 it's not yet working (Iguess it will take some time until OAB is updated ? )Thank you all ...

On Mon, 14-Dec-09 07:23:59 GMT, hamdim wrote:>Hi,Solution provided by Jon-Alfred is working perfectly , I just enabled options " Index this attribute in the Active Directory" and "Ambiguous Name Resolution"."Replicate this attribute to the Global Catalog" option was already enabled.The result appears immediatly in OWA and working fine , but with Microsoft Outlook 2007 it's not yet working (Iguess it will take some time until OAB is updated ? )Thank you all ... at's why I suggested using themailNickname (a.k.a. 'alias') property.See these (and probably more) KB articles:http://support.microsoft.com/kb/831124http://support.microsoft.com/kb/841273---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Rich,I prefered to keep original mailNickname attribute, as i would like also to search users by their AliasThe 1st KB article (How to force Outlook 2007 or Outlook 2003 to resolve proxy addresses and custom properties in Cached Exchange Mode) was very helpful for me, and put me on the right wayI tried Manual setting and Group Policy setting , and both methods working fine with Microsoft Outlook 2007 !Many Thanks ... Hamdi Msalhi| System Engineer MCSE, MCITP (Messaging)

On Tue, 15-Dec-09 16:02:20 GMT, hamdim wrote:>Rich,I prefered to keep original mailNickname attribute , as i would like also to search users by their AliasThe 1st KB article (How to force Outlook 2007 or Outlook 2003 to resolve proxy addresses and custom properties in Cached Exchange Mode) was very helpful for me, and put me on the right wayI tried Manual setting and Group Policy setting , and both methods working fine with Microsoft Outlook 2007 !Many Thanks ... working in Exchange cached modeand using the OAB it'll work. If they're using the OAB it won't work.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP