You may find it better not to have the users store documents in their profile
at all, but this can be difficult if your users insist on saving documents on
their desktop, or the "my documents" folder is still part of their profile
and not their homedrive.
If you have not already been here, take a look at
http://www.microsoft.com/windowsserv...anage_faq.mspx
this document discusses using redirected folders, so documents are saved to
the users homedrive and not their profile
Advantage - You are not relying on the profile being written back to the
server for the document to be saved
Logon/off speed should be greatly decreased - the documents will not be
copied from the server each time
Disadvantage - if the user has a slow link to their homedrive (or where ever
you redirect the folders) then it could impact the responsiveness of their
applications when accessing these files
hope this helps
ewan
"Alexandru TUDOSE" wrote:
> I have a small computer network with a Windows 2003 Small Bussines Server /
> Active Directory. The users have their roaming profiles stored on a hard
> disk on the server.Normally, when the users are logging off, their profiles
> on the server must be updated (the new files created on the workstations
> must be copyed, the erased files on the workstations must be erased on the
> server, and so on ...). But, sometimes, if a user erase a file the change is
> not reflected on the server when the user log off. After he/she log on again
> the file is copyed again on the local profile (C:\Documents and Setting....)
> on the workstation. This is very unpleasent for the users. Does anyone have
> some information about this problem ?
> Best regards,
> Alexandru TUDOSE
>
>
>