Re: Requirements for front end server 2003

  • From: "Steve Moffat" <steve@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 4 Jan 2005 19:28:26 -0400

Why not??

Steve 

-----Original Message-----
From: alexis [mailto:maitchoukow@xxxxxxxxxxx] 
Sent: Tuesday, January 04, 2005 6:33 PM
To: [ExchangeList]
Subject: [exchangelist] Re: Requirements for front end server 2003

http://www.MSExchange.org/

For everything I had read you need to install windows 2000 server and
then exchange to configure as Front end server, windows 2003 can't be a
front end server

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

This E-Mail is confidential. It is not intended to be read, copied, disclosed 
or used by any person other than the recipient named above.

Unauthorised use, disclosure, or copying is strictly prohibited and may be 
unlawful. Optimum IT Solutions Ltd disclaims any liability for any action taken 
in connection of this E-Mail. The comments or statements expressed in this 
E-Mail are not necessarily those of Optimum IT Solutions Ltd or its 
subsidiaries or affiliates.

administrator@xxxxxxxxxx




Other related posts: