Before installing Quickmap on a Terminal Server / Citrix server, you need to determine your space requirements, which will in turn effect the type of install that you do. If you have enough space on each Terminal Server for a Typical Install of Quickmap (highly recommended for performance reasons!), then you should do so (Plans, Aerials and other expansions can be installed in a separate storage location, discussed later). If you do not have enough space for a Typical Install, you can install a Typical Install on another machine, then perform a Minimal Install on each Terminal Server.
Next install any expansion packs you have on each Terminal Server. Some expansion packs take up a lot of space, so you may wish to install these on each Terminal Server, but keep the data on a central server (NAS or SAN), to be used via a network share. To do this, copy the data to the share, then run a Minimal Install on each Terminal Server.
After installing Quickmap on each Terminal Server, you need to copy Qmap.exe to a unique location for each user (such as the user’s profile or home directory). In the same location, create a folder called “Data” and copy QMap.mdb, Custom.mdb, QMapData.mdb. In the Data folder, create a folder called “Scratch” and copy Scratch.mdb into the Scratch folder. Finally, create a link that points to each users own copy of QMap.exe for the user to launch to start Quickmap. This step is required because these databases contain settings and personalisations unique to the user, which are shared by default. When you run QMap.exe, Quickmap detects the current working directory (the directory it was run from) and uses this to work out where those databases are. Each user running their own copy of the exe enables each user to only use their own copy of the databases for their personalisations.