Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / CLR / October 2005

Tip: Looking for answers? Try searching our database.

Security for remote EventLog access?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
JV - 20 Oct 2005 14:58 GMT
It's great that the CLR gives us this cool EventLog object for managing
event logs.   And they even give you this cool property "MachineName" to
allow you to deal with event logs on a remote server.

But what access rights are needed by an application if it is to do this?
THAT information is hard to come by.  I have yet to find a clear and concise
explanation.  You have to piece together information from multiple pages.
And to complicate things even more, changes to Win2003 security complicate
this question.

Anyone know of a good writeup on this?  Hey, Microsoft!
Richard Grimes - 20 Oct 2005 22:06 GMT
> It's great that the CLR gives us this cool EventLog object for
> managing event logs.   And they even give you this cool property
> "MachineName" to allow you to deal with event logs on a remote server.

Its good that they created a way to *read* the event log. Its just a
pity that they mad such a mess of *writing* to it. IMO it was simply a
lazy developer at Microsoft not understanding how the event log works.
They have trie to make ammends in Whidney, but the damage has already
been done, and in my opinion they may as well scrap the event log and
come up with something else.

> But what access rights are needed by an application if it is to do
> this? THAT information is hard to come by.  I have yet to find a
> clear and concise explanation.  You have to piece together
> information from multiple pages. And to complicate things even more,
> changes to Win2003 security complicate this question.

As I said, I think the people involved don't understand the event log.

You need to have to be in the Administrators group on the remote
machine. That's simple to do if you are running under a domain account.
If you are in a workgroup there's a trick with XP - make sure that you
have an account on the remote machine with the same name and password as
your account and put that in the Administrators group. Also make sure
that you've got the appropriate ports open.

Richard
Signature

http://www.grimes.demon.co.uk/workshops/fusionWS.htm
http://www.grimes.demon.co.uk/workshops/securityWS.htm


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.