Exchange to OCS Communication

All Replies

• Sunday, July 01, 2007 5:06 PM

   

   
  

  0
  Hi,
  
  I have had the same issues. Please look at the following post and let me know if you have got it working.
  
  http://forums.microsoft.com/Ocs2007publicbeta/ShowPost.aspx?PostID=1722035&SiteID=57
  
  Cheers,
  
  Thomas
  
  • Reply
  • Quote

   
• Monday, July 02, 2007 1:39 PM

   

   
  

  0

  I have read your thread a number of times now hoping too find something new, but no i do no have it working just yet.  Can you identify what is different about your current installation (that works) and the previous one that you had your problems with?

   

  Thanks Thomas.

   

  Chris

  • Reply
  • Quote

   
• Tuesday, July 03, 2007 12:59 PM

   

   
  

  0
  Not many differences... fresh install of AD and Exchange did the trick for us....
  
  Is you Exchange UM machine trusted by OCS?
  Have you imported the OCS chain certificates on the Exchange Server?
  Have you done a complete reboot of Exchange after importing the certificates on the Exchange Server?
  Have you restarted the OCS frontend service after importing the certificates on Exchange?
  Are you using the OCS public beta from MSDN or an older version like i.e. (Pivate beta (III))
  Have you applied SP1 Beta on Exchange (because via this SP you can find the exchucutil.ps1 script)
  Have you run the script exchucutil.ps1 from the Exchange script directory (it uses other scripts in that directory when running)?
  Are you sure that Exchange is connecting with the OCS server instead of the Mediation server?
  Can you ping the OCS server form you Exchange server?
  Are you setting the IP address of the OCS server as UM gateway?
  Are you using the same dailplan name on the Exchange machine (small caps/big caps) as on the OCS machine (OCS will make a fully qualified name out of the dailplan on the OCS server; Exchange UM will use the short name?
  
  Please let me know if you have solved it.
  
  • Reply
  • Quote

   
• Tuesday, July 03, 2007 2:14 PM

   

   
  

  0

  1.  I am not sure what you mean by trusted.  Do you mean trusted site?

  2.  I have an internal CA and have imported the chain and it seems to work everywhere else fine except for communications betweeent these two servers.  When i view the debug when i try to call a mailbox, i get a very clear TLS error in the negotiation netween OCS and Exchange.

  3.  I have rebooted both servers after any major certificate or technical chages.

  4.  Server restared with reboot

  5.  I have deplolyed the most recent (fresh install) copy of OCS 2007

  6.  SP1 is installed, exchucutil has been run successfull (as has ocsumutil been run successfully)

  7.  Definitely connecting the correct server

  8.  Ping by FQDN and IP

  9.  OCS is defintely UM gateway

  10.  dialplans name match to the letter

   

  Do i need to have a matching certificate for the dial plan fqdn?  I did not think so.  Thanks for the assistance and i am stilll plugging away.  I will post my debug error i was referring to!!

  • Reply
  • Quote

   
• Tuesday, July 03, 2007 2:21 PM

   

   
  

  0

  here is the result of the debug where a TLS issue is evident:

   

  LogType: connection

  Severity: error

  Text: Outbound TLS negotiation failed

  Local-IP: 10.117.117.14:1487

  Peer-IP: 10.117.117.8:5061

  Peer-FQDN: exchangeum.winxnet.com

  Connection-ID: 0x2E401

  Transport: TLS

  Result-Code: 0x80090325

  $$end_record

  
  TL_ERROR(TF_CONNECTION) [1]0A64.0C58::07/03/2007-14:16:11.579.00000157 (SIPStack,SIPAdminLog::TraceConnectionRecord:8.idx(51))$$begin_record

  LogType: connection

  Severity: error

  Text: The connection was closed before TLS negotiation completed. Did the remote peer accept our certificate?

  Local-IP: 10.117.117.14:1487

  Peer-IP: 10.117.117.8:5061

  Peer-FQDN: exchangeum.winxnet.com

  Connection-ID: 0x2E401

  Transport: TLS

  $$end_record

  
  TL_WARN(TF_COMPONENT) [1]0A64.0C58::07/03/2007-14:16:11.579.00000159 (SIPStack,SendQueueProcessor:ropPendingSends:1185.idx(488))Cleaning up outstanding messages on a socket that is being closed
  TL_ERROR(TF_DIAG) [1]0A64.0C58::07/03/2007-14:16:11.579.0000015a (SIPStack,SIPAdminLog::TraceDiagRecord:8.idx(34))$$begin_record

  LogType: diagnostic

  Severity: error

  Text: Message was not sent because the connection was closed

  SIP-Start-Line: INVITE sip:WinXOCS@exchangeum.winxnet.com:5061;transport=tls;maddr=exchangeum.winxnet.com SIP/2.0

  SIP-Call-ID: 0d6efe9d846049dda207fed38d2b604d

  SIP-CSeq: 1 INVITE

  Peer: exchangeum.winxnet.com:5061

  $$end_record

   

  In addition, this is what i am seeing in my event log on the OCS server:

   

  Event Type: Error
  Event Source: OCS Protocol Stack
  Event Category: (1001)
  Event ID: 14428
  Date:  7/3/2007
  Time:  10:08:29 AM
  User:  N/A
  Computer: UM
  Description:
  TLS outgoing connection failures.

  Over the past 0 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090325 (The certificate chain was issued by an authority that is not trusted.) while trying to connect to the host "exchangeum.winxnet.com".
  Cause: Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.
  Resolution:
  For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the computer.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

   

  This is the error i see on my exchange server:

   

  Event Type: Warning
  Event Source: MSExchange Unified Messaging
  Event Category: UMService
  Event ID: 1113
  Date:  7/3/2007
  Time:  10:08:29 AM
  User:  N/A
  Computer: EXCHANGEUM
  Description:
  The Unified Messaging server failed to exchange the required certificates with an IP gateway to enable Transport Layer Security (TLS) for an incoming call. Please check that this is a configured TLS peer and the certificates being used are correct. More information: A TLS failure occured because the remote end disconnected while TLS negotiation was in progress. The Error Code = -2146233088 and the Message = Unknown error (0x80131500).  .

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  
  

   

   

  • Reply
  • Quote

   
• Wednesday, July 04, 2007 6:46 AM

   

   
  

  0

  Chris,

   

  One more thing you can check: is your dailplan in Exchange UM SIP secured (please check the properties of your dailplan in the Exchange UM admin console)? OCS requires it to be SIP secured.

   

  Could you tell me what certificates you have used on Exchange UM ?

   

  You'll need to issue the Exchange UM server a cert from a certificate authority that all servers trust. You can then disable the self-signed certificate that UM is using now.

   

  Please have a look at the following pages to know about importing certificates.

   

  http://technet.microsoft.com/en-us/library/bb232157.aspx

  http://technet.microsoft.com/en-us/library/bb232157.aspx

   

  Regards,

   

  Thomas

   

  • Reply
  • Quote

   
• Wednesday, July 04, 2007 10:28 PM

   

   
  

  0
  I was copying the following steps from the OCS VOIP Planning Guide.

   

  Step 1     Configure Exchange UM to Work with Communications Server

   

  Important

  If you are not using Exchange UM to provide call answering, Outlook Voice Access, or auto-attendant services for Enterprise Voice, skip this step and proceed to Step 2 Create Location Profiles.

  To configure Exchange UM servers, the following tools must be available on each server:

  §         The Exchange Server 2007 SP1 Management Shell (also known as the “Power Shell” or “Monad Shell”), which is a snap-in for the Windows PowerShell.

  §         The exchucutil tool, which is available in the Exchange Server 2007 SP1 Resource Kit. The exchucutil tool performs the following tasks:

  §         Creates a UM IP gateway for each Communications Server 2007 Enterprise Pool.

  §         Creates a hunt group for each gateway. (The pilot identifier of each hunt group specifies the UM dial plan used by the Enterprise Pool that is associated with the gateway.)

  §         Grants Communications Server permission to read Exchange UM objects in Active Directory.

  Requirements and Recommendations

  Before you begin:

  §         Make sure that you have deployed the following Exchange server roles either (in the same or a different forest as Communications Server 207): Hub Transport, Client Access, Mailbox, Unified Messaging. For information on deploying Exchange Server 2007 SP1 see the Exchange Server 2007 SP1 product documentation.

  §         Read Plan for Exchange Server 2007 SP1 Unified Messaging. Integrating Exchange UM and Communications Server requires careful planning and a clear understanding of the technologies involved, the features you want to enable, and important configuration details that you must be aware of to successfully complete your deployment.

  Also note the following:

  §         If Exchange UM is installed in multiple forests, the Exchange integration steps must be performed for each UM forest. In addition, each UM forest must be configured to trust the forest in which Communications server is deployed.

  §         The integration steps are performed on both Exchange UM server and Communications Server. You should perform the Exchange UM integration steps before you do the Communications Server integration steps.

  §         For an overview of the Exchange 2007 SP1 UM integration process, descriptions of supported topologies, and a list of planning tasks, see. You are strongly urged to read this topic before you begin the following procedures.

  Overview

  Configuring Exchange UM to work with Enterprise Voice consist of the following tasks:

  §         Creating one or more UM dial plans as needed, and then creating corresponding location profiles.

  §         Creating a SIP-URI for each user and associates users with a UM dial plan.

  §         Using the exchucutil tool to:

  §         Create UM IP gateways.

  §         Create UM hunt groups.

  §         Grant Communications Server permission to read UM Active Directory objects.

  §         Creating a UM auto-attendant object.

  §         Configuring UM servers to work with Communications Server 2007 A/V Authentication Service.

  To configure an Exchange 2007 SP1 UM Server

  You can perform this procedure using either the Exchange Management Console or the Exchange Management Shell command line.

  Important The commands shown in the following procedure are examples only. You will need to modify them to fit your particular configuration and requirements.

  
  

  1.      Create a UM dial plan for each of your Enterprise Voice location profiles.

  new-umdialplan -name <dial plan name> -UriType "SipName" -VoipSecurity "Secured" -NumberOfDigitsInExtension 5 -AccessTelephoneNumbers “<access number>”

  2.      Obtain the FQDN for each UM dial plan.

  (Get-UMDialPlan <dialplanname>).PhoneContext

  3.      Record the dialplanname of each UM dial plan. You will later use the FQDN of each dialplanname as the name of each UM dial plan’s corresponding Communications Server location profile.

  4.      Add the dial plan to the UM server.

  $ums=get-umserver;

  $dp=get-umdialplan –id <name of dial-plan created in step 1>;

  $ums.DialPlans +=$dp.Identity;

  $ums | set-umserver

   

  Note Before performing the following step, you should make sure that all Enterprise Voice users have been configured with an Exchange 2007 or SP1 mailbox. For information on configuring users with a mailbox, see the Exchange Server 2007 product documentation. When specifying a mailbox policy for each dial plan that you created in step 1, you can select either the default policy or on that you have created.

  
  

  The following step should be performed after you have enabled Communications Server users for Enterprise Voice and know their SIP-URIs.

  5.      Associate Exchange UM users with the UM dial plan and create a SIP-URI for each user.

  enable-ummailbox -id <user alias> -ummailboxpolicy <name of the mailbox policy for the dial plan created in step 1> -Extensions <extension> -SIPResourceIdentifier "<user alias>@<full domain name>" -PIN <user pin>

  6.       Navigate to %EXCHANGEINSTALLDIR%\Scripts and then

  If Exchange is deployed in a single forest, type:

  exchucutil.ps1

  exchucutil.ps1 –verify

  Else if Exchange is deployed in multiple forests, type:

  exchucutil.ps1 -Forest:“<forest FQDN>” for multiple forest deployments

  7.       Create a UM auto-attendant for each Communications Server location profile.

  New-umautoattendant –name <aa name> –umdialplan < name of dialplan created in step 1> –PilotIdentifierList <aa name>,<aa phone number>

  
  

   

  To configure UM servers to work with Communications Server 2007 A/V Authentication Service

  Important The A/V Authentication Service authenticates media traffic flowing through the A/V Access Edge Server, on which it is collocated. For scenarios in which UM traffic must traverse the enterprise firewall, UM servers must obtain appropriate authentication tokens, which means they must know the A/V Access Server assigned to each Communications Server pool. At present this configuration is done statically. In a future milestone, each UM server will receive this information dynamically from the appropriate Communications Server pool. To configure a UM Server with A/V authentication information, you must run the PowerScript Configure-MRAGruu.ps1, which is located in %ExchangeInstallDir%\Scripts. This script must be run on every UM server. If an A/V Access Edge Server is added or replaced, the script must be rerun on every UM server. After running the script, the UM service must be restarted on every UM server. Note: The script should be run only after the A/V Authentication Service has been fully installed and configured.

  
  

  1.       Start the Exchange UM service.

  2.       Log on an Exchange UM server, using the Admin role.

  3.       From the PowerShell, run Configure-MRASGruu.ps1. (The script is located in %ExchangeInstallDir%\Scripts.)

  4.       Restart the Exchange UM service.

  5.       Repeat this procedure on every Exchange UM server in the system.

  Step 2    Create Location Profiles

   

  Important

  If you are want to deploy Exchange UM for call answering and other services, go to Step 1 Configure Exchange UM to Work with Enterprise Voice. Otherwise, skip Step 1 and begin your Enterprise Voice deployment here.

  Location profiles specify how Communications Server is to interpret and route phone numbers that are dialed from various locations. You need to create a separate location profile for each geographic location where your organization maintains an office. If you maintain a single dial plan for your organization, you may nevertheless need a separate location profile for users who are enabled for Enterprise Voice.

  A location profile is essentially a named set of normalization rules. Normalization rules translate dialed numbers in various formats into a standard (E.164) format. You need to create one or more normalization rules for each location profile. You can copy an existing normalization rule in one location profile to a new location profile.

  Recommendations

  If you are configuring Exchange UM to work with Enterprise Voice, it is recommended that you perform that step before you create location profiles. For further information, see Choosing Your Deployment Path.

  Overview

  Creating a location profile consists of the following tasks:

  ·         Assigning a name to a new location profile.

  ·         Providing a description that will describe the location profile to users.

  ·         Creating one or more normalization rules.

  To create a location profile

  1.Open the Communications Server 2007 administrative snap-in.

  2.In the console pane, right-click the Forest node, point to Properties, and click Voice Properties.

  3.On the Location Profiles tab. click Add to create a new location profile. Repeat this step as needed to create all the location profiles that your organization requires.

  1.       In the Name box, type one of the following:

  ·         If you have configured Exchange UM for Enterprise Voice and have completed Step 1 above, type the FQDN of the corresponding Exchange UM dial plan.

  ·         A useful descriptive name. This name must be unique. Spaces are not allowed and the only special characters that are permitted are a dot (.), and hyphen (-).

  Important If you are planning to configure Exchange UM for Enterprise Voice but have not yet done so, stop now and perform Step 1 before you continue  creating location profiles.

  
  

  2.       In the Description box, type a description of the location profile that will be readily understood by another administrator or an end user.

  3.       Click Add.

  1.In the Add Location Profile dialog box, do the following:

  4.       In the Name box, type a name that describes the number pattern being normalized; for example, 5DigitExtension or 7 digit calling Toronto.

  1. 

  2. 

  3. 

  4.In the Add Phone Number Normalization rule dialog, do the following:

  Important Communications Server 2007 Beta 3 allowed you create a single set of normalization rules and then apply these rules to multiple location profiles. This practice is no longer permitted.   Communications Server 2007 Public Beta allows you to copy the phone pattern and translation pattern of an existing normalization rule to a new location profile but you must give it a new name.

  
  

  5.       If you want to create a new normalization rule, skip this step. If you want to copy the phone pattern and translation pattern of an existing normalization rule, click Copy.

  6.       In the Copy Phone Number Normalization Rule dialog box, select the normalization rule that you want to copy, and then click OK. If you want to view a normalization rule before copying it, select the rule, and then click View.

  7.       In the Description box, type a brief description (optional) of the normalization rule; for example “Translates 5-digit extensions” or “Translates 7-digit numbers to Toronto local number.

  8.       In the Phone pattern regular expression box, use .NET Framework regular expressions to describe a phone number pattern; for example, ^9(\d{7})$, which describes a phone number pattern consisting of the number 9 followed by any seven digits. For information on using .NET Framework regular expressions, see http://msdn2.microsoft.com/en-us/library/hs600312.aspx.

  9.       In the Translation pattern regular expression box, use .NET Framework regular expressions to describe the E.164 phone number corresponding to the number entered in the Phone pattern regular expression box.

  10.    Click Helper if you require assistance in formulating regular expressions.

  11.    In the Sample dialed number box, type a phone number to test whether the number translation works properly. If the number matches the phone pattern, the translation is shown in the Translated number box.

  12.    If the translation matches the phone pattern, click OK.

  13.Create as many normalization rules as your location profile requires.

  14.When you are done, click OK.

   

  Step 3    Configure Communications Server to Work with Exchange UM

  This step requires the ocsumutil tool. The tool is located at %installDir%\Office Communication Server 2007\Server\Support.

  The ocsumutil.exe tool must be run from a domain admin user account with the following characteristics:

  §         Membership in the RTCUniversalUserAdminsGroup.

  §         Domain rights to create contact objects in the specified OU/Container.

  §         Domain rights to read  Exchange UM settings.

  The ocsumutil tool performs the following tasks:.

  §         Creates contact objects for each auto-attendant and subscriber access number to be used by Enterprise Voice users.

  §         Verifies that the name of each Enterprise Voice location profile matches its corresponding UM dial plan FQDN.

  Important In order for the ocsumutil tool to work, it must be run on a Communications Server Front End from a domain admin user account with: §        Full rights to the OU/Container where the contacts will be created §        Membership to RTCUniversalUserAdmins group.

  
  

  To run ocsumutil

  1.       On a Front End Server, open a command prompt and then navigate to %installDir%\Office Communication Server 2007\Server\Support, where ocsumutil is located.

  2.       At the command prompt, type ocsumutil / domain:<SIP domain name> for each forest domain in which Exchange UM is deployed.

  For example:

  ocsumutil / domain:<SIP domain> /forest:fabrikam.com

  ocsumutil /domain: <SIP domain> /forest:contoso.com

  and so on

  3.       Optionally, to verify that the name of the Exchange UM SIP dial plan matches that of the Communications Server location profile, you can type

  ocsumutil /domain:<SIP domain> /forest:fabrikam.com /verify

  for each forest in which Exchange UM is deployed.

  Note The ocsumutil /verify switch does not actually correct name mismatches, but merely notifies you of the error condition.

  
  

   

  If ocsumutil fails, you can obtain useful diagnostic information by running the tool with the verbose option:

  Ocsumutil /domain:<SIP domain> [/forest:<forestname>] /verbose

  • Reply
  • Quote

   
• Thursday, July 05, 2007 1:26 PM

   

   
  

  0

  Thomas,

   

  Thanks for the reply.  In regards to certififcates, i have used a number of different certs in attempts to get it working.  Initially i began with a Godaddy cert that i had been successfully using for OWA and that did not produce good results.  I ensured that the certificate chain was installed on all necessary servers so the cert would be legitimate.  After that, i began generating my own certs using an internal MS CA, also instaling the chain on all servers and still no luck.  Finally, i am going to purchase an additional cert from comodo or entrust to fully rule out the cert issue.  I have done some extensive debugging with wireshark to look at all the packets and can provide that as needed.  I am using an internal CA right now with the correct subject name and that works for all other aspects of OCS (edge server, av server, etc.) but not for UM.

   

   

    Here is the OCS event log entry with debugging turned up when i try to make a call to a UM user:

   

  Event Type: Error
  Event Source: OCS Inbound Routing
  Event Category: (1037)
  Event ID: 45024
  Date:  7/5/2007
  Time:  9:14:35 AM
  User:  N/A
  Computer: UM
  Description:
  An attempt to use an Exchange UM Server for a missed call notification failed: exchangeum.test.com.
  Failure occurrences: 1, since 7/5/2007 9:14:05 AM.
  Failure Details: Failure occurred while connecting. The target principal name is incorrect outgoing TLS negotiation failed; HRESULT=-2146893022

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  

  Event Type: Error
  Event Source: OCS Exchange Unified Messaging Routing
  Event Category: (1040)
  Event ID: 44022
  Date:  7/5/2007
  Time:  9:14:34 AM
  User:  N/A
  Computer: UM
  Description:
  An attempt to route to an Exchange UM server failed.

  The attempt failed with response code 504: exchangeum.test.com.
  Failure occurrences: 1, since 7/5/2007 9:14:04 AM.
  Resolution:
  Check this server is correctly configured to point to the appropriate Exchange UM server. Also check whether the Exchange UM server is up and whether it in turn is also properly configured.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  

  Event Type: Error
  Event Source: OCS Protocol Stack
  Event Category: (1001)
  Event ID: 14428
  Date:  7/5/2007
  Time:  9:12:41 AM
  User:  N/A
  Computer: UM
  Description:
  TLS outgoing connection failures.

  Over the past 1 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090322 (The target principal name is incorrect.) while trying to connect to the host "exchangeum.test.com".
  Cause: Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.
  Resolution:
  For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the computer.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  

   

   

  • Reply
  • Quote

   
• Thursday, July 05, 2007 4:28 PM

   

   
  

  1

  FYI i created a new certificate without and SANs and that seemed to clear up all my TLS connection issues.  I will chalk this up to a long, painful lesson in certificates, TLS and the absolute mandate for certs to not only match, but also be the correct type ie, no wildcard certs, SANs, etc.

   

  Thanks for all your assistance!

  • Reply
  • Quote

   
• Friday, July 06, 2007 5:18 PM

   

   
  

  0

  Well done!!! Could you explain what you did one more time?

   

  FYI i created a new certificate without ............. and

   

  Hopefully it will help other people not to make the same mistake...

  • Reply
  • Quote

   
• Friday, July 06, 2007 5:34 PM

   

   
  

  0

  I ended up using an internal Microsoft Certificate Authority to distribute my internally used certificates.  So these are the steps i took:

   

  from the MONAD:

   

  1.  New-Exchangecertificate -Friendlyname yourname -generaterequesttrue -keysize 1024 -path c:\certrequest.req -privatekeyexportabletrue –subjectname "c=US, o=winxnet, CN=your fqdn (mail.microsoft.com)"

   

  2.  Browse to your MS certificate authority...usually https://servername/certsrv (You may need to remove digest/integrated authentication to browse the site form the network or you can upload the CSR from the CA server itself).

   

  3.  Request a certificate

  4.  advanced certificate request

  5.  Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.

  6.  Paste your CSR ino the cert request area and change your Certificate Template to "Web Server"

  7.  Download your Certificate

   

  from the MONAD:

   

  8.  import-exchangecertificate -path c:\newcert.cer

  9.  get-exchangecertificate | fl *  (note the thumbprint of the cert you just created)

  10.  enable-exchangecertificate -services "um,iis,smtp,pop" -thumbrint (the thumbprint of the new cert)

  11.  From each of your servers using TLS, be sure to install the certificate chain for your internal MS CA so each is trusted.

   

  That should be all you need and be sure to enable the appropriate service with the appropriate certificate so you don't impact other CAS roles for your Exchange server.  You can also likley accomplish this with a public CA just be sure not to use wildcards and use SANs with discretion.

   

  Hope that helps.

   

  Chris

   

  • Reply
  • Quote

   
• Thursday, July 26, 2007 4:28 PM

   

   
  

  0

  Hi,

   

  I am using Exchange 2007 SP1. I am not able to execute the command:

   

  enable-exchangecertificate (step 10)

   

  Error: Insufficient rights to grant network service access to the certificate with thumbprint ... .

   

  Please suggest how to get through this.

   

  Thanks.

   

  • Reply
  • Quote

   
• Wednesday, October 24, 2007 10:19 PM

   

   
  

  0

  hi, i have the some problem, my OCS don´t comunicate wtih my exchange server,

  I haven´t the sp1 for Exchange 2007, could you tell me how can get it?

   

  Thanks

   i will be waiting for your help.

   

  • Reply
  • Quote

   
• Thursday, December 17, 2009 12:12 AM

   

   
  

  0
  Can you assist a little bit more with how to create the certificate and from what server?
  • Reply
  • Quote