OK, it's true, but we aren't simple customers. :P ;) -- Otto Horvath [MS MVP - Group Policy] On Fri, Mar 7, 2008 at 9:58 PM, Darren Mar-Elia <darren@xxxxxxxxxx> wrote: > OK. Well, good to know I guess. I wonder if the "correct" key would > enable more verbose behavior or maybe this is just a fallback (or maybe > something changed btw my information in Vista beta and RTM). At the time, > Microsoft told me that gpsvc.log was only useful for MS support and should > not be enabled by customers J. > > > > Darren > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *FlowMaN > *Sent:* Friday, March 07, 2008 12:55 PM > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: UserEnv... Finally gone from Vista? > > > > I tried it. Without the reg key, there is no gpsvc.log. After I have set > the key, the gpsvc.log appeared in the debug folder, and the > file's content & structure are similar than the old userenv.log. I don't > know the official statement about this behaviour. ;) > > > > -- > Otto Horvath > [MS MVP - Group Policy] > > On Fri, Mar 7, 2008 at 9:49 PM, Darren Mar-Elia <darren@xxxxxxxxxx> wrote: > > OK. Well the reg value that you put forward is not supposed to enable > verbose gpsvc.log logging, at least not according to what MS told me back > in the Vista beta days. That log requires a different reg hack. > > > > Darren > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *FlowMaN > *Sent:* Friday, March 07, 2008 12:46 PM > > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: UserEnv... Finally gone from Vista? > > > > Yes, there is no userenv.log at all, I mistyped the file name. :) > > > > *%Systemroot%\Debug\UserMode\gpsvc.log* > > -- > Otto Horvath > [MS MVP - Group Policy] > > On Fri, Mar 7, 2008 at 9:37 PM, Darren Mar-Elia <darren@xxxxxxxxxx> wrote: > > The last time I looked, userenv in Vista no longer held detailed GP > related data. That had all been moved to the Operational log and gpsvc.log, > which contains much more low level detail than userenv used to. > > > > Microsoft does provide a nifty command-line utility for view the > Operational Log data, called GPLogView. Its at www.codeplex.com/gplogviewand > in fact you can download its source code from there as well. It has some > cool features, including real-time monitoring of Ops Log data—you can > actually see the GP events scroll onto the screen as GP is refreshing. > > > > Darren > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Alan & Margaret > *Sent:* Friday, March 07, 2008 12:31 PM > > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: UserEnv... Finally gone from Vista? > > > > > > Gee Whiz. I thought I had tried that, but miss-spelt it. Now it works.., > Thanks > > > > > ------------------------------ > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *FlowMaN > *Sent:* Saturday, 8 March 2008 7:13 AM > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: UserEnv... Finally gone from Vista? > > > > Same reg key as Windows XP or Server 2003. > > > > *Hive: HKEY_LOCAL_MACHINE** > Key: Software\Microsoft\Windows NT\Current Version\Winlogon > Name: UserenvDebugLevel > Type: REG_DWORD > UserenvDebugLevel=30002* > > > > *File path:* > > *%Systemroot%\Debug\UserMode\Userenv.log* > > > -- > Otto Horvath > [MS MVP - Group Policy] > > > > > On Fri, Mar 7, 2008 at 9:12 PM, Alan & Margaret <syspro@xxxxxxxxxxxxxxxx> > wrote: > > Some of you may know of my free program that formats the UserEnv log so > that you can see what is happening with Group Policy Processing. > > > > When Vista was first released, the file was renamed to gpsvc.log with > minor changes to the format. > > > > My latest release of Vista seems to have removed it totally, placing > information in the event viewer instead. Does anyone know if there is a > registry key to reenable it… or is it gone for good? > > > > Alan Cuthbertson > > > ------------------------------ > > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). > ------------------------------ > > >