1 Reply Latest reply on May 5, 2016 1:59 PM by dmshimself

    Secure token log on failed


      We have 1 user that keeps getting the 'Secure token log on failed' error when accessing Landesk.  Works for everyone except one guy.  Seemed like a possible AD issue, but I've poured through his account and it looks just like everyone else's.  Any thoughts?