Has anyone else experienced extreme slowness while using activities from the AD IP? I
created a runbook to look for orphaned user folders in our user directories
across all our sites which used the "Get User" activity and I had to
find something else due to the length of time it took to search. A list of 286
folders took over 1 1/2 hours before I finally killed it. I can do the same
search with the AD cmdlets in about 15-20 seconds from the same runbook server.
The criteria of my search is the homdirectory field and I flag the folder as
orphaned if there is no corresponding account in AD. The runbook then takes
ownership of the directory and moves it to another location.<o:p></o:p>
What I had to end up doing was to create a powershell script that does a for loop and then
passes the data to the next activity as delimited text. Surely not as
convenient as using the published data supplied by the "Get User"
I have notice that some activities takes around of one minute, to connector, execute and disconned, from the remote system. Also for example the Invoke Runbook activity can take one minute. If you then have one activity that results in 300 reponses, the next activity will run in 300 instanses. That could take some time. If you enable logging (properties of the runbook) you can investigate a bit deeper which activity that takes time and what parameters it runs with. This blog post explains it a bit better http://blogs.technet.com/b/orchestrator/archive/2012/05/11/sequential-vs-parallel-processing-of-runbook-activities.aspx
Anders Bengtsson | Microsoft PFE | blog at http://www.contoso.se
You could try using the community AD integration pack. It supports querying for objects using your own LDAP filters http://msdn.microsoft.com/en-us/library/windows/desktop/aa746475(v=vs.85).aspx