Re: Trouble with TS Admin over RDP
- From: "Trust No OneŽ" <dana.scully@xxxxxxxx>
- Date: Thu, 4 Jan 2007 18:18:00 -0000
"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>
.
- Prev by Date: Re: [2003] Why can't app print?
- Next by Date: Re: [2003] Why can't app print?
- Previous by thread: No License Server
- Next by thread: Re: Trouble with TS Admin over RDP
- Index(es):
Relevant Pages
|
