8.7 Starting a Windows server from the graphical user interface
You can start a Windows server from the graphical user interface.
To configure and start the floating license server software on a Windows
server using the graphical user interface:
If you are adding a new license to a system with a running floating license
server, you must stop the server, point the server to the new license file, then restart the
server. If this is not done, the new license information might not be recognized by the
license daemons. Arm® does not
recommend the use of the
On the Server/License File tab,
select the Configuration using Services option, as
the figure shows.
8-1 Selecting Configuration using Services
Click the Config Services tab to
display the dialog as the following figure shows. This example shows the dialog with
typical paths entered.
8-2 Server setup dialog
Enter the paths that specify the required files, or click the browse
buttons to locate and select the files. You must specify paths for the following:
Executable file lmgrd.exe.
License file license.dat.
Log file, which is debug.log in this example.
Note: The server log file can become very large, so it might be
necessary for you to control its size.
If you require the server software to start running automatically when
the server computer is turned on:
Select the Use Services
Select the Start Server at Power
Click Save Service.
At the prompt, confirm saving the FlexNet License Manager
Click the Start/Stop/Reread tab,
and ensure that the FlexNet License Manager service is selected.
Click Start Server to start
running the floating license server software.
Check whether the floating license server started successfully:
Click the Server Status
Click Perform Status
The status information shows that the floating license server and
vendor daemon are both UP, followed by a licensed feature usage list. Any floating
license server errors are shown in the status information.
After you have started the floating license server, you can use a text
editor, such as Notepad, to inspect the server debug log file.