Terminal Server Compatibility
"David Meredith" <dmeredith-+TV8j9Eoovaw5LPnMra/[email protected]> Fri, 12 Jan 2007 15:37:28 -0800
| Newsgroups | gmane.network.jabber.exodus.user |
|---|---|
| Message-ID | <0DFCE0A4B93F434A941642B9CA85D4C30109A491@W2KSERVER1.baywest-mgt.com> |
This is a multi-part message in MIME format.
--===============0520141357==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C736A2.9C06274E"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C736A2.9C06274E
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I'm putting together a cost benefit analysis of deploying an IM
server/client configuration on our network. Jabber looks really good as
it is literally infinitely more cost-effective! We use Windows Terminal
Server for all our users to access everything from e-mail to office
applications from dumb terminals. My boss wants to know if Exodus (or
any other Jabber clients) are compatible with Terminal Server, as they
are very concerned about keeping things "M$-compatible"
------_=_NextPart_001_01C736A2.9C06274E
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I’m putting together a cost benefit analysis of
deploying an IM server/client configuration on our network. Jabber =
looks
really good as it is literally infinitely more cost-effective! We =
use Windows
Terminal Server for all our users to access everything from e-mail to =
office
applications from dumb terminals. My boss wants to know if Exodus =
(or any
other Jabber clients) are compatible with Terminal Server, as they are =
very concerned
about keeping things =
“M$-compatible”<o:p></o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C736A2.9C06274E--
--===============0520141357==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Exodus mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/exodus
--===============0520141357==--