What is the Maptitude remote desktop license and how should it be set up?

To convert your Maptitude license to the Remote Desktop license, you can purchase the Remote Conversion in our online store:

Remote Conversion

The Remote Conversion is just the difference in price between the two license options, $300 per license.

For the architecture of this version please see: http://www.caliper.com/Graphics/architecture.png 

The Maptitude Remote Desktop/Concurrent user license is only intended for users who intend to access the software through one of the following network options: VPN, Amazon Cloud, Terminal Services, Remote Desktop Services (RDS), or Citrix Server environments
If you do use remote desktop, then a remote license allows you to use Maptitude via remote desktop.
If you use Terminal Services or Citrix Server then one user at a time can access Maptitude via Terminal Services or Citrix Server: Additional concurrent/simultaneous users can be added to this license for US$995 per additional concurrent user.
If you use remote desktop into a Windows Server then one user at a time can access Maptitude via simultaneous remote connections: Additional concurrent/simultaneous users can be added to this license for US$995 per additional concurrent user.
Please note that there is no client-server version: Unless you have VPN, Amazon Cloud, Terminal Services, Citrix Server, or Remote Desktop Services (RDS) then you cannot remotely access Maptitude.
Please note that: Each Maptitude license can be installed and activated on a single computer. This includes the desktop/remote/concurrent/cloud licenses.
Please note that: The only Cloud version of Maptitude requires you to have an Amazon EC2 Microsoft Windows Instance*.
For concurrent-user licenses (including VPN, Amazon Cloud, Terminal Services**, or Citrix Server environments**), Maptitude allocates simultaneous users via RDP up to the number purchased for that license. Each remote or concurrent license is US$995 per concurrent user. If you have purchased the Single-User Desktop License, then the cost to convert this to a Single-User Remote License is US$300. 
== Bulk deployment for multiple users:  There is currently no “System Center” or equivalent package designed for bulk distribution/deployment of the software to multiple users/PCs.  However, the installer has an option to install and skip over the “activation” step, thus providing a complete, yet “inactive” installation. This can then be packaged and deployed to your end-users who, upon launching the software for the first time, will be prompted to supply their individual license number, thereby allowing them to request “activation” for their license. **We strongly recommend temporarily disabling the system’s anti-virus during the installation, as this is the most common cause of installation problems.
**Full administrative privileges are required to install and activate the Maptitude Mapping software.
You will need the product serial number and if prompted, an access code (supplied over the web or manually via the Activation Wizard).
The Installation media can be provided through an EXE download manager, a DVD, or an FTP or Sharefile site.
All of these options will provide the user with a collection of files and folders that contain the necessary information to install the Maptitude Mapping software and the data for the country pack chosen.
Included with the installation media are the “MaptitudeInstallation.exe”, which will install the software, and the “DataInstaller.exe”, which will install the data.  To install, simply run the executables.
The installer will detect if a version of the Microsoft Access database engine is installed, and if not, the 2010 version will be installed along with the Maptitude application.
Once the installation completes, the software will also need to be activated.  The activation is handled through a “Wizard”, which is a stand-alone application installed with he software.  The Activation Wizard allows for activation over the internet automatically, or by email.  The activation process will generate a license file that is written to the registry of the host computer.  This license file must be present for the software to run, and it is checked each time the software starts.
To install to an image:
From the extracted files launch MaptitudeInstallation.exe with the /BypassActivation command line switch, recording installation as you normally would. ***You can also install from a specific folder. Each installer accepts the /BypassActivation argument. The top-level installer will also install any data that came in your download.*** This installs Maptitude and the included data in the regular way, except it will not prompt for a serial number and it will not try to activate. This image can be copied to end-users machines. 
End-user activation: When a user launches Maptitude, it will say the software is not licensed, would you like to activate. Advise the user to choose “Yes” and enter their private serial number and activate the software.

Citrix Installations

Typically, a Citrix installation is performed by an IT Specialist or a system administrator, but this is not always the case.
There are no special installation instructions for installing Maptitude in a Citrix environment.
You will need the product serial number and if prompted, an access code (supplied over the web or manually via the Activation Wizard).
• Number of Maptitude Instances a Citrix Server can Support
The Citrix server should comply with the basic requirement provided by Citrix.
To determine the amount of RAM required for your Citrix server to serve Maptitude, multiply the base footprint by the number of concurrent Maptitude users. If the footprint is 100M and there are five (5) concurrent Maptitude users, then multiply 5 x 100M = 500M RAM required.
The previous calculation is an estimate, because Maptitude has many dependencies, such as the type of data in use and type and frequency of operations performed. Different operations may have different memory requirements; the following are the most memory intensive operations:

  • Running complex SQL statements
  • Editing and drawing objects
  •  Extensive labeling
• Use of Server Virtualization
Many IT organizations desire to virtualize all servers including Citrix XenApp servers. To date, virtualizing Citrix XenApp with Maptitude has resulted in mixed results in terms of performance and scalability. The lack of adequate performance in some deployments may be related to the size of the full Maptitude application coupled with the overhead associated with server virtualization. It is believed that particulars related to the target virtualized infrastructure are also a significant factor. Therefore, virtualizing Citrix XenApp servers should be approached with caution, particularly for industries with process and memory intensive applications, such as utilities.
It is recommended that prudent pilot testing be undertaken before deciding to move forward with server-virtualized Citrix XenApp servers running Maptitude.
• Use of Application Virtualization
Citrix XenApp provides two methods for delivering applications, session virtualization (also known as hosted sessions) and application virtualization (also known as application streaming).
• • Session virtualization represents the traditional and most popular method where a remote session is established and the application is executed remotely from a server. In this configuration, the application is installed onto the server in a manner similar to a typical desktop.
• • Application virtualization focuses on virtualizing the application itself. The application is ‘sequenced’ into a special format that prepares it for streaming to the client. The application, along with supporting registry information and other components, is essentially wrapped up into a customized file structure and served from a file server on demand. The application can be accessed by a Citrix XenApp server for delivery via a remote session or directly from a desktop client. However, deploying Maptitude as a virtualized application has been shown to be troublesome in terms of performance. Poor performance is often exhibited when performing tasks such as starting applications, where it can take minutes to start Maptitude. The exact cause is unknown, but is believed to be due to the large application footprint that results in large amounts of overhead as the application works between the isolated virtualized application environment and the host operating system. Therefore, at this time, using application virtualization with Maptitude is not considered a best practice.
• Recommended Guidelines
These are the recommended guidelines for Maptitude running on a Windows Server via Citrix or Terminal Services:
• Operating system: Windows Server 2012 R2, Server 2012 or Server 2008 R2
• Running Maptitude as a 64-bit application is required and requires 64-bit Windows in addition to Citrix
• A minimum of 2GB of memory per concurrent user is required, plus the operating system (16-32GB total)
• A multi-core processor with 4 or 8 cores is recommended but a faster clock speed is more important than additional cores
• Consider RAID or SSD for the speed benefits they will provide
• 1TB+ of storage is recommended  (this is highly subjective to the end user’s needs and should not be seen as a requirement)

Scroll to Top