To remedy the situation in task manager you can simply copy the existing executable to a set of new names:

copy sesame.exe sesame_1.exe
copy sesame.exe sesame_2.exe

etc...

and then running them in a meaningful order. You might consider naming them so as to include the base port number that server is meant to use:

copy sesame.exe sesame_20002.exe

etc...

To tell one admin window from another, I recommend arranging them on the screen in a particular order.

Also,

Just because you were interested, I just added a new command line argument to Sesame3, "-window_title <title>" that allows you to change the window title when launching Sesame.

They should be above 1024, below 65536, and unused by any other program you might consider running. Otherwise, simply use port numbers that will be easy to remember. You can assign them to environment variables, so you can call them by name rather than number, if that helps at all.

How many instances of Sesame server are you running?

When I start the second instance of Sesame on the server it only shows one client seat available instead of mirroring what the first server says is available.  They are both running from the same location, only the ports are different.  They can both see the license file because they are running from the exact same location.  Any ideas?

So, create directories and put sesame.exe and the LIC file in each one and start them from there?

E:\Sesame2\App1\Program\Sesame_app1.exe
E:\Sesame2\App2\Program\Sesame_app2.exe

Something like that?

To run the server one shortcut would be for example:
E:\Sesame2\App1\Program\Sesame_app1.exe -server machinename:port1:port2

Just to clarify a bit, it doesn't matter where the executable is located. What matters is the value of the "start in" environment variable (as set in the executable's icon - usually). The "start in" tells the executable what directory path to consider the current working directory. Looking at it from a command line perspective, if you issue a command to start an executable from a particular directory path:

c:\User\Cow\Example> c:\Programs\hello.exe

The "hello.exe" program will run believing that it is in the "\User\Cow\Example" directory, and look for its files there.

The same thing is accomplished with icons, by setting the "start in" value in the properties for that icon to "C:\User\Cow\Examples". In which case the executable is invoked from wherever it resides (in this case "c:\Programs") and runs in the "c:\User\Examples" directory.

So, no - you really don't have to copy the Sesame executable into any directories. You can leave it wherever you want it and simply make new Sesame icons that have different "start in" values.

Sesame will look for its license file in the current working directory, as set by the "start in" value. A license file must reside in whatever "start in" directories you specify.

While we have always given a wink to those that would copy our license file so as to connect more clients than they have purchased, we do appreciate it if you purchase additional licenses for any additional clients over and above your current license.