jw

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » WinRM  ·  Flag idea as inappropriate…  ·  Admin →
    jw commented  · 

    wow...amazingly I finally figured out the issue.

    For whatever reason giving the computer account (of the endpoint) "Read" permission on the user in active directory fixed the issue....I suspect this has something to do with special mods that had been done to the pre-windows 2000 compatible access group

    jw shared this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Zachary Alexander responded

    Per Ryan’s response:
    “This is a known issue in WMF 5.0 and Windows Server 2016 Technical Preview. We are working to get this fixed in a future release, but until then you can only use virtual accounts in JEA on domain-joined machines.”

    jw commented  · 

    i get the exact same error but using a domain account....if I add the connecting user as a local admin is works...kind of defeats the purpose..

Feedback and Knowledge Base