Large-Scale Deployment Guide
Abstract
This document provides complete information about how to customize and administer largescale deployments of MindManager. Topics include:
Mindjet MindManager components
Understanding large-scale deployment strategies
Deploying MindManager using the installation wizard or from the command lin
Contents
Abstract ........................................................................................................ ii
Contents ...................................................................................................... iii
List of Tables ...........................................
Dictionaries ............................................................................................... 11
Tutorials ..................................................................................................... 11
PDF-XChange .............................................................
Deploying with Windows Server ...................................................45
Deploying with Citrix Presentation Server ............................................... 48
Basic Installation for the Citrix Desktop ..................................................... 48
Advanced Installation of
List of Tables
Table 1: System Requirements for MindManager
1
Table 2: Configuration Files 12
Table 3: Location of Shared System Components
Table 4: Third-Party Software Overview
13
14
Table 5: MindManager Registry Key Overview
18
Table 6: Remaining Files, Folders, and Software components
Tab
About This Guide
Many Mindjet customers have requested support for customized deployment of MindManager to
large numbers of client machines. The Admin MSI supports the following options:
Running the standard setup manually or automatically
Running the admin setup manually or automatically
Deploying
System Requirements
The following are the hardware and software requirements for MindManager:
Table 1: System Requirements for MindManager
SYSTEM
REQUIREMENTS:
IBM or
compatible
Pentium®
processor (1
GHz or
greater)
SUPPORTED OPERATING
SYSTEMS:
1 GB RAM or
greater
Microsoft® WindowsÂ
For deploying Mindjet MindManager in a terminal server environment, the following are
prerequisites:
Windows Server 2008 running Terminal Services
or
Citrix MetaFrame Presentation Server 4.5 and above 32-bit , or XenApp 6 64-bit
When using this method, each client machine must also meet the s
Understanding Deployment Strategies
This section describes different deployment strategies, including their basic technologies,
advantages, limitations and their level of support.
Running the Standard Setup Manually or Automatically
You can deploy MindManager on a machine-by-machine basis using the
The installer is not cached on the client machine, reducing the required disk space
And these disadvantages:
Access to the original installer is required for repair and other setup operations
Deploying MindManager with Active Directory
This method is not yet fully supported. Due to the application
It takes time to create the custom setup
The installed software uses up disk space on each user's system
Deploying MindManager on a Shared Network Drive
Mindjet does not support installing MindManager on a shared network drive and having users
run it directly from there.
Mindjet MindManager Large
Using the Admin Setup
The MindManager Admin setup gives systems administrators more control over an installation.
It is distributed in a .zip archive file that contains the following files:
Mindjet MindManager Admin.msi
dotnetfx35setup.exe
instmsi30.exe
msxml6_x86.msi
vcredist_2005_sp1_x86.exe
vcred
Required Software
All required software is in included in the Admin setup package. It contains some software
which must be installed on your system before using the setup. You should verify that this
software is already installed on your system, and if not, install it from the admin package.
dotnetf
Differences between the Standard and Admin Setups
The MindManager Admin setup is based on the standard setup with a number of important
differences:
Caching: The admin setup does not cache the setup on the computer where it is being
installed. Instead the setup should be run from a network location
Administrator privileges are required to install any Windows software, including MindManager.
Per-user setup
Each time MindManager launches; it checks the UserData.ini file, located in:
C:\Documents and Settings\\Local
Settings\Application Data\Mindjet\MindManager\
to see if a per-user setup needs
What Gets Installed
The MindManager Admin setup installs:
Required program files
Configurable MindManager Components
Shortcuts and Start Menu items
Third-party add-ins or components
Shared system software
Registry keys
The default location for required program files is:
C:\Program Files\Mindjet\Mind
MindManager Components
MindManager installs a variety of configurable components, including:
Library
Dictionary
Tutorials
PDF-XChange
User configuration files are also installed to help govern their behavior.
Library
The Library component consists of two sub-components: Images and the Template Orga
C:\Program Files\Mindjet\MindManager\
You can customize your tutorial installation by choosing:
To deploy them to a server, rather than installing them on local machines
To not deploy tutorials at all
To customize tutorial installation, see Deploying User Data, the Library, and Tutorials from the
Co
File Name
Library.ini
Location and Function
C:\Documents and Settings\\Local
Settings\Application Data\Mindjet\
MindManager\\Library\
This file detects the library installation time. Because
MindManager installs the library the first time it gets
launched, this file prevents multiple library
instal
Folders and Files
Component
InkEd.dll
PipRes.dll*
wisptis.exe
* These components are installed only on Tablet PCs.
C++ runtime libraries
%WINDIR%\system32
msvcp60.dll
msvcp80.dll
For a complete list of these merge modules'
components, see Microsoft's documentation
Environment variable name
Description and Vendor
Third-Party Software
ChartFX.ClientServer.core.dll
Chart FX Client Server ActiveX Control is
used with spread-sheets to create bar charts
Software FX, Inc.
dunzip32.dll
DynaZIP-32 Multi-Threading UnZIP DLL
Inner Media, Inc.
dzip32.dll
DynaZIP-32 Multi-Threading ZIP
Third-Party Software
Mfc80.dll
Description and Vendor
Microsoft Foundation Classes, wrap Windows
APIs in C++ libraries, forming application
framework
Other components are associated with this
.dll. See Microsoft's documentation for
complete information.
Microsoft
msvci70.dll
Microsoft C++ Run
Description and Vendor
Third-Party Software
Sfxfe32.exe
A 32-bit active delivery self-extracting front
end zip executable.
Inner Media, Inc.
Spr32du70.dll
FarPoint Spreadsheet Control
FarPoint Technologies, Inc.
Ssce5532.dll
Spell checker engine
Wintertree Software, Inc.
TER32MM.DLL
R
To not install the JRE, simply remove the installer's "MMPlayerExport" Feature at install time. To
re-enable MindManager Viewer functionality and install the JRE, add the "MMPlayerExport"
Feature back in. See "Sample Customized Installation Using ADDLOCAL and REMOVE" for
more detailed instructions.
Location/Key
Key Type
Mindjet.MindManager.MapMarkerSet.x
MMindjet.MindManager.MapPart.x
Mindjet.MindManager.Style.x
Mindjet.Mm5GenericSmartMapPart.AddIn
Mindjet.Mm5GenericSmartMapPart.AddIn.x
Mindjet.Mm5Sort.AddIn
Mindjet.Mm5Sort.AddIn.x
Mindjet.Mm5WebExpor
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersio
n\Uninstall
The name of the sub-key is the Globally Unique Identifier (GUID) for the program (which
changes with each release). You can find it by using RegEdit to search for "MindManager" in the
Uninstall key. The uninstallation key does n
What Remains After Uninstallation
When you uninstall MindManager, almost all traces of the application are removed, including all
components located at C:\Program Files\Mindjet\MindManager (except for PDF-XChange
program files). Most registry keys get removed as well. Map files (.mmp and .mmap files
Location and Explanation
Component
Ink related files
See Shared System Components for locations.
These files may be in use by other applications.
MMXRegistryBackup_
_
msvcp60.dll
C:\MyDocuments\
Opening this file gives you the option to add its
contents to your current registry.
%WINDIR%\system
Location and Explanation
Registry Key
HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE\SOFTWARE\Mindjet\MindMa
nager\\Installer\
This key and those below it are left behind for the
installer.
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
23
Deploying with the Installation Wizard
Using the admin setup to install MindManager is straightforward and simple. Unlike the basic
setup, you have customization options, though not as many as from the command line.
Starting the Installation
To install MindManager:
1. Launch the installer.
2. At th
At this point you can customize your deployment or complete the installation.
Customizing the Installation
A custom installation allows you to:
Disable default features
Change the default installation directory
Deploy user data and the library on a separate server
If you need to customize the insta
10. Select the desired feature setting.
For each selected feature, a description and storage requirement appears.
11. Repeat this process until you have made all of your feature customization
choices.
12. Complete the installation as outlined in Completing the Installation.
Changing the Default In
15. Click Change.
The Change Current Destination Folder dialog appears.
16. Select the destination folder.
17. Click OK.
The new destination folder appears in the Custom Setup dialog.
18. Complete the installation as outlined in Completing the Installation.
Deploying User Data and the Library to a
C:\Documents and Settings\UserName\Local
Settings\Application
Data\Mindjet\MindManager\\Library\
where UserName is the current user's logon name.
You can store user data and the library in a network folder for various reasons in order to:
Save space on users' systems
Decrease the time required to ru
22. Click Browse.
The Browse for Folder dialog appears.
23. Select the destination folder.
24. Click OK.
The new directory appears in the Server base path field.
25. Choose from the following options:
Extract library to the server path the first time MindManager starts
Use Separate folders per us
Deploying from the Command Line
While you may wish to customize your MindManager deployment from the installer interface , you
have much greater control over the installation from the command line, including:
Configuring installation parameters
Specifying what to install on a feature by feature basi
Description of Values
Parameter
ISX_SERIALNUM
Specifies the license key for your MindManager
installation. Note: No validation is performed for this
key, it is simply written to the registry. If the license
key is not valid, MindManager runs in a restricted
(trial) mode.
USERNAME
Specifies the U
Tip
Here are examples of adding and removing features through the setup.exe file,
using silent install:
Adding: \setup.exe /v"ADDLOCAL=\"MSWordAddin\" /qn"
Removing: \setup.exe /v"ADDLOCAL=\"ALL\"
"REMOVE=\"MSWordAddin\" /qn"
You can also string together multiple features for inclusion or removal:
\
msiexec /i "\filename.msi" ADDLOCAL="ALL"
REMOVE="MSWordAddin,PDFWriter,RSS" /qn
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
33
Table 9: Configuring Features with MSI from the Command Line
Comments
Feature
Library
Available add-ins
The default add-in is Library, which installs add-ins
below. You can also specify a subset.
Images
Shapes
BackgroundImages
Icons
ImageGallery
Icons
TemplateOrganizer
Templates
WebTemp
Comments
Feature
Microsoft Add-Ins
Available add-ins
The MSAddins feature is a container for the following
Microsoft-related add-ins. Any or all of these subfeatures can be all installed by specifying them on the
command line. Examples below will clarify this.
MSWordAddin
MSOutlookLinkerAddin
MSO
Comments
Feature
above.
PDF Writer
The add-in is PDFWriter
Example:
msiexec /i "\filename.msi"
ADDLOCAL="ALL" REMOVE="PDFWriter" /qn
RSS
The add-in is RSS
Example:
msiexec /i "\filename.msi"
ADDLOCAL="ALL" REMOVE="RSS" /qn
Configuring Functions from the Command Line
During installation, you c
Functions
Online Help
Examples
/v"INTERNETACCESS=0 /qn"
The function name is ONLINEHELP.
Example (msi):
msiexec /i "\Mindjet
MindManager Admin.msi" /qn
ONLINEHELP="0"
Example (setup.exe):
\setup.exe /s /v"ONLINEHELP=0
/qn"
UI Customization
The function name is UICUSTOMIZATION.
Example (msi):
m
Examples
Functions
Internet Access
The registry key is InternetConnectionEnabled.
Example:
HKEY_LOCAL_MACHINE\Software\Mindjet\MindMa
nager\\Settings
"InternetConnectionEnabled" (0)
Online Help
The registry key is OnlineHelpEnabled.
Example:
HKEY_LOCAL_MACHINE\Software\Mindjet\MindMa
nager\\Set
Deploying User Data and the Library
As discussed in Deploying User Data and the Library to a Server , you may want to deploy user data
and the library to a server. If you want to deploy the user data and library on separate servers,
you must do so from the command line or by editing the registry.
D
Command
LIBRARIESPERUSERPATH="1
"
Resulting Registry Entry
Deploy libraries in a per-user folder.
1=Enable
0=Disable
HKEY_LOCAL_MACHINE\Software\Mindjet\Mind
Manager\\Installer
"LSDLibraryPerUser" (1)
LIBRARIESPATHSUFFIX=""
This folder is appended to the per-user folder.
HKEY_LOCAL_MACHINE\Softwa
Table 14: User Data Registry Key Values
Data Value
Registry Value
LSDUserDataPath
See "Server base path", above.
Examples:
N:\User Data\All
Users\Mindjet\MindManager\
or
N:\User Data (if LSDUserDataPerUser is
set to 1)
LSDUserDataPerUser
0 = Do not use separate folders per user
1 = Do use separ
"LSDLibraryExtract"=dword:0000001
Sample Setup Commands
The following sections provide sample commands in order to demonstrate various installation
scenarios.
Simple Installation
This command simply runs the installer in the usual interactive mode.
Msiexec.exe /i "Mindjet MindManager Admin.msi"
Y
Uninstallation
This command uninstalls MindManager: Msiexec.exe /x "Mindjet MindManager
Admin.msi"
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
43
Deploying with Active Directory
Deploying MindManager via Active Directory and Group policies is has limited supported at this
time because:
MindManager setup only supports Computer-based software installation
Some MindManager properties can only be configured from the command line
You can use confi
Property
USERDATAPERUSERPATH=0/1
Description/Default Setting
User Data deployed per user
Default=1
MACROUI=1/0
Enable Macros in UI
Default=1
ONLINEHELP=1/0
Enable online help
Default=1
REBOOTISREQUIRED=No/Yes
Require reboot after installation
Default=No
TOPICALERTSLINKER=1/0
Enable
Deploying with Windows Server
You can install MindManager with Windows Server 2003 running Terminal Services and then
deploy it to variety of client machines.
To install MindManager on a Windows Server 2003 running Windows Terminal Services
(WTS):
1. Log on to the Windows Terminal Server as an admin
15. Please make sure to finish the Admin Install wizard of the Windows Terminal Server by
clicking the Finish or Cancel button. DO NOT START MINDMANAGER BEFORE THIS
DIALOG IS FINISHED!
You can now run MindManager on the server with the Windows Remote Desktop Connection
client.
MindManager runs in f
Deploying with Citrix Presentation Server
The Citrix MetaFrame Presentation Server is a sophisticated terminal server environment built on
top of the Windows Terminal Services provided by Windows Server. This is currently the only
tested and supported Citrix platform for MindManager, though other co
i.
4. In the tree, select Applications.
i.
5. Right-click Applications.
6. Select Publish Applications. (The Application Publishing Wizard appears).
i.
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
49
7. Specify what to publish.
i.
8. Define the Program Neighborhood Settings.
9.
10. Define the Application Appearance options. (Set to High Color or True Color).
i.
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
50
11. Specify special client requirements. (Default settings are fine).
i.
12. Specify the number of licenses you have purchased in the "Maximum instances" field.
i.
13. Specify which servers will deploy MindManager.
i.
14. Specify users. (We recommend doing this by group to ease adding single user
i.
15. Leave the File Type Associations page empty; MindManager is registered on the server.
i.
ii. Once you are done, you should see the MindManager application in the
Applications section:
iii.
iv. The MindManager icon now appears in authorized users' Citrix Program
Neighborhood.
Mindjet MindMan
16.
17. For more configuration options, please consult your Citrix documentation.
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
53
Administering MindManager
There are other administrative issues involved in deploying MindManager on a large scale. You
can address many of them using administrative tools and methods described below.
Managing Add-Ins
MindManager uses a number of add-in DLLs. The Add-Ins are automatically registere
The Registry Add-In List
The list of add-ins that MindManager loads at startup is in the Registry at:
HKEY_LOCAL_MACHINE\SOFTWARE\Mindjet\MindManager\\AddIns
Removing or Restoring Add-Ins from the Registry
To remove a MindManager add-in (i.e. make it "invisible" to MindManager) delete its registry
To remove the Word add-in, delete the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Mindjet\MindManager\x\AddIns\Mi
ndjet.MmWord.AddIn.x
This makes the add-in "invisible" to MindManager so it will not be loaded on program startup
and will not be seen in the list of add-ins in the Tools -> Add-Ins dialo
If it does not exist, MindManager copies the LoadBehavior value from the
HKEY_LOCAL_MACHINE subkey to the HKEY_CURRENT_USER subkey and then uses that
value.
Mindjet MindManager Large Scale Deployment Guide
Version 10.0.1
September 13, 2011
57
Therefore, to disable an add-in for the current user, set the LoadBehavior value in the
HKEY_CURRENT_USER subkey to 0.
To disable the add-in for all new users, set the LoadBehavior value in the
HKEY_LOCAL_MACHINE subkey to 0.
Note: This has no effect on users that have already run MindManager at lea
Note that Word handles the Tools -> "COM Add-Ins" command and user interface differently
than MindManager. In Word, if an add-in is registered in HKEY_LOCAL_MACHINE (HKLM),
then it is not displayed in the COM Add-Ins dialog. If an add-in is registered in
HKEY_CURRENT_USER (HKCU), it is displayed in
Table 17: HKEY_LOCAL_MACHINE Settings
Value Name
LocalUserDataDirectory
Type
REG_SZ
Value Data
Path to copy user data files (e.g. Image
Library files, etc.)at first launch. May contain
environment variables. For example:
N:\UserData\%USERNAME%\MindManager
If no path is specified, then this path
DisableAnimation
REG_DWORD 0 to allow animation of maps for smoother
scrolling.
1 to disable animation of maps for one-jump
scrolling which is less graphics intensive and
perhaps more desirable in a low-bandwidth
Windows Terminal Server environment.
LocalUserDataDirectory
REG_SZ
Path to copy use
When Fired
Event Name
OnFirstUse
Just before we install "per-user data"
OnBuyButtonPressed
Just before the "Buy MindManager" dialog is displayed
When a macro event is fired, 0 or more macros are run. The mapping of macro event names to
macro filenames is determined on startup.
On startup, Mind
EventMacro_OnApplicationStarted.mmbas
Therefore, it is possible to get macro events to run a macro simply by putting macros with the
proper name in the user's macro folder. However, for most typical IT uses, the "Event Macros"
key will be used since this can point to macros on some network drive, fo
Managing User Licenses
Each MindManager user must have a license. Please contact your reseller or Mindjet sales
representative for licensing terms appropriate for Large-Scale Deployment. MindManager does
not include any special support for proprietary third-party license management software.
MindMan
Optional silent install argument:
SITECONNECTIONFILE=full_path_to_custom_site_connection_file
This file can have any name but must be reachable from install-to machine
This file is copied to "SiteConnections.xml" in the MMD INSTALLDIR
Note: This argument will have no operational effect when MindMana
