RSS Subscription 167 Posts and 2,643 Comments

Office Communications Server 2007 R2 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 2007 R2 Server which is connected to an x64 SQL Server 2008 Back-End Server. We first discussed what the lab setup is going to be using Hyper-V, and then proceeded to the configuration of our Enterprise Certificate Authority. In Part 2, we went over the Environmental Preparation for our OCS 2007 R2 environment.

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 (exchange.shudnow.net) that is separate than our AD Namespace (shudnow.net). 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 R2 Server Installation

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

  1. Prepare Environment (Completed in Part 2)
    1. Prepare Active Directory (Completed in Part 2)
    2. Create Enterprise Pool (Completed in Part 2)
    3. Deploy Hardware Load Balancer (Completed in Part 2)
    4. Configure Pool (Completed in Part 2)
  2. Add Enterprise Edition Server to Pool
    1. Add Server to Pool
    2. Configure Certificate
    3. Configure Web Components Server Certificate
    4. Verify Replication
    5. Start Services
    6. Validate Server and Pool Functionality

Add Enterprise Edition Server to Pool

Add Server to Pool (Step 1)

Because we are using Server 2008, our IIS version will be 7.  Kernel Mode Authentication runs under the context of a computer account.  OCS runs its services under the context of a user account.  With Kernel Mode Authentication enabled, Kerberos tickets will fail.  Because of this OCS 2007 R2 disabled Kernel Mode Authentication on IIS during installation.

Instead of disabling kernel mode authentication in IIS, you can configure IIS to use the Web application pool’s identity for internal virtual directories used by OCS.  We can do so by modifying Windows Authentication on the Default Website of the Web Components Server using the ApplicationHost.config File.  Open the %windir%system32inetsrvconfigApplicationHost.config file in a text editor. For all folders under the Default Web Site location path, set the value of the WindowsAuthentication element and the useAppPoolCredentials attribute to true. For example:

<system.webServer>
<security>
<authentication>
<windowsAuthentication enabled=”true” useAppPoolCredentials=”true” />
</authentication>
</security>
</system.webServer>

When I went to look for the above (from the OCS R2 docs), I didn’t find any useAppPoolCredentials but I did see windowsAuthentication and set it to true which you can do via the IIS Manager.

We are now on Step 1 which is to Add Server to Pool. As a prerequisite, you’ll need to install IIS by following the instructions here for Server 2003 and here for Server 2008.  For Server 2008, make sure you install Windows Authentication and all IIS 6 Management Compability Role Services. 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 OCSPool.shudnow.net. 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 2)

We are now on Step 2 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 (exchange.shudnow.net), we will need to add a Subject Alternative Name (SAN) for sip.exchange.shudnow.net (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 CA, OCS will display this server as the CA to use.  Choose SHUD-DC2.shudnow.netCA 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.  Choose Assign certificate immediately. Click Next to Continue.

You can continue through the remaining prompts to finish the certificate request and assign it to your server

Configure Web Components Server Certificate (Step 3)

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

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

Go to the ServerName > Sites > Default Website >IIS > Authentication > Select Bindings from the Action Pane.

Choose https and select our Pool Certificate.  Make sure IP address is set to All Unassigned.  Click Ok then Close to Continue.

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 4)

We are now on Step 4 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 5)

We are now on Step 5 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.

Note: I did notice an issue with the Monitoring Agent not being able to start.  I then noticed in the Event Viewer that this service is for QOE and it can’t start because it can’t create an administrative message queue.  Because we didn’t choose to deploy QOE, I have disabled this service.  If QOE is needed in the future, you can set up QOE and re-enable this service.

IMPORTANT UPDATE: As I said, I disabled the service but do not do this.  Make sure you install Message Queuing as an OCS April Update doesn’t work properly and will try to mess with this service and render your OCS Server in an unworkable state.  Future patches such as ones after June state that they don’t have this problem.  So if you plan on installing June update or later, you can safely disable this service and patch your servers without worry (hopefully.) You can read more about this issue here.

Validate Server and Pool Functionality (Step 6A)

We are now finally on our final Step, Step 6 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; Step 6a and Step 6b.  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 6 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 > Control Panel > Administrative Tools > Active Directory Users and Computers.

So now that ADUC 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 exchange.shudnow.net and setting up a new e-mail address policy so they obtain a primary e-mail address domain of exchange.shudnow.net.

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 OCSPool.shudnow.net. Click Next to Continue.

Here is where we can assign the user as either shudnow.net or exchange.shudnow.net.  We only specified exchange.shudnow.net to allow for automatic sign-on so we will want to make sure we assign our users as exchange.shudnow.net.  You can use the shudnow.net name as long as you set those users to manually log on and you configure DNS appropriately.  You can allow shudnow.net 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 shudnow.net 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.

Summary

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.

Share

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

  1. on 13 Jan 2009 at 5:57 pmDaniel A. Galant

    I have been messing with trying to get OCS R2 installed into a similar lab setup for a number of days now. I keep running into the same error when trying to add the OCS Server to the Enterprise Pool. It always fail with “No mapping between user accounts and security IDs was done”. This is also installing with 64bit SQL running on Server 2008. One difference, my SQL is also the DC, to save on Virtual Machines. This worked with no issues for OCS 2007. R2 seems to be throwing a fit however. Any thoughts on this?

  2. on 13 Jan 2009 at 6:32 pmElan Shudnow

    Did a search online and saw others having this issue when SQL was on a DC.

  3. on 21 Jan 2009 at 11:06 pmLiam

    Same issue myself. Windows 2008 Enterprise DC, with SQL 2005 SP3 Enterprise installed. I get the ‘No mapping between account names and security IDs was done’ – If I run the activation or installation (eg Archiving Role) on the DC/SQL box, it works fine, when trying to activate any role, on any domain member it fails.

  4. on 27 Jan 2009 at 7:26 pmDaniel A. Galant

    As a follow up, though still having the problem with Server 2008, replacing the DC/SQL combo with a Server 2003 version, the Add Server to Pool works just fine. My conclusion then, there is something with either the Security settings on a 2008 DC or something in IIS7 that is causing the “No mapping” issue. Unfortunately, I don’t have the time to run this down right now. If anyone does find the answer to this, I’d really appreciate a nudge.

  5. on 10 Mar 2009 at 8:28 amMarc Mengerink

    Daniel/Liam,

    Had the same issue using win2k8/SQL2k8. Turns out that the passwords where too complex/long for my RTC…… service accounts that are used in the process of adding the OCS server to the enterprise pool. Changing the passwords to simple/short ones solved it for me. Weird!

  6. on 21 Apr 2009 at 11:37 amMarc G

    It looks like I have a port conflict on my FE server due to the fact that I added Web Access on port 443. What alternative port do you recommend I use for the default web site? Or should I change the web access port? It looks like if I stop the default web site, I can get web access started. However, authentication errors out because of this. But regular local MOC client works fine (strange). Thanks for your help!

  7. on 21 Apr 2009 at 12:31 pmElan Shudnow

    CWA isn’t supported on any other server. It needs to have its own dedicated server. Either change the port on CWA and have ISA proxy to it via another port so if you hit something like chat.something.com it hits ISA on 443 and then ISA communicates to the actual CWA on a custom port. But again, it’s not supported on any other server anyways.

  8. on 29 Apr 2009 at 11:33 pmAaron Tiensivu's Blog

    RtcQmsAgent fails to start on OCS 2007 R2 server – and causes KB 967831 (April 2009 update for Front End Server components) install to fail…

    If you are not planning on using the Office Communications Server Monitoring Agent, which is fairly common assumption in lab environments, you likely never planned on installing MSMQ or knew that you had to. Unfortunately, the OCS 2007 R2 setup program…

  9. on 30 Jun 2009 at 9:03 amPatrick Tran

    Hi Elan,
    I tried to add server to pool, but at select main service account stage, the system shows RTCService as Use An Existing Account and asks a password I didn’t put before (what password is it for that?). So I created RTCFService as Create A New Account and entered a new password. I did the same for RTCFComponentService and RTCFGuestAccessUser. But the run failed with error 0×80070533 on RTCFService account saying it is a desactivated account and failure of opening session. I got the same error on Activate ConferencingServer and on Activate Enterprise Edition Server.
    I guess I have to activate RTCFService account to solve all the problems but how can you activate it?
    Or should I use RTCService as Use An Existing Account but where is its password?
    Thanks for your help!

  10. on 01 Jul 2009 at 11:12 pmElan Shudnow

    Patrick, I always just pre-create all my service accounts and ensure I set them to not expire. That way when I get to each part of the service account selection page, I can specify the account and password to use.

  11. on 02 Jul 2009 at 11:13 amPatrick Tran

    Ok Elan,
    It was strange I didn’t pre-create the service accounts and it asked a password I couldn’t enter.
    I had to create new service accounts with a new password, ran configure certificate 3 times and it passed after I added a role or fonctionnality.
    But I have the error code 0xC3EC79E6 on starting front-end and monitor agent now. It failed.
    I have a valid certification authority assigned to front-end and monitor agent except it is for controlling identity of a remote comp.
    I don’t understand why starting of services for front-end and monitoring agent failed with that error, with the certificate being valid.
    Should I create a new certificate and restarted the services?
    Thank you!

  12. on 02 Jul 2009 at 11:46 amElan Shudnow

    That error code most likely means there’s a wildcard in your certificate. Search for that error code and there’s tons of stuff online…

    Also, I already included information on the Monitoring Agent failing to start in this article. Search for the words Important Update.

  13. on 06 Jul 2009 at 9:30 amPatrick Tran

    Elan,
    Thanks.
    For Monitoring Agent, I entered these 2 lines:
    ServerManagerCmd -i MSMQ-Services
    ServerManagerCmd -i MSMQ-Server
    and ran Starting Services again.
    And Monitoring Agent starts.
    It’s fine.
    But front-end service not, due to target not reachable.
    So I let OCS for a while.

  14. on 10 Jul 2009 at 7:16 amNick Kenyon

    Elan,

    I’ve done this but, when I right click on one of the users I do not have the option for “Enable Users for Communications Server” I have prepped the Schema, Forest and Domain, and checked replication.

    Could you advise?

  15. on 13 Jul 2009 at 1:03 pmElan Shudnow

    You need to manually install the Administrative Tools to get that option. They’re not installed as a part of the regular installation option as they were with R1.

  16. on 16 Jul 2009 at 7:56 amAdi Nugraha

    hi, do you have a setting for IIS Authentication when installing OCS 2007 R2 on windows 2008 ? My installation is behaving funny in that the Integrated Authentication to IIS Website of the OCS web components isn’t working, that is I can log in from a client by supplying the username and password, but I can’t go the web components site when Browsing from within the server itself, and it gives validation errors when i validate web components server

  17. on 21 Jul 2009 at 1:16 pmMax

    I managed to get CWA working on a FE server. I just assigned two different IPs with the appropriate DNS records and certificates assigned to them. May be not ideal, but it works.

  18. on 22 Jul 2009 at 11:40 amElan Shudnow

    Adi, you should be able to re-install web components to get IIS websites re-created.

  19. on 24 Jul 2009 at 3:03 amAdi Nugraha

    Elan, thanks for the tip, I was able to find the problem on my installation, because I was upgrading from OCS 2K7 RTM the service account I used [RTCComponentService] was only granted delegation to the old pool name, once I use setspn to grant the delegation permission to the new pool and server i was able to validate succesfully and everything else worked as expected, though the validation still came up with a warning that it can’t access the external fqdn eventhough it was registered in DNS and I’ve already granted delegation permission [setspn] to the external fqdn pool name. this is the result of setspn -L [Service Account Name]

    http/ocs.domain.com –> [External FQDN of OCS]
    http/ocs02.domain.com –> [New Pool FQDN]
    HTTP/ocs01.domain.com –> [Old pool FQDN]
    HTTP/ocsupd01.domain.com [Old updateServer FQDN]

    Max, I was considering using 2 IP for the FE as well but was concerned about how it would effect DNS Registration, how did you limit DNS resgitration to the IP that is used for FE only ?

  20. on 24 Jul 2009 at 8:59 amElan Shudnow

    I always use different service accounts for pools so there’s no issues with SPNs.

  21. on 08 Aug 2009 at 7:13 amally_r

    Hi Elan,

    After a few issues I have finally got OCS 2007 R2 implemented. Your blog and OCSepedia certainly helped a lot. One problem I did have though was when editing the ApplicationHost.config. I copy and pasted it from your blog and kept on being warned that it wasn’t well formed XML. It wasn’t until I opened the file in visual studio that I noticed the quotes where ” and not “. Thought I would mention it as I’m sure someone else will be lazy like me a get caught out by this too.

    Cheers

    Ally

  22. on 08 Aug 2009 at 7:15 amally_r

    Actually that hasn’t been displayed write either. Guess it must be the way the blog is styled.

  23. on 06 Sep 2009 at 5:25 pmCooper

    Elan,
    Great post. Thank you.
    After Step 5, there is no "Enable users for Communications Server" option when "right click a user in ADUC. Office Communications Server 2007 R2 Deployment Log shows no errors.
    Could you advice?

    Thank you,
    Cooper

  24. on 06 Sep 2009 at 8:08 pmElan Shudnow

    Install the Administrative Tools.

  25. on 06 Sep 2009 at 8:14 pmCooper

    Regarding "There is no "Enable users for Communications Server" option when "right click a user in ADUC".
    You have to install Administrative Tools – located on the right side of OCS 2007 R2 ENT installation window.

  26. on 18 Sep 2009 at 3:44 ammahbod

    hi
    when i want to issue Ca from Domain internal Root Ca for Internal Interface of Edge Server It make Fail
    Beacuse Edge server is Stand-alone, then if i Join Edge server to domain the issue make sucessful.

    Plz Help Me

    i want to know that can i Issue All Certificate from Public Ca

    Including:
    Pool Ca
    Extwebfarm Ca
    Int ,EXT,AV,WebConf Ca……………

  27. on 21 Sep 2009 at 7:43 pmPablo

    Hello Elan,
    First, let me say that this is a very nice step-by-step, and helped a lot.

    I have an OCS R2 installed in a ad/dns server 2003 x86

    It's possible to install the administrative tools (R2) in this domain?

    Thank you,

  28. on 22 Sep 2009 at 8:23 pmElan Shudnow

    The OCS Admin Tools can be installed in any domain as long as it's in the same forest.

  29. on 08 Oct 2009 at 2:52 amVenky

    Hi I have Office Communications Server 2007 R2 Eval.
    In this application Im not able to check and uncheck options in Tools>Options>general and personal tabs.

    Is there any way that we can make them activate ?

    Pls do reply your suggestions

    Regards
    Venky

  30. on 09 Oct 2009 at 2:05 amElan Shudnow

    Pablo, sorry I didn't see this comment till now. You can install the administrative tools in any domain within the forest that contains OCS 2007 R2.

  31. on 18 Feb 2010 at 10:12 pmbob

    I get failure [0x80070534] no mapping between account names & security IDs was done when I am trying to deploy the STD OCS R2 server to a 2008 R1 server. This is a pilot deployment with hyper-v images….

    Thanks

  32. on 06 Apr 2010 at 4:19 amAlham

    Hi!
    Can anyone help me?
    We have OCS 2007 installed in our organization and woking fine, a couple of days ago i change password for RTCService account and modify on services where it works:
    Office Communications Server Telephony Conferencing
    Office Communications Server Audio/Video Conferencing
    Office Communications Server Web Conferencing
    Office Communications Server IM Conferencing
    Office Communications Server Front-End
    And on IIS application pools:
    LSConferencingAppPool
    LSGroupExpAppPool
    But a receive events on my DC
    Event looks like:
    Pre-authentication failed:
    User Name:RTCService
    User ID:domainnameRTCService
    Service Name:krbtgt/domainname
    Pre-Authentication Type:0×2
    Failure Code:0×18
    Client Address:ip address of server

    Can somebody tell me, where i should insert new password too?

  33. on 06 Apr 2010 at 12:03 pmeshudnow

    The following article should help you out:

    Hyperlink is corrupted, can u put it again?

  34. on 07 Apr 2010 at 2:55 amAlham

    Thanks a lot, i find it.

  35. on 09 Apr 2010 at 9:52 pmRocky

    Hi,

    when I am running the "Add Server to Pool" command its raising following exception:

    "Product: Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit — Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit installation requires Microsoft .NET Framework version 3.5. Installation can not continue."

    I already have .net framework 3.5.1 installed on my system. Am I missing something here. I am doing the installation on WIN 2008 R2 standard edition.

    Would appreciate your response.

  36. on 09 Apr 2010 at 11:16 pmeshudnow

    Check this article out. It may key in to something you haven't done. Make sure you install that KB article: http://msunified.net/2010/04/09/installing-ocs-20

  37. on 12 Apr 2010 at 2:52 pmReza

    I can not Start IIS . Event viewer show this error : Cannot register the URL prefix 'https://*:443/Abs/Ext/Handler/&#039; for site '1'. The necessary network binding may already be in use. The site has been deactivated. The data field contains the error number.

  38. on 12 Apr 2010 at 4:11 pmRocky

    I already ensured that I have all the prerequisites in place. What i am suprised is that its asking me for .NET 3.5 which is already installed.

    At this point I havent even installed the OCS also.

  39. on 12 Apr 2010 at 4:12 pmRocky

    Also, I have AD on WIN 2008 R2 machine.

  40. on 12 Apr 2010 at 7:10 pmRocky

    finally figured out what is the issue: I have .NET framework 4.0 installed :( I uninstalled it and installation moved .

  41. on 29 Apr 2010 at 3:20 pmRichard

    Hi Bob

    Did you find a resolution for this problem?

  42. on 04 May 2010 at 2:55 pmAndy

    I manage to install QoE service on a 2008 R2 Std. edition. Just install Message Queue feature and start the service by manual and it will do it.

  43. on 11 May 2010 at 4:59 amChris

    I am getting the error "[0xC3EC78D8] failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time. I have uninstalled KB974571 and tried running OCS again getting same error. I have applied MS Patch ocsasnfix.exe and getting same error. This has worked for 99% of people with the same issue on Forum, I am that 1% it has not worked for. Have been battling this for days. Running my SQL 2008 Database and DC on the same VM

  44. on 15 May 2010 at 11:37 amChris

    I am having the "Communicator could not determine the location of your Exchange Web Services" error…help

  45. on 25 May 2010 at 2:42 pmeshudnow

    Chris, it sounds like you're on Exchange 2007 or Exchange 2010. Communicator uses autodiscover.domain.com to look up web services. If you're on Exchange 2003, it uses MAPI to connect to Public Folders. I would make sure Autodiscover is functional using autodiscover.domain.com. If you have Outlook 2007 SP1, COmmunicator can utilize the Autodiscover information Outlook 2007 SP1 or above retrieved.

  46. on 10 Jun 2010 at 9:36 pmVladimir Abadzhiev

    Great HOWTO, here is my little contrinution. In this step i ran into a problem when adding my server to the newly created pool. I got the below error msg:

    "Failure [0xC3EC78DB] Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time."

    This is a known issue which requires registry change or downloading a 66kb file from the MS KB here: http://support.microsoft.com/kb/974571

    Simply download and run: ocsasnfix.exe As Admin in Command Prompt and pefrom the Add Server to pool action again.

  47. on 08 Jul 2010 at 9:39 amErik

    If you get the error
    “Product: Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit — Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit installation requires Microsoft .NET Framework version 3.5. Installation can not continue.”
    by installing any component, check out if you have installed Net framework 4.0.
    I had installed net framework 3.5 over features on w2k8 r2 together with net framework 4.0.
    I got this error and after I installed net framework 4.0 I was able to install the cwa role.

    Erik

  48. on 26 Aug 2010 at 6:04 amHIMAYAT ULLAH KHAN

    i have installed OCS 2007 R! on my DC but i am unable to Enable OCS for Users.
    The Tasks Fail Everytime.

    Can you tell me what else i am missing?

    thanks.

  49. on 08 Sep 2010 at 4:02 pmMukhtar Qazi

    Hi,
    Can anyone let me know to how set the password or code for international dialing in OCS 2007 R2 environment i.e. to control the miss use of the International calling facility?

    Thanks,

    Mukhtar

  50. on 22 Sep 2010 at 10:10 amMichaelH

    When I try to add server to the created Back-end pool, I only have the option to select my front end server.

    The setup is:
    Back-end server:
    * Server 2k8 R2
    * SQL 2008 64bit.
    * Name ocssql

    Front-end server:
    * Server 2k8 R2
    * Name ocs

    The Pool is installed direct on the SQL server in the default instance.
    Poolname is ocspool.domain.com
    When I get to the "Select a Pool" part of the front-end installation I can only select ocs.domain.com, and not ocspool.domain.com

    Anyone thats can help me here.

    Thanks in advance

    Michael

    I have created a DNS entry that points ocspool to thew IP of ocssql

  51. on 04 Oct 2010 at 10:44 pmRonaldo

    Dear Elan Shudnow.
    I use windows server 2003 sp2. I install ocs enterprise edition.
    when I go to step Configure Web Components Server Certificate (Step 3). Because me use IIS6 therefore I doesn't config IIS.
    You can help me config https on IIS6 in windows server 2003??
    Thanks and BRs.

  52. on 05 Oct 2010 at 8:03 amElan Shudnow

    All you have to do is add the server certificate to the default website. Everything else with SSL is already set.

  53. on 06 Oct 2010 at 1:30 amRonaldo

    Hi Elan.
    I know is must config with default website, but how doesn't add protocol https with ssl?
    Are you can upload step config IIS with images detail?
    Thahnks and BRs.

  54. on 12 Feb 2013 at 12:41 amFanny Mesmer

    Nice web site. Does one manage your site with the software?

Trackback this post | Feed on Comments to this post

Leave a Reply