12-20-2021 10:45 PM
I have a rather large problem that is causing grief with an ISE rollout.
The workstations that we have are 99% running windows 7.
We have administrators that want to be able to log in via remote desktop when the users aren't present (i.e. after a Wake on LAN request) and troubleshoot issues.
When they do this windows does not treat the remote desktop session as an interactive login and hence the computer does not jump from the domain to the user policy.
I am after suggestions on how we can get this working.
Is it possible for the Anyconnect supplicant to treat the remote login as an interactive login (we aren't using AnyConnect as a supplicant at the moment)?
Or is there another way - I can't believe that we there isn't a known function for bypassing this issue.
Alternatively I could just move back to computer authentication and give the computer account full access.
Thanks in advance
Solved! Go to Solution.
12-21-2021 02:13 PM
This is an exact duplicate of this post from 2015 - ISE 1.3 Issues with domain computer and remote desktop.
As per the other post, NAM is the only way to fix the RDP issue.
Also see the post for ISE issue with RDP.
12-21-2021 02:13 PM
This is an exact duplicate of this post from 2015 - ISE 1.3 Issues with domain computer and remote desktop.
As per the other post, NAM is the only way to fix the RDP issue.
Also see the post for ISE issue with RDP.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide