Help-Dumb question

From: nobody (nunya_at_bidness.com)
Date: 10/18/04 

Date: Mon, 18 Oct 2004 04:11:35 GMT

Trying to upgrade Exchange 5.5 to Exchange 2003 Standard. One server, in
one site in one organization in the same domain. The dsScopeScan reports:

Warning: Organization or Site Relative Distinguished Name (RDN) 'blah blah
blah, Inc.' in the Exchange 5.5 directory contains one or more of ,=+<>#\"
characters, please see Knowledge Base article Q281456 if you want to upgrade
any Exchange 5.5 servers to Exchange Server 2003 by upgrading to Exchange
2000 Server first.

Simple enough. According to several sources, just change the Display Name
in 5.5 to blah_blah_blah. I did. I restarted all the exchange services and
retried the dsScopeScan report and got the same result. I re-booted the 5.5
server with the same result.

I can't proceed with the upgrade until I can clear up this problem (can I?).
Anybody know how to change the Organization name on Exchange 5.5?

TIA,
Eddie

BTW: Q281456 doesn't show up in Microsoft's search results

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: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • 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: forestprep and domainprep on a Windows 2000/Exchange 2000 Dire
    ... 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. ... OK with the Windows Server 2003 forestprep/domainprep? ...
    (microsoft.public.windows.server.active_directory)
Loading