Reporting on privileged Active Directory accounts with SQL Server

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm One of a very common requirements when it comes to assessing Active Directory security is reporting on the user accounts which are part of the high privilege groups: Enterprise…

0

Extracting object ownership information from Active Directory into SQL

This posting is provided “AS IS” with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm There could be many reasons why tracking Active Directory objects ownership might be important: audit requirements, identity management processes enforcement, just to name a few. This blog will outline…

0

Extracting data from FIM Synchronization Service Run Profile log

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm Analyzing run history logs is an essential tasks in ensuring proper operation of your FIM environment. Often we need to go beyond analysis by creating scripts to detect and…

0

Correlating Active Directory accounts with their corresponding HR records in the absence of unique identifiers

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm The question of how the records stored in various repositories could be linked together inevitably comes up in most identity management related projects. For a variety of reasons (see…

0

Installing AD Connection Manager and AD Source components

Two DLLs make up the content of the package which you will need to deploy on your SQL Server: ADSource.dll – Active Directory Source Component ADSourceUI.dll – UI for the Source Component Placement of the components I am assuming that SQL 2008 was deployed using the default location of "C:\Program Files\Microsoft SQL Server\”, and that…

0