Remote Desktop login as administrator
It is recommended to be connected to the console (Session ID=0) of the server during the Storage Foundation for Windows (SFW) installation or during SFW Rollup Patch / Maintenance Pack / Service Pack installations. With Microsoft Remote Desktop, connect to the console by using the correct "/admin" or "/console" switches (mstsc.exe /admin or mstsc.exe /console) depending on the Remote Desktop Client (RDC) version being used. The Remote Desktop Client (RDC) 6.1 no longer uses the "/console" switch to connect to the session 0. The "/admin" switch (mstsc.exe /admin) should be used instead. RDC 6.1 is included with the following operating systems:•Windows Server 2008•Windows Vista Service Pack 1 (SP1) and later •Windows XP Service Pack 3 (SP3) and later You can type “mstsc /?” to see if the /admin option has to be used for the console (see image1 as below):
Image1: Remote Desktop Connection Usage
Image2: "query session" command output Please note that in Windows Server 2003, you can start the RDC client (Mstsc.exe) by using the /console or /admin switch to remotely connect to the physical console session on the server (also known as session ID=0). However, in Windows Server 2008 or Windows Server 2008 R2, the /console switch has been deprecated. In Windows Server 2008 and Windows Server 2008 R2, session 0 is a non-interactive session that is reserved for services. For more information, please visit the following Microsoft article: Changes to remote administration in Windows Server 2008.
Modern businesses rely on computers for everything from communicating with customers and suppliers to managing finances and inventory. Thanks to Internet and networking technologies, companies can transact business, attract new customers and share information within the office easier than ever before. However, these technologies can cause complex problems when not maintained properly. If your business is like most, you probably have key employees to whom you turn to fix computer problems. Providing these employees with remote administrator access to computers on your business network can enable them to correct many problems even when they're on the road or working at home. Add an Administrator
Grant Remote Desktop Access to an Administrator
ShadgaAF asked • Dec 2, '21 | piaudonn edited • Dec 2, '21
Hello, on fresh domain (on premise), with working windows terminal server for RDP access, i got the problem users who wants to connect to the server needs to run RDP as Admin. I tried many things like GPO "Allow User to login as Terminal service" or adding the user to the local RDP User group on the terminal server, but none are working. I get the error message "Access denied" "Try to run RDP with higher/admin rights". If the user gets added as local admin and runs rdp with admin, it works fine and even after removing as the local admin, he can still connect to the terminal server afterwards (Question is for how long?). First i thought the user profiles needs to be created on the terminal but just yesterday i had user who proved me the opposite he wanted to go on the terminal server from the meeting-computer and got the same error but he was already using the terminal server way before that happens. Comment Hi, Using Server 2008 R2. In the past I remember that if I was logged in under some account, and attempted to use the same credentials from a different machine to log into the same server (using mstsc /admin), it would kick the current connection and connect me to that session instead. However, now this does not seem to be the case. When I preform the steps above I get the "This computer can't connect to the remote computer" message. How do I take over an existing session by force? Thanks, DB
|