Export (0) Print
Expand All

Migrating Group Chat Server

 

Topic Last Modified: 2013-10-04

Microsoft Lync Server 2010, Group Chat is an extension of the Microsoft Lync Server 2010 infrastructure. Depending on your topology, you can migrate Lync Server 2010, Group Chat to a single server or to multiple servers. For details about available topologies and the technical and software requirements for migrating Group Chat Server, see Planning for Group Chat Server in the Planning documentation.

noteNote:
This topic assumes that you have already installed Lync Server 2010 in coexistence with Microsoft Office Communications Server 2007 R2.

If your organization requires compliance support, you can install a Compliance service on a separate computer after you have completed installing and configuring Group Chat Server. For details, see Deploying Compliance Support for Group Chat Server in the Deployment documentation.

At a minimum, each topology requires a server running Lync Server and a server that has Microsoft SQL Server 2008 database software installed on it.

importantImportant:
Group Chat Server must be installed on an NTFS file system to help enforce file system security. FAT32 is not a supported file system for Group Chat Server.

Specific combinations of server and client versions can coexist when migrating from Office Communications Server 2007 R2 Group Chat to Lync Server 2010, Group Chat. The following table summarizes the supported combinations. Note that Microsoft Lync 2010 Group Chat, the latest client, cannot connect to Office Communications Server 2007 R2, the previous server version.

Both the latest and previous versions of Group Chat Server support multiple Group Chat Server pools. We strongly recommended that you use only one version in your deployment to ensure that all clients can access channels in all pools; however, we support having both a Communications Server 2007 R2 Group Chat pool and a Lync Server 2010, Group Chat pool. The following table shows the limitation to this design: Microsoft Office Communicator 2007 R2 Group Chat, the previous client, can connect to channels in both pools, while Lync 2010 Group Chat is limited to joining channels only in the Lync Server 2010, Group Chat pool.

Supported Server and Client Coexistence Combinations

Communications Server 2007 R2 with Communications Server 2007 R2 Group Chat Communications Server 2007 R2 with Lync Server 2010, Group Chat Lync Server 2010 with Communications Server 2007 R2 Group Chat Lync Server 2010 with Lync Server 2010, Group Chat

Communicator 2007 R2 with Communicator 2007 R2 Group Chat

Yes

Yes

Yes

Yes

Communicator 2007 R2 with Lync 2010 Group Chat

No

No

No

Yes

Lync 2010 with Communicator 2007 R2 Group Chat

No

No

Yes

Yes

Lync 2010 with Lync 2010 Group Chat

No

No

No

Yes

Lync Server 2010, Group Chat does not support coexistence with Communications Server 2007 R2 Group Chat when using a single Group Chat database.

Review the coexistence details in the previous section and then complete the following step.

importantImportant:
This step must be completed much earlier than migration to allow time for replication.
  • Create a trusted application pool on the Lync Server that you will install Lync 2010 Group Chat (client software) on. You can create a trusted application pool on any computer that has Lync Server Management Shell installed on it by using the New-CSTrustedApplicationPool cmdlet.

To migrate from an earlier version of Group Chat Server, use either of the following two methods:

  • Swap server upgrade (recommended upgrade path).   Keep your existing Group Chat Server on standby, and install Lync Server 2010, Group Chat on a separate server. For information about installing and configuring Group Chat Server, see Installing and Configuring Group Chat Server in the Deployment documentation.

  • Static (in-place) server upgrade.   Uninstall Microsoft Office Communications Server 2007 R2 Group Chat, and then install Lync Server 2010, Group Chat on the same computer. Choose this method if you do not have the hardware required to install Lync Server 2010, Group Chat on a separate server. With this method, you must first delete the existing trusted service entry (TSE) to enable replication. Expect some downtime while replication occurs, before you can install Lync Server 2010, Group Chat.

importantImportant:
We recommend that you move the Lookup service account to the Lync Server pool that will service the Group Chat Server pool.

If you are performing a swap server upgrade (recommended), complete the following steps to migrate from Communications Server 2007 R2 Group Chat to Lync Server 2010, Group Chat.

  1. Stop the existing Channel and Lookup services on your existing server.

  2. Back up the existing Group Chat database.

  3. Install Lync Server 2010, Group Chat on a separate server.

  4. Specify the existing Lync Server 2010, Group Chat database.

  5. If the upgrade succeeds, uninstall the original (old) Group Chat Server.

  6. If the upgrade (ServerSetup.exe) fails, uninstall the new Group Chat Server, restore the Group Chat database from the backup, and restart the original Communications Server 2007 R2 Group Chat services. Examine what has failed (for example, the new Group Chat Server had not fully replicated, or an issue appeared external to the installation).

If you are performing a static (in-place) server upgrade, complete the following steps to migrate from Communications Server 2007 R2 Group Chat to Lync Server 2010, Group Chat.

  1. Stop the existing Channel and Lookup services.

  2. Back up the existing Group Chat database.

  3. Update the Group Chat database to reference the Lync Server pool by moving the server running Office Communications Server 2007 R2 to a Lync Server pool by using the Microsoft Lync Server 2010, Group Chat Configuration tool. Do not restart the services.

  4. Uninstall Communications Server 2007 R2 Group Chat. Choose the option to keep the database.

  5. Run a Microsoft SQL Server query to change the Communications Server 2007 R2 pool to a Lync Server 2010 pool in tblConfig, in the pool row that has the highest configuration sequence ID.

    The following sample SQL Server query shows how to change to a Lync Server pool.

    importantImportant:
    This sample query uses placeholder text that must be replaced with information from your organization. Placeholder text is in italic type.
    UPDATE [tblConfig]
       SET [configContent] = '<configuration label="pool">
      <pool>
        <serveredition>PE</serveredition>
        <serverlogin>
          <type>AUTH_MA7_OCS_MTLS</type>
          <port>0</port>
          <server>serverName.domainName.com</server>
        </serverlogin>
        <channelserver>
          <ADConnect>
            <GlobalCatalog>
              <findgc>True</findgc>
              <host>
              </host>
              <allownonssl>False</allownonssl>
              <usecreds>False</usecreds>
              <username>
              </username>
              <adsynchfreq>10</adsynchfreq>
            </GlobalCatalog>
          </ADConnect>
          <adupdate>
            <querysize>1</querysize>
            <batchsize>20</batchsize>
            <sleeptime_ms>10000</sleeptime_ms>
            <accesspoll_ms>604800000</accesspoll_ms>
            <accesspoll_size>50</accesspoll_size>
            <accesspoll_enabled>False</accesspoll_enabled>
          </adupdate>
          <chat>
            <messagesizelimit>512</messagesizelimit>
            <storysizelimit>4096</storysizelimit>
          </chat>
          <serverbackchat>
            <querylimit>500</querylimit>
            <cache_size_limit>2500000</cache_size_limit>
          </serverbackchat>
          <watermarks>
            <batch_message_count_max>20</batch_message_count_max>
            <async_send_max>100</async_send_max>
            <async_send_max_lo>90</async_send_max_lo>
            <outbound_queue_max>100000</outbound_queue_max>
            <outbound_queue_max_lo>90000</outbound_queue_max_lo>
            <low_priority_queue_max>500</low_priority_queue_max>
            <inbound_queue_size_max>10000</inbound_queue_size_max>
            <channelinvitemax>50</channelinvitemax>
            <participantlist_high>75</participantlist_high>
            <participantlist_low>60</participantlist_low>
          </watermarks>
          <compliance>False</compliance>
        </channelserver>
        <lookupserver>
          <serverlogin>
            <username>domainName\userName</userName>
            <uri>sip: username@domainname.com</uri>
          </serverlogin>
        </lookupserver>
        <compliance>
          <filerepository>
          </filerepository>
        </compliance>
      </pool>
    </configuration>'
    WHERE configLabel = 'pool' AND configSeqID = highest sequence ID
    
    noteNote:
    In this sample, the configLabel and configSeqID are column names in the table.
  6. Run ServerSetup.exe, and follow the instructions for installing Lync Server 2010, Group Chat. For details, see Deploying Group Chat Server in the Deployment documentation.

    noteNote:
    If this step fails, follow the steps in “Group Chat System Maintenance and Operations” for installing Communications Server 2007 R2 Group Chat against an already patched database. For details, see “Group Chat System Maintenance and Operations” at http://go.microsoft.com/fwlink/p/?LinkId=224491.
  7. If you use the Compliance service, do the following:

    1. Verify that Compliance service has processed all messages. In other words, ensure that no new output files have been created within the last compliance interval.

    2. Stop the Communications Server 2007 R2 Group Chat services.

    3. Uninstall the Communications Server 2007 R2 Group Chat Compliance Server.

    4. Install the new Lync Server 2010, Group Chat Compliance Server.

    5. Start Lync Server 2010, Group Chat services.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft