RE: In place upgrade to Windows 2003 w/Exchange 2003

  • From: "Medeiros, Jose" <jmedeiros@xxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 2 Jun 2005 11:53:37 -0700

Hi Bill, 

How about using this procedure instead, "How to move Exchange 2003 to new 
hardware and keep the same server name"? 
http://support.microsoft.com/default.aspx?scid=kb;en-us;822945

The concept is the same if you plan on using the same hardware and just 
changing the OS.

Hope this helps!

Jose 

-----Original Message-----
From: Bill Daniels [mailto:BDaniels@xxxxxxxxxxxxxxxxxxx]
Sent: Thursday, June 02, 2005 8:40 AM
To: [ExchangeList]
Subject: [exchangelist] In place upgrade to Windows 2003 w/Exchange 2003


http://www.MSExchange.org/

I am wanting to upgrade our Exchange 2003 server from Windows 2000
standard to Windows 2003 standard.  I've had zero luck finding
documentation on doing this and I'm not willing to jump in without
knowing if there are potential problems.  Has anyone here done this or
know where I can find relevant documentation? 

Thanks
Bill

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as: 
jmedeiros@xxxxxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx



Other related posts: