Disabling the download / upload of roaming profiles

[Guest]

Archived from groups: microsoft.public.windows.server.general,microsoft.public.windowsnt.domain (More info?)

When a user logs on the Win2k roaming profile is downloaded and cached
locally to C:\Documents and Settings, when the user logs off the server
profile is updated and the local copy is deleted. So far, everything works
quite normal.

My proplem occurs when a users logs on to two machines at the same time.
Both clients download one copy each. Because all changes are done to the
local copies, the user creates two different inconsistent versions of his
profile while he works. When the user logs off from the second client, this
copy is stored to the server, which means that all earlier changes from the
first client are overwritten. Is there any option which disables the local
profile caching totally, so that the user directly works in
\\server\\%username%? I know that means a lot of network traffic, but every
change is immediatly visible to every client.

Tanks, Matthias

 

[Guest]

Archived from groups: microsoft.public.windows.server.general,microsoft.public.windowsnt.domain (More info?)

Matthias Nagel wrote:
> When a user logs on the Win2k roaming profile is downloaded and cached
> locally to C:\Documents and Settings, when the user logs off the
> server profile is updated and the local copy is deleted. So far,
> everything works quite normal.
>
> My proplem occurs when a users logs on to two machines at the same
> time. Both clients download one copy each. Because all changes are
> done to the local copies, the user creates two different inconsistent
> versions of his profile while he works. When the user logs off from
> the second client, this copy is stored to the server, which means
> that all earlier changes from the first client are overwritten. Is
> there any option which disables the local profile caching totally, so
> that the user directly works in \\server\\%username%? I know that
> means a lot of network traffic, but every change is immediatly
> visible to every client.

My preference is to instruct users not to log into two computers
simultaneously. Explain that the "last one out" wins -

If there's really some need for them to do this, you might want to force
mandatory profiles (rename the profile's ntuser.dat to ntuser.man on the
server, while the user is not logged in). They won't be able to make any
profile changes at all this way.

>
> Tanks, Matthias

 

[Guest]

Archived from groups: microsoft.public.windows.server.general,microsoft.public.windowsnt.domain (More info?)

> When a user logs on the Win2k roaming profile is downloaded and cached
> locally to C:\Documents and Settings, when the user logs off the server
> profile is updated and the local copy is deleted. So far, everything works
> quite normal.
>
> My proplem occurs when a users logs on to two machines at the same time.
> Both clients download one copy each. Because all changes are done to the
> local copies, the user creates two different inconsistent versions of his
> profile while he works. When the user logs off from the second client, this
> copy is stored to the server, which means that all earlier changes from the
> first client are overwritten. Is there any option which disables the local
> profile caching totally, so that the user directly works in
> \\server\\%username%? I know that means a lot of network traffic, but every
> change is immediatly visible to every client.


As Lanwench said, it's best if they don't log into multiple systems.
I played with some tips I found at JSI to not allow users to log onto
multiple systems, but I got mixed results with them... sometimes they
work, sometimes they don't...