This chapter details how to stop and start the Manager.
Please remember that the Manager launches automatically
after install.
Before restarting a Manager:
 |
Send a message to the active users before stopping or
restarting the Manager. Simply click on the E-meetings
link from the administration pages. Look at the active
meetings and press the View button next
to them. From there, you may send a message to all active
users or to only those selected. |

Windows
The Marratech Manager can only be started and stopped
as a Service. Use the Start and Stop options from the Start
menu program group as pictured here:
 |
To install a Marratech Manager service, press
the Start Menu, Open the Marratech
Manager program group, select Service Administration
and Install as Service. |
Before uninstalling the Marratech Manager server,
remember to remove the service first. To do so, , press
the Start Menu, Open the Marratech Manager
program group, select Service Administration
and Uninstall Service.
To start, stop or restart the Manager, simply use the Start
service and Stop service shortcuts.

Mac
OS X
The Manager will start automatically when rebooting. Additionaly
you can start and stop the Manager using the shortcuts in
your setup folder.
To start and stop the Manager simply open the Marratech
Manager application folder: Since it is a server process,
your Administrator's password will be prompted.

To stop it, choose the Stop option.
If you wish to use the terminal:
- To start:
sudo SystemStarter start MarratechManager3.5
Linux
Choosing the automatic restart option during the installation
phase is recommended. In addition to the Manager starting
automatically when rebooting, you will be able to start
and stop the Manager using the System Starter in a UNIX
terminal:
/etc/init.d/MarratechManager start
/etc/init.d/MarratechManager stop
/etc/init.d/MarratechManager restart
To install
a the autostart feature manually simply run the InstallAutostart.sh
script as sudo from the bin directory.
Note that the command may be located at a different location
on your system and that the command name matches the node
name you assigned during installation.