rolltama.blogg.se

Now let’s search for the keyword “warning” anywhere in the log, in the last 3 days, on a remote computer: Parse-WindowsUpdateLog.ps1 -Component "Content Install" | Out-Gridview

So there are 54 entries for the “Content Install” component, lets read those: Parse-WindowsUpdateLog.ps1 -GroupBy Component Note: due to the number of results returned when parsing log entries, I recommend piping to Gridview for easier viewing.įirst, let’s find the number of entries in the log for each component: Downloadĭownload the script from the Technet Gallery. I haven’t tried this with Windows 10 yet, where the WU logging mechanism has changed, but it will work for older operating systems that have PowerShell installed. This allows us to summarise the number of entries in the log by either component or date, for example, or provide some search filters to find specific entries and in a specific time period, for example all the software updates installed in the last 3 days. The script will retrieve the most important elements of the log – the date, time, component and entry text – and put them into a PS object.

To make searching this log file easier both on the local computer, a remote computer (where PS remoting is enabled) or groups of computers, I wrote a simple but handy PowerShell script. The WindowsUpdate.log, which logs activities of the Windows Update client, is not the easiest of log files to parse through but it’s handy one for finding details about update installation successes and failures.