Skip to main content

Implementing Parallelism With A SearchResultCollection

Implementing Parallel.ForEach with a SearchResultCollection:
The below piece of code helps to check the given user is a part of the given active directory group. To implement Parallel.ForEach with a SearchResultCollection, do the casting with the SearchResult object and covert it into a list.

//// Directory Searcher
var directorySearcher = new DirectorySearcher(string.Format("(CN={0})", groupName));

//// Find group
var searchResultCollection = directorySearcher.FindAll().Cast().ToList();
Parallel.ForEach(searchResultCollection, searchResult =>
{
 // enumerate members
 var resultPropColl = searchResult.Properties;
 Parallel.ForEach(resultPropColl["member"].Cast().ToList(), member =>
 {
   var memberEntry = new DirectoryEntry("LDAP://" + member);
   var userProperties = memberEntry.Properties;
   if (GetUserNameFromProperties(userProperties, "sAMAccountName") == userName)
   {
     return true;
   }
  });
 });
Labels:

Popular posts from this blog

ISAPI & CGI Restriction configuration missing in IIS

In windows 7 by default ISAPI & CGI Restrictions are not configured. To enable ISAPI & CGI restrictions, GoTo -> Control Panel -> Programs -> Click on "Windows features on or off -> Expand Internet Information Services - >Expand World Wide Web Services ->Select CGI and ISAPI extensions and Click OK. After enabling, Check in IIS, Open your IIS and the feature will be available. What is ISAPI and CGI restrictions : ISAPI and CGI restrictions are request handlers that allow dynamic content to execute on a server. These restrictions are either CGI files (.exe) or ISAPI extensions (.dll). You can add custom ISAPI or CGI restrictions if the IIS configuration system allows this.
Read more

Error : Task Scheduler - This task requires that the user account specified has Log on as batch job rights

In one of the production environment, we were running with low disk space problem because of the logs. To cleanup the old logs created a  task within the scheduler and have specified "Run whether use is logged on or not". The user account we used was the system logged on user. The task was running fine, after few months as a security policy the password expired. Since the old password expired we had to apply the new password for the task also, but this time we decided to create a new account specifically for the task scheduler with password never expire option. While setting up the new user account and password, run into the below issue: "The task required that the user account specified has log on as batch job rights" To fix the issue follow below steps: From Run type "secpol.msc /s" and enter, the local security policy snap in will open. Select "Local Policies" in MSC snap in Select "User Rights Assignment" Righ...
Read more