HI Daren,
Thanks for posting here!
For your description, I understand that the user can not apply roaming
profile after the workstation upgraded from Windows 2000 to XP. If I am off
base, please don't hesitate to let me know.
Roaming user profiles enable users to log on to computers in a domain while
preserving their user profile settings. User profiles are stored at an
administrator specified server location. When a user logs on and has been
authenticated within the directory service, the user profile, including
user settings and documents, are copied to the local computer. User profile
changes made on the local computer are then captured. Changes will then be
copied to the user profile stored on the server and be applied the next
time the user logs on.
Based on my experience, the issue should be caused by access permissions to
the roaming profile. Let us do some tests to try to isolate the issue:
1. Could the user access the shared folder directly? Try to access the
roaming profile using UNC path, such as: \\Server\ShareName\UserName, can
you access it?
2. Try to logon the server box using domain admin account to check the
shared folder permissions to ensure the user account has Full Control
permission to the folder. If not, try to verify to see if the issue be
fixed.
3. If it is not above situation, please try to refresh the user account
permissions to see if any thing works well now.
To refresh user account permissions:
a. Start Server Management console -> Users
b. Click the user account and then click Change User Permissions link to
refresh the user account permissions.
And then re-logon the workstation use the user account to test, how about
the result?
4. Try to logon the workstation use another user account to test, how about
the result? Does it can apply its roaming profile to the workstation?
More information:
To create a roaming user profile:
1. Click Start, point to Administrative Tools and then click Active
Directory Users and Computers.
2. Expand applicable domain, expand applicable container (such as Users),
in the details section, right-click the applicable user account, and then
click Properties.
3. Click the Profile tab.
4. In Profile path, type the path information.
Use a full path in each user account:
\\Server\ShareName\UserName
The user profile path location can be on any server. It does not have to be
a domain controller. When the user logs on, Windows checks the user''s
account to see if a user profile path exits. If it does, the user profile
is located by the system and copied to the local computer.
Additional information:
294887 How to Check User Profiles on a Windows XP-Based Computer
http://support.microsoft.com/?id=294887
312138 HOW TO: Switch Between a Local and Roaming User Profile on a Mobile
http://support.microsoft.com/?id=312138
NOTE:
1. Do not use Offline Folder caching on roaming user profile shared
directories.
It is important to turn off Offline Folder caching for shared directories
where roaming user profiles are stored. If you do not turn off Offline
Folder caching for a user''s profile, you might experience synchronization
problems when both Offline Folders and roaming user profiles try to
synchronize the files in a user''s profile. This does not affect your
ability to use Offline Folders with redirected folders such as My
Documents.
2. Do not use Encrypted File System (EFS) on files in a roaming user
profile.
The Encrypted File System (EFS) is not compatible with roaming user
profiles. If you encrypt profile folders or files in the user profile using
EFS, the user''s profile will not roam.
3. Do not set disk quotas too low for users with roaming user profiles.
If a user''s disk quotas are set too low, roaming user profile
synchronization might fail. Make sure enough disk space is allocated to
allow the system to create a temporary duplicate copy of a user''s profile.
The temporary profile is created in the user''s context as part of the
synchronization process, so it debits the user''s quota.
4. When creating a roaming profile shared directory, limit access to only
those users that need access.
- Because a users roaming profile can contain personal information such as
confidential documents and EFS certificates, care should be taken to
protect access to the shared directory. Restrict access to the shared
directory to only those users that need access. You can also create a
security group for users that have profiles on a particular shared
directory, and limit access to only those users.
- Only give users the minimum amount of permissions needed.
- When creating the shared directory, hide it by putting a $ after the
share name. This hides the shared directory from casual browsers, and it
will not be visible in My Network Places.
5. Use at least Windows 2000 servers to host user roaming profile shared
directories.
Because a users roaming profile contains personal information which is
copied to and from a client computer, and the server hosting the roaming
profile, it is important to ensure that data is protected as it travels
over the network. Potential threats to the privacy and integrity of a
user''s data come from intercepting the data as it passes over the network,
tampering with the data as it passes over the network, and spoofing the
server hosting the user''s data. Features such as Kerberos, IPSec, and
Server Message Block (SMB) signing included in Windows 2000 and the Windows
Server 2003 family can help to secure a user''s data.
6. Always use the NTFS file system for volumes holding user''s data.
Configure servers hosting roaming profiles to use the NTFS File System.
Unlike FAT, NTFS supports Discretionary access control lists (DACLs) and
system access control lists (SACLs), which control who can perform
operations on a file and what events will trigger logging of actions
performed on a file.
How to configure a user account to use a roaming user profile in Windows
Server 2003, Windows 2000 Server, or Windows NT 4.0
http://support.microsoft.com/?id=316353
Hope above information helps! I am happy to be assistance of you and
looking forward to your reply!
Have a nice day!
Best Regards,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! -
www.microsoft.com/security
================================================== ====
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities...s/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Lanwench [MVP - Exchange]"
< ahoo.com>
>References: <0330F0D4-2D8C-4353-BEE0->
>Subject: Re: Roaming Profile Question
>Date: Tue, 18 Oct 2005 10:52:53 -0400
>Lines: 23
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OP2XaQ$>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: cpe-24-193-74-240.nyc.res.rr.com 24.193.74.240
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:162320
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>
>
>In news:0330F0D4-2D8C-4353-BEE0-,
>Daren <> typed:
>> I have user who's PC I have upgraded from W2k to XP Pro.
>>
>> Everytime the user logs off and back on all their desktop settings
>> switch back to default. I am sure it is something on the server but
>> what?
>>
>> Daren
>
>User profiles aren't compatible between OS versions - although I've been
>able to make the same kind of 'one time' switch, you may be best off
>creating a brand-new profile for the user.
>
>That said:
>Check the event logs on the workstation for userenv errors, d/l & install
>the user profile hive cleanup tool from MS, and make sure the profile size
>is TINY. Use folder redirection for My Documents and tell users never to
>store items on their desktops (shortcuts are fine).
>
>
>
Similar Threads
Linear Mode
