[THIN] Re: Profile
- From: "Greg Moseley" <greg@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 11 Oct 2005 20:17:46 +0100
Only if the timestamp on the local cached profile is the same/newer:
This is an article from around the NT4 days, but I'm pretty sure it remained
the same for 2000.
Troubleshooting Roaming Profiles
Of course, things can go wrong, and roaming users get upset, angry, or
confused when that occurs. This section covers some of the most common
problems with roaming profiles. Before examining specific problems, however,
it's a good idea to look at what the operating system does with roaming
profiles.
There is a checklist the operating system follows in an effort to load the
appropriate profile and to save changes the roaming user might make to the
profile back to the roaming profile. Let's examine what happens when
everything goes smoothly before discussing the problems that can occur.
When a roaming user logs on, the system checks to see if the server-based
profile is available. If it is, the system checks the date/time stamp of the
hive file and then looks for a local profile for this user. Depending on
what is found, one of the following events occurs:
* If a local profile is found and the date/time stamp of the hive
file is later than the date/time stamp on the server-based hive, the local
profile is loaded and placed in the cache.
* If a local profile is found and it is older than the server-based
profile, the server-based profile is loaded and cached.
* If no local profile is found, the server-based profile is loaded
and cached.
When the user logs off, the profile that is in the cache is saved back both
to the server and to the local disk (a local profile is created if none had
been found during logon). As you can see, this pretty much ensures that the
most recent profile is saved on the server. The next time this user logs on
from any workstation, this new profile, containing all the changes the user
made, is loaded.
Thanks
Greg
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Matthew Shrewsbury
Sent: 11 October 2005 20:11
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Profile
My understanding is if there is a local copy Windows will always use that.
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Bill Beckett
Sent: Tuesday, October 11, 2005 3:06 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Profile
Right but what if you want to keep the copy of the profile there? Does the
TS server still pull from the file server and use that profile or does it
see the cached copy locally and use it?
On 10/11/05, Matthew Shrewsbury <MShrewsbury@xxxxxxxxxxxxxxx> wrote:
There is a GPO settings to delete profile on logoff.
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Bill Beckett
Sent: Tuesday, October 11, 2005 2:54 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Profile
Can someone just yes or no this for me?
Roaming profiles used on a file server. TS profile pointing to this
location. Terminal Server is W2K and is keeping a cached copy of the
profile.
Does the server always use the cached copy? I thought that the roaming
profile was pulled in, copied locally and then upon logoff, copied back out
to the TS profile location. This doesn't seem to be the case.
Other related posts:
