Tips for it to work: 1. Check if there isn’t another Group Policy Object (GPO) granting permission for remote desktop. In my case, there was one set to request user permission. 2. To discover the user ID remotely, use the command “qwinsta /server:IP or computer name.” 3. To connect, you can add “/noConsentPrompt” at the end. For example: mstsc /shadow:User ID /v:Name or IP /noConsentPrompt. 4. You can also control the computer by appending “/Control” to the command. For instance: mstsc /shadow:User ID /v:Name or IP /Control. I hope this helps! Thank you for the video; it was very helpful. 😊
You can run the command that shows you the ID. Sometimes, for an unknown reason, the ID is changed. Check this point and I will wait for your response. Good luck, command query user. 👊
Here the client was not requested to allow remote control. The client's computer that is already joined to the domain is allowed to be controlled remotely, and I did not set policy control without the client's permission. Because he is already affiliated with the domain, and therefore I can control him. The idea is in the ID through which I connect to the client screen. I don't know how to deliver the information to you. But you must understand that any computer joined to the domain is already something you can control without permission. Thank you also for the comment, and as I told you, I am waiting for any other inquiry to clarify in detail. Thank you, Rana 👍🤍
please help rana ? Hello, 1- remote desktop computer connection requires user confirmation. 2-Also, when the user accepted the control, the client computer could not be managed. 3-An unauthorized connection was selected but it requests permission from the user.
Hello, 1- remote desktop computer connection requires user confirmation. 2-Also, when the user accepted the control, the client computer could not be managed. 3-An unauthorized connection was selected but it requests permission from the user.
Tips for it to work: 1. Check if there isn’t another Group Policy Object (GPO) granting permission for remote desktop. In my case, there was one set to request user permission. 2. To discover the user ID remotely, use the command “qwinsta /server:IP or computer name.” 3. To connect, you can add “/noConsentPrompt” at the end. For example: mstsc /shadow:User ID /v:Name or IP /noConsentPrompt. 4. You can also control the computer by appending “/Control” to the command. For instance: mstsc /shadow:User ID /v:Name or IP /Control. I hope this helps! Thank you for the video; it was very helpful. 😊
I also thank you for these tips. I always love someone who leaves me information that I can benefit from. Thank you again and good luck to you. Don't deprive us of your advice. I thank you 🤍🤍👍
Tips for it to work:
1. Check if there isn’t another Group Policy Object (GPO) granting permission for remote desktop. In my case, there was one set to request user permission.
2. To discover the user ID remotely, use the command “qwinsta /server:IP or computer name.”
3. To connect, you can add “/noConsentPrompt” at the end. For example: mstsc /shadow:User ID /v:Name or IP /noConsentPrompt.
4. You can also control the computer by appending “/Control” to the command. For instance: mstsc /shadow:User ID /v:Name or IP /Control.
I hope this helps! Thank you for the video; it was very helpful. 😊
I will try the commands immediately. Thank you very much for your reply.
Can you please help me with the step 1
All configuration has been set as mentioned, but remote desktop computer connection requires user confirmation!
When I run the cmd this error shows The operator or administrator has refused the request
You can run the command that shows you the ID. Sometimes, for an unknown reason, the ID is changed. Check this point and I will wait for your response. Good luck, command query user. 👊
when do that send client request to allow remote control why ? iam set policy control without permission ?
Here the client was not requested to allow remote control. The client's computer that is already joined to the domain is allowed to be controlled remotely, and I did not set policy control without the client's permission. Because he is already affiliated with the domain, and therefore I can control him. The idea is in the ID through which I connect to the client screen. I don't know how to deliver the information to you. But you must understand that any computer joined to the domain is already something you can control without permission. Thank you also for the comment, and as I told you, I am waiting for any other inquiry to clarify in detail. Thank you, Rana 👍🤍
please help rana ? Hello, 1- remote desktop computer connection requires user confirmation. 2-Also, when the user accepted the control, the client computer could not be managed. 3-An unauthorized connection was selected but it requests permission from the user.
Hello, 1- remote desktop computer connection requires user confirmation. 2-Also, when the user accepted the control, the client computer could not be managed. 3-An unauthorized connection was selected but it requests permission from the user.
Tips for it to work:
1. Check if there isn’t another Group Policy Object (GPO) granting permission for remote desktop. In my case, there was one set to request user permission.
2. To discover the user ID remotely, use the command “qwinsta /server:IP or computer name.”
3. To connect, you can add “/noConsentPrompt” at the end. For example: mstsc /shadow:User ID /v:Name or IP /noConsentPrompt.
4. You can also control the computer by appending “/Control” to the command. For instance: mstsc /shadow:User ID /v:Name or IP /Control.
I hope this helps! Thank you for the video; it was very helpful. 😊
I also thank you for these tips. I always love someone who leaves me information that I can benefit from. Thank you again and good luck to you. Don't deprive us of your advice. I thank you 🤍🤍👍
remote desktop computer connection requires user confirmation...
Nice
Thank you for your comment. Good luck to you