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 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 server upgrade.   Uninstall 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 Group Chat Server 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.
  
  

Important:
You must install Lync Server 2010, Group Chat on a computer running Lync Server. We recommend that you move the Channel, Lookup, and Compliance services to the computer running Lync Server 2010, Group Chat.

Specific combinations of server and client versions can coexist when migrating from 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 Communications Server 2007 R2, the previous server version.

Both the latest and previous versions of Group Chat Server support multiple Group Chat 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 Lync Server 2010, Group Chat pool. The following table shows the limitation to this design: Communicator 2007 R2 Group Chat 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

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

Review the coexistence details in the previous section and then complete the following steps. This procedure must be completed much earlier than migration to allow time for replication.

1. Create a trusted application pool on the Lync Server that you will install Microsoft Lync 2010 Group Chat (client software) on. You can create a trusted application pool on any computer that has Microsoft Lync Server 2010, Group Chat Admin Tool installed on it by using the New-CSTrustedApplicationPool cmdlet.
   
   
2. In Administrative Tools, click Microsoft Lync Server 2010.
   
   
3. Right-click your Front End pool, click Properties, and then click Front End Properties.
   
   
4. On the Front End Properties page, select the Host Authorization tab, and click Add. The Add Authorized Host page appears.
   
   
5. On the Add Authorized Host page, in the Server window, enter the fully qualified domain name (FQDN) for the Microsoft Office Communications Server 2007 R2, Enterprise pool.
   
   
6. On the Add Authorized Host page, in the Settings window, select the Throttle as Server and Treat as Authenticated check boxes for the Group Chat Server.
   
   

Important:
You must install Lync Server 2010, Group Chat on a computer running Lync Server.

If you are performing a static server upgrade, use the following steps to migrate from Communications Server 2007 R2 Group Chat to Lync Server 2010, Group Chat.

1. Stop the Communications Server 2007 R2 Group Chat 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 Communications Server 2007 R2 server to a Lync Server pool by using the Microsoft Lync Server 2010, Group Chat Configuration tool. Do not restart the services.
   
   
4. If you perform a static upgrade, 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 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.
   
   

   Copy Code

   UPDATE [gcdatabase].[dbo].[tblConfig] SET [configContent] = '<configuration label="pool"> <pool> <serveredition>PE</serveredition> <serverlogin> <type>AUTH_MA7_OCS_MTLS</type> <port>0</port> <server>server.<domain>.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>domain\username</username> <uri>sip:username@<domain>.com</uri> </serverlogin> </lookupserver> <compliance> <filerepository> </filerepository> </compliance> </pool> </configuration>'

   Note:
   In this sample, the configLabel is pool and the configSeqID is the highest configSeqID. (The configLabel and configSeqID are column names in the table.  The configLabel is a string in the XML.)

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.
   
   If this step fails, do one of the following:
   
   
   • If you performed a swap upgrade, restore the database from the backup, and start Communications Server 2007 R2 Group Chat.
     
     
   • If you performed an in-place upgrade, follow the steps for installing Communications Server 2007 R2 Group Chat against an already patched database.
     
     
7. If you use the Compliance service, do the following:
   
   
   • 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.
     
     
   • Stop Lync Server 2010, Group Chat services.
     
     
   • Uninstall the Compliance Server.
     
     
   • Install the Lync Server 2010 Compliance Server.
     
     
   • Start Lync Server 2010, Group Chat services.