Well, I'll be the first to ask respectfully if you can post some of your code ~ I'm sure you're not the only one fighting with AD. My assumption, without having seen your code is that your DN is incorrect, or at least not what you really want it to be. For instance.

#LDIF
dn: CN=Submersible Toaster, CN=Users, DC=underwater, DC=appliances, DC
+=com
givenname: Submersible
sn: Toaster
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
 <insert relevant AD nonsense GUID sUID etc>
[download]

So your DN is what places the object into the LDAP tree..again I make the assumption that you are interfacing with LDAP. To put the user someplace else, you need to make that clear in the DN

#LDIF
dn: CN=Submersible Toaster, OU=Naughty Boys, DC=underwater, DC=applian
+ces, DC=com
givenname: Submersible
sn: Toaster
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
[download]

Would place Mr Toaster in the "Naughty Boys" OU rather than the "Users" container. I believe you can even reference another LDAP object , sort of symlinking one DN to another. Hence all users could exist in a master branch, but be linked to their relevant OU's , or the other way round. Don't take my word as gospel though - I've never made LDAP or AD actually do this, there is a chunk of documentation tapping me on the shoulder saying that it is possible.

I can't believe it's not psellchecked