Understanding Mandatory vs Roaming profiles?

[Guest compsosinc@gmail.com]

We have a SBS Windows 2000 Domain Controller with a single Windows

2003 Terminal Server. We are setting up (10) XP-based computers with

(10) users that will login to the 2000 Domain to use the TS. They do

not need to use their local desktops/hardware for anything. They are

to be restricted to the using the TS and one or two TS apps, no

Internet, etc.

 

Since a user should not be changing their local profile, and since all

(10) computers/users should display the same TS profile, shouldn't we

use a mandatory profile for each user instead?

 

Thanks.

[Guest Lanwench [MVP - Exchange]]

Re: Understanding Mandatory vs Roaming profiles?

 

compsosinc@gmail.com wrote:

> We have a SBS Windows 2000 Domain Controller with a single Windows

> 2003 Terminal Server. We are setting up (10) XP-based computers with

> (10) users that will login to the 2000 Domain to use the TS. They do

> not need to use their local desktops/hardware for anything. They are

> to be restricted to the using the TS and one or two TS apps, no

> Internet, etc.

>

> Since a user should not be changing their local profile, and since all

> (10) computers/users should display the same TS profile, shouldn't we

> use a mandatory profile for each user instead?

>

> Thanks.

 

I don't like mandatory profiles - I think it makes it too hard to change

stuff later. But your question is a little misleading - if you use roaming

profiles on the LAN, you must not use the same profile path for TS. Set up

TS profiles in each user's ADUC properties - don't use the roaming profile

path. You don't want users sharing the profiles anyway - each user should

have his/her own. That has nothing to do with what they can see or access,

remember.

 

If you use group policy wisely, you should be able to lock down what they

see/do pretty easily...as well as use folder redirection for My Documents,

App Data, Desktop, to the file server. You might want to post in

m.p.windows.group_policy for more guidance there.....

[Guest Bart Van Vugt]

Re: Understanding Mandatory vs Roaming profiles?

 

I totally agree with Lanwench. You can also use hybrid profiles and use the

flexprofile kit from Login Consultants.

 

"Lanwench [MVP - Exchange]" wrote:

> compsosinc@gmail.com wrote:

> > We have a SBS Windows 2000 Domain Controller with a single Windows

> > 2003 Terminal Server. We are setting up (10) XP-based computers with

> > (10) users that will login to the 2000 Domain to use the TS. They do

> > not need to use their local desktops/hardware for anything. They are

> > to be restricted to the using the TS and one or two TS apps, no

> > Internet, etc.

> >

> > Since a user should not be changing their local profile, and since all

> > (10) computers/users should display the same TS profile, shouldn't we

> > use a mandatory profile for each user instead?

> >

> > Thanks.

>

> I don't like mandatory profiles - I think it makes it too hard to change

> stuff later. But your question is a little misleading - if you use roaming

> profiles on the LAN, you must not use the same profile path for TS. Set up

> TS profiles in each user's ADUC properties - don't use the roaming profile

> path. You don't want users sharing the profiles anyway - each user should

> have his/her own. That has nothing to do with what they can see or access,

> remember.

>

> If you use group policy wisely, you should be able to lock down what they

> see/do pretty easily...as well as use folder redirection for My Documents,

> App Data, Desktop, to the file server. You might want to post in

> m.p.windows.group_policy for more guidance there.....

>

>

>