%3CLINGO-SUB%20id%3D%22lingo-sub-310590%22%20slang%3D%22en-US%22%3EText%20files%20generated%20by%20MSEXTMZ%20v2%20are%20missing%20some%20characters.%20Is%20this%20normal%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-310590%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Feb%2028%2C%202007%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Q%3A%20%3C%2FSTRONG%3E%20After%20running%20the%20MSEXTMZCFG%20(V2)%20my%20txt%20files%20with%20the%20mailboxes%20that%20will%20be%20update%20are%20missing%20a%20character%20or%202%20randomly%20in%20the%20mailbox%20name.%26nbsp%3B%20That%20is%2C%20JSMITH%20is%20listed%20as%20JSMIT.%26nbsp%3B%20Is%20this%20supposed%20to%20happen%20or%20do%20I%20have%20some%20incorrect%20files%3F%20%3CBR%20%2F%3E%20%3CB%3E%20A%3A%20%3C%2FB%3E%20You%20may%20want%20to%20verify%20whether%20the%20user's%20legacyExchangeDN%20was%20created%20using%20UNICODE%20characters%20or%20not.%26nbsp%3B%20Try%20validating%20it%20via%20ADSIEdit%20or%20another%20similar%20utility.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-310590%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Feb%2028%2C%202007%20Q%3A%20After%20running%20the%20MSEXTMZCFG%20(V2)%20my%20txt%20files%20with%20the%20mailboxes%20that%20will%20be%20update%20are%20missing%20a%20character%20or%202%20randomly%20in%20the%20mailbox%20name.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-310590%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on TECHNET on Feb 28, 2007
Q: After running the MSEXTMZCFG (V2) my txt files with the mailboxes that will be update are missing a character or 2 randomly in the mailbox name.  That is, JSMITH is listed as JSMIT.  Is this supposed to happen or do I have some incorrect files?
A: You may want to verify whether the user's legacyExchangeDN was created using UNICODE characters or not.  Try validating it via ADSIEdit or another similar utility.