Re: Trouble with TS Admin over RDP
- From: Saint027 <Saint027@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 26 Jan 2007 08:26:01 -0800
I was finally able to solve my own problem. It seems I thought it would be a
good idea to set the Terminal Services service to automatic inside my Group
Policy instead of configuring it manually on all my servers. I noticed that
every time GP would update, the RDP Listener would disappear. When I
configured the Group Policy setting for Terminal Services to Not Configured,
the problem resolved itself.
Still not sure what the deal is with that behavior, but figured I'd post my
results in case anyone else has the same "bright idea" I did.
"Saint027" wrote:
I can wait 'till monday. Unless the problem miraculously disappears. Either.
way, its all good, right? :)
I've already removed the network service rights. I did notice a drop in the
number of Event 560 Failure Audits when I did that though. Interesting ...
"Trust No One®" wrote:
"Saint027" <Saint027@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C5CABE0-F648-46A2-B9B8-0DA1A8EC658A@xxxxxxxxxxxxxxxx
OK, I granted Full Control access to the Terminal Services Service to theDarn!
Network Service account. Still no joy. It works temporarily, but does
not
survive the reboot.
The reason I said hmmm.. in my previous post ns that we been through a
similar problem with our Windows 2003 SP1 DMZ servers, which as it happens
are locked down via the High Security baseline policy. I posted about this a
few weeks back and had planned to raise a fault with Microsoft PSS. None of
the servers in our internal network exhibited the problem and I'm sure it is
related to the High Security GPO.
The terminal services listener refused to start up on rebooting the server.
It could be re-instated (until the next reboot) by simply running the
"gpupdate" command. I devised a temporary workaround of implementing a
start-up script on each server which contained the gpupdate command.
I spent ages looking into this and eventually got it all working and so did
not need to contact PSS. Unfortunately I committed the cardinal sin of not
fully documenting my troubleshooting steps :( my bad!
If you can wait until Monday when I'm next into work I'll go through my
notes and collate the changes I made.
BTW I wouldn't recommend granting the Network Service full control to the
terminal services service. Read access should be sufficient.
--
Peter <X-Files fan>
- References:
- Re: Trouble with TS Admin over RDP
- From: Trust No OneŽ
- Re: Trouble with TS Admin over RDP
- Prev by Date: Re: Remove Terminal Server Temporary licences
- Next by Date: Office 2000 splash screen on Windows 2003 Server with Terminal Services
- Previous by thread: Re: Trouble with TS Admin over RDP
- Next by thread: Re: Handle leak in Remote Desktop Web Connection?
- Index(es):
Relevant Pages
|
