<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It is an involved process to get the certs loaded, especially if
you have a cluster. You very well may be able to get it to work, but in this
customer’s case it would not. So far, only single exchange servers I have been
able to make work. Perhaps Cisco has a fix for it now or knows how to do it.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ratko Dodevski
[mailto:rade239@gmail.com] <br>
<b>Sent:</b> Friday, March 06, 2009 3:38 PM<br>
<b>To:</b> Matt Slaga (US)<br>
<b>Cc:</b> Samuel Womack; cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Microsoft Exchange gateway for Outlook
Calendaring<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Thanks for helping me
understand what this means. Do you want to say that this feature doesn't work
if there is exchange cluster? Here is what i found, maybe can help you.<br>
<br>
<span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>-Create
a Enterprise Root Microsoft Certificate Services on a W2K3 <br>
domain member server. <br>
-Upload this root CA certificate to CUPS as a 'presence-trust' certificate. <br>
-Add this root CA to your domain security group policy. push group <br>
policy to the clients. <br>
-Create a CSR on my <b><span style='background:#FFFF80'>Exchange</span></b> box
via IIS. Had this CSR signed by the <br>
enterprise root CA. <br>
-Upload the signed cert back to IIS on <b><span style='background:#FFFF80'>exchange</span></b>.
restart iis. <br>
-Configure CUPS presence engine for Outlook. The common name is the <br>
name of the presence-trust certificate as viewed in the CUPS OS admin <br>
certificate page. <br>
-Reboot presence. <br>
<br>
Regards<br>
<br>
Ratko<br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>