I am starting a migration from a Windows 2000 server based AD to a Windows 2003 based AD. I am going by the instructions contained in KB325379, How to upgrade Windows 2000 Domain Controllers to Windows Server 2003. So far, so good, no suprises. I reached the part where it talks about mangled attributes. I copied and pasted the InetOrgPersonPrevent.ldf, no problems there. I had errors the first time I ran it. Looking at the file it tries to modify 3 attributes: ms-Exch-Assistant-Name, ms-Exch-LabeledURI and ms-Exch-House-Identifier. Should be simple enough. Fails though. Using LDP.exe I dug into my AD. I don't have any ofthose attributes in my structure anywhere. Closest I could find to one was ms-Exch-Telephone-Assistant. it's not the same, so it's not going to modify anything like that. Our Exchange server is Exchange 2000, running in native mode. We only have one. One forest, one domain, not complex. Does anyone have any notion as to why I am missing these attributes? Does it matter? If they are not there for the /forestprep to mangle is it something I should be worried about? Or is was something not done properly years ago and need to be done before I upgrage. Thanks! Jerry

Hi, The attributes should be there. Is this the article you are following? http://support.microsoft.com/kb/314649/en-us Leif

Actually it's http://support.microsoft.com/kb/325379but the verbage is the exactly the same. I don't have the mangled attributes because I haven't run /froestprep or /domainprep yet. I was running the script to modify the attributes prior. the script is pretty simple. Basically find and modify: dn: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,DC=Xchangetype: Modifyreplace:LDAPDisplayNameLDAPDisplayName: msExchAssistantName- But the results are: ldap_search_s(ld, "CN=Schema,CN=Configuration,DC=nnn,DC=nnn", 2, "(ldapdisplayname=*ms-Exch-Assistant-Name*)", attrList, 0, &msg)Result <0>: (null)Matched DNs: Getting 0 entries: In order to modify the CN=ms-Exch-Assistant-Name it has to be there to modify.