In the middle of rolling out terminal services and I have hit a bit of a snag.

My Terminal Services Client PC's autologon and then automatically run a
script to connect to the terminal server. All of this works fine.

My problem is this : -
I want to be able to remote to the destop of the TS PC to maintain it (I.e
login as administrator and see what is going on)

With auto logon enabled my attempt to connect to the remote PC is refused
with a 'policy is inforce that prevents you connecting message'

Research has proved that this is not policy related. The only thing that
seems to cause this behaviour is the fact that the current user on the pc is
the auto logon user.

Has anyone seen this specific behaviour before

Yes. It is the default action. For you to connect remotely the current user
should be logged out.

"Groves_Nigel" <(E-Mail Removed)> wrote in message
news:E7AD3D85-FB27-4369-8FBB-(E-Mail Removed)...
> In the middle of rolling out terminal services and I have hit a bit of a
> snag.
>
> My Terminal Services Client PC's autologon and then automatically run a
> script to connect to the terminal server. All of this works fine.
>
> My problem is this : -
> I want to be able to remote to the destop of the TS PC to maintain it (I.e
> login as administrator and see what is going on)
>
> With auto logon enabled my attempt to connect to the remote PC is refused
> with a 'policy is inforce that prevents you connecting message'
>
> Research has proved that this is not policy related. The only thing that
> seems to cause this behaviour is the fact that the current user on the pc
> is
> the auto logon user.
>
> Has anyone seen this specific behaviour before