Logging on locally after RD session

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Hi,

I'm experiencing a strange problem in a machine where I have just
installed Windows XP. This machine is part of a domain and the user who
is going to use it is a member of the "Standard Users" (not "Power
users" ) group on the machine and also a member of the "Domain users"
group on the domain.

In order to avoid wasting time setting up the machine I have enabled
Terminal Services on it as soon as the network got alive, so I could
install and configure all the needed stuff without leaving my room.

Before using Remote Desktop I made a test and the user could properly
perform a local logon. Then I connected through RD from my machine
using the domain admin account. Everything worked. Service Pack 2 and
every software needed was installed remotely. And some reboots were
also done remotely without any problem.

When I asked the user to logon locally and start working he received
the message: "Your interactive logon privilege has been disabled." I
went back to that machine, logged on as the domain admin, openned the
"Local security policies" snap-in and ensured the group "Standard user"
(the group the user belongs to) had local logon privilege. Then I
logged off and tried to logon as that user. It worked even without
rebooting nor changing any security setting.

Afterwards I had to do some other things and logged again as the domain
admin through RD. Thereon the problem was back. Logging in locally as
the domain admin solved it.

Thus, the problem is easily reproduceable. After logging on through RD
using the domain admin account the only way to make the user logon
again is to perform a local logon using also the domain admin account.
What's happening?

I intend to leave TS enabled on that machine in order to solve any
problem remotely. This way, after setting up everything, I just call
the user back and say "It's done!", without moving from my chair. Is
this a known (and fixable) problem or I'll always need to stay in front
of that computer?

Thanks in advance.

--
Romulo A. Ceccon
<id>@yahoo.com.br (replace '<id>' by 'romuloceccon')

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

"Carl Hopkins" wrote:
> Romulo,
>
> Did you ever get an answer to your problem? I have the exact
> same problem!
> XP SP2 on my machine at my home/office and XP SP2 on my
> client's machines 15
> minutes away. After I perform a remote desktops session the
> local user
> cannot log on, same error message. the "solution" is a
> reboot. So now, when
> I am finished, instead of doing a "log off", I always do a
> reboot. It works,
> but there has t be a better solution.
>
> Carl
>
> "Romulo A. Ceccon" wrote:
>
> > Hi,
> >
> > I'm experiencing a strange problem in a machine where I have
> just
> > installed Windows XP. This machine is part of a domain and
> the user who
> > is going to use it is a member of the "Standard Users" (not
> "Power
> > users" ) group on the machine and also a member of the
> "Domain users"
> > group on the domain.
> >
> > In order to avoid wasting time setting up the machine I have
> enabled
> > Terminal Services on it as soon as the network got alive, so
> I could
> > install and configure all the needed stuff without leaving
> my room.
> >
> > Before using Remote Desktop I made a test and the user could
> properly
> > perform a local logon. Then I connected through RD from my
> machine
> > using the domain admin account. Everything worked. Service
> Pack 2 and
> > every software needed was installed remotely. And some
> reboots were
> > also done remotely without any problem.
> >
> > When I asked the user to logon locally and start working he
> received
> > the message: "Your interactive logon privilege has been
> disabled." I
> > went back to that machine, logged on as the domain admin,
> openned the
> > "Local security policies" snap-in and ensured the group
> "Standard user"
> > (the group the user belongs to) had local logon privilege.
> Then I
> > logged off and tried to logon as that user. It worked even
> without
> > rebooting nor changing any security setting.
> >
> > Afterwards I had to do some other things and logged again as
> the domain
> > admin through RD. Thereon the problem was back. Logging in
> locally as
> > the domain admin solved it.
> >
> > Thus, the problem is easily reproduceable. After logging on
> through RD
> > using the domain admin account the only way to make the user
> logon
> > again is to perform a local logon using also the domain
> admin account.
> > What's happening?
> >
> > I intend to leave TS enabled on that machine in order to
> solve any
> > problem remotely. This way, after setting up everything, I
> just call
> > the user back and say "It's done!", without moving from my
> chair. Is
> > this a known (and fixable) problem or I'll always need to
> stay in front
> > of that computer?
> >
> > Thanks in advance.
> >
> > --
> > Romulo A. Ceccon
> > <id>@yahoo.com.br (replace '<id>' by 'romuloceccon')
> >

Check the properties of the AD acct that cannot logon locally to the
machine. On the Terminal Services Profile tab, enable the "Allow
logon to terminal server" option. It appears that the computer gets
"stuck" in terminal services mode after a Remote Desktop user logs
off. When a domain user w/o the rights to logon via terminal services
subsequently tries to logon locally, they are denied access.

-Chad

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/Work- [...] 16296.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1177714