Re: Roaming profile in problem

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 02/19/05 

Date: Sat, 19 Feb 2005 12:43:41 -0500

danieltan@time.net.my wrote:
> After i created the roaming profile in win2000 server AD domain users
> and computers , when my user logged on, it has the following error. I
> have shared the folder and make it full rights for everyone. I even
> added the user to administrator groups. Pls help. Thanks
>
>
> "Windows cannot locate the server copy of your roaming profile and is
> attempting to log you on with your local profile. Changes to the
> profile will not be copied to the server when you logoff. Possible
> causes of this error include network problems or insufficient security
> rights."
>
>
> Regards
> Daniel

General tips:

1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing.
2. Make sure the share permissions on profiles$ indicate everyone=full
control. Set the NTFS security to administrators, system, and users=full
control.
3. In the users' ADUC properties, specify \\server\profiles%\%username% in
the profiles field
4. Have each user log into the domain once from their usual workstation
(where their existing profile lives) and log out. The profile is now
roaming.

Notes:

* Make sure users understand that they should never log into multiple
computers at the same time when they have roaming profiles (unless you make
the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't
change them). Explain that the
last one out
 wins, when it comes to uploading the final, changed copy of the profile.

* Keep your profiles TINY. Redirect My Documents
 to a subfolder of each user's home directory on the server - either via
group policy (folder redirection) or manually (less advisable). If you
aren't going to also redirect the desktop using policies, tell people that
they are not to store any files on the desktop or you will beat them with a
stick. Big profile=slow login/logout, and possible profile corruption.

* Note that user profiles are not compatible between different OS versions,
even between W2k/XP. Keep all your computers. Keep your workstations as
identical as possible - meaning, OS version is the same, SP level is the
same, app load is (as much as possible) the same.

* Do not let people store any data locally - all data belongs on the server.

Relevant Pages

  • RE: redirected-redirected folders
    ... The SBS server denies access to these files so his logout sycronization ... local workstation and checked the files and folders the syncronization ... is having this problem is also set up with a roaming profile. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2 Domains
    ... server in the child domain, if thats ok?, ... don't have Exchange in the picture yet. ... Yes....but you don't want a user in one location dragging a roaming profile ...
    (microsoft.public.exchange.setup)
  • RE: need to migrate a older win 2003 srvr sbs to newer one
    ... as I assume I should reading upon Windows Server 2003 inside out book. ... there are three method to move the SBS 2k3 to new ... Also check the path of the public folder database ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.migration)
  • Re: Connecting a remote workstation to a domain
    ... then ship to the remote office but the remote office computers were ... do this using a profile pre-configured on the server LAN then copied ... Do this *before* the users' roaming profile folders ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 changed hardware
    ... For your situation, the old server hardware has failed, we only have to do ... the Disaster Recovery of SBS if you have full backup of your SBS. ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)