{"id":164,"date":"2016-04-11T03:00:26","date_gmt":"2016-04-11T03:00:26","guid":{"rendered":"http:\/\/eventlogxp.com\/blog\/?p=164"},"modified":"2016-04-11T09:58:52","modified_gmt":"2016-04-11T09:58:52","slug":"event-log-explorer-forensic-edition-preview","status":"publish","type":"post","link":"https:\/\/eventlogxp.com\/blog\/event-log-explorer-forensic-edition-preview\/","title":{"rendered":"Event Log Explorer Forensic Edition Preview"},"content":{"rendered":"

Several days ago, we published a preview of the new edition of Event Log Explorer software \u2013 Forensic Edition! Here I will show what benefits you can get from this edition. First, I should say that currently it is fully compatible with the standard edition of Event Log Explorer \u2013 it uses the same workspace, the same settings and currently the same registration key. By default, it installs itself into another folder, so you can use both editions concurrently.\u00a0By the way, the forensic edition preview is available at
\nhttp:\/\/eventlogxp.com\/download\/elex_fe_setup.exe<\/a><\/p>\n

What should you pay attention to?<\/h3>\n

You can find a new button on the tool bar \"add\u00a0– Add imaged computer.<\/p>\n

How it works. When you have a forensic image, you can mount it as a disk on your computer. And this command lets you add this imaged computer to the tree, and then view event logs from it.<\/p>\n

Example: <\/em>
\nI currently don’t have forensic images, but I have an old hard drive and connected it to my computer for tests. It is drive E:. I click “Add imaged computer” button and get this dialog:
\n\"Addimaged
\n<\/a>Event Log Explore tries to detect a mounted system drive automatically \u2013 it found it in my case, but if it wouldn’t find, just type correct path to the Windows folder on the mounted disk.<\/p>\n

Type any name in “Friendly name” field, and press OK.<\/p>\n

Now you can see that this “computer” has been added to the tree and you can open it and view event logs.\"forensic
\n<\/a>Let’s try to open any log from this imaged computer, e.g. Application. Double click on Application and the event log will appear as a log file.
\n\"forensic
\n<\/a>Pay attention to the icon that appears on the log icons area. Commonly it appears when you set a description server. But now it notifies you that Event Log Explorer will try to get descriptions from the mounted disk, when if it failed to find them locally. Whenever Event Log Explorer tries to get event description, it will try to get it locally first (as always), but if the description is not available, it will open registry on the mounted disk, find a resource file that contains event description and try to extract the description from this file. Note that if you research this disk not only with help of Event Log Explorer, but with e.g. Registry Editor and opened registry files (loaded them as hives), you should unload the hives, or Event Log Explorer won’t be able to open them. If you want disable \u00a0getting descriptions from the imaged computer, just double click on that icon and uncheck “If no description available, get it from imaged disk” option.<\/p>\n

What else<\/h3>\n

We disabled functionality that lets you modify event logs, such us clear log command, modifying event log properties.<\/p>\n

What’s next?<\/h3>\n

We are planning to add the following features to forensic edition:<\/p>\n