Forgive me if this seems to be a stupid question but I'm having a bit of a hard time setting up an ADLDS system to develop against.
The background: powers that be have decided that it would be nice to have all the custom data (there's not much) stored with the users in Active Directory rather than a custom database. I'm happy with that as we do need to integrate with AD to manage users better, and it seems to make sense to store the limited data there too.
So I have looked into setting up an ADLDS server to store the custom data in a custom schema class or two, and hook it up to AD at a later date.
I've managed to get ADLDS installed on Windows 7 dev box, I've got the schemas sorted using ADSIEdit and 'Active Directory Schema' snapins. I've created a user in a container in my new OU.
So now I have a user class that contains extra attributes in a flat format. Is this the way AD 'works' or can I get the data associated with the user stored separately in another object that can be linked with the user?
I cannot seem to get a dynamic auxiliary class associated with a user object at all in ADLDS - there is no objectClass in the list of attributes, and when I add it manually using LDP, ADSIEdit refuses to show the list of attributes (so I assume its bust). Is this a limitation of ADLDS? The docs suggest it should work.
The admin tools for this seems to be pretty rubbish - I don't think I'd like to give an admin ADSIEdit and let them create users and user data, are there better tools that can work with ADLDS in a more admin-friendly look (eg AD's Users and Computers)?
And lastly, am I approaching this right - is this something that is recommended for ADLDS, should I forget ADLDS and stick everything in AD, or should I just put user login info in AD and store all custom data in a local DB?