Re: Remote Desktop Users not able to connect to Terminal Server
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Nov 2008 12:19:26 -0800
Did you add the users to the *local* Remote Desktop Users group on
the TS, or in the Active Directory Remote Desktop Users group?
They need to be member of the *local* RDU group.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SW5keVBhdWw=?= <IndyPaul@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 20 nov 2008 in
microsoft.public.windows.terminal_services:
"To log on to this remote computer, you must be granted the.
Allow log on through terminal services right. By default,
members of the Remote desktop users group have this right. If
you are not a member of the Remote Desktop Users group or
another group that has this right, or if remote desktop user
group does not have this right, you must be granted this right
manually
I saw this message in a lot of posts and have tried everything I
saw from the analysts. Let me explain how I got to where I am:
Our site had a DC running Windows 2003. We decided we were
going to add about 20 - 25 Wyse terminals running CE to run one
specific application. We ordered a test system from Wyse and a
new server to use as the terminal server. The Wyse terminal
came in but the server was delayed a couple of weeks. At this
point, I hadn't read all the valuable information here so I did
something not recommended, I added Terminal Services to the
domain controller.
I was able to set up and test the thin client and all was fine.
At this point, though, I was using my own logon -- I'm a domain
admin.
New server came in. First step, removed terminal services from
the DC. Then loaded Windows 2003 on the new TS server. Did
some testing to make sure functionality looked okay (it did, to
the best of my knowledge) so I loaded the 25 TS licenses on the
TS server. The TS server is also running as an applicaiton
server with IIS to support the Wyse Device Manager software.
I then set up a test user to try and get a production profile
ready to go. The test user is in the Remote Desktop Users group
as well as the Domain Users group and a third group called
M2MUsers. The last group is for security on an ERP system. As
soon as I tried logging on as this user to the TS, I got the
above message. If I logon as an admin, everthing works. I have
edited the GPO for "Allow log on through Terminal Services" and
made sure the policy is active on the TS and that the Remote
Desktop Users and Domain Admins are both in there.
At this point, there have been some other suggestions that I saw
but didn't understand. There were two users with the same
problem that said they found the fix and never told how. I'm a
consultant and have worked with MS servers for years, but mostly
SBS (this is NOT and SBS client). This is my first time setting
up a TS server and I'm a bit overwhelmed. I've spent the better
part of 12 hours reading web articles, MS Server manuals and
posts in this newsgroup (very nice to see this level of support
by the way) and am no closer to figuring out a solution.
I hope I haven't been vague about what server I've been talking
about through this. As I read so many of the posts here, there
were many times I couldn't follow which server the MS folks were
talking about -- probably due to my lack of experience in
multi-server environments as well as working with the group
policies. Thanks in advance for any help you can provide :-)
- Follow-Ups:
- References:
- Remote Desktop Users not able to connect to Terminal Server
- From: IndyPaul
- Remote Desktop Users not able to connect to Terminal Server
- Prev by Date: Re: TS License Question - Help
- Next by Date: Re: TS License Question - Help
- Previous by thread: Remote Desktop Users not able to connect to Terminal Server
- Next by thread: Re: Remote Desktop Users not able to connect to Terminal Server
- Index(es):
Relevant Pages
|
