[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3724
  • Last Modified:

Move datastore to a new server

I have a Citrix Metaframe XP 1.0 environment running Windows 2000 server. I need to replace my server that is running my MS Access datastore. The new server will have the same IP address and same name. Do I just need to restore my "Independant Management Architecture" folder to the new server along with the HKLM/Software/Citrix registry key or is it a little more involved? Also, during the install of Citrix it asks where the datastore is, do I just point the server to itself?

Thank you for any help you can provide.
1 Solution
There's a couple more steps to it than that.  See this document: http://support.citrix.com/article/CTX677542&searchID=10806140

Here's the steps you basically need:

Access Databases

To move or restore an Access data store

Follow this procedure to install a backup of the data store or move an original data store to a new host server in the event of a hardware failure or upgrade:

1. Copy the backup database or the original database to the server that is to become the new host server.

2. On the new host server, create a new “File DSN” pointing to the new local database from Step 1.

3. On all servers in the farm, execute dsmaint failover to point to the new host server.

Note: The IMA Service must be running on these servers for the command to execute properly. You must do this before executing dsmaint config on the new host server as specified in the next step; otherwise the other servers in the farm cannot write to the database.

4. On the new host server, execute dsmaint config to point the IMA Service to the newly created DSN file from Step 2. If no security was set on the Access database, use the default user account and password information (citrix/citrix).

Note: Include the full path (in quotes) in the /dsn: switch to the file dsn. For example, /dsn:"C:\Program Files\Citrix\Independent Management Architecture\MF20.dsn"

WARNING! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

5. Change the original host server to its new role as an indirect server (it will now access the data store indirectly through the new host server) by running the Registry Editor (Regedt32.exe) and changing the value of the following registry key from Imaaccess.dll to Imaodbc.dll:


Note: If you are performing these steps with a MetaFrame XP Feature Release 3 farm, the previous step is no longer necessary. With a MetaFrame XP Feature Release 3 server, running the command dsmaint failover new_direct_servername on the original host server removes the value in the registry. Feature Release 3 no longer uses the value Imaodbc.dll for indirect servers.

6. Stop and restart the IMA Service on the new host server.

7. When the IMA Service on the new host server is running, stop and restart the IMA Service on all of the other servers in the farm.

Important: Restarting the IMA Service instead of restarting the server might cause the SNMP service to Dr. Watson if SNMP is enabled. This error is benign.

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now