The following files make up the OS X license server installation:

hlserver 

This is the server application.

hlmanager 

This is the manager application. See The Manager chapter for details.

hlserver.conf 

The contents of this file, explained in detail in the Server Config chapter, controls the behavior of the server.

hlserver.log 

This is a series of date stamped log messages from the server showing, amongst other things, who is grabbing which licenses.

setup 

Installation script.

uninstall 

Remove service daemon and all files.

unload 

Unload service daemon, but leave all the files intact.

reload 

Restart the service daemon.

keys.txt 

This file holds the floating license keys. Was called .keys in earlier versions.

[edit] Setup v2

Double click the setup script to start the installation.

First you will be asked where you want to install the hlserver files, so just tap the Enter key here to accept the default ...

If prompted, type in your password for sudo access.

Installation location (/usr/local/hlserver) ?

Next you will most likely be asked for your password for sudo access; this is so the install folder can be created and the service daemon started ...

sudo mkdir -p /usr/local/hlserver
Password:
sudo chown architec /usr/local/hlserver
sudo cp com.headus.hlserver.plist /Library/LaunchDaemons
sudo chown root /Library/LaunchDaemons/com.headus.hlserver.plist
sudo chmod 644 /Library/LaunchDaemons/com.headus.hlserver.plist
cp -f hlmanager hlserver hlserver.conf .keys /usr/local/hlserver
sudo launchctl unload /Library/LaunchDaemons/com.headus.hlserver.plist
sudo rm -f /tmp/hlserver.pid
sudo launchctl load /Library/LaunchDaemons/com.headus.hlserver.plist

After that, the setup script will wait for the service to start up, and then runs the hlmanager command ...

Waiting for HLServer to start ... 10 9 8
Trying HLManager ...
Trying architec@localhost ... Connected ... Fetching ...

Once hlmanager is connected, you will see something like this ...

Server v2.00 localhost up 00:00

  Your login has been added automatically to
  the hlserver.conf file for Manager access.
  If you want to add Manager access for other
  users, you will need to edit that file on
  the server.

----------------------------------------------

  No valid floating licenses found. Please
  email the following code to your vendor so
  new license keys can be generated.

  RF55 RDH4 WGA4 9P2D XECG F530 2MHX 9ZST

  Copy of above code: '/tmp/hlmanager-code.txt'

  If you've already received your license keys,
  now use the "add" command to append one at
  a time to the keys file on the server.

So email that code to your vendor to get your license keys.

Once you have some keys, re-run hlmanager and use the 'add' command to append them to the keys file on the server. You should see something like this once the keys have been added.

> add
Enter key string below ...
FMWM 6N8S 0BPS 4FXP K4GL W7H7 6JFY R8B4 8NDB JP3A
Sending key to server ...
Updating status ...
Server v2.00 localhost up 00:05
<--------- Licenses ---------->
Name        Status    Free Used
uvlayoutv2  29 days      4    0

Users should now be able to access the license server from others systems on the local network.

hlserver will be automatically restarted whenever the system is rebooted, and you can stop and start it via the launchctl command.

We recommend you keep a copy of the hlmanager command, but the rest of the contents of that extracted hlserver folder can now be deleted.

[edit] Setup v1

Double click the setup script to start the installation.

1. First you'll be asked to check the config file. The "GROUP lan" IP range will have been set already to match your local network, but this may need to be adjusted if you have a more complicated setup (e.g. multiple sub-nets in a larger campus network). Save the file, kill the window, then re-run the setup script to continue.
   
   
2. Initially you wont have license keys, so at the "Do you have the keys" question type n followed by Enter to generate the code strings. Email the 5 code strings to your vendor to get your license keys.
   
   
3. When you get your license keys, re-run the setup script and answer y to the "Do you have the keys" question, then type Enter to continue and the keys file will open up in the text editor. Cut'n'paste your license keys in, save the file, kill the window, then re-run the setup script to continue.
   
   
4. At the "Do you have updated license keys" question, answer n and then you'll be asked for an installation location. By default the script will want to put the binaries and config files into /usr/local/hlserver, but you can type in a different path at the prompt if you wish.

If the setup script runs smoothly, hlserver will be started and hlmanager is run as a final check. You should see something like the following as output ...

 Waiting for HLServer to start ... 10 9 8 
 Trying HLManager ...
 Trying architec@localhost ...
 Server localhost up 4 seconds
 <--------- Licenses ---------->  <------------------------- Users ------------------------->
 Name        Status    Free Used  Id Hostname        User     App           Age       Idle   
 uvlayoutv2  29 days      4    0

hlserver will be automatically restarted whenever the system is rebooted, and you can stop and start it via the launchctl command.

We recommend that you keep the hlserver folder in case you need to re-run the setup script. It can be moved if you dont want to leave it on your Desktop or in the Downloads folder.

[edit] Update

If you need to update your keys file (e.g. replacing temp keys with permanent ones) then re-run the setup script and answer y to the "Do you have updated keys" question. Type Enter to edit the keys file, cut'n'paste in the new keys, then save the file, kill the window, and re-run the setup script to restart HLServer and check the results with HLManager.