https://community.checkpoint.com/t5/Firewall-and-Security-Management/IDA-terminal-agent-change-from-UPN-to-sAMAccountName/m-p/140139#M21464 <P><a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/8232">@Royi_Priov</a>&nbsp;</P> Wed, 02 Feb 2022 05:39:57 GMT PhoneBoy 2022-02-02T05:39:57Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/IDA-terminal-agent-change-from-UPN-to-sAMAccountName/m-p/138895#M21156 <P>Hi Folks,</P><P>I have running a MDM with R81.10 + JHF9 and a VSX Cluster with R80.40 + JHF-121.<BR />On one of the virtuall systems is IDA enabled and the checkbox for using ida agents for terminal is checked.<BR />The muh1 agent on one of my terminal server is used, as it is an older windows server.</P><P><BR />In the "user" section of the ida agent, I can see that lots of the active terminal users are "Not authenticated".</P><P>For me it looks like the ida agent is using the UPN.</P><P>All my users are in the same domain, but they have "historically grown" (my favorite term, when dealing with network trouble) different UPN.</P><P>&nbsp;</P><P>SK110858 discribes how to change form sAMAccountName to UPN.<BR />I need the oposite way, changeing from UPN to sAMAccountName.</P><P>Does anyone has an idea?</P><P>Best regards,<BR />Christian</P> Wed, 19 Jan 2022 13:24:49 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/IDA-terminal-agent-change-from-UPN-to-sAMAccountName/m-p/138895#M21156 Christian_Koehl 2022-01-19T13:24:49Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/IDA-terminal-agent-change-from-UPN-to-sAMAccountName/m-p/140139#M21464 <P><a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/8232">@Royi_Priov</a>&nbsp;</P> Wed, 02 Feb 2022 05:39:57 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/IDA-terminal-agent-change-from-UPN-to-sAMAccountName/m-p/140139#M21464 PhoneBoy 2022-02-02T05:39:57Z