I am doing a K2 process for a client which has about 5000 users in Active Directory, most of which reside in a singe OU called Users. If I try to locate a user for a destination by drilling down into the OU structure, when I open the Users OU the retrieval of that data pegs my CPU at 100% and K2 Studio stops responding for 5+ minutes!
Is there an alternative way of specifying users for a destination when they belong to such a group? This is quite cumbersome to work with.
+2
Hi
K2 Studio has been enhanced to deal with large AD groups more effectively.
Tests with user counts similar to your figures have been timed between 7 and 20 seconds, depending on AD and network load at the time of the AD call.
This enhancement will be available in K2.net 2003 Service Pack 2, due for release this quater.
Emile
K2 Studio has been enhanced to deal with large AD groups more effectively.
Tests with user counts similar to your figures have been timed between 7 and 20 seconds, depending on AD and network load at the time of the AD call.
This enhancement will be available in K2.net 2003 Service Pack 2, due for release this quater.
Emile
+1
Alternatively,
You could use the search functionality, by expanding the domain, right-clicking on the domain name, and select search.
This should take a lot less time than waiting for all the users to be retrieved.
You could use the search functionality, by expanding the domain, right-clicking on the domain name, and select search.
This should take a lot less time than waiting for all the users to be retrieved.
Reply
View our Community Site Map
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.