RSS Subscription 168 Posts and 2,769 Comments

Office Communications Server 2007 Enterprise Deployment – Part 3

Welcome to Part 3 of this article series. In Part 1, we started off by discussing the goal of this lab. That goal is how to deploy a single Enterprise Edition OCS Server which is connected to an x64 SQL Server 2005 SP2 Back-End Server. We first discussed what the lab setup is going to be using VMware Workstation, and then proceeded to the configuration of our Enterprise Certificate Authority.  In Part 2, we went over the preparation and installation of a Front End OCS 2007 Server Pool which were the first few steps in deploying OCS in an Enterprise Deployment.

In this Part, I will go over the remaining steps required to deploying our Front End Server in an Enterprise Pool Deployment. This includes going through the initial configuration of the pool, certificates, and adding our Front End Server to our newly created pool that uses a SIP namespace ( that is separate than our AD Namespace ( We will begin the steps needed to validate our configuration to make sure the Front End OCS Server is healthy.

Part 1

Part 2

Part 3

Part 4

Part 5

Front End OCS 2007 Server Installation

When installing OCS in a consolidated Enterprise Edition deployment, you would perform the following steps:

  1. Prepare Active Directory (Completed in Part 2)
  2. Create an Enterprise Pool (Completed in Part 2)
  3. Configure a Load Balancer (Completed in Part 2)
  4. Configure Pool / DNS
  5. Add Server to Pool
  6. Configure Certificate
  7. Configure Web Components Server Certificate
  8. Verify Replication
  9. Start Services
  10. Validate Server and Pool Functionality

Configure Pool / DNS (Step 4)

We are now on Step 4 which is to Configure our Pool and Configure DNS. Click Run to Continue.

As stated previously, we will be using a SIP domain that is different from our Active Directory domain.  This SIP domain is called  The reason I am doing this is to show you how you can set up your SIP namespace to be different from your Active Directory domain which is not uncommon.  For example, in many organizations, their domain may be domain.local while their SMTP namespace will be

The method I am using would be the same thing.  You would have an Active Directory domain, and then use a different namespace for SMTP/SIP.   In the case of our lab, I am only using Exchange to show distribution group expansion within OCS.  But in a production environment, you can use the same namespace for both Exchange and OCS.  This is the actually recommended.

Note: A person by the name of Simo notified me that Exchange is not required for group expansion.  As long as your distribution group has a value in the “mail” attribute field, group expansion will work.

So just to ensure you understand, let me show some examples:

Example 1:

  • Active Directory Domain Namespace-
  • OCS Namespace –
  • Exchange Namespace –

Example 2:

  • Active Directory Domain Namespace-, shudnow.local,, staff.shudnow.local, etc…
  • OCS Namespace – (can be different from Exchange Namespace)
  • Exchange Namespace – (can be different from OCS Namespace)

On the Welcome Screen, Click Next to Continue.

You will then be prompted to install the Administrative Tools if they have not been installed already.  You don’t have much of a choice here and you must install these tools. Click Next to Continue which will begin the installation process of the Administrative Tools.

We now must choose what Pool we want to configure.  Considering we only have one pool, leave the selection (don’t have much of a choice) at Click Next to Continue.

I would make sure you fully understand the differences between choosing SNAT Vs DNAT.  In a previous Part, I posted two links which provide you with the information you need to understand load balancing for OCS.  One of these guides was the planning document for hardware load balancing which you can view here.  It is recommended not to change this setting after OCS has been installed.  So please make sure you understand the differences and make your choice appropriately.

Choose SNAT as the method of load balancing. Click Next to Continue.

We are now presented with the SIP domains in our environment.

Since we will be using, we will need to add that in there.  Do not remove as a SIP domain.  If you recall, when we did our Forest Prep, we chose our Active Directory domain for SIP Routing.  Because of this, we will have two SIP domains; one for routing and one for user access.  You will then want to type in and click Add. Click Next to Continue.

When you set Communicator to connect to your OCS pool, you can configure it to automatically connect or to manually connect.  We will configure OCS to allow for automatic client logons.  If we had multiple pools and we wanted users who connected to this Pool to be redirected to another Pool, we would ensure that “Use this server or pool to authenticate and redirect automatic client logon requests” is checked. Click Next to Continue.

Since we are enabling our Pool to allow automatic logons, we must specify which SIP domains will be allowed for automatic logons.  Choose and then Next to Continue.

Note: We will not be doing the actual DNS configuration to support our new SIP namespace until we get to the part where will be connecting via Communicator.  This way, you can see step by step what fails and how to rectify the failure to ensure a successful automatic logon.

We do not have our Edge Topology up and running.  The recommended method of deploying a new OCS organization is to bring up your internal servers and then your Edge Servers.  If you are migrating from LCS, you must deploy your new Edge Topology first since an LCS Access Proxy cannot proxy to an OCS organization whereas an OCS Access Edge can proxy to both LCS and OCS. Select, “Do not configure for external user access now” and then Next to Continue.

We are finally ready to Configure our Enterprise Pool, you can review your Current Settings.  When satisfied, Click Next to Continue.

The configuration will now commense which will be pretty quick.  In fact, it’s too quick for me to grab a screenshot.  When the Pool Configuration is finished, Click Finish.  You will be given the option to view the log which I advise you to do to ensure everything went OK.

Add Server to Pool (Step 5)

We are now on Step 4 which is to Configure our Pool and Configure DNS. As a prerequisite, you’ll need to install IIS by following the instructions here. You may also need your SP2 binaries and CD1 of your Server 2003 Installation CD. Once IIS has been installed, you will have to restart Setup. Once back at the Deploy Pool in a Consolidated Topology, Click Run to Continue.

On the Welcome Screen and Licensing Information (after reading all the licensing information and choosing that you agree if you agree with the licensing terms), Click Next to Continue.

Specify where you want OCS to be installed.  We will use the default location. Click Next to Continue.

We are ready to Add our Server to our Enterprise Pool. You can review your Current Settings.  When satisfied, Click Next to Continue.

The configuration will now commence which will install all of the OCS roles onto this Front End Server due to it being Consolidated Front End.

Once the roles have been installed on your Front End Server, you will have to specify what Pool we want to join this server to.  Considering we only have one pool, leave the selection (don’t have much of a choice) at Click Next to Continue.

You will now be prompted to specify passwords for your Service Accounts.  I recommend to use long secure passwords.  You can view this and this site which assist in choosing strong passwords.  You will have to do this for several Service Accounts:

  • RTCService
  • RTCComponentService
  • RTCGuestAccessUser

Once you have set a password for all three accounts, Click Next to Continue.

We are ready to Activate our Components. You can review your Current Settings.  When satisfied, Click Next to Continue.

The server will go through a procedure which activates each OCS Server role on our Front End Server. When the Activation is finished, Click Finish.  You will be given the option to view the log which I advise you to do to ensure everything went OK.

Configure Certificate (Step 6)

We are now on Step 6 which is to Configure our Certificate. Click Run to Continue.

On the Welcome Screen, Click Next to Continue.

The next screen will be familiar to many of you.  It’s going through the process of creating a certificate request.  Since we have not created a certificate for our Front End Server, we will want to Choose to Create a new certificate. Click Next to Continue.

Because we have an internal CA installed, we can send the request immediately to an online certificate authority. Click Next to Continue.

By default, the Certificate Name will be set to your server name.  Change this to the FQDN of the Enterprise Pool. Click Next to Continue.

Note: The Certificate Name is not the Subject Name (SN) / Common Name (CN) of the certificate, but I always match the SN / CN of the certificate to the Certificate Name.  On a Standard Edition Server, this would be the FQDN of the server’s computer name.  When deploying OCS in an Enterprise Pool, this would be the FQDN of the pool name, not the server name.  You would then export this certificate after you have obtained the certificate and place the certificate on all other Front End Servers.

You will be asked for your Organization information.  Enter it appropriately. Click Next to Continue.

You will now be asked for your SN / CN.  As stated previously, because we created an Enterprise Pool, we want this name to be the FQDN of our Enterprise Pool.  Because we will be using a second SIP domain (, we will need to add a Subject Alternative Name (SAN) for (sip.SIPDomainName.TLD).  The SAN should automatically be filled in for you due to Step 4 which is when we Configured our Pool. Click Next to Continue.

You will be asked for your Geographical information.  Enter it appropriately. Click Next to Continue.

Since we specified the OCS Certificate Request to send the request immediately to an online certificate authority, OCS will search for an Issuing CA. The name of our CA (not server name but the name of the CA) is OCS-ROOTCA, OCS will display this server as the CA to use.  Choose\OCS-ROOTCA as our CA. Click Next to Continue.

We are ready to Request our Certificate. You can review your Current Settings.  When satisfied, Click Next to Continue.

We should now have our certificate.  Click Assign to ensure that OCS begins to use this certificate. Click OK and Finish to Continue.

Configure Web Components Server Certificate (Step 7)

We are now on Step 7 which is a really straight forward manual step.

It consists of opening IIS (Start > Control Panel > Administrative Tools > Internet Information Services (IIS) Manager).

Go to the Default Website > Right-Click > Choose Properties.

Click on the Directory Security Tab.

In Directory Security, you will see a Secure Communications Section. Click Server Certificate to Continue.

On the Welcome Screen, Click Next to Continue.

Since we already have a certificate on this Front End Server, we will choose to Assign an existing certificate. Click Next to Continue.

Since the certificate is installed on this server already, it’ll find this certificate automatically.  If you are deploying a second Front End Server, you’ll need to make sure you import the certificate with its’ private key into the Local Computer Certificate Store. Click Next to Continue.

The last prompt through this wizard will be for what SSL port to use.  Leave the default at 443. Click through the remaining prompts to finish assigning the certificate.

Note: The reason why you want to assign the certificate to IIS is because the Address Book is a part of the web components server.  Remember setting up the share for this?  Because clients access this Address Book via SSL and the ABS folder within IIS is set to use SSL, we need to make sure IIS uses a certificate to grant SSL access to ABS.  If you don’t, clients won’t be able to access the ABS and will get an ABS error when using Communicator.

Verify Replication (Step 8)

We are now on Step 8 which is to Verify Replication. This is a manual step that I will not go over. Click Help to see the LCSCMD commands used to verify replication.

Start Services (Step 9)

We are now on Step 9 which is to Start Services. Click Run to start the OCS Services.  I will not provide screenshots of this process as it is extremely straightforward.

Validate Server and Pool Functionality (Step 10A)

We are now finally on our final Step, Step 10 which is to Validate Server and Pool Functionality.  This step helps us ensure that our environment is working properly.  I am dividing this step between 2 steps; Step10a and Step10b.  Part of this, is to go through with the validation, DNS needs to be set up.  But because, as I stated earlier, I want to not to DNS yet so we can go through the Communicator logon step by step without DNS and see how to get automatic client logon working, we will finish Step 10 in the next Part.

Server and Pool Validation requires you to have a SIP enabled user account.  To do this, we must use Active Directory Users and Computers on our OCS server.  To do this, go to Start > Run > Type dsa.msc and Click OK.  If you are running a 64-bit OCS Server, you would do this by typing “dsa.msc -32” in the run field.  64-bit OCS servers are only allowed for specific roles.  An Enterprise Front End is not one of them, so we will not have to use the -32 option.

For a list of OCS roles that support 64-bit using Windows on Windows 64 (OCS 32-bit installed on Windows x64), download the OCS planning guide here which I find to be more accurate than the Technet version in regards to 64-bit information.

So now that ADUC (dsa.msc) is open, go ahead and create a couple accounts.  For these user’s, I also mailbox enabled them after creating a new Accepted Domain for and setting up a new e-mail address policy so they obtain a primary e-mail address domain of

I created the following two users:

  • OCS User 1 (username of ocsuser1)
  • OCS User 2 (username of ocsuser2)

Once these users are created, Right-Click the User and choose Enable users for Communications Server.

Tip: One of these options is to Move a User from one pool to another.  If you do this while the source server is up, the user will retain all user configuration/settings that are stored on the server.  For some reason if you have a catastrophic failure on one server, you can move the user to another pool without the source server being up, but that user will lose all of its server stored configuration/settings.

On the Welcome Screen, Click Next to Continue.

We now must choose what Pool we want to assign this user to.  Considering we only have one pool, leave the selection (don’t have much of a choice) at Click Next to Continue.

Here is where we can assign the user as either or  We only specified to allow for automatic sign-on so we will want to make sure we assign our users as  You can use the name as long as you set those users to manually log on and you configure DNS appropriately.  You can allow to allow for automatic logon by re-running the previous wizards.

For purposes of this lab, I will use the user’s e-mail address since they are mailbox enabled and I don’t want users to have to know more than two sets of login usernames (one for Exchange/AD and a different one for OCS). Click Next which will begin the OCS-Enable process.  Once this is complete, click Finish to Finish.

But let’s say you wanted some users to have a different OCS SIP Address than their Exchange address.  Or even if you wanted to use the domain for SIP.  You could choose the following  option although you can e ither choose only firstname.lastname@SIPDomain or sAMAccountName@SIPDomain.

I would now go ahead and OCS enable your second user.  Once finished, you can refresh ADUC and verify these users have a Communications Server address.


Well folks, that is all for Part 3 of this article. For Part 4, I will go through the installation of our Office Communicator 2007 client and get it connected through OCS by configuring DNS. I will then begin preparation of our Edge Servers followed by configuring our ISA 2006 Server.


31 Responses to “Office Communications Server 2007 Enterprise Deployment – Part 3”

  1. on 24 Jul 2008 at 10:44 amDariusCyrus


    Could you please clarify something? Is the Enterprise Pool installed on the Front-end server (OCS-OCS1) ?

    Btw, I’m learning a lot based on your article.


  2. on 25 Jul 2008 at 4:54 pmElan Shudnow

    Go look over Step 2 on Part 2. We created an Enterprise Pool when we installed the databases in SQL. Essentially, our SQL Server holds our Pool information. In Part 3, we added our OCS Server to our Pool. So essentially, a Pool is installed on our SQL Server. We then attach our OCS Server to the Pool.

  3. on 21 Feb 2009 at 5:29 pmMoe

    Thank you for this interesting sample article. Please help me in the following:
    I have a problem, on a consolidated deployment for the servers:
    – Do I have to add the sip A record?
    – I put the shared folders in the form of \\\Presentation , \\~\metadata, \\~\ABS , is that ok?
    – Web Conferencing Service has Stopped and can’t run, reason: Event log is shown Metadata error, it says that metadata is pointing to wrong location, but no errors for the other shares, I can’t find how to reconfigure the metadata location from the OCS Console? or I have to delete the whole Pool and create again?
    – I want to have Internal Web Farm FQDN different than the Pool FQDN in order to expand in the future, is that a problem in the consolidated deployment? and do I create two certificates? and if so, is it possible to apply two certificated on the same server at the same time?
    – Did you install the edge server on the ISA server , or these are separate servers?
    – Do you substitute expanded deployment of Edge Servers with One Server with 4 NICs?

  4. on 23 Feb 2009 at 1:55 pmElan Shudnow

    For your internal pool, you will add an A record for the Pool Name. In Standard Edition, this Pool name is the FQDN of your server. For Enterprise, you specify the pool name during installation. The share names can be whatever you want. You most likely fat fingered the Metadata share name during install which is causing the error. You can re-run through the install wizard and modify as needed.

    Changing the internal web farm FQDN will need to be done directly via WMI. I wouldn’t suggest this unless you are in a massive deployment with tens of thousands of users. Check out the OCS documentation where it discusses scalability. OCS R2 Consolidated Configuration is very highly scalable (100,000 users). OCS R2 Consolidated Configuration is not as scalable but still scales to 40,000 users.

    I do not install the Edge on the ISA Server. These should be separate servers.

    I deploy Edge Servers with 4 NICs. If I need multiple Edge Servers, I also deploy them with 4 NICs and just load balance. Load balance requirements are in the planning documentation.

  5. on 20 Mar 2009 at 11:26 amPablo

    Really thanks for this Article. It helped me a lot.

    However, i had I problem in “Enable this user for Office Communications” on my AD.

    I get, in the “Enable Operation Status” a failed Operation, that show the user that I right-clicked.

    When I try to acces the Communications, I get the following error:

    “There was a problem verifying the certificate from the server. Please contact your system administrator”

    Can you help me in that?
    Really thanks,

    Pablo Bertrão

  6. on 20 Mar 2009 at 11:29 amPablo

    To complete my last message, here some informations:

    Domain – OcsServer
    Computer name – WINOCS
    Application POOL – Ocs2007

    I created a certificade by the OCS Installer and assigned that.
    I also sent this certificate to my default web site on my IIS

    If you need some information to help me, please contact me.

    Really Thanks again,
    Pablo Bertrão

  7. on 21 Sep 2009 at 10:59 pmgrimey

    You have created mailboxes for these people havent you? And they are mail(box) enabled? The tutorial assumes this.

  8. on 20 Mar 2009 at 11:52 amElan Shudnow

    That sounds like you assigned it correctly but your client does not contain the certificate chain used by OCS.

  9. on 24 Mar 2009 at 2:53 pmMoe

    Thank you for the reply,
    As for the meta data error, I fixed this error using the (Wbemtest.exe) command then clicked (Connect), in Namespace, I typed (root\cimv2) etc.. as in the Administration guide and I had the Web Services Running again.

    Now I have the O Communicator running OK, but the problem is that it cannot detect the Telephone system, even after the Voice Integration options are enabled.

    We are using Nortel CS1000 Communications Server, which requires TLS communications, in Nortel Guide, it wants us to configure LDAP over SSL, which I’m not sure if it’s necessary for the deployment or not. Also I have read somewhere that the OCS Proxy activation command should be used as if you have a workgroup not domain activation, as this is the only way to support TLS communications. is that true?
    Please comment on that.
    Thank you in advance.

  10. on 30 Mar 2009 at 9:29 amElan Shudnow

    IIRC, Nortel requires SIP over TLS. I recently just heard this last week but I’m not familiar with Voice Integration with Nortel.

  11. on 30 Mar 2009 at 1:53 pmPablo

    Elan, thank you. It was the problem.

    I imported the certificate to a pfx file and installed under my client.

    My office Communicator is working well.

    Really thanks.

    But I have another question.

    I’m trying now to make Live Meeting works too.

    I installed the Live Meeting client, and their ADD-in too.
    When I try to create a meeting, for example, in my Microsoft Office Word, it tells me that I need to put a “Live Meeting URL”, called “Portal URL”.

    My dns was configured to “Ocs2007.OcsServer”.
    My default website access is “http://ocs2007.ocsserver”

    I configured the SSL under this site, but i can’t access by using https.

    Could, if its possible, you tell me how can I make it works?

    Thank you again,

    Pablo Bertrão

  12. on 03 Apr 2009 at 2:44 pmElan Shudnow

    The Live Meeting URL part is for hosted Live Meeting Service. You only need to worry about the Office Communications Server portion of it which is the top text field and the advanced button.

  13. on 03 Apr 2009 at 2:56 pmPablo

    I found the problem.
    It was my certificate.

    But i’m still trying to know where is this “Portal Url”, required by Live Meeting usage.

  14. on 06 Apr 2009 at 10:38 amPablo

    But when i try to make a “Meet now” – “Share this document to view” option, under for example my microsoft word, It says that I need to make a synchronization. When I click “yes” i get the following error:
    “A connection to the live meeting service could not be established. Please check the live meeting or Portal URL and try again. Do you want to update your user preferences now?”

    If I click yes, a box with tree fields is open.
    A field for a user, a field for my password, and the last for the Meeting URL.

    I don’t know where to find this URL.

    I opened the Live Meeting Client and I make a test connection under “User accounts” It gave to me a message saying that my connection is OK.

    I could not test yet using Outlook because is just a test before the installation under the company. So i don’t have a configured exchange to test.

    My office communcator is working well know. i just need to make the Live Meeting works well.

    Thank you for this support,

    Pablo Bertrão

  15. on 12 Apr 2009 at 7:57 amsunil

    HI Elan,

    can i install dc,exchange,rootca,sql,ocs FE server,isa on a single machine and edge server on a seperate machine ?

  16. on 13 Apr 2009 at 1:14 pmElan Shudnow


  17. on 14 Apr 2009 at 11:54 amPablo

    The OCS gives me this “Hosted live meeting service”?
    I really need to install the live meeting client and give to my users it access.
    Should I install this hosted service into my OCS server?

    Thank you again,
    Pablo Bertrão

  18. on 15 Apr 2009 at 1:34 pmElan Shudnow

    Hosted Service has nothing to do with OCS. They are two different products. I’m not sure what you’re referring to. Please provide a screenshot. If you’re talking about the Conferencing Plugin, you can enter either your Hosted Live Meeting information, your OCS information, or both. If you enter both, when creating a Web Conference, you can choose from either Live Meeting or OCS Web Conferencing.

  19. on 16 Apr 2009 at 10:35 amPablo

    Your explanation was helpful,
    But let me explain better what i’m trying to say.

    I have a functional OCS 2007 Enterprise working. My instant messaging, my video/audio conferences (by using Communicator) is working well.

    However, I want to know if the Live Meeting (and their add-ins for office) is also a client of Office Communications Server, or if it’s a client of another product. (Maybe a client of “hosted service”).

    I understood know that this hosted service is a another product.
    Please, consider this image to understand better:

    This is the error that I get by trying to use the Live Meeting.

    Live Meeting client and their add-ins is just for hosted service?

  20. on 16 Apr 2009 at 10:38 amPablo

    If the Live meeting client and their office add-ins can be supported by OCS, how can I make they work?

  21. on 17 Apr 2009 at 5:50 amToke

    Hi Elan,
    I’m sorry if this is the wrong place to ask this question but I’ve been looking around the virtual world to get some information about initiate a Live Meeting… I landed here and I really appreciate you article! It’s really great information!

    I’m currently working on a SharePoint project and need to do something as simple as to make a button – a C# webpart – that initiates an intranet Live Meeting. We have a complete setup with AD, Exchange and OCS that is running and the Outlook “Meet now” works perfectly. What I need to know is where to start :) Do I have to use Live Meeting Services or anything else?

    Maybe it’s me but I find it really difficult to get some information from Microsoft on “how-to-do-it”…

    Thanks in advance!

  22. on 17 Apr 2009 at 10:59 amElan Shudnow

    Pablo, you can use the same Live Meeting client for either OCS Web Conferencing or Hosted Live Meeting. When you configure the Live Meeting client, you can put in your OCS information and/or your Hosted Live Meeting. If you enter both you can configure which account is used for Meet Now. Or if someone invites you to a meeting, the Live Meeting client can connect to either Hosted Live Meeting or OCS.

  23. on 17 Apr 2009 at 11:04 amElan Shudnow

    Toke, anything related to development for OCS makes me *shrug*. There are some development blogs out there that share information on using the OCS API. I’d ask the questions there.

  24. on 17 Apr 2009 at 2:45 pmPablo

    Thank you Elan,
    I found this material teaching how can I schedule a meeting by using Communications server :

    In this document, at the page 14, it shows how can I start a meeting by using LiveMeeting Client.

    This option “Meet Now”, in the step 3, doesn’t exist/show into my LiveeMeeting client.

    I’ve verifyed my user connection by “Test connection” and everything is ok.

    Do you have any idea? How can I schedule a meeting by using LiveMeeting Client in a Office Communications Server 2007?

    Thank you again for this replies,

    Pablo Bertrão

  25. on 23 May 2009 at 2:03 pmsodiq

    Please can you kindly help with steps of deploying OCS EE for multiple domains in a single forest.

  26. on 23 May 2009 at 4:26 pmElan Shudnow

    Steps? That’s quite a lot to ask for. Instead, try asking a specific question and I’ll try to answer.

  27. on 26 Jun 2009 at 12:28 pmPablo

    Just to share,
    I found the source of my problem (23)

    The option “meet now” were not showing because I didn’t give to my user permission to use live meeting, and also didn’t configured the policy setting for live meeting usage.

    This permission can be configured into administrative tools console.

    Thank you Elan, again,
    Now I have a fully/functional OCS working.

    Just a point: What infra-structure do you recommend to a demand of 30.000 ( max 100.000) users ?

  28. on 18 Nov 2009 at 3:01 pmPablo

    Hello Elan.
    Could you tell if exist some tool or feature that we can install or configure to control our users access?

    For example, I have 3 Groups.
    People of group 1 can talk to group 1 and also group 2
    people of group 3 can talk to group 3 and also group 2
    People of group 2 can tank to anybody.

    Like deny a group to speak with another

    This is possible?

    Thank you.

  29. on 18 Nov 2009 at 4:52 pmElan Shudnow

    Can only do it on a user by user basis by using the LCSAddACEs.wsf script in the OCS Resource Kit. Instructions for it are provided in the LCS 2005 Resource Kit. If you want more granular control, you'll need to have custom development using the Ethical Walls API. A sample is here:

  30. on 02 Apr 2010 at 6:37 pmAbdul

    Hello Elan ,
    thanks for your superb walk through ,. i just have a question i wanted to ask. I have deployed OCS 2007 r2 in a front end server and the MOC client works fine with the Audio and Video call but when i try to configure the live meeting it does not connect to the server i get an error message saying
    "Cannot connect to the server because the information in the User Accounts dialog might be incorrect or improperly formatted. Please verify that this information is correct, an then click Test Connection. If you still can't connect the server might not be available." any idea on this please.

  31. on 02 Apr 2010 at 10:03 pmeshudnow

    I've seen this from an older version of the Live Meeting client. Make sure you are running the latest. If you are, try uninstalling it and re-install. This is for both the Live Meeting client and the Outlook Conferencing Plugin.

Trackback this post | Feed on Comments to this post

Leave a Reply