Migrating a XenApp 6.5 SQL Database
- Backup the Database (Using SQL Server Management Studio)
- Restore the Database on another server. Make sure that server is accessible (TCP/IP Pipies, SQL Browser Service, Firewall)
- Stop the IMA Service on the XenApp Server.
- Update the “C:\Program Files (x86)\Citrix\Independent Management Architecture\mf20.dsn” file on the XenApp server with the new Database Server hostname and instance name (eg. SERVER=Server1\SQLEXPRESS). You can use Notepad or the ODBC MMC to edit the file (Notepad is easier)
- Run “dsmaint recreatelhc” on the XenApp server to recreate the Local Host Cache.
- Start the IMA Service on the XenApp Server.
- The IMA service will not start if the value for ‘SERVER’ in the DSN file is incorrect.
- If the DSN file is correct but the IMA is not starting check the event log. If you’re getting an access denied error the username/password for the database might be incorrect, in which case you need to run the command below.
dsmaint config /user:domain\user /pwd:Password1 /dsn:"C:\program files (x86)\citrix\independent management architecture\mf20.dsn"
- If you create a new DSN file you need to run the ‘dsmaint config…’ command again pointing to the new file.
- After running the ‘dsmain config…’ command the DSN file doesn’t get updated with the new username (UID=admin.xen), the UID changes when you use ODBC MMC to change the DSN file.
- Make sure the Group Policy settings for the DSN file match the .dsn file. These can be set on each server locally (gpedit.msc) or via AD policies. The setting is under ‘Computer Configuration\Citrix Policies’