keeping AD in sync with a nother database


hey guys,

this more of best practices question, work large company , keep lot of our detailed employee information in employee sql database.  have been asked try keep of information the employee database in sync ad several times per day.  dba of employee database says can kick out csv file or whatever employee info several times day.  know can use ldifde or csvde import user attribute data, if work fine test is it a practice have scripts run several times every day?  feels little rigged when start bulk importing everyday using tools.  else keep stuff going time? guess worry somthing changing 1 day and the data being exported in incorrect format , ldifde or csvde imports incorrectly , blows away attribute, etc because stop monitoring it.  trying figure out best practice keeping ad updated info sql database.  if guys feel common or have going on everyday in automated process let me know feel little better.  if has ever seen problem pop-up automating ever few hours, let me know.


dan heim

this identity managment systems for

in microsft native world forefront identity manager,   there 3rd party ones well.

for example, our ad synced sap, on 2 hour refresh.

yeah cobble scripts, that's going bite 1 day.

 



Windows Server  >  Directory Services



Comments

Popular posts from this blog

DCOM received error "2147746132" from...

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

DFSR RPC replication errors 5014 1726 with large files over VPN