Hi -
I'm going to take a different tact on your post. First, from the schema master where you ran the ADSchemaSetup.exe, you will see ldif logs posted on your desktop. The number of files you will have depend on whether you updated your AD for Bridge or VPIM support in addition to Exchange. You can review the main ldif file Avdirmonex2k. Open the file and scroll to the end of the file. Locate the last instance of cisco-Ecsbu_UM-Schema-Version. Click UP for the search direction. Click Find Next. A few lines down you should see a line containing the word "Description" followed by 4.0(5) Unity or it may even say 4.0(1), I don't recall. There were no changes in 4.0(5) to the schema for Avdirmonex2k since 4.0(1). You can also use ADSIEdit to inspect your schema, CN=Schema,CN=Configuration,DC=root Domain,DC=com or net or org and check for CN=cisco-Ecsbu-. Some of the fields are cisco-Ecsbu-Object-Type and cisco-Ecsbu-Prefixes. Also if you don't see any errors in the ldif.err file(s) you should be OK. Here is a link to the 4.0(5) install and schema extend section - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/products_installation_guide_chapter09186a00804419f5.html#wp1805856
Secondly, the behavior you are describing when not seeing users in import CAN ALSO MEAN the users already exist in Unity. Or that Unity thinks subscriber properties are already associated with these user accounts. Could that be possible?
Ginger
