Lithnet Access Manager 2.0 reached end of life in November 2024 and is no longer supported
Upgrade to v3.1 to remain supported
Lithnet Documentation Hub
⌘Ctrlk
Main websiteEnterprise support quote
  • Home
  • Lithnet Access Manager
  • Lithnet Password Protection
Lithnet Documentation Hub
  • Home
  • What's new in Access Manager v2
  • How does Lithnet Access Manager help prevent lateral movement?
  • Access Manager Editions
  • Licensing
  • Change log
    • Getting started
    • System Requirements
    • Downloads
    • Upgrading from Access Manager v1
    • Installing the Access Manager Server
    • Installing the Access Manager Agent
    • Setting up Authentication
    • Deploying Features
    • Importing authorization rules
    • Frequently asked Questions
    • Troubleshooting
    • Quick start guides
    • Support Articles
      • KB000001: The Access Manager Agent cannot connect and logs a token-validation-failed error
      • KB000002: Users retain their admin rights after their JIT period expires
      • KB000003: Configuring the Access Manager Agent to manage an account other than 'root' on Linux
      • KB000004: Creating a log file to troubleshoot installation issues with the Access Manager Service
      • KB000005: Access Manager stops working after applying the November 2022 Windows update
      • KB000006: Migrating the Access Manager Database
      • KB000007: Adding JIT groups via Group Policy doesn't work with NTLM Disabled
      • KB000008: AMS is unable to JIT into privileged groups such as Domain Admins
    • Advanced help topics
    • PowerShell reference
    • Application help pages
    • Getting Support
Powered by GitBook
For the complete documentation index, see llms.txt. This page is also available as Markdown.
  1. Lithnet Access Manager
  2. v2.0
  3. Help and support

Support Articles

KB000001: The Access Manager Agent cannot connect and logs a token-validation-failed errorKB000002: Users retain their admin rights after their JIT period expiresKB000003: Configuring the Access Manager Agent to manage an account other than 'root' on LinuxKB000004: Creating a log file to troubleshoot installation issues with the Access Manager ServiceKB000005: Access Manager stops working after applying the November 2022 Windows updateKB000006: Migrating the Access Manager DatabaseKB000007: Adding JIT groups via Group Policy doesn't work with NTLM DisabledKB000008: AMS is unable to JIT into privileged groups such as Domain Admins
PreviousGetting started with Windows LAPS for Azure Active Directory
NextKB000001: The Access Manager Agent cannot connect and logs a token-validation-failed error

Last updated 4 years ago

x-twitterlinkedin