Move SQL datastore from one server to another

Website Visitors:

How to Move a Microsoft SQL Server Desktop Engine Data Store From One Server to Another


This article describes how to move a Microsoft SQL Server Desktop Engine (MSDE) data store from one server to another.


The steps involved in moving an MSDE data store from one server to another is similar to those used for an Access database.

A step-by-step process is detailed below.

  • Server 1 is the old server

  • Server 2 is the new host for the data store

It is necessary to install MSDE from the Citrix Presentation Server CD-ROM, in the folder \Support\MSDE\setupmsdeforMetaFrame.cmd.

Note: Citrix does not recommend installing MSDE on an existing Presentation Server installation.


  • On server 1, run dsmaint backup <destination_path>. <destination_path> - The destination for the backup copy of the Data Store database. The path can refer to a network share point for Access but not for MSDE.

  • Refer to article CTX104005 – How to Modify the IMA Data Key to Match the Hex Value in the Data Store to gather the value of the Data key in HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Data.

  • On all the indirect servers in the farm, run the command dsmaint failover to point them to the new Data Store server. This action is similar to Access Data Store and is explained in the article CTX677542 – Advanced Concepts - XenApp Farm Maintenance.

  • On server 2, run chfarm and create a new farm using the same name as the existing one in the MSDE database.

  • Copy the backup file MF20.dat created in step 1 to the server 2 hard drive.

  • On server 2, stop the IMA service and run dsmaint recover**[<Source_path\Database_to_recover>]** pointing to the MF20.dat copied in step 5.

  • Recreate the LHC on server 2 with the command dsmaint recreatelhc. For more information, on this command, refer to CTX759510 – Function of the Local Host Cache.

  • On Server 2, make sure the Data key value in HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Data matches the one gathered in step 2.

  • Restart the IMA Service on server 2.

Want to learn more on Citrix Automations and solutions???

Subscribe to get our latest content by email.

If you like our content, please support us by sponsoring on GitHub below: