S
SuperGumby [SBS MVP]
Guest
H Guys,
brand new install, Server 2003 (x32).
SO OK, I put together this nice new Windows Server 2003 (x32), join it to
the domain, and enable TS. I then connect to it remotely as Administrator,
all's well. So let's take the KB/mouse off and run her headless, move her
into the server room. Apps are installed as Admin, all is well.
Go for it guys, use it.
'The policy of this system does not allow you to logon interactively', HUH?
Even though Terminal Services is installed the server is acting like 'Remote
Desktop', 2 sessions and Admins only. I've just been in (remote) and removed
the tick from the TS win component, used Petri notes to enable RD again,
then put TS back, all as Domain Administrator. She's still acting as RD
only.
I've run RSOP against her and cannot see any policy which may be causing it.
She's a member of an SBS2000 domain but I know of no reason why that would
be affecting it.
brand new install, Server 2003 (x32).
SO OK, I put together this nice new Windows Server 2003 (x32), join it to
the domain, and enable TS. I then connect to it remotely as Administrator,
all's well. So let's take the KB/mouse off and run her headless, move her
into the server room. Apps are installed as Admin, all is well.
Go for it guys, use it.
'The policy of this system does not allow you to logon interactively', HUH?
Even though Terminal Services is installed the server is acting like 'Remote
Desktop', 2 sessions and Admins only. I've just been in (remote) and removed
the tick from the TS win component, used Petri notes to enable RD again,
then put TS back, all as Domain Administrator. She's still acting as RD
only.
I've run RSOP against her and cannot see any policy which may be causing it.
She's a member of an SBS2000 domain but I know of no reason why that would
be affecting it.