RE: Roaming profiles won't work unless client PCs are rebooted
- From: "TimB" <TimB@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 8 Sep 2005 02:39:03 -0700
Jenny you are a star - thankyou very much.
Deleting the duplicate profile image path registry entries has sorted my
customers problem and they are very happy. Thanks :-)
""Jenny wu [MSFT]"" wrote:
> Hi Tim,
>
> Thanks for posting here!
>
> These error logs indicate that the user profiles in your Server is either
> corrupted, or are not properly configured.
>
> Suggestion 1:
> ==================
> This can happen if some users'' ProfileImagePath registries are duplicated
> with other users'' ProfileImagePath. To resolve the issue, perform the
> following steps:
>
> WARNING: If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system. Microsoft
> cannot guarantee that you can solve problems that result from using
> Registry Editor incorrectly. Use Registry Editor at your own risk.
>
> 1. Run "WHOAMI /USER /SID" to determine the user''s correct SID.
>
> If you don''t have the whoami command tool, you can download and install it
> from:
> http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/whoami-o
> .asp
>
> Note: By default, it will install to C:\Program files\Resource Kit folder.
> To run it, go to Command Prompt and change the path to C:\Program
> Files\Resource Kit>. Then type "whoami /USER /SID" (without quotes) and
> press Enter. It should display the current user''s name and SID.
>
> 2. Check the ProfileImagePath value under the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\ProfileList\<SID>
>
> Note down this ProfileImagePath value.
>
> 3. Check the other ProfileList\<SID> keys for matching ProfileImagePath
> values and deleted those keys.
> Note: Please make sure you have backed up the registry key before you
> delete them.
>
> 4. Try to test, how about the result?
>
> Did you manually move your users'' profiles to another drive? If you have
> moved the Documents and Settings folder, it will lead to the issue. Moving
> the Documents and Settings folder in Windows server 2003/Windows XP to
> another drive is not supported by Microsoft. Although you can try the steps
> in the article below, we provide it for informational purposes only;
> Microsoft makes no guarantee that this configuration functions properly for
> Windows Server 20003/Windows XP.
> 236621 Cannot Move or Rename the Documents and Settings Folder
> http://support.microsoft.com/?id=236621
>
> Suggestion 2:
> ==================
> If the issue persists, I suggest that you create a new user and then copy
> the user profile. When copying, the following files should be excluded, see:
> - Ntuser.dat
> - Ntuser.dat.log
> - Ntuser.ini
>
> 811151 How to Copy User Data to a New User Profile
> http://support.microsoft.com/?id=811151
>
> Try to test, how about the result?
>
> I appreciate you time and effort. I am currently standing by for you about
> the test result. I am always happy to be of further assistance.
>
> 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/newsgroups/en-us/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.
>
> --------------------
> >Thread-Topic: Roaming profiles won't work unless client PCs are rebooted
> >thread-index: AcWdmSEN5uW+JlbUShaJcaYchXTsXQ==
> >X-WBNR-Posting-Host: 80.177.237.201
> >From: "=?Utf-8?B?VGltQg==?=" <TimB@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: Roaming profiles won't work unless client PCs are rebooted
> >Date: Wed, 10 Aug 2005 03:49:06 -0700
> >Lines: 55
> >Message-ID: <6F545683-85BA-4EC7-9A4A-40C30FEF1F6E@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:143031
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi
> >
> >I have 2003 SBS with 7 client workstations. Roaming profiles do work but
> >after a period of time, say 24 hours or less they stop working and when a
> >different user tries to log on they get the following error messages
> >
> >Event Type: Error
> >Event Source: Userenv
> >Event Category: None
> >Event ID: 1508
> >Date: 10/08/2005
> >Time: 07:18:05
> >User: NT AUTHORITY\SYSTEM
> >Computer: 08-006
> >Description:
> >Windows was unable to load the registry. This is often caused by
> >insufficient memory or insufficient security rights.
> >
> > DETAIL - The process cannot access the file because it is being used by
> >another process. for C:\Documents and Settings\steveb\ntuser.dat
> >
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> >
> >
> >Event Type: Error
> >Event Source: Userenv
> >Event Category: None
> >Event ID: 1502
> >Date: 10/08/2005
> >Time: 07:18:10
> >User: DASHSOUTHWESTLT\SteveBudge
> >Computer: 08-006
> >Description:
> >Windows cannot load the locally stored profile. Possible causes of this
> >error include insufficient security rights or a corrupt local profile. If
> >this problem persists, contact your network administrator.
> >
> > DETAIL - The process cannot access the file because it is being used by
> >another process.
> >
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> >
> >
> >There are 2 more similar messages which are Event ID's 1515 and 1511
> >afterwards.
> >
> >Rebootig the workstations sorts the problem.
> >
> >Of the 7 workstations 5 have this problem but the other 2 only have 1 user
> >so I suspect that the problem would happen on these also.
> >
> >Any help would be most appreciated.
> >
> >
>
>
.
- Follow-Ups:
- Re: Roaming profiles won't work unless client PCs are rebooted
- From: Jenny wu [MSFT]
- Re: Roaming profiles won't work unless client PCs are rebooted
- Prev by Date: device - (australia) smartphone or pda
- Next by Date: RE: ActiveSync Error with SBS2003 and ISA2004
- Previous by thread: device - (australia) smartphone or pda
- Next by thread: Re: Roaming profiles won't work unless client PCs are rebooted
- Index(es):
Relevant Pages
|
Loading
