The JAMS Agent for Windows includes background services that execute JAMS Jobs under the direction of a JAMS Scheduler on a different machine.
Manually Installing the JAMS Agent for Windows
- To manually install the JAMS Windows agent, go to the JAMS Primary Engine (Scheduler) machine and navigate to the following path: Program Files\MVPSI\JAMS\Scheduler\Agents\Windows
- Once there, obtain either the SetupAgent.msi or SetupAgentx64.msi file and copy it to the remote Agent machine.
- From the remote agent machine, double-click to run the installer and follow the prompts. When the installation is complete you will see a Windows service called 'JAMS Agent' running.
- The installer package set up an agent service on the machine called 'JAMS Agent', and a directory is expanded containing the executable files in C:\program files\MVPSI\JAMS\Agent by default.
- The JAMS Agent service listens on port 77 in order to communicate with the JAMS Scheduler.
- The agent must then be defined in the JAMS Client.
- Select the Agents shortcut and click the Add button on the Ribbon bar to open the Agent Definition Wizard.
- Enter the appropriate information to define the agent.
 |
Note: the agent deployment is not necessary, leave the Deploy JAMS Agent box unchecked, as you have already performed a manual install of the agent. |
- It is recommended that the JAMS Agent Service run as 'Local System'.
Push Deploy the Windows Agent using Local User Accounts
When deploying a remote JAMS Agent to a Windows server, the standard practice is to use a domain account user with Administrator privileges on both the JAMS Primary Engine (Scheduler) and the remote JAMS Agent machine.
However, if you don’t have an environment that uses domain accounts, there are two alternative options for setting up the remote JAMS Agent software for a Windows server:
- Manually install the JAMS Agent for Windows (see the preceding section) or . . .
- Modify the registry setting changes on the Agent Machine. In order to allow the push deployment of the Windows JAMS Agent to a remote server when not using domain user accounts, make sure that the JAMS Primary Engine (Scheduler) and remote Agent server utilize the same administration level user account and password. Once that step is complete, perform the following registry edit on the remote agent machine:
 |
CAUTION: Improperly modifying the registry can harm your system. It is always recommended that you back up your registry prior to making any changes. |
- Browse to the following folder: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\
- Right-click a blank area in the right pane.
- Click New.
- Click DWORD Value and Name it LocalAccountTokenFilterPolicy.
- Double-click the item you just created and Type “1” into the Value Data box and click the OK button.
- Restart your computer.
You should now be able to push deploy the JAMS Agent to the remote machine.