Failure to Login, no Permissions.

[Guest The Rev]

I have a WIn2003 terminal server that runs as a member Srv in application

mode. It has no licenses, it's been up for 45 days. The server is in its own

OU. I have the checkmark in the Remote Desktop box.

I've added myself and the domain admins group to the local Remote Desktop

Users group. I've also added the groups to the domain servers RDU group. When

ever I attempt to logi in , I receive this message

 

"To log on to this remote computer, you must have Terminal Server

User access permissions on this computer. By default, members of the Remote

Desktop Users group have these permissions. If you are not a member of the

Remote Desktop Users group or another group that has these permissions, or if

the Remote Desktop User group does not have these permissions, you must be

granted these permissions manually."

 

I've been able to login with the "mstsc /console /v:ServerName" as and

Admin, but it fails when I login as a regulart term user. The only changes to

the system are MS updates.

 

I must get this TermSrv ready for production by years end.

Please help me login.

[Guest The Rev]

RE: Failure to Login, no Permissions.

 

After reviewing my log files, I found an 1008 Error. It says that the grace

period has expired. When does the clock start. I put the server in

Application mode less that two months ago. Did the clock start on the first

day of remote adminstration connection?

 

"The Rev" wrote:

> I have a WIn2003 terminal server that runs as a member Srv in application

> mode. It has no licenses, it's been up for 45 days. The server is in its own

> OU. I have the checkmark in the Remote Desktop box.

> I've added myself and the domain admins group to the local Remote Desktop

> Users group. I've also added the groups to the domain servers RDU group. When

> ever I attempt to logi in , I receive this message

>

> "To log on to this remote computer, you must have Terminal Server

> User access permissions on this computer. By default, members of the Remote

> Desktop Users group have these permissions. If you are not a member of the

> Remote Desktop Users group or another group that has these permissions, or if

> the Remote Desktop User group does not have these permissions, you must be

> granted these permissions manually."

>

> I've been able to login with the "mstsc /console /v:ServerName" as and

> Admin, but it fails when I login as a regulart term user. The only changes to

> the system are MS updates.

>

> I must get this TermSrv ready for production by years end.

> Please help me login.

>

>

[Guest The Rev]

RE: Failure to Login, no Permissions.

 

Check you servers error logs. It could disclose information to you.

 

"The Rev" wrote:

> After reviewing my log files, I found an 1008 Error. It says that the grace

> period has expired. When does the clock start. I put the server in

> Application mode less that two months ago. Did the clock start on the first

> day of remote adminstration connection?

>

> "The Rev" wrote:

>

> > I have a WIn2003 terminal server that runs as a member Srv in application

> > mode. It has no licenses, it's been up for 45 days. The server is in its own

> > OU. I have the checkmark in the Remote Desktop box.

> > I've added myself and the domain admins group to the local Remote Desktop

> > Users group. I've also added the groups to the domain servers RDU group. When

> > ever I attempt to logi in , I receive this message

> >

> > "To log on to this remote computer, you must have Terminal Server

> > User access permissions on this computer. By default, members of the Remote

> > Desktop Users group have these permissions. If you are not a member of the

> > Remote Desktop Users group or another group that has these permissions, or if

> > the Remote Desktop User group does not have these permissions, you must be

> > granted these permissions manually."

> >

> > I've been able to login with the "mstsc /console /v:ServerName" as and

> > Admin, but it fails when I login as a regulart term user. The only changes to

> > the system are MS updates.

> >

> > I must get this TermSrv ready for production by years end.

> > Please help me login.

> >

> >

[Guest Vera Noest [MVP]]

RE: Failure to Login, no Permissions.

 

Yes. Documented here:

 

813052 - Maximizing the Windows Server 2003 Terminal Services

Evaluation Period

http://support.microsoft.com/?kbid=813052

 

So you'll have to install a TS Licensing server. It will issue

temporary licenses, which last for 90 days. After that, you'll need

purchased TS CALs.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?VGhlIFJldg==?= <TheRev@discussions.microsoft.com> wrote

on 19 dec 2007 in microsoft.public.windows.terminal_services:

> After reviewing my log files, I found an 1008 Error. It says

> that the grace period has expired. When does the clock start. I

> put the server in Application mode less that two months ago. Did

> the clock start on the first day of remote adminstration

> connection?

>

> "The Rev" wrote:

>

>> I have a WIn2003 terminal server that runs as a member Srv in

>> application mode. It has no licenses, it's been up for 45 days.

>> The server is in its own OU. I have the checkmark in the Remote

>> Desktop box. I've added myself and the domain admins group to

>> the local Remote Desktop Users group. I've also added the

>> groups to the domain servers RDU group. When ever I attempt to

>> logi in , I receive this message

>>

>> "To log on to this remote computer, you must have

>> Terminal Server

>> User access permissions on this computer. By default, members

>> of the Remote Desktop Users group have these permissions. If

>> you are not a member of the Remote Desktop Users group or

>> another group that has these permissions, or if the Remote

>> Desktop User group does not have these permissions, you must be

>> granted these permissions manually."

>>

>> I've been able to login with the "mstsc /console /v:ServerName"

>> as and Admin, but it fails when I login as a regulart term

>> user. The only changes to the system are MS updates.

>>

>> I must get this TermSrv ready for production by years end.

>> Please help me login.