Re: Help-Dumb question

From: Glenn L (the.only_at_gmail.com)
Date: 10/18/04 

Date: Mon, 18 Oct 2004 00:57:51 -0700

It sounds like you are attempting an inplace upgrade of Exchange 5.5 to
Exchange 2003.

"Trying to upgrade Exchange 5.5 to Exchange 2003 Standard. One server, in
> one site in one organization in the same domain"

This is not a supported method to get to Exchange 2003. 

-- 
Glenn L
CCNA, MCSE 2000, MCSE 2003 + Security
"nobody" <nunya@bidness.com> wrote in message
news:XnHcd.7305$q%7.2564@newssvr11.news.prodigy.com...
> 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: 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: 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)
  • 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: SBS Transition Pack
    ... you're going to need to have a new name for your exchange server. ... > Before you run the Transition Pack there are a few steps you should> take to ... Disconnect the server from the internet completely. ... >> Going to get the SBS Standard SP1 transition pack to move from SBS to ...
    (microsoft.public.windows.server.sbs)
  • Re: Transition pack sbs premium 2003
    ... Just be aware that your exchange move won't be any different than it would be on a standard exchange install in Server 2k3. ... When you're done running the TP, you will have Windows Server 2003 Standard Edition, and Microsoft Exchange 2003 Standard Edition. ... Before you run the Transition Pack there are a few steps you should take to ...
    (microsoft.public.windows.server.sbs)