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 AdminsKB000009: Access Manager may return an out-of-date LAPS password, or no password at allKB000010: The Access Manager agents fail to register on macOS 15 (Sequoia)KB000011: Users report delays in obtaining just-in-time access via ADKB000012: Troubleshooting Windows authentication in the Access Manager Web AppKB000013: Access Manager cannot be installed on Windows Server 2016 with TLS 1.0 disabled
PreviousChoosing between the Lithnet and Microsoft agent for LAPS
NextKB000001: The Access Manager Agent cannot connect and logs a token-validation-failed error
Last updated