Greetings RaJ, No..Interesting.. do you have happen to have multiple mailbox's associated with the same account on Exchange 5.5? Is this issue occurring on those mailboxes'? Another possibility may be a corrupt message store ( Just another wild guess ). I've noticed that on several Exchange Migrations, however generally the management does not want you running ESUTIL and ISNTEG prior to migrating as they do not want any down time. Hope you don't mind if I vent as I share your frustration and pain, it's a Damn if you do and Damn if you don't situation, in most case's companies want to hire an outside consultant knowing perfectly well they were experiencing exchange problems prior to upgrading and hoping that all goes well, and if it doesn't , well blame the consultant, he'll be gone after it's over any ways, who cares if it damages their reputation and prevents them from finding another position, they'll just put them out to pasture supporting desktops and small business server. (Usually happens to us admins who reach the age of 40 ) With the few Exchange accounts that your having issue's with, export the mailbox using exmerge and then use it to re-import the mail back into the new Exchange server. May God deliver us from our enemies and grant us justice for what they have done, Hope this helps and may peace be with you, Jose ________________________________ From: raj nair [mailto:rajnair7@xxxxxxxxx] Sent: Tuesday, August 22, 2006 10:53 AM To: Medeiros, Jose Subject: Re: NTDSNoMatch utility No. We dont have BlackBerry and Call manager. Thanks. raj On 8/22/06, Medeiros, Jose <Jose.Medeiros@xxxxxxxxx> wrote: Raj, Would you happen to also be running a Blackberry and or a Cisco Call Manager / AVVID Server along with your Exchange Infrastructure ? Sincerely, Jose Medeiros Storage Area Network Systems Engineer MCP+I, MCSE, NT4 MCT 408-765-0437 Direct, 408-449-6621 Cell "Anyone who has never made a mistake has never tried anything new." Albert Einstein ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto: exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of raj nair Sent: Tuesday, August 22, 2006 8:31 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: NTDSNoMatch utility Thanks for your reply Jason. One more doubt . i have ran the ntdsnomatch from exchange 200 version and from the list there is a mailbox iam listing below which does not come under the exchange 2003 version. I dont know about the exchange 2003 sp2 version and have never run it. That mailbox also has the Sam acct name and alias different. whay is that not listed in the 2003 version? Obj-Class Extension-Attribute-10 Display Name Primary Windows NT Account Alias Name Directory Name Home-Server Mailbox NTDSNoMatch Sandy May is-dp\TC7 Sandy.May FA12 Revenue04 Similarly there are some more mailboxes that i have seen which have SAM acct names and aliases different and which are not listed both in exch 2000 version and 2003 version . PS: Is it because the accounts that is owning these mailboxes does not own any other ? Thanks Raj On 8/21/06, Jason Sherry < Jason.Sherry@xxxxxxxxxxxxxxxxxx <mailto:Jason.Sherry@xxxxxxxxxxxxxxxxxx> > wrote: ~DEL means that custom attribute 10 will be cleared. If the samAccountName (Windows NT Account) and alias match it is assumed that the mailbox is the primary mailbox for the account and attribute 10 will be cleared. Entries without a value in attribute 10 will be assume to be the primary mailbox for the associated Windows NT Account. "NTDSNoMatch" should be put in attrib 10 for all other mailboxes that have the same Windows NT Account, only one mailbox for each NT Account should have a blank attrib 10, the rest should have NTDSNoMatch. For the non-primary or resource mailboxes, the ones with NTDSNoMatch, a new account will be created for each of them, based on the directory name I believe. This new account will be made the primary account for the mailbox it was created for. In addition, the account that used to have be the primary NT Account will be granted user access to the other mailboxes. Note: You should be using the ADC Wizard in Exchange 2003 SP2 instead of ntdsatrb utility, if that is what you are using. From your example data provided below your Exchange directory should be fixed so alias names are unique within your org. Getting the primary NT account and resource mailbox issues addressed is the hardest part in migrating from Exchange 5.5 to Exchange 2003. I would suggest using the ADC Wizard to set the primary mailbox for each account that is currently associated with multiple mailboxes. Then export the information from the wizard and review it to make sure it is correct. Then import the output file, using Exchange 5.5 Administrator, and rerun the ADC Wizard, after waiting for directory replication to carry out. Jason Sherry - Pro Exchange http://www.theproexchange.com <http://www.theproexchange.com/> From: exchangelist-bounce@xxxxxxxxxxxxx [mailto: exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of raj nair Sent: Monday, August 21, 2006 2:09 PM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] NTDSNoMatch utility Hi , I have used the exchange 2003 version NTDSNomatch Utility and have printed the output .Now it has printed all accounts with more than a mailbox with the NTDSNoMatch stamping. Here is the output .where the SAM acct name and the alias is different it has stamped NTDSNoMatch.But it has stamped a ~DEL to the account where the alias and SAM acct name are same . For eg : For 1 entry from the output file : Obj-Class Extension-Attribute-10 Display Name Primary Windows NT Account Alias Name Directory Name Home-Server Mailbox ~DEL Phyllis Grigsby IS-DP\COMM3 COMM3 COMM3 REVENUE04 Mailbox ~DEL Janie Doolos IS-DP\COMM3 comm3 SDFairley REVENUE20 What it means by ~DEL stamping ? Does it mean if if i did not use the NTDSNoMatch the user Phyllis Grigsby is not going to access his mailbox ( even though his alias and SAM acct name is same in the first row) once i move th emailboxes to win2003 ? Thanks Raj