Problems with logging in using Remote Connection....

[Guest Eric]

I installed Terminal Server and created a user "Apptest" w/(Account Operator,

Domain User & Desktop Remote User) membership, but evertime I try to log in

from my labtop I get the message saying I don't have the rights to log in,

but, I can log in as the Admin.

 

another thing happen after I completing the Configure Your Server is, the

User & Group Object is no longer in the Computer Management Console, but it's

available in the Active Directory User & Computer Manager.

 

So, my question is, what is wrong with my user not being able to connect, do

I need to recreate the user in the Active Director Manager?

--

Eric Miller

[Guest Vera Noest [MVP]]

Re: Problems with logging in using Remote Connection....

 

Sounds like you installed Terminal Services on your Domain

Controller, is that correct? That's *not* recommended, for both

security and performance reasons.

_________________________________________________________

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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 14

jan 2008 in microsoft.public.windows.terminal_services:

> I installed Terminal Server and created a user "Apptest"

> w/(Account Operator, Domain User & Desktop Remote User)

> membership, but evertime I try to log in from my labtop I get

> the message saying I don't have the rights to log in, but, I can

> log in as the Admin.

>

> another thing happen after I completing the Configure Your

> Server is, the User & Group Object is no longer in the Computer

> Management Console, but it's available in the Active Directory

> User & Computer Manager.

>

> So, my question is, what is wrong with my user not being able to

> connect, do I need to recreate the user in the Active Director

> Manager?

[Guest Eric]

Re: Problems with logging in using Remote Connection....

 

Yea, that is what I did, but that is what I didn't want to do.

 

This is my first time diving into creating a server. What I wanted to do is

install the Virtual Server and create all my VM for all the Server needs and

just use the Host Server for the Terminal Server.

 

Do I have to reinstall everything to do this or can I uninstall the Server

Configuration?

 

--

Eric Miller

 

 

"Vera Noest [MVP]" wrote:

> Sounds like you installed Terminal Services on your Domain

> Controller, is that correct? That's *not* recommended, for both

> security and performance reasons.

> _________________________________________________________

> 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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 14

> jan 2008 in microsoft.public.windows.terminal_services:

>

> > I installed Terminal Server and created a user "Apptest"

> > w/(Account Operator, Domain User & Desktop Remote User)

> > membership, but evertime I try to log in from my labtop I get

> > the message saying I don't have the rights to log in, but, I can

> > log in as the Admin.

> >

> > another thing happen after I completing the Configure Your

> > Server is, the User & Group Object is no longer in the Computer

> > Management Console, but it's available in the Active Directory

> > User & Computer Manager.

> >

> > So, my question is, what is wrong with my user not being able to

> > connect, do I need to recreate the user in the Active Director

> > Manager?

>

[Guest Vera Noest [MVP]]

Re: Problems with logging in using Remote Connection....

 

Depends on your goal. If you are just testing, you can either

continue to run TS on your DC, or uninstall TS or demote the server

to a standalone server. To give users access to a TS running on a

DC, you have to do the following:

1. add the users to the built-in domain local Remote Desktop Users

group in AD

2. enable the following setting in the Default Domain Controller

Policy:

Computer Configuration - Windows Settings - Security Settings -

Local Policies - User rights Assignment - "Allow log on through

Terminal Services"

and add the Remote Desktop Users group to the list of allowed users

3. add the Remote Desktop Users group to the permission list of the

rdp-tcp connection

 

If you are preparing a production DC or a production TS, I'd rather

start afresh.

 

_________________________________________________________

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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 14

jan 2008 in microsoft.public.windows.terminal_services:

> Yea, that is what I did, but that is what I didn't want to do.

>

> This is my first time diving into creating a server. What I

> wanted to do is install the Virtual Server and create all my VM

> for all the Server needs and just use the Host Server for the

> Terminal Server.

>

> Do I have to reinstall everything to do this or can I uninstall

> the Server Configuration?

[Guest Eric]

Re: Problems with logging in using Remote Connection....

 

Thanks MVP for the help! So I don't get to deep in confusing myself, I will

start afresh and do it right from the beginning. I want the seperate

production servers.

 

This is my Goal:

So I can better understand what I'm doing is ok, could I make production VM

Servers (for the x32 Server 2005) each for (File Sever, Application Server

(Web & Intranet), Remote Access/VPN Server, Domain Controller (Active

Director) Server) to run on my x64 version of Server 2005?

 

I don't want all the server types running at once on the host, but seperate

as Guest in VM Servers. Just run the Terminal Server on the Host.

 

If not what is the best setup for what I am trying to do, because for now I

only have one cpu x64 AMD 300+MHz, 2+gb RAM (DDR400), 320 SATA Drive.

--

Eric Miller

 

 

"Vera Noest [MVP]" wrote:

> Depends on your goal. If you are just testing, you can either

> continue to run TS on your DC, or uninstall TS or demote the server

> to a standalone server. To give users access to a TS running on a

> DC, you have to do the following:

> 1. add the users to the built-in domain local Remote Desktop Users

> group in AD

> 2. enable the following setting in the Default Domain Controller

> Policy:

> Computer Configuration - Windows Settings - Security Settings -

> Local Policies - User rights Assignment - "Allow log on through

> Terminal Services"

> and add the Remote Desktop Users group to the list of allowed users

> 3. add the Remote Desktop Users group to the permission list of the

> rdp-tcp connection

>

> If you are preparing a production DC or a production TS, I'd rather

> start afresh.

>

> _________________________________________________________

> 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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 14

> jan 2008 in microsoft.public.windows.terminal_services:

>

> > Yea, that is what I did, but that is what I didn't want to do.

> >

> > This is my first time diving into creating a server. What I

> > wanted to do is install the Virtual Server and create all my VM

> > for all the Server needs and just use the Host Server for the

> > Terminal Server.

> >

> > Do I have to reinstall everything to do this or can I uninstall

> > the Server Configuration?

>

[Guest Eric]

Re: Problems with logging in using Remote Connection....

 

I mean Server 2003 R2 not 2005.

 

--

Eric Miller

 

 

"Vera Noest [MVP]" wrote:

> Depends on your goal. If you are just testing, you can either

> continue to run TS on your DC, or uninstall TS or demote the server

> to a standalone server. To give users access to a TS running on a

> DC, you have to do the following:

> 1. add the users to the built-in domain local Remote Desktop Users

> group in AD

> 2. enable the following setting in the Default Domain Controller

> Policy:

> Computer Configuration - Windows Settings - Security Settings -

> Local Policies - User rights Assignment - "Allow log on through

> Terminal Services"

> and add the Remote Desktop Users group to the list of allowed users

> 3. add the Remote Desktop Users group to the permission list of the

> rdp-tcp connection

>

> If you are preparing a production DC or a production TS, I'd rather

> start afresh.

>

> _________________________________________________________

> 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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 14

> jan 2008 in microsoft.public.windows.terminal_services:

>

> > Yea, that is what I did, but that is what I didn't want to do.

> >

> > This is my first time diving into creating a server. What I

> > wanted to do is install the Virtual Server and create all my VM

> > for all the Server needs and just use the Host Server for the

> > Terminal Server.

> >

> > Do I have to reinstall everything to do this or can I uninstall

> > the Server Configuration?

>

[Guest Vera Noest [MVP]]

Re: Problems with logging in using Remote Connection....

 

I doubt if your setup comes even near to being realistic.

All those virtual machine do have overhead costs, and your hardware

is simply not sufficient.

 

_________________________________________________________

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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 15

jan 2008 in microsoft.public.windows.terminal_services:

> Thanks MVP for the help! So I don't get to deep in confusing

> myself, I will start afresh and do it right from the beginning.

> I want the seperate production servers.

>

> This is my Goal:

> So I can better understand what I'm doing is ok, could I make

> production VM Servers (for the x32 Server 2005) each for (File

> Sever, Application Server (Web & Intranet), Remote Access/VPN

> Server, Domain Controller (Active Director) Server) to run on my

> x64 version of Server 2005?

>

> I don't want all the server types running at once on the host,

> but seperate as Guest in VM Servers. Just run the Terminal

> Server on the Host.

>

> If not what is the best setup for what I am trying to do,

> because for now I only have one cpu x64 AMD 300+MHz, 2+gb RAM

> (DDR400), 320 SATA Drive.

[Guest Eric]

Re: Problems with logging in using Remote Connection....

 

Ok thanks for helping relize this, because I wasn't sure if this could be

done with my current hardware.

 

....but after getting a good night sleep over my goal I came to grips as to

what I really want to do.

 

I reinstalled 2003 Server and next I'm going to install VS 2005:

1) Create a VM for my TS (this is where all my development software is going

to be install)

2) Create VM for my DC (this is where my production Web & Intranet will be)

 

right now it's just me, I have a small business, but later I will have

developers creating commercial software. My pro Web is where I will have my

software available for custumers to download & purchase.

 

I will be getting 3 additional SATA Drives with 4 additional nVidia SATA

RAID drives for data protection. Right now I just want to get a basic Server

running.

 

Does this sound more realistic?

 

--

Eric Miller

 

 

"Vera Noest [MVP]" wrote:

> I doubt if your setup comes even near to being realistic.

> All those virtual machine do have overhead costs, and your hardware

> is simply not sufficient.

>

> _________________________________________________________

> 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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 15

> jan 2008 in microsoft.public.windows.terminal_services:

>

> > Thanks MVP for the help! So I don't get to deep in confusing

> > myself, I will start afresh and do it right from the beginning.

> > I want the seperate production servers.

> >

> > This is my Goal:

> > So I can better understand what I'm doing is ok, could I make

> > production VM Servers (for the x32 Server 2005) each for (File

> > Sever, Application Server (Web & Intranet), Remote Access/VPN

> > Server, Domain Controller (Active Director) Server) to run on my

> > x64 version of Server 2005?

> >

> > I don't want all the server types running at once on the host,

> > but seperate as Guest in VM Servers. Just run the Terminal

> > Server on the Host.

> >

> > If not what is the best setup for what I am trying to do,

> > because for now I only have one cpu x64 AMD 300+MHz, 2+gb RAM

> > (DDR400), 320 SATA Drive.

>

[Guest Vera Noest [MVP]]

Re: Problems with logging in using Remote Connection....

 

Eric, we've come a long way from my field of expertise, so you

should seek other advice as well.

That said, I think you are making some serious design errors:

* you can't combine your webserver with your DC! Your DC should be

the most safeguarded server of them all, because without the DC,

your whole domain is gone. Your webserver, on the other hand,

should be accessible from the Internet. It must be in your DMZ

(with a firewall between your DC and the webserver).

* I'm not sure if it is feasible at all to run your DC on a VM.

* developers creating software usually need *lots* of resources,

which your server doesn't have. And usually, they are *not* happy

working on a Terminal Server, because of the very special nature of

a TS regarding installing and running applications. Most likely,

your developers will need their own, powerful workstation.

 

I think that you can save yourself a lot of money and time by

hiring a consultant, and let them write a proposal listing the

minimum hardware requirements to reach your goal.

_________________________________________________________

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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 15

jan 2008 in microsoft.public.windows.terminal_services:

> Ok thanks for helping relize this, because I wasn't sure if this

> could be done with my current hardware.

>

> ...but after getting a good night sleep over my goal I came to

> grips as to what I really want to do.

>

> I reinstalled 2003 Server and next I'm going to install VS 2005:

> 1) Create a VM for my TS (this is where all my development

> software is going to be install)

> 2) Create VM for my DC (this is where my production Web &

> Intranet will be)

>

> right now it's just me, I have a small business, but later I

> will have developers creating commercial software. My pro Web

> is where I will have my software available for custumers to

> download & purchase.

>

> I will be getting 3 additional SATA Drives with 4 additional

> nVidia SATA RAID drives for data protection. Right now I just

> want to get a basic Server running.

>

> Does this sound more realistic?

[Guest Eric]

Re: Problems with logging in using Remote Connection....

 

Thanks for shedding more lite on how this works. I'm new to this part of

administration. I want to do this myself to learn every aspect of my server.

Not in a hurry in hiring anyone yet. I'm just that type of person that

wants to know everything about what I'm trying to accomplish.

 

With your repsonse give me more understand on how to do what I need to do to

make my server work properly with my goals. This mean I have to get a

serperate server for my DC, and serperate PC's for my developers, plus other

servers for Files, Media and so forth.

 

Thanks for the help! Will be back for more help on TS ok...

--

Eric Miller

 

 

"Vera Noest [MVP]" wrote:

> Eric, we've come a long way from my field of expertise, so you

> should seek other advice as well.

> That said, I think you are making some serious design errors:

> * you can't combine your webserver with your DC! Your DC should be

> the most safeguarded server of them all, because without the DC,

> your whole domain is gone. Your webserver, on the other hand,

> should be accessible from the Internet. It must be in your DMZ

> (with a firewall between your DC and the webserver).

> * I'm not sure if it is feasible at all to run your DC on a VM.

> * developers creating software usually need *lots* of resources,

> which your server doesn't have. And usually, they are *not* happy

> working on a Terminal Server, because of the very special nature of

> a TS regarding installing and running applications. Most likely,

> your developers will need their own, powerful workstation.

>

> I think that you can save yourself a lot of money and time by

> hiring a consultant, and let them write a proposal listing the

> minimum hardware requirements to reach your goal.

> _________________________________________________________

> 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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 15

> jan 2008 in microsoft.public.windows.terminal_services:

>

> > Ok thanks for helping relize this, because I wasn't sure if this

> > could be done with my current hardware.

> >

> > ...but after getting a good night sleep over my goal I came to

> > grips as to what I really want to do.

> >

> > I reinstalled 2003 Server and next I'm going to install VS 2005:

> > 1) Create a VM for my TS (this is where all my development

> > software is going to be install)

> > 2) Create VM for my DC (this is where my production Web &

> > Intranet will be)

> >

> > right now it's just me, I have a small business, but later I

> > will have developers creating commercial software. My pro Web

> > is where I will have my software available for custumers to

> > download & purchase.

> >

> > I will be getting 3 additional SATA Drives with 4 additional

> > nVidia SATA RAID drives for data protection. Right now I just

> > want to get a basic Server running.

> >

> > Does this sound more realistic?

>

[Guest Vera Noest [MVP]]

Re: Problems with logging in using Remote Connection....

 

I understand your wish to do things yourself and learn, but

designing a network with an internal domain for your own employees

as well as an external website to sell your products is not a

trivial task.

 

If you have lots of money, time doesn't play a role and, most

important of all, you don't intend to make a living out of this

company, then go ahead and try it yourself.

 

But if you have any ideas of making a living based on this, then I

would really recommend hiring a consultant. It will save you *lots*

of money!

 

That said, feel free to come back here with more questions.

_________________________________________________________

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?RXJpYw==?= <Eric@discussions.microsoft.com> wrote on 17

jan 2008 in microsoft.public.windows.terminal_services:

> Thanks for shedding more lite on how this works. I'm new to

> this part of administration. I want to do this myself to learn

> every aspect of my server.

> Not in a hurry in hiring anyone yet. I'm just that type of

> person that

> wants to know everything about what I'm trying to accomplish.

>

> With your repsonse give me more understand on how to do what I

> need to do to make my server work properly with my goals. This

> mean I have to get a serperate server for my DC, and serperate

> PC's for my developers, plus other servers for Files, Media and

> so forth.

>

> Thanks for the help! Will be back for more help on TS ok...