Just to verify what John said... You do have to have another license. I went to a seminar about Virtual Server 2005 (which is nifty, by the way -- everyone should at least check it out, especially if you run old OS's like QNX 4.25) and he did mention that for each machine you have to have a separate license for. It's just like another computer, hense "Virtual PC" or "Virtual Server". If any case, good luck on the transition. Kenny -----Original Message----- From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx] Sent: Wednesday, March 09, 2005 11:26 AM To: [ExchangeList] Subject: [exchangelist] RE: Windows 2003 Active Directory http://www.MSExchange.org/ > You could have always gone the VMWare router if your server if > powerful enough. In my professional opinion, that would still require another OS license, which is what he does not have. I am sure people can depate this on both sides of the argument. Only way to find out for sure is to see which side's lawyers can come up with the most convincing BS. 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: kennymann@xxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx