Quest Gurus, I have returned with another question. It's not as big of a problem as some of the others but I am trying to figure out what happened.
After I rebuilt the database for our test environment, I went in and setup all of the configuration parameters as they should be. I made sure to include the Custom ADS paramaters that we have in our production environment. Then, I ran the Target System Wizard for Active Directory on our domain. Once the wizard completed, I opted to NOT do the full synch just yet. I modifed the AD Synchronization by adding a container filter to the synch that limited the container to only be in a particular OU - let's call it Corp Users. I made sure to select the "Object with this cannonical name" option and typed the path mydomain.net/Corp Users (names changed). I then ran the full synch.
As soon as the synch was completed, I checked the Employees in Q1 and found that several accounts that exist OUTSIDE of Corp Users got imported. This should not be since the filter was set to limit those users. I can't figure out why the synch did this. In fact, it almost seems like the filter didn't work at all. I found accounts from other OUs that were completely outside of Corp Users. What gives? I can't figure out what went wrong but as a result, my "Person" table is all messed up now and includes accounts that we will never need to do anything with.
The weird thing is that I am almost 100% certain that I set the configuration EXACTLY the same as our Production environment and that environment DOES NOT have these extra users. I can't figure out what I missed.
I have never felt like I want to punch a software in the face until now. Quest is driving me insane with its ridiculous complexity.