Caching of user profiles on local machines, with roaming profiles.

[sspfusion]

Hi guys,

One of these questions everyone asks, but to be be fair never have really got an accurate answer - any advice appreciated.

Basically, with roaming profiles enabled for users directed to a profile share - there is no problem with user files being synced there on logon and logoff. Thats all good, but the issue of files mainly being cache on the local workstation when the user is logged on until logoff and the fact that the files are left there after wards is a little annoying.

Has anyone found a way around this or is there a proper way of sorting it out so that user profiles are regularly synced from the profile share and the same for the local files cached on the local machine

As i say, any advice appreciated.

Fusion

 

[RLEE5]

Greetings:
In my last life (in the Air Force), I had multiple machines that were accessed by multiple users. I had to set the systems to delete the local copy of the profile on logoff. (

http://www.microsoft.com/resources/...n/Windows/2000/server/reskit/en-us/gp/66.asp)

This worked OK, but it produced ALLOT of network traffic at certain times of day. Also, you had to be careful about backing up the server(s) where the profiles resided, and figure out a way to keep thier profiles from getting too big (temp internet files, etc)

R.Lee
MIS

 

[sspfusion]

Thanks for the advice there - will follow up further. To be completely honest thats clearly the reason why cached profiles done i guess so that net traffic is cut down, which is a good idea and will work great on larger networks.

But to be completely honest with you - its a bit of a pain, alot of users have access to local drives on a number of workstations.. and not sure that those folders should reside there really.

alot of my users are moving around from station to station anyway.. so by the time they need to recall profiles locally they need to be sync from server again so its catch 22 really.

But thanks again, appreciate the response.