Prev: Sentinel service depends on the Parport service which failed to start
Next: SNMP service crashing
From: Brooster on 30 Aug 2006 19:05
I had a user call get escalated, the issue has occured with a different user now...

Idea's?
From: Vincent Xu [MSFT] on 31 Aug 2006 01:52
Hi Brooster,

Please send me some log file for troubleshooting:

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.
Use Registry Editor to add the following registry value (or modify it, if
the value already exists):
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
Value: UserEnvDebugLevel
Value Type: REG_DWORD
Value Data: 10002 (Hexadecimal)

UserEnvDebugLevel can have the following values:
NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000

The default value is NORMAL|LOGFILE (0x00010001).

Note To disable logging, select NONE (where the value is 0X00000000).

You can also combine the values. For example, you can combine VERBOSE
0x00000002 and LOGFILE 0x00010000 to get 0x00010002. So if
UserEnvDebugLevel is set with a value of 0x00010002, this turns on both
LOGFILE and VERBOSE. Combining these values is the same as using an OR
statement: 0x00010000 OR 0x00000002 = 0x00010002

The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log
file. If the Userenv.log exists and is greater than 300 KB, the existing
file will be renamed to Userenv.bak, and a new log file created.

Please send me the log via v-xuwen(a)microsoft.com


As well as, please help me confirm with your customer that when logged on ,
is the user prompted that the local is newer than the roam

Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
>>From: brooster(a)nospam.postalias (Brooster)
>>X-Newsreader: RssBandit/1.3.0.42 (.NET CLR 2.0.50727.42; WinNT 5.2.3790
Service Pack 1; http://www.rssbandit.org)
>>Subject: Re: Re: Re: Re: Re: RE: W2K3 x64 and roaming profile issues
>>References: <qwcYgJBzGHA.4464(a)TK2MSFTNGXA01.phx.gbl>
>>Message-ID: <OCy77iIzGHA.3656(a)TK2MSFTNGP04.phx.gbl>
>>Newsgroups: microsoft.public.windows.server.general
>>Date: Wed, 30 Aug 2006 16:05:05 -0700
>>NNTP-Posting-Host: s01060002b3924a1d.ed.shawcable.net 70.74.30.123
>>Lines: 1
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:103892
>>X-Tomcat-NG: microsoft.public.windows.server.general
>>
>>I had a user call get escalated, the issue has occured with a different
user now...
>>
>>Idea's?
>>

From: Vincent Xu [MSFT] on 3 Sep 2006 23:08
Hi Brooster,

thanks for your mail reply.

Actually, I noticed that you have done right step to resolve the "roaming
profile not updated" issue that : Use User Profile Hive Cleanup Service .
It is recommended because it helps to ensure user sessions are completely
terminated when a user logs off. System processes and applications
occasionally maintain connections to registry keys in the user profile
after a user logs off. In those cases the user session is prevented from
completely ending. This can result in problems when using Roaming User
Profiles in a server environment or when using locked profiles as
implemented through the Shared Computer Toolkit for Windows XP.

I suggest you install this utility on every computer using roaming profile
to prevent such "roaming profile not updated" issue happen again.

Thanks.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
>>X-Tomcat-ID: 122771398
>>References: <qwcYgJBzGHA.4464(a)TK2MSFTNGXA01.phx.gbl>
<OCy77iIzGHA.3656(a)TK2MSFTNGP04.phx.gbl>
>>MIME-Version: 1.0
>>Content-Type: text/plain
>>Content-Transfer-Encoding: 7bit
>>From: v-xuwen(a)online.microsoft.com (Vincent Xu [MSFT])
>>Organization: Microsoft
>>Date: Thu, 31 Aug 2006 05:52:51 GMT
>>Subject: Re: Re: Re: Re: Re: RE: W2K3 x64 and roaming profile issues
>>X-Tomcat-NG: microsoft.public.windows.server.general
>>Message-ID: <Wmt94GMzGHA.400(a)TK2MSFTNGXA01.phx.gbl>
>>Newsgroups: microsoft.public.windows.server.general
>>Lines: 78
>>Path: TK2MSFTNGXA01.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:103912
>>NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>>
>>Hi Brooster,
>>
>>Please send me some log file for troubleshooting:
>>
>>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.
>>Use Registry Editor to add the following registry value (or modify it, if
>>the value already exists):
>>Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
>>NT\CurrentVersion\Winlogon
>>Value: UserEnvDebugLevel
>>Value Type: REG_DWORD
>>Value Data: 10002 (Hexadecimal)
>>
>>UserEnvDebugLevel can have the following values:
>>NONE 0x00000000
>>NORMAL 0x00000001
>>VERBOSE 0x00000002
>>LOGFILE 0x00010000
>>DEBUGGER 0x00020000
>>
>>The default value is NORMAL|LOGFILE (0x00010001).
>>
>>Note To disable logging, select NONE (where the value is 0X00000000).
>>
>>You can also combine the values. For example, you can combine VERBOSE
>>0x00000002 and LOGFILE 0x00010000 to get 0x00010002. So if
>>UserEnvDebugLevel is set with a value of 0x00010002, this turns on both
>>LOGFILE and VERBOSE. Combining these values is the same as using an OR
>>statement: 0x00010000 OR 0x00000002 = 0x00010002
>>
>>The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log
>>file. If the Userenv.log exists and is greater than 300 KB, the existing
>>file will be renamed to Userenv.bak, and a new log file created.
>>
>>Please send me the log via v-xuwen(a)microsoft.com
>>
>>
>>As well as, please help me confirm with your customer that when logged on
,
>>is the user prompted that the local is newer than the roam
>>
>>Thanks.
>>
>>Best regards,
>>
>>Vincent Xu
>>Microsoft Online Partner Support
>>
>>======================================================
>>Get Secure! - www.microsoft.com/security
>>======================================================
>>When responding to posts, please "Reply to Group" via your newsreader so
>>that others
>>may learn and benefit from this issue.
>>======================================================
>>This posting is provided "AS IS" with no warranties,and confers no
rights.
>>======================================================
>>
>>
>>
>>--------------------
>>>>From: brooster(a)nospam.postalias (Brooster)
>>>>X-Newsreader: RssBandit/1.3.0.42 (.NET CLR 2.0.50727.42; WinNT 5.2.3790
>>Service Pack 1; http://www.rssbandit.org)
>>>>Subject: Re: Re: Re: Re: Re: RE: W2K3 x64 and roaming profile issues
>>>>References: <qwcYgJBzGHA.4464(a)TK2MSFTNGXA01.phx.gbl>
>>>>Message-ID: <OCy77iIzGHA.3656(a)TK2MSFTNGP04.phx.gbl>
>>>>Newsgroups: microsoft.public.windows.server.general
>>>>Date: Wed, 30 Aug 2006 16:05:05 -0700
>>>>NNTP-Posting-Host: s01060002b3924a1d.ed.shawcable.net 70.74.30.123
>>>>Lines: 1
>>>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
>>>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.general:103892
>>>>X-Tomcat-NG: microsoft.public.windows.server.general
>>>>
>>>>I had a user call get escalated, the issue has occured with a different
>>user now...
>>>>
>>>>Idea's?
>>>>
>>
>>

From: Brooster on 4 Sep 2006 11:27
Vincent,

User ProfileHive Cleanup Service is currently only available for x86. This is installed on all the x86 machines. However, if you recall the machine affected runs x64.

Robin sent me a beta of 2.0 that supported x64, and I am having mixed results with, and seems to be better with it off. I let Robin know of my issues, and I haven't heard back.
From: Vincent Xu [MSFT] on 4 Sep 2006 21:17
Hi Brooster,

Thanks for your reply.

I'm sorry that I didn't mention that UPHClean v1.6d does not function under
Windows XP x64 Edition or Windows Server 2003 x64 Edition. UPHClean v2.0
will be supported under those operating systems. If you are interested in
helping with testing of v2.0 please email uphclean(a)microsoft.com.

I noticed that you already called our Microsoft CSS and work with an
engineer named Robin, right? Feel free to post back the results.

Thanks.



Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
>>From: brooster(a)nospam.postalias (Brooster)
>>X-Newsreader: RssBandit/1.3.0.42 (.NET CLR 2.0.50727.42; WinNT 5.2.3790
Service Pack 1; http://www.rssbandit.org)
>>Subject: Re: Re: Re: Re: Re: Re: RE: W2K3 x64 and roaming profile issues
>>References: <ptNv598zGHA.4548(a)TK2MSFTNGXA01.phx.gbl>
>>Message-ID: <OMoWjaD0GHA.4580(a)TK2MSFTNGP05.phx.gbl>
>>Newsgroups: microsoft.public.windows.server.general
>>Date: Mon, 04 Sep 2006 08:27:29 -0700
>>NNTP-Posting-Host: s01060002b3924a1d.ed.shawcable.net 70.74.30.123
>>Lines: 1
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:104212
>>X-Tomcat-NG: microsoft.public.windows.server.general
>>
>>Vincent,
>>
>>User ProfileHive Cleanup Service is currently only available for x86.
This is installed on all the x86 machines. However, if you recall the
machine affected runs x64.
>>
>>Robin sent me a beta of 2.0 that supported x64, and I am having mixed
results with, and seems to be better with it off. I let Robin know of my
issues, and I haven't heard back.
>>

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Sentinel service depends on the Parport service which failed to start
Next: SNMP service crashing