Upgrading a Branch or the HQ from Exchange 2010 to Exchange 2013 or later (4330965)

We are upgrading a Branch from Exchange 2010 to 2013 or Exchange 2016/2019 that currently has QCS running and need to know what the process is to keep QCS working.

All steps should reflect the Location (one of the Branches or the HQ) that is being upgraded from Exchange 2007 to Exchange 2010 or later. This process will also work if you are upgrading from Exchange 2003 to 2010 or from Exchange 2010 to Exchange 2013 or later. 

Stop all three Quest Collaboration Services in the following order:
- Quest Collaboration Services Watchdog Service
- Quest Collaboration Services Synchronization Service
- Quest Collaboration Services Logging Service

1. Go into the Collaboration Services Mailbox and clean out all emails in the Inbox
2. Go to the <installedDirectory>\Program files\Quest Software\Collaboration Services\PacketHistory and Backup all files to another location and then delete all files. Or on 64 bit server go here \Program Files (x86)\Quest Software\Collaboration Services\PacketHistory
3. Then do a local move request and move all Stub Mailboxes from your 2007 Information store to a Exchange 2010 or later Database also move the Service account mailbox (It is recommended to keep all of the Stub mailboxes on the same Database.) Also, make sure all your AD objects stay in the same Quest Collaboration Services Objects container
4. Verify via Outlook or OWA that the moved Service account mailbox can send and receive mail to and from the partner service account mailbox
5. Ensure the Collaboration Services account is a member of the Organization Management AD group
6. Restart all 3 Quest Collaboration Services
7. From the Quest Collaboration services console:
   - Right click on the Collaboration services node in the Top left and select properties
   - Change the Exchange server to a new valid Exchange server (if necessary)
   - Click on the Test button and make sure it completes successfully and click OK
8. From the Quest Collaboration services console right click on the Collaboration services node in the Top left, select properties and then generate a new Key
9. Send the new key to all your Partners (Everyone that has subscribed to your publications)

10. Each partner that is subscribed to this location will need to apply the new key:
    - In the Quest Collaboration services console right click on the Collaboration services node in the Top left and select properties
    - If you are applying it to a Branch click on the Branches node and select Update Key and browse to the new key and click OK
    - If you are updating to the HQ select the HQ node and then select Update Key and browse to the key and click OK

11. If any of your subscriptions are a Calendar Synchronization, you will need to update Calendar information of the subscription as follows:
    - Expand Subscriptions
    - Right click on the subscription that is setup as a Calendar Synchronization and select properties
    - Select the Advanced Tab
    - Change the “Create an Exchange Mailbox” to the new server and to the new Database where the stub mailboxes should be created

12. Right click on all your collections and select Request Re-Publication for Everything

For more information on the permissions requried by QCS please see the following solution:
https://support.quest.com/SolutionDetail.aspx?id=SOL9801