Re: EventLog - Writing to Application Log
From: Drew Cooper [MSFT] (dcoop_at_online.microsoft.com)
Date: 02/08/04
- Next message: David Barnes: "SecureSystemPartition value in securit policy .inf files"
- Previous message: Eric Chamberlain: "Re: Single signon with kerberos option/directions"
- In reply to: Roger Abell [MVP]: "Re: EventLog - Writing to Application Log"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 7 Feb 2004 17:31:31 -0800
Hey - you're right. They only removed AN - I somehow mis-remembered it as
both and when I skimmed over the linked doc I read what I expected to see.
:-(
Thanks for keeping me honest.
-- Drew Cooper [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "Roger Abell [MVP]" <mvpNoSpam@asu.edu> wrote in message news:OGLalda7DHA.632@TK2MSFTNGP12.phx.gbl... > Hi Drew, > > The ref in MSDN you cite actually seems to say BG is still > covered within WD in XP, 2003. It is just AN that is no longer > included. This was part of removing anonymous sessions > from Everyone, but Guest is still included. > > Roger > "Drew Cooper [MSFT]" <dcoop@online.microsoft.com> wrote in message > news:OPhlfG46DHA.1804@TK2MSFTNGP12.phx.gbl... > > The registry settings are picked up when the service starts. The eventlog > > service is not a stoppable service. If it were, you could stop and > restart > > to pick up registry changes. As it is, the service only stops when you > shut > > down, thus a reboot is needed to pick up the changes. > > Why it doesn't poll the registry I don't know. > > > > Builtin Guest not in WD on XP, 2003 as documented here: > > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/kmarch/hh/kmarch/devobjts_5e07.asp > > (I don't know why the change was made.) > > -- > > Drew Cooper [MSFT] > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > > > > "Mauro" <mauro_c@mpt-ltd.com> wrote in message > > news:ulpyZmx6DHA.360@TK2MSFTNGP12.phx.gbl... > > > Hi, > > > > > > We've taken across a VB6 DLL from W2K to Windows 2003 and are no longer > > able > > > to write to the event log. From Q251264 we have verified that under W2K > > the > > > correct permissions needed to be assigned to the GUEST account group, > and > > > are saved in > > > > > > > > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\Re > > > strictGuestAccess > > > > > > We've looked up in MSDN and found that new registry keys settings have > > been > > > defined and, in particular(search for "EventLogging - Event Logging > > > Security"). > > > > > > In particular we have modified the string in the key: > > > > > > > > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\Cu > > > stomSD > > > > > > so that AN(Anonymous) and BG (Builtin Guests) have write permission. > > > > > > CRITICISM: Microsoft fails to tell you that you need to reboot the > server > > > for the new registry settings to take effect > > > > > > Quetion1: Why is the BG group not part of the WORLD account, which as > MSDN > > > indicates, should have read/write privileges by default??? > > > > > > > > > > > >
- Next message: David Barnes: "SecureSystemPartition value in securit policy .inf files"
- Previous message: Eric Chamberlain: "Re: Single signon with kerberos option/directions"
- In reply to: Roger Abell [MVP]: "Re: EventLog - Writing to Application Log"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|