![]() The /admin switch does not affect this behaviour. I am not personally aware of any Windows components or third-party software that only allow access to the console logon except for the "Restrict access to locally logged-on user only" policies, which are off by default. In particular, applications run in Remote Desktop sessions have the REMOTE INTERACTIVE LOGON token whereas applications run in local sessions have the CONSOLE LOGON token. ![]() Whatever documentation you are reading that suggests that you do may be out of date.Īddendum: Windows does allow components and third-party software to distinguish between Remote Desktop sessions and local sessions. In summary: in theory, at least, you should not need to connect to the console session. When connecting to a modern version of Windows Server that does not have Remote Desktop Services installed, or to a modern version of a Windows client edition, you do not need the /admin switch. (Note: prior to Windows 2008 R2, the Remote Desktop Services component was called Terminal Services.) When connecting to a modern server version of Windows with the Remote Desktop Services component installed, the /admin switch affects certain behaviour, most notably whether a CAL ( Client Access License) is consumed, as described in the linked article. (I am not sure whether the /admin switch has any effect when connecting to a Windows XP machine.) It does not behave like the /console switch when connecting to a modern version of Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |