- #Administrator running a console session how to#
- #Administrator running a console session software#
- #Administrator running a console session windows#
#Administrator running a console session windows#
I no longer have access to any Windows Server 2003 machines to see what the /console switch did in this respect. The /admin switch does not affect this behaviour.
#Administrator running a console session software#
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 Destkop 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.
![administrator running a console session administrator running a console session](https://khoshamoz.ir/site_binarydata/img_post/small/00000000000000009078.jpg)
(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 have tried the /admin switch or adding administrator session:i:1 to an rdp file. an administrator running a console session in order to use the sfc utility. (I am not sure whether the /admin switch has any effect when connecting to a Windows XP machine.) I have not been able to log into the console session as shown by qwinsta. SFC (System File Checker) is a utility available in Windows Operating System. It does not behave like the /console switch when connecting to a modern version of Windows. This functionality is no longer considered useful, and has been removed.įor backwards compatibility, the /admin switch behaves like the /console switch when connecting to a Windows 2003 or Windows 2003 R2 server.
#Administrator running a console session how to#
I no longer have access to any Windows Server 2003 machines to see what the /console switch did in this respect.The /console switch was for connecting to the console session. 2020 FIX - You must be an administrator running a console session in order to use the sfc utility.In this video, you will learn how to fix error messages. 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. It tells me You must be an administrator running a console session in order to use the sfc console. Solution: Hold on a sec:You must be an administrator running a console sessionYoure doing this over RDP arent youTry it from the actual console on the. 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. Step 1: Click on the Start button on your desktop and type Command Prompt in the search field.
![administrator running a console session administrator running a console session](https://www.thewindowsclub.com/wp-content/uploads/2021/05/POWERSHELL-AS-ADMIN-1.jpg)
![administrator running a console session administrator running a console session](https://i.stack.imgur.com/QotR2.png)
whereas applications run in local sessions have the CONSOLE LOGON token. 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 have tried the /admin switch or adding administrator session:i:1 to an rdp. (I am not sure whether the /admin switch has any effect when connecting to a Windows XP machine.) The /console switch was for connecting to the console session.