Jump to content

Terminal Server Profile


Recommended Posts

Posted

I configured a NLB Terminal Server. Users are in AD logging to domain

with Local Profile. I configured in user account properties 'Terminal

Services Profile' to folder in network for individual user. Each and

every time I'm logging to 2 nodes profile is working properly but

problem is when I log to other severs (Member) (didn't check in

PCs)Terminal servers profile will apply. Such as desktop, shortcuts

documents created on desktop etc. We want to isolate terminal server

profile and domain user profile.

Does some one know what's wrong with above mention issue? Or another

method of keep same profile for users even user log to different node?

  • Replies 4
  • Created
  • Last Reply
Guest Dragos CAMARA
Posted

RE: Terminal Server Profile

 

hi,

on computers where you dont want to apply set the "Only allow local user

profiles" in computer configuration/administrative templates/system/user

profiles.

--

Dragos CAMARA

MCSA Windows 2003 server

 

 

"Rush" wrote:

> I configured a NLB Terminal Server. Users are in AD logging to domain

> with Local Profile. I configured in user account properties 'Terminal

> Services Profile' to folder in network for individual user. Each and

> every time I'm logging to 2 nodes profile is working properly but

> problem is when I log to other severs (Member) (didn't check in

> PCs)Terminal servers profile will apply. Such as desktop, shortcuts

> documents created on desktop etc. We want to isolate terminal server

> profile and domain user profile.

> Does some one know what's wrong with above mention issue? Or another

> method of keep same profile for users even user log to different node?

>

>

Posted

Re: Terminal Server Profile

 

Hi CAMARA,

Thanks for the reply you mean by GP. I will test in LAB I hope this

will be great clue for me.

If I want to point the same share folder in network for default users

(new users logging first time) , I'm planning to add as

\\servername\tsprofile\%username%. Do have idea apply this setting

from GP to OU for specially made for Terminal server users or for the

terminal server? Your opinion is highly appreciated.

 

 

On Sep 3, 2:36 pm, Dragos CAMARA <drago...@remove-this.hotmail.com>

wrote:

> hi,

> on computers where you dont want to apply set the "Only allow local user

> profiles" in computer configuration/administrative templates/system/user

> profiles.

> --

> Dragos CAMARA

> MCSA Windows 2003 server

>

>

>

> "Rush" wrote:

> > I configured a NLB Terminal Server. Users are in AD logging to domain

> > with Local Profile. I configured in user account properties 'Terminal

> > Services Profile' to folder in network for individual user. Each and

> > every time I'm logging to 2 nodes profile is working properly but

> > problem is when I log to other severs (Member) (didn't check in

> > PCs)Terminal servers profile will apply. Such as desktop, shortcuts

> > documents created on desktop etc. We want to isolate terminal server

> > profile and domain user profile.

> > Does some one know what's wrong with above mention issue? Or another

> > method of keep same profile for users even user log to different node?- Hide quoted text -

>

> - Show quoted text -

Guest Dragos CAMARA
Posted

Re: Terminal Server Profile

 

hi,

weel that will depends of what users are using on TS's. On my organizations

there are some TS's where users are using for some kind of applications

(these are sets with local GP) and some TS's wich ar used by a lot of users

with the same OU and same applications - here i have GP set on OU of TS's.

 

computer configuration\administrative templates\windows components\terminal

services\set path for TS roaming Profiles.

--

Dragos CAMARA

MCSA Windows 2003 server

 

 

"Rush" wrote:

> Hi CAMARA,

> Thanks for the reply you mean by GP. I will test in LAB I hope this

> will be great clue for me.

> If I want to point the same share folder in network for default users

> (new users logging first time) , I'm planning to add as

> \\servername\tsprofile\%username%. Do have idea apply this setting

> from GP to OU for specially made for Terminal server users or for the

> terminal server? Your opinion is highly appreciated.

>

>

> On Sep 3, 2:36 pm, Dragos CAMARA <drago...@remove-this.hotmail.com>

> wrote:

> > hi,

> > on computers where you dont want to apply set the "Only allow local user

> > profiles" in computer configuration/administrative templates/system/user

> > profiles.

> > --

> > Dragos CAMARA

> > MCSA Windows 2003 server

> >

> >

> >

> > "Rush" wrote:

> > > I configured a NLB Terminal Server. Users are in AD logging to domain

> > > with Local Profile. I configured in user account properties 'Terminal

> > > Services Profile' to folder in network for individual user. Each and

> > > every time I'm logging to 2 nodes profile is working properly but

> > > problem is when I log to other severs (Member) (didn't check in

> > > PCs)Terminal servers profile will apply. Such as desktop, shortcuts

> > > documents created on desktop etc. We want to isolate terminal server

> > > profile and domain user profile.

> > > Does some one know what's wrong with above mention issue? Or another

> > > method of keep same profile for users even user log to different node?- Hide quoted text -

> >

> > - Show quoted text -

>

>

Posted

Re: Terminal Server Profile

 

Hi,

 

Thank you very much for your help. Things are working fine obviously

clean.

You done great job here. Have a nice day.

 

 

 

On Sep 3, 11:28 pm, Dragos CAMARA <drago...@remove-this.hotmail.com>

wrote:

> hi,

> weel that will depends of what users are using on TS's. On my organizations

> there are some TS's where users are using for some kind of applications

> (these are sets with local GP) and some TS's wich ar used by a lot of users

> with the same OU and same applications - here i have GP set on OU of TS's.

>

> computer configuration\administrative templates\windows components\terminal

> services\set path for TS roaming Profiles.

> --

> Dragos CAMARA

> MCSA Windows 2003 server

>

>

>

> "Rush" wrote:

> > Hi CAMARA,

> > Thanks for the reply you mean by GP. I will test in LAB I hope this

> > will be great clue for me.

> > If I want to point the same share folder in network for default users

> > (new users logging first time) , I'm planning to add as

> > \\servername\tsprofile\%username%. Do have idea apply this setting

> > from GP to OU for specially made for Terminal server users or for the

> > terminal server? Your opinion is highly appreciated.

>

> > On Sep 3, 2:36 pm, Dragos CAMARA <drago...@remove-this.hotmail.com>

> > wrote:

> > > hi,

> > > on computers where you dont want to apply set the "Only allow local user

> > > profiles" in computer configuration/administrative templates/system/user

> > > profiles.

> > > --

> > > Dragos CAMARA

> > > MCSA Windows 2003 server

>

> > > "Rush" wrote:

> > > > I configured a NLB Terminal Server. Users are in AD logging to domain

> > > > with Local Profile. I configured in user account properties 'Terminal

> > > > Services Profile' to folder in network for individual user. Each and

> > > > every time I'm logging to 2 nodes profile is working properly but

> > > > problem is when I log to other severs (Member) (didn't check in

> > > > PCs)Terminal servers profile will apply. Such as desktop, shortcuts

> > > > documents created on desktop etc. We want to isolate terminal server

> > > > profile and domain user profile.

> > > > Does some one know what's wrong with above mention issue? Or another

> > > > method of keep same profile for users even user log to different node?- Hide quoted text -

>

> > > - Show quoted text -- Hide quoted text -

>

> - Show quoted text -


×
×
  • Create New...