Hi Folks,

I'll try to explain this best I can, I've been very frustrated as I haven't found a single article on the net, and I've been searching for 3-4 days. Perhaps Im using wrong terms, but I've decided to hit the coders forums.

I have an Active Directory Server (With Exchange), an SQL Server on another, and I have a custom application on a final server.

Now, I can get users to authenticate in the Custom application fine, but whats racking my brain is how to link user settings(preferences, etc) that would be stored in SQL Server to the authenticated user.

Someone mentioned to me using the SID of a user, as that is pretty much unique, however the problem I see, is when a user is deleted using Active Directory Users and Computers (Or some other method that isn't controlled by my application). When one is deleted, if that same user is recreated would it not clash or would there not be a possiblity of clashing and picking up the old users data? (And the fact that the data still exists in the SQL server after the account is deleted)

What I need to know is if there is any sort of way to process an Account Deletion in AD if it is done using the Users and Computers MMC snap-in.

Or any other way that I could go about to solve the problem.

Cheers,
Ben

A simple scheduled database job should do the trick. Using an LDAP provider within a SQL Server stored procedure, you can gain a list of all users from the directory.

The information can then be inserted into a temp table, compared to the data within your SQL table. Any that exist in your SQL table and not in the temp table are presumed deleted and you can mark as deleted from your SQL tables.

This should provide a solution for your problem albeit not the one your were looking for.

Cheers


Squatss