=== Installing AgentMax on a Terminal Server Handling Multiple ACCAMs === The administrator should do the following: 1) Install AgentMax normally on the terminal server, only once. 2) It is not necessary to activate this master copy under any ACCAM after installing, but you may do so if you like. Probably only the administrator will use this copy. (Currently, anyone can receive application updates on behalf of everyone, but we might decide it is better to update only from this master instance.) 3) Delete the AgentMax2 shortcut that the installer created under the Startup folder in the Start Menu. 4) Make a copy of the “Start AgentMax 2.0” shortcut created by installer in the AgentMax folder. 5) Open the copied shortcut properties and add a command-line option to the end of the Target box. The command-line option is: /Terminal TermName “TermName” can be anything you like, such as T1, the branch name, or the ACCAM number, but it can’t include special characters or blanks. Do include a space before the slash and between the two words. 6) Make a copy of this shortcut for each branch, and change the shortcut name and the TermName setting to a different name and word for each branch. 7) Open AgentMax once from each shortcut, and enter the ACCAM and Activation Code for that TermName, then shut it down (File menu). Note that you can’t open AgentMax multiple times in the same Windows session. You must shut down the previous instance each time before starting a new one. If you don't, the second instance will just shut itself down immediately. 8) Give each user the appropriate shortcut for his branch. A user can be given multiple shortcuts, but again, only one instance will run at the same time in each user's session, so explain this to them. === Explanation === When AgentMax.exe is started with the new “/Terminal xxx” command-line option (Terminal is not case-sensitive), it does two things differently (assuming the default install folder C:\AgentMax2): 1) It creates or connects to a folder named “xxx” within a new folder named “C:\AgentMax2\Terminals” (which it creates automatically). Each “xxx” folder contains its own independent copy of subfolders Booking, Config, Product, Terminal, and Users. These normally all reside in the “C:\AgentMax2\Data” folder. 2) It pretends in all communication with our servers that its Computer Name is actually “ServerName.TermName” rather than just “ServerName”. Thus, each folder is handled independently by our servers, rather than confusing them all together and changing the ACCAM number of all of them if any of them changes. === Notes === As before, if "Continuous Login" is permitted by the agency, AgentMax will reconnect each user to the same AgentMax Agent Account each time they login. But now, each TermName will remember the previous login of each user separately. Recall that the Agent Account that users login to AgentMax with is independently defined under each ACCAM, so they will need to have multiple AgentMax Agent Accounts in this case. Note that the “C:\AgentMax2\Data\Bin” folder, which contains some common help files and such, is not replicated into the Terminals subfolders. Neither is the “C:\AgentMax2\Data\Logs” folder. Application logging for all terminals is stored in the common “C:\AgentMax2\Data\Logs” folder, rather than under the Terminals subfolders. Since log file names include the logged-in Windows user name and the date, each user's logs is kept separate. But if the same user is logged into AgentMax twice, using two distinct terminal sessions, whether on the same or different ACCAMs, then his log file will contain interleaved lines from both of his sessions. Each line includes a Terminal ID number, so we can tease them apart for debugging.