Roaming profiles and local profiles etc

  • Thread starter Thread starter Bob Williamson
  • Start date Start date
B

Bob Williamson

This may sound like a simple question, but.....

In the user data in AD you can define a "roaming Profile". The user logs on
workstations A and it shows the profile is of type "roaming".

On workstation A one can then make the profile "local", even though the
roaming profile is still defined for the user.

I made some modifications to a GPO to not copy the temp directories etc in
the roaming profiles. After which when the user logged on workstation A
using the locally cached roaming profile and then logged off, the temp
directories as defined in the GPO disappeared......

Please correct me if I m wrong:
1. If a user has a roaming profile defined in AD he/she will always have a
roaming profile regardless of how it is defined on the wkst.
2. If a wkst profile is defined as "local" instead of roaming it will log
the user in without accessing eth roaming data.

The question is what happens when he/she logs out? Will it overwrite the
data that is on the network?

I perfect example of this is someone logs on to their local machien 90% of
the time. The other 10% they roam...

Thanks,
Bob
 
This may sound like a simple question, but.....
In the user data in AD you can define a "roaming Profile". The user logs on
workstations A and it shows the profile is of type "roaming".
Click to expand...
On workstation A one can then make the profile "local", even though the
roaming profile is still defined for the user.
Click to expand...

Yes, that confuses a lot of people -- the "machine specific" setting is
if you want that profile to be LOCAL just on THAT computer.

I have tons of stuff installed on my Demo machine and I don't want those
shortcuts interfering with my REAL profile (that roams) so I use it. I
could just use another account but this is another way at the problem.
I made some modifications to a GPO to not copy the temp directories etc in
the roaming profiles. After which when the user logged on workstation A
using the locally cached roaming profile and then logged off, the temp
directories as defined in the GPO disappeared......

Please correct me if I m wrong:
1. If a user has a roaming profile defined in AD he/she will always have a
roaming profile regardless of how it is defined on the wkst.
Click to expand...

No, you can convert it on the workstation to Local and then THAT
machine will not participate in the roaming nature.
2. If a wkst profile is defined as "local" instead of roaming it will log
the user in without accessing eth roaming data.
Click to expand...

This is correct -- it's there to OVERRIDE the roaming nature from the
domain so you don't mess up the profile on one machine with the others.
The question is what happens when he/she logs out? Will it overwrite the
data that is on the network?
Click to expand...

Nope -- it's EITHER roaming or local, not both.
I perfect example of this is someone logs on to their local machien 90% of
the time. The other 10% they roam...
Click to expand...

It's more like, if they want the roaming profile on 9 machines but not on
number
10 because it is special; or they don't want the settings on number 10 to
mess
up 1-9.
 
Back
Top