Re: forestprep and domainprep on a Windows 2000/Exchange 2000 Dire

Hello PM,

Problems will start when you try to upgrade, not before. You can not upgrade the schema until you change the names with the .ldf script.
During the upgrade phase it will use the RFC compliant name versions, that are not existing, because Exchange 2000 use names that where not RFC compliant as stated in the document.
Mangled attributes does not cause problems with the functioning of Active Directory or the operating system, because the names are not used in this context. However, you might have an application that needs to access these values, which will be inaccessible.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

If I do somehow get the mangled attributes, what problems do they
cause? Will the domain be down? Will exchange be down? mangled
attributes sound scary, but I don't understand what they actually do
to the network.

Thanks
PM
"Meinolf Weber" wrote:

Hello PM,

The main part is, if you see this:

lDAPDisplayName: DUP-labeledURI-9591bbd3-d2a6-4669-afda-48af7c35507d;
lDAPDisplayName: DUP-secretary-c5a1240d-70c0-455c-9906-a4070602f85f
lDAPDisplayName:
DUP-houseIdentifier-354b0ca8-9b6c-4722-aae7-e66906cc9eef

instead of this:

CN=ms-Exch-Assistant-Name or msExchAssistantName

CN=ms-Exch-LabeledURI or msExchLabeledURI

CN=ms-Exch-House-Identifier or msExchHouseIdentifier

when checking one of the 3 attributes with ADSIedit like described in
scenario2 part 4, then you have this mangled attributes. In all my
upgrades i never saw them. The script is to correct them otherwise
adprep will not run.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Meinolf:

I appreciate your response. It makes me less nervous! I have one
follow up question.

I read the 'mangled attributes' article, but I don't fully
understand what it is telling me to do in my situation.

I have a current Windows 2000/Exchange 2000 environment. Am I still
OK with the Windows Server 2003 forestprep/domainprep? There is
some LDF file that some articles say I must run before the prep.

"Meinolf Weber" wrote:

Hello PM,

Run server 2003 to prepare the schema for 2003. Then run during the
exchange install the exchange update.

Adprep command will run or stop with an error. Will not break
anything, did it myself more often now and never had problems.

Also check out this one before, about mangled attributes:
http://support.microsoft.com/?id=314649

How to Verify That ForestPrep and DomainPrep Completed Successfully
in Exchange
2000 Server or Exchange Server 2003
http://support.microsoft.com/kb/274737/
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hello: I've been researching this issue.

I have a Windows 2000/Exchange 2000 Active Directory currently. I
am ADDING new 2003 R2 (Windows and Exchange) servers to the
network. I am not doing any upgrades to existing servers.

The part that I've been researching the most involves the
forestpreps and domainpreps that I need to run. I've read many
articles, but still cannot come to a definitely conclusion. My
questions are:

1. Which forestprep/domainprep do I run first? The Windows
Server
2003 R2
ones, or the Exchange 2003 ones?
2. Can forestprep/domainprep damage the active directory at all?
I've read
the articles on MANGLED ATTRIBUTES but cannot determine how to
avoid
them.
Can someone please reply? I've already read the articles that
others
have forwarded to me. I'd just like some feedback if possible.


.

Relevant Pages

  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Validation for 2000 to 2003 upgrade
    ... Concerning the Exchange attribute in schema that will get duplicate during ... I don't want to have to run the adprep from the exchange server cdrom before ... Inplace upgrade will work without problem from 2000 to 2003, ...
    (microsoft.public.windows.server.active_directory)
  • RE: NT4 to 2003 server upgrade including Exchange 5.5 to Exchange 2003
    ... my understanding of your current issue is totally ... related to Exchange 5.5 upgrade to Exchange 2000. ... Domain A includes the Exchange 5.5 server which B and C ...
    (microsoft.public.windows.server.migration)
  • Re: WinNT Domain to Win2K Active Directory? Help!!!
    ... ---domains can remain NT until those Admins feel like doing their upgrade? ... Microsoft Online Partner Support ... Also, we already have a Server 2000 running our DNS and WINS, do I need ... Perform an inplace upgrade to Exchange 2000. ...
    (microsoft.public.windows.server.migration)
  • Re: forestprep and domainprep on a Windows 2000/Exchange 2000 Dire
    ... I have a current Windows 2000/Exchange 2000 environment. ... OK with the Windows Server 2003 forestprep/domainprep? ... exchange install the exchange update. ...
    (microsoft.public.windows.server.active_directory)
Loading