Any help would be much appreciated, also you might like to look ad the ldap_details.php it has a "hidden switch" if you use the inject=y option, it will attempt to "inject" the current user in to the database from the AD, however this was only a proof of concept, so you don't need to do things this way.
It does illustrate how to create the database table "on the fly" however, which I needed to do, as I couldn't find any complete documentation about what AD was likely to throw back with the query. (It doesn't (yet) work for the Computer account from AD, but I would like to add this functionality somehow, and is very buggy, so use with care
)
To try this idea out, look at the ldap details for a user from the OA page, for example
..ldap_details.php?name=MYDOMAIN%5Cjsmith&full_details=y&record_type=user&
then try
..ldap_details.php?name=MYDOMAIN%5Cjsmith&full_details=y&record_type=user&inject=y
Look at the OA tables, and the new ldap tables should have "automagically" appeared and the user jsmith should be in the table.
The alternative method would be to use the audit script to do the job, (as per the above example) for which we would need to pin down all of the fields we want to harvest, and create the tables in advance of running the script on the domain.
If we also harvest the Computer accounts, we can see which machines have never been audited, by comparing the AD info with the audited machine info.. in fact there are lots of things we can do with this info.....
I was thinking of having a page to "harvest" the Active details, say 100 records at a query till it got the lot, so as not to kill my DC, but never completed the code as I have other things to do
which pay the bills...