So, we have our people picker working to add users to a site collection or User Info List in WSS 3. We implemented the STSADM command to search a specific OU and this works fine. Our problem is that a user has to be in the User Info list or they can not be added to a task because we will receive the error "The user does not exist or is not unique.". If we add the user to the User Info list first by using the same people picker it works fine and then we can give that user a task. We have sort of resolved this by running a script that adds about 13K to 40K users to each site collections User Info list which is not a great resolution by any means. Our problem is that we do not control the OU in question and every user exists in that OU with 2 or more accounts though they will only logon with one of them. I am trying to see if I can create a new people picker field or what can be modified so that we do not get this error and we can add users to tasks without having to first add them to the User Info list. Any thoughts are appreciated!
EDIT: I wanted to make it a little more clear on what is happening. The people picker returns the user that you search for. Unfortuantely it returns all of the accounts because they all exist in the same OU and we can not modify this at all. You can use the people picker to add users to the site, but not to a task unless you add them to the site first. So can we use an AD group to store the users we want to search for or will it still have an issue? Just want the best approach!
EDIT 2: Aftore more research, I am wodering if we have 1 site collection that has all the users in it, can we use this site collection for restricting the people picker for all other site collections and will it still try to validate the user in AD?