RE: Chat Requirment

  • From: "Martin Blackstone" <MBlackstone@xxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 4 Jul 2005 07:57:39 -0700

As Roger says, LCS is the replacement.
As for feeling cheated, I can understand your feelings. Since I never
used it have no exposure to it, I cant say whether what MS did was a
good or bad thing, but I can understand you feeling that way.

As for your MSDN question, I suspect you would be in a licensing
violation if you used MSDN to deploy LCS.


From: Praveen Ramaswamy [mailto:ramaswamy_praveen@xxxxxxxxx] 
Sent: Monday, July 04, 2005 7:46 AM
To: [ExchangeList]
Subject: [exchangelist] Chat Requirment 
I wanted to implement chat server which comes with exchange. Now that MS
has st oped giving it with Exchange 2003, i need to find an alternative.
Why did MS do this ?? If my present company had exchange 2000 and if i
had pay extra for chat service when i move to 2003 then i feel cheated..
Do you guys agree with me ??
I just want employees to provide workgroup instant messaging with
address directory. Netmeeting with ILS server probably would have been
best solution, but i think it is absolute now. Communication server 2005
is a costly solution just for this requirement. 
Is there any thing else which is less cost or comes bundled with any MS
products in MSDN CD ..!!
Praveen R


Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
------------------------------------------------------ List Archives: Exchange
Newsletters: Exchange
------------------------------------------------------ Other Internet
Software Marketing Sites: World of Windows Networking: Leading Network Software Directory: No.1 ISA Server Resource Site: Windows Security Resource Site: Network Security Library: Windows 2000/NT Fax Solutions:
------------------------------------------------------ You are currently
subscribed to this Discussion List as:
mblackstone@xxxxxxxxxxxxxxxxxx To unsubscribe visit Report abuse to

Other related posts: