{"id":1029,"date":"2013-12-13T08:45:25","date_gmt":"2013-12-13T00:45:25","guid":{"rendered":"http:\/\/www.jhouseconsulting.com\/?p=1029"},"modified":"2014-01-21T22:55:16","modified_gmt":"2014-01-21T14:55:16","slug":"a-change-to-the-fields-in-the-netlogon-log-file-from-windows-2012-and-above","status":"publish","type":"post","link":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/2013\/12\/13\/a-change-to-the-fields-in-the-netlogon-log-file-from-windows-2012-and-above-1029","title":{"rendered":"A change to the fields in the Netlogon.log file from Windows 2012 and above"},"content":{"rendered":"

If you collate and report on the Netlogon.log files from Domain Controllers, you’ll notice that many existing scripts may fail to correctly split the lines when processing the logs from Windows 2012 Domain Controllers; unless of course you’ve already noticed and made an allowance for it.<\/p>\n

Here is a sample of the contents from a Windows 2008 R2 Netlogon.log file:<\/p>\n

\"Windows2008R2Netlogon.log\"<\/a><\/p>\n

Here is a sample of the contents from a Windows 2012 R2 Netlogon.log file:<\/p>\n

\"Windows2012R2Netlogon.log\"<\/a><\/p>\n

The additional field in square brackets is the process ID (PID). This is indeed a new feature introduced into Windows Server 2012, Windows 8 and above where it logs the process ID of the application logging the event in the Netlogon.log file. So now the fields within the Netlogon.log differ from that of older Windows Operating Systems.<\/p>\n

I have not read or found a single article from Microsoft to explain this other than one mention in a TechNet blog<\/a>.<\/p>\n

I’m not complaining, as this is very handy information, but had broken a couple of my scripts as it caught me by surprise. It would be nice if Microsoft had released updates for older OS’s too.<\/p>\n

It’s no big deal, and easily fixed in a script by either processing the fields differently depending on OS version or simply using a regular expression to remove the PID field when you get the contents of the Netlogon.log file using the Get-Content cmdlet.<\/p>\n

For example:<\/p>\n

\r\n$NetlogonLog = Get-Content -Path $pathtothenetlogondotlogfile\\Netlogon.log |\r\n  Foreach-Object {$_ -replace "\\[\\d{1,5}\\] ", ""}\r\n<\/pre>\n
So now when you export this to a CSV, all fields across all Netlogon.log files will be consistent.<\/p>\n
I hope this quick post helps to remove any confusion.<\/p>\n
See here<\/a> for the full script.<\/p>\n","protected":false},"excerpt":{"rendered":"
If you collate and report on the Netlogon.log files from Domain Controllers, you’ll notice that many existing scripts may fail to correctly split the lines when processing the logs from Windows 2012 Domain Controllers; unless of course you’ve already noticed and made an allowance for it.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[202,5],"tags":[279,277,280,278],"class_list":["post-1029","post","type-post","status-publish","format-standard","hentry","category-active-directory","category-scripting","tag-fields","tag-netlogon-log","tag-pid","tag-process-id"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t