You, as Administrator contact, are responsible for installing MathWorks® products along with the license manager on a central server on your network. This system is referred to as your license server. Users run MATLAB® on their own computers, called client systems, that are connected to the license server over a network. A computer running Windows® can act as a license server for Linux® or Mac OS X clients, and conversely. For instructions about installing MATLAB products on a license server, see the license manager installation instructions in the installation documentation.
In Network Concurrent User installations, you can install MATLAB and other products on a server and have client systems access products over the network, or you can install products on each client system. In this scenario, called a local access configuration, clients communicate with the server only when they check out a license key.
While a local access configuration can improve performance, it makes system administration more complex. For example, deploying a new version of MATLAB is easier when you only have to install it on a central server, rather than on multiple client computers.
Note When requesting your license, you must provide MathWorks with the host ID of the system (or systems) on which you intend to run the license manager.
To install MATLAB on client systems in your network, follow the instructions in the installation documentation. The following sections highlight some additional information about these installations.
When you install MathWorks products, the installation includes a utility program that can speed up MATLAB startup, called the MATLAB Startup Accelerator. By default, the installer configures this utility as a scheduled task on your computer that runs several times each day. (For information about changing this default behavior, see Install Without Configuring the MATLAB Startup Accelerator.)
In network configurations, the computer on which you install MathWorks products may not be the computer on which you (and others) use MathWorks products. For example, in remote access configurations, you install MathWorks products on a server and clients run MATLAB from the server over the network. In this scenario, clients could benefit from the startup accelerator, especially when starting MATLAB over the network, but the utility is not installed and configured on their computers.
To speed up MATLAB startup on client systems, MathWorks includes a second utility that can configure the MATLAB startup accelerator on computers where MathWorks products are not installed. The following section describes how to run this startup accelerator configuration utility on client systems.
To install the MATLAB Startup Accelerator on client systems in a network installation, follow this procedure.
Install MathWorks products on your server.
Distribute the network location of the startup accelerator
configuration utility to network clients. The startup accelerator
configuration utility is named
is located in the
matlabroot represents the MATLAB installation
folder on the server and
$ARCH represents a platform-specific
On each client system, run the startup accelerator configuration utility. This utility adds the MATLAB Startup Accelerator as a scheduled task on the client computer. By default, the task is scheduled to run at 8:00 a.m. and again at 1:00 p.m., but you can change this configuration using the Windows Task Scheduler. (For more information, see Configure the MATLAB Startup Accelerator on Client Systems.)
When you install MathWorks products, the installer
configures the MATLAB Startup Accelerator as a scheduled task
on your computer. If you prefer to install MathWorks products
without configuring the startup accelerator, use the
on the installer command line or in an installer input file. A sample
installer input file, named
is included in the top-level folder on the MathWorks product
DVD. You can customize this file to suit your needs.
For example, to install MathWorks products
without configuring the startup accelerator, run the installer and
createAccelTask option on the command
line, setting the value to
setup.exe -createAccelTask false