RE: Exchange 2003 ESM manage Exchange 2000

  • From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Sun, 20 Mar 2005 19:43:37 -0500

For that kind of money, I'd leave it in place until a problem arises ;)

Stability comes from slow change (or is defined as depending on your
perspective.) That said, if isn't broke, don't fix it.  Conversely, don't
propagate it to others as well.  That's a risk that may not be worth it.  

I'd have to say that it's odd that it worked for you. It should have failed
and been difficult to install on a 2K3 server.  

Al
 

-----Original Message-----
From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx] 
Sent: Saturday, March 19, 2005 3:49 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Exchange 2003 ESM manage Exchange 2000

http://www.MSExchange.org/

So now for the $64,000 question: On the other clients server, should I leave
the Exchange 2000 ESM already installed on a Windows Server 2003 DC, or
should I remove it?

John Tolmachoff
Engineer/Consultant/Owner
eServices For You


> -----Original Message-----
> From: Mulnick, Al [mailto:Al.Mulnick@xxxxxxxxxx]
> Sent: Friday, March 18, 2005 2:11 PM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Exchange 2003 ESM manage Exchange 2000
> 
> http://www.MSExchange.org/
> 
> According to Evan, no.
> 
> "Some additional scenarios that are not supported. Non-support for 
> .NET
and
> Windows XP scenarios (slide 9). Installation of Exchange 2000 (the
released
> version) and Exchange 2000 Service Pack 3 is not possible on Microsoft 
> Windows .NET servers or Windows XP (either Professional or Home Edition).
> This is primarily because Exchange 2000 service packs do upgrades only.
You
> can't slipstream and install a service pack for Exchange 2000. That 
> means
in
> order for Exchange 2000 Service Pack 3 to be applied to a server, you 
> must first have installed Exchange 2000 (the released version). Since 
> the released version of Exchange 2000 cannot install on .NET or XP, 
> then
neither
> can the SP3 update. "
> 
>
http://support.microsoft.com/?scid=http://support.microsoft.com%2Fservicedes
> ks%2Fwebcasts%2Fen%2Fwc080602%2Fwct080602.asp
> 
> The intended implementation of E2K ESM on XP or .NET is to use RDP to
remote
> to the Exchange server (I know, I know, that breaks security best
practice)
> to administer the Exchange servers.  That's why Exchange 2003 exists 
> :)
> 
> Al
> 
> 
> -----Original Message-----
> From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx]
> Sent: Friday, March 18, 2005 4:01 PM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Exchange 2003 ESM manage Exchange 2000
> 
> http://www.MSExchange.org/
> 
> > In fairness, it's not supposed to :)
> >
> > If you ran into issues, that could be a bigger problem.
> 
> Ah, now that makes sense.
> 
> > Why not install on an admin workstation and stop messing with the 
> > dc's altogether?
> 
> That is the next item on the agenda. On that note, does Exchange 2000 
> ESM install on Windows XP Pro?
> 
> John Tolmachoff
> Engineer/Consultant/Owner
> eServices For You
> 
> 
> 
> ------------------------------------------------------
> 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:
> al.mulnick@xxxxxxxxxx To unsubscribe visit 
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
> 
> ------------------------------------------------------
> 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:
> johnlist@xxxxxxxxxxxxxxxxxxx
> To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx


------------------------------------------------------
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:
al.mulnick@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx


Other related posts: