- Remove From My Forums
-
Общие обсуждения
-
Windows Server 2008 R2 Терминальный сервер, не удается подключиться
к активной сессии пользователя, разрешения на удаленное управление с взаимодействием сеанса без подтверждения пользователя в настройках выставлены,
уч запись Администратор пытаюсь подключиться к активному пользователю в диспетчере задач — Ошибка удаленного управления сеансом (ID 3), в
логе системы Не удается запустить диспетчер окон рабочего стола, так как составная тема не используется.
на сервере кроме 1с 8.2 ничего не установлено, сервер развернут на днях, все хорошо за исключением этой ошибки, подскажите что можно предпринять.-
Изменен тип
23 января 2012 г. 8:16
-
Изменен тип
Права для удаленного управления
-
Simol
- Сообщения: 41
- Зарегистрирован: Чт янв 20, 2005 10:47 am
- Контактная информация:
Права для удаленного управления
Кем должен быть пользователь сервера терминала чтобы мог удаленно управлять сесиями других пользователей — пользователей домена?
Администратор домена может
Пользователь домена + Локальные администратор этого сервера не может
-
Simol
- Сообщения: 41
- Зарегистрирован: Чт янв 20, 2005 10:47 am
- Контактная информация:
Сообщение
Simol » Ср сен 20, 2006 12:38 pm
Ошибка была в этом:
Примечание. В случае, если диспетчером служб терминалов будет выведено сообщение об ошибке «Ошибка удаленного управления сеансом (Id x) (Ошибка 7025. Была сделана попытка подключения к сеансу с видеорежимом, не поддерживаемым данным клиентом)», возможно, потребуется изменить видеорежим на сервере или использовать для удаленного управления другой клиент.
-
Ejean
- Сообщения: 403
- Зарегистрирован: Сб апр 16, 2005 9:30 am
- Контактная информация:
Сообщение
Ejean » Ср сен 20, 2006 9:50 pm
1) Управление другим сеансом возможно только из терминальной сессии.
2) Если твоя сессия имеет более низкие параметры: разрешение экрана, количество цветов, то возможны проблемы…
3) «Управляющий» пользователь должен иметь права на управление, они задаются Администрирование/Настройка служб терминалов/свойства RDP-Tcp/Разрешения
-
Simol
- Сообщения: 41
- Зарегистрирован: Чт янв 20, 2005 10:47 am
- Контактная информация:
Сообщение
Simol » Чт сен 21, 2006 11:14 am
Спасибо за исчерпывающую информацию
-
Simol
- Сообщения: 41
- Зарегистрирован: Чт янв 20, 2005 10:47 am
- Контактная информация:
Сообщение
Simol » Пн сен 25, 2006 3:32 pm
А как клиент может сопративлятся удаленному управлению кроме нажимать «не разрешаю»?
Ситуация. Захожу под пользователем Х у себя, захожу под админом у себя. Пробую управлять — появляется окошко с запросом, разрешаю и управляю.
Пользователь в другом породе заходит под пользователем Х, пытаюсь управлять его сесией, у меня после некогорого времени ошибка, а пользователь говорит, что у него сообщение не появляется.
-
Ejean
- Сообщения: 403
- Зарегистрирован: Сб апр 16, 2005 9:30 am
- Контактная информация:
Сообщение
Ejean » Пн сен 25, 2006 10:35 pm
Всё у него появляется 
-
Simol
- Сообщения: 41
- Зарегистрирован: Чт янв 20, 2005 10:47 am
- Контактная информация:
Сообщение
Simol » Вт сен 26, 2006 9:05 am
Убрал подтверждение пользователя, все подключилось. Саботаж одним словом.
-
dsm
Re:
Сообщение
dsm » Пт апр 17, 2009 1:00 pm
[quote=»Simol»]Убрал подтверждение пользователя, все подключилось. Саботаж одним словом.[/quote]
А как убрать это подтверждение??? Можно ли так сделать, что бы подключаться к сессии без запроса на разрешение?
Заранее благодарен!!!
-
gserg
- Сообщения: 351
- Зарегистрирован: Вс мар 05, 2006 12:19 pm
- Откуда: рядом с Москвой
- Контактная информация:
Re: Re:
Сообщение
gserg » Чт май 14, 2009 7:35 am
dsm писал(а):
Simol писал(а):Убрал подтверждение пользователя, все подключилось. Саботаж одним словом.
А как убрать это подтверждение??? Можно ли так сделать, что бы подключаться к сессии без запроса на разрешение?
Заранее благодарен!!!
Может быть поздно 
В картинках интереснее Эх молодежь
- Вложения
-
- rdp.JPG (70.25 КБ) 30769 просмотров
- Remove From My Forums
-
Question
-
Hello all,
I am having an issue when trying to remote control a user session on Windows Server 2008 R2.
If I log onto the system as the domain Administrator, I am able to control the session of users. However If I log onto my own account as Domain Admin, member of the Administrator group. I recieve an error which is:
Windows Task Manager:
Session (ID x) Remote Control FailedThere are many Domain Admins in my organization — which means we can’t all simply log on as the Domain Administrator to our servers.
How can I enable Remote Desktop Session Shadows on all of my Domain Admin accounts?
The current process I use is:
#
Open Task Manager
Click the Users Tab
Right Click the User — Remote Control
The error is then shown.
#
Doing this using the Administrator account work, however doing it from my account which like I say is in the Domain Admin group — does not work.
Thank you for your time.
Answers
-
Hi all,
Just so you know i’ve found the soloution to this — after 3 days of research. It was UAC control which prevents this running.
I disabled UAC and all is fine.
Grr..
Thanks for your input.
-
Marked as answer by
Thursday, February 17, 2011 10:24 AM
-
Marked as answer by
- Remove From My Forums
-
Question
-
Hello all,
I am having an issue when trying to remote control a user session on Windows Server 2008 R2.
If I log onto the system as the domain Administrator, I am able to control the session of users. However If I log onto my own account as Domain Admin, member of the Administrator group. I recieve an error which is:
Windows Task Manager:
Session (ID x) Remote Control FailedThere are many Domain Admins in my organization — which means we can’t all simply log on as the Domain Administrator to our servers.
How can I enable Remote Desktop Session Shadows on all of my Domain Admin accounts?
The current process I use is:
#
Open Task Manager
Click the Users Tab
Right Click the User — Remote Control
The error is then shown.
#
Doing this using the Administrator account work, however doing it from my account which like I say is in the Domain Admin group — does not work.
Thank you for your time.
Answers
-
Hi all,
Just so you know i’ve found the soloution to this — after 3 days of research. It was UAC control which prevents this running.
I disabled UAC and all is fine.
Grr..
Thanks for your input.
-
Marked as answer by
Thursday, February 17, 2011 10:24 AM
-
Marked as answer by
SYMPTOMS
When a user remote controls another user’s session using Remote Desktop Services Manager or Terminal Services Manager on a Windows Server 2008-based computer, and then stops remote controlling, one or both sessions are disconnected with the following error:
Remote Desktop Disconnected
Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.
CAUSE
This problem occurs if Remote Desktop Connection Client version 6.0.6001 or 6.0.6002 is used with the highest RDP Compression setting. Windows Server 2008 SP1/SP2 defaults to a lower RDP Compression setting, and thus will only exhibit the above symptoms if the setting has been changed to «Optimized to use less network bandwidth», which is the maximum. Windows Server 2008 R2 defaults to the maximum RDP Compression setting.
WORKAROUND
Change the RDP Compression setting on the server to «Balances memory and network bandwidth» (recommended) or «Optimized to use less memory» using Group Policy. If using Windows Server 2008 R2 you may also choose «Do not use an RDP compression algorithm». An alternative workaround is to use a different Remote Desktop Connection Client version than those mentioned above, however, this may not be practical. Below are instructions for making the change to the local group policy; if preferred you can use a domain group policy instead.
Windows Server 2008 R2
1. Logon to the Remote Desktop Services Session Host computer as an administrator
2. Start—Run gpedit.msc
3. In the left pane, under Computer Configuration, navigate to following:
Administrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostRemote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
Windows Server 2008 (SP1 or SP2)
1. Logon to the Terminal Services computer as an administrator
2. Start—Run gpedit.msc, click Continue if prompted by UAC
3. In the left pane, under Computer Configuration, navigate to following:
Administrative TemplatesWindows ComponentsTerminal ServicesTerminal ServerRemote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
STEPS TO REPRODUCE
Windows Server 2008 R2 x64
1. Install 2008 R2 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck «Require user’s permission»
5. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
7. In the administrator’s session, open up Remote Desktop Services Manager, right-click on the test user and choose Remote Control, click OK
8. After you are viewing the test user’s desktop, press Ctrl-Tab to end the Remote Control
Windows Server 2008 x64
1. Install 2008 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck «Require user’s permission»
5. Change RDP Compression algorithm to «Optimized to use less network bandwidth» using instructions above
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
7. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
8. In the administrator’s session, open up Terminal Services Manager, right-click on the test user and choose Remote Control, click OK
9. After you are viewing the test user’s desktop, press Ctrl-Tab to end the Remote Control
NOTE: This problem may occur when connecting to a Windows Vista or Windows 7 host under similar conditions. I have not tested this theory, however.
As always I welcome your comments/questions/corrections/suggestions/etc.
Thank you for reading.
-TP
SYMPTOMS
When a user remote controls another user’s session using Remote Desktop Services Manager or Terminal Services Manager on a Windows Server 2008-based computer, and then stops remote controlling, one or both sessions are disconnected with the following error:
Remote Desktop Disconnected
Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.
CAUSE
This problem occurs if Remote Desktop Connection Client version 6.0.6001 or 6.0.6002 is used with the highest RDP Compression setting. Windows Server 2008 SP1/SP2 defaults to a lower RDP Compression setting, and thus will only exhibit the above symptoms if the setting has been changed to «Optimized to use less network bandwidth», which is the maximum. Windows Server 2008 R2 defaults to the maximum RDP Compression setting.
WORKAROUND
Change the RDP Compression setting on the server to «Balances memory and network bandwidth» (recommended) or «Optimized to use less memory» using Group Policy. If using Windows Server 2008 R2 you may also choose «Do not use an RDP compression algorithm». An alternative workaround is to use a different Remote Desktop Connection Client version than those mentioned above, however, this may not be practical. Below are instructions for making the change to the local group policy; if preferred you can use a domain group policy instead.
Windows Server 2008 R2
1. Logon to the Remote Desktop Services Session Host computer as an administrator
2. Start—Run gpedit.msc
3. In the left pane, under Computer Configuration, navigate to following:
Administrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostRemote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
Windows Server 2008 (SP1 or SP2)
1. Logon to the Terminal Services computer as an administrator
2. Start—Run gpedit.msc, click Continue if prompted by UAC
3. In the left pane, under Computer Configuration, navigate to following:
Administrative TemplatesWindows ComponentsTerminal ServicesTerminal ServerRemote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
STEPS TO REPRODUCE
Windows Server 2008 R2 x64
1. Install 2008 R2 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck «Require user’s permission»
5. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
7. In the administrator’s session, open up Remote Desktop Services Manager, right-click on the test user and choose Remote Control, click OK
8. After you are viewing the test user’s desktop, press Ctrl-Tab to end the Remote Control
Windows Server 2008 x64
1. Install 2008 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck «Require user’s permission»
5. Change RDP Compression algorithm to «Optimized to use less network bandwidth» using instructions above
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
7. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
8. In the administrator’s session, open up Terminal Services Manager, right-click on the test user and choose Remote Control, click OK
9. After you are viewing the test user’s desktop, press Ctrl-Tab to end the Remote Control
NOTE: This problem may occur when connecting to a Windows Vista or Windows 7 host under similar conditions. I have not tested this theory, however.
As always I welcome your comments/questions/corrections/suggestions/etc.
Thank you for reading.
-TP