Skip to main content

Filter MsiInstaller installation in Event viewer


How to filter or check successful msi installation on a Windows system?

There are quite a lot of ways to filter event viewer, it will solely depend on the taste of the person doing the event viewer audit.

It can be done via PowerShell, XML query, or use command line tools and other methods which the Sys Admin feels comfortable doing.

But when it comes to auditing logs, it’s a tedious task and takes a lot of time and depends on the raw data that you have so you exactly know what you’re searching for.

Command line still a useful tool since it comes handy, you just open the command prompt window and type the command and get the output.

The hardest part is how you digest or do another filtering on the output since it might be convoluted with lots of data. But don’t depend on a single tool, make use of whatever you have on your system and other tools available on the net.

This command line below filters the MsiInstaller for event ID 1033.

wevtutil qe application /q:"*[System[Provider[@Name='MsiInstaller'] and (EventID=1033)]]" > e:\outputmsi_events.txt

What the command does is look for event id 1033 in application event viewer and look for the source of msiinstaller. See the screen shot below for details.




The friendly view details of the event viewer will give you an idea how the command is being parsed and constructed to get the query or that output that we wanted.

If you have been doing json parsing in other programming languages it’s the same logic that is used to process the parsing of the data in event viewer.



The challenge here is the amount of data in the output and how you will process it further. But if you know what you’re looking for you can just open the text file in notepad or other editor then just search for that string or data.


Here’s an example of the data but I already formatted this manually, the output of the command above will just be in a single line, one line may contain up to 1,000 or more characters in a single line.



Cheers..till next time…

================================
Free Android Apps:


Linux Android App cheat sheet:

Divine Mercy Chaplet Guide (A Powerful prayer):
Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more