Agent command line reference
This document provides a comprehensive reference to the command line interface (CLI) for the Lithnet Access Manager Agent. The agent supports different commands based on the operating system platform (Windows, macOS, or Linux).
Global Options
These options apply to all platforms:
--help
Shows help information for the command
--version
Shows version information
Core Commands
Service Management
Control the Access Manager Agent service:
Lithnet.AccessManager.Agent service <command>Available commands:
start
Start the Access Manager Agent service
stop
Stop the Access Manager Agent service
restart
Restart the Access Manager Agent service
Examples:
Lithnet.AccessManager.Agent service start
Lithnet.AccessManager.Agent service stop
Lithnet.AccessManager.Agent service restartAgent Management
Control the agent state:
Lithnet.AccessManager.Agent agent <command>Available commands:
enable
Enable the agent
disable
Disable the agent (sets the agent to a disabled state that persists across reboots)
Examples:
Lithnet.AccessManager.Agent agent enable
Lithnet.AccessManager.Agent agent disableConfiguration
Configure the agent:
Lithnet.AccessManager.Agent config [options]Available options:
--server <server>
Set the hostname of the AMS server
--port <port>
Set the HTTPS port for the AMS server (default is 443)
--registration-mode <mode>
Set the registration mode (iwa, key, or entra on Windows)
--registration-key <key>
Set the registration key (automatically sets mode to key)
Examples:
Lithnet.AccessManager.Agent config --server ams.example.com --port 443
Lithnet.AccessManager.Agent config --registration-mode iwa
Lithnet.AccessManager.Agent config --registration-mode key --registration-key YOUR-KEYNote: The
entraregistration mode is only available on Windows platforms. Setting a--registration-keyautomatically sets the registration mode tokey.
Setup Command
Interactive setup wizard to configure the agent:
Lithnet.AccessManager.Agent setupThis command will:
Prompt for server address
Prompt for registration mode
Collect additional information based on the selected mode
Apply the configuration and restart the service
Reset Command
Reset the agent configuration:
Lithnet.AccessManager.Agent reset [options]Available options:
--force
Skip confirmation prompt
--keep-cert
Keep the authentication certificate during reset
Examples:
Lithnet.AccessManager.Agent reset
Lithnet.AccessManager.Agent reset --force
Lithnet.AccessManager.Agent reset --keep-certShow Command
Display agent information:
Lithnet.AccessManager.Agent show <command>Available commands:
config
Display the current configuration settings
state
Display current agent state information
Examples:
Lithnet.AccessManager.Agent show config
Lithnet.AccessManager.Agent show statePlatform-Specific Commands
Linux Only
service install
Install the agent as a service (Linux only, non-packaged installs only, not required for DEB or RPM-based installations)
Example:
Lithnet.AccessManager.Agent service installmacOS Only
Secure Token Support
Manage secure token support for macOS:
Lithnet.AccessManager.Agent secure-token-support <command> [options]Available commands:
set
Set initial credentials for a managed admin account with secure token
get
Show information about accounts configured for secure token support
clear
Clear stored credentials for secure token support
Options for the set command:
--username <username>
The username of the account (required)
--password <password>
The password of the account (if omitted, you will be prompted)
Options for the clear command:
--username <username>
The specific account to clear (if omitted, all accounts are cleared)
Examples:
Lithnet.AccessManager.Agent secure-token-support set --username adminuser --password YOUR-PASSWORD
Lithnet.AccessManager.Agent secure-token-support set --username adminuser
Lithnet.AccessManager.Agent secure-token-support get
Lithnet.AccessManager.Agent secure-token-support clear
Lithnet.AccessManager.Agent secure-token-support clear --username adminuserRegistration Modes
The agent supports different registration modes depending on the platform:
iwa
Active Directory authentication (Integrated Windows Authentication/Negotiate)
All
key
AMS registration key authentication
All
entra
Microsoft Entra ID (formerly Azure AD) authentication
Windows only
Note: When using the
keymode, you must also provide a registration key. Setting--registration-keyautomatically sets the registration mode tokey.
Administration Requirements
Many commands require administrator rights:
Windows: Run Command Prompt or PowerShell as Administrator
macOS/Linux: Use sudo or run as root
Examples of Common Workflows
Initial Setup
Lithnet.AccessManager.Agent setupChanging Server Configuration
Lithnet.AccessManager.Agent config --server new-server.example.com --port 8443Resetting the Agent
Lithnet.AccessManager.Agent reset --forceViewing Current Configuration
Lithnet.AccessManager.Agent show configSetting Up macOS Secure Token Support
Lithnet.AccessManager.Agent secure-token-support set --username adminuserTroubleshooting
If you encounter issues:
Ensure you're running with administrator rights
Check the agent logs
Try using the
show statecommand to verify current agent stateTry resetting the agent with
reset --force
For additional help, consult the full Lithnet Access Manager documentation.
Last updated
Was this helpful?