Process Information > Process Name: Name of the process that closed the handle (C:\Windows\System32\mstsc.exe).Subject > Security ID/Account Name/Account Domain: SID/Account name/Domain of the user who executed the tool.Access Request Information > Access/Reason for Access/Access Mask: Requested privileges (including WriteAttributes).RDP ClientActiveX is trying to connect to the server (). Microsoft-Windows-TerminalServices-RDPClient/Operational Image: Path to the executable file (C:\Windows\System32\mstsc.exe).UtcTime: Process execution date and time (UTC).CommandLine: Command line of the execution command.Add Remote Desktop Users to the Policy.CLOSE+DATA_EXTEND+DATA_OVERWRITE+FILE_CREATE.Select: Allow log on through Remote Desktop Services.Expand: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Management.The simplest way to resolve this issue is to add your thin client users into the Remote Desktop Users Group (or any other group for that matter) then grant that OU the "Allow log on through Remote Desktop Services" ("Terminal Services" in pre 2008 R2 releases) via: If you are not a member of the Remote Desktop Users group or another group that has this right, or if the Remote Desktop Users group does not have this right, or if the Remote Desktop Users group does not have this right, you must be granted this right manually. By default, members of the Remote Desktop Users group have this right. To log on to this remote computer, you must be granted the Allow log on through Terminal Services right. When trying to login through remote desktop services to a server with a Non-Admin account, you will be prompted with the following error: This can present problems when deploying ThinManager and configuring thin clients to use a regular user account. By default, Windows Server does not allow login through remote desktop services by Non-Admin users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |