Mandatory User Profiles stored on a server. What is best practice policy for profiles on the workstations?

If you set up a mandatory user profile stored on a server, and direct each
user to grab this profile when logging in, what is Msoft best practice for
dealing with any leftover user profiles sitting in Documents and Settings on
the workstations themselves? Should you delete them? What about any admin
account user profiles? Should those reside only on the server too?

Also, what if anything do you do with the "All Users" and "Default Users"
profiles that reside on the workstations?

Finally, what is best practice for setting up security on the server folders
holding these profiles? Give Authenticated Users Read Only to the folder,
and admins full access?

Thanks
R

I don't know of any best practice. It is a good practice to clean up old
local profiles just to save space and keep things clean. You can use delprof
for this.
Administrators should not need to retain a local profile on a workstation.
They have no reason to be logging on to it regularly or retaining specific
user settings on that one workstation.
All Users and Default User should remain.
Those permissions are OK,
http://technet.microsoft.com/en-us/l.../cc786301.aspx
Anthony,
http://www.airdesk.co.uk


"RS" <> wrote in message
news:7OFkl.46224$...
> If you set up a mandatory user profile stored on a server, and direct each
> user to grab this profile when logging in, what is Msoft best practice for
> dealing with any leftover user profiles sitting in Documents and Settings
> on the workstations themselves? Should you delete them? What about any
> admin account user profiles? Should those reside only on the server too?
>
> Also, what if anything do you do with the "All Users" and "Default Users"
> profiles that reside on the workstations?
>
> Finally, what is best practice for setting up security on the server
> folders holding these profiles? Give Authenticated Users Read Only to the
> folder, and admins full access?
>
> Thanks
> R
>
>
>
>