Hi all, I've run into a spot of trouble with getting SharePoint to recognise 3 custom active directory attributes we have created. These3 custom attributes are: Fire Warden, First Aider & OHS Member. They have been created (but none are set as of yet) and applied to the user class (sorry if my AD terms are wrong, basically, they are the same as how you set your phone number, manger, etc in AD). However, after a full user profile import, they are not showing up anywhere, Not in Managed or crawled. Am I missing something? Has anyone done these before? Edited the AD schema and got SharePoint to see the new custom attributives/ properties? I'm also aware I could be doing this completely wrong, so if you see an error in my logic, please point it out. Cheers and Thanks in Advance, Daniel Brown

Sorry for the brief exploitation previous, here is a little more detail. Our AD Administrator has created (modified the Schema) 3 custom AD attributes for the User Class and we can search on them via AD MMC snap in, etc. Currently no data has ever been set to any user, marking them a fire warder, first aider or OHS member. Again, they have never been set on any user every (so far). So I perform a full import (via SSP -> User Profiles & Properties -> Start Full import). No errors occur. From here, I click on "Add profile property". (Via SSP -> User Profiles & Properties -> Add profile property). I fill out: Name Display Name Policy: Required Default Privacy Setting: My Manager Show in the profile properties section of the user profile page: ticked Alias: ticked Source Data Connection: Master Connection Data source field to map: ----> this is a problem. The Custom fields do not show in this list at all. Should they? I am assuming that they should appear in this list. Surly, I am doing something wrong, or something is wrong with my process. Any clues or insight would be greatly appreciated. Also, I'd like to recap on what Im trying to achieve. We have a requirement from our HR department to provide a way for people to be marked as either a Fire Warden, First Aider and/or OHS Committee member. We have decided to create 3 new attributes in the AD schema and apply them to the User class (sorry if this terminology is incorrect, really they are just another "Phone" field or something which can be set on the account) I wish to be able to search via these 3 fields via People Search. where you an select if you want to list all Fire Wardens, First Aiders and/or OHS Committee members (separate lists or combined). Now Im confident that I can indeed modify people search to give me this ability. If you have any thoughts or ideas on how I can archive this goal or problems with the path I am travelling to try to archive it, I'd love to hear your comments / views. Regards, Daniel Brown

Hi Daniel, You probably already found a solution but here's what got me going: http://paulhorsfall.co.uk/archive/2007/07/13/Unable-to-Configure-MOSS-Property-Import-Mappings.aspx

First of all, check if you can use the custom attributes from AD Users and Computers. Do you have the rights to see(read access) them and if so do you have the rights to change them? You can also test this from within ADSIedit! Hope this gives you a way to tackle the problem. Regards, Bart.