Skip to main content

Finding Your DSC Event Log Messages

Happy Friday!!!

Often when I am writing large amounts of code, I like to enter items into an event log of some type.  For those of you who have been sitting in my Advanced PowerShell classes where we use SAPIEN PowerShell Studio, you may have noticed that I will sometimes include a tabbed page where I have a log file.   

In DSC we have an Analytic log that we can send messages to using a DSC resource called Log,
PS C:\WINDOWS\system32> Get-DscResource -Name Log

ImplementedAs   Name   ModuleName                     Version    Properties        
-------------   ----   ----------                     -------    ----------        
Binary          Log    PSDesiredStateConfiguration    1.1        {Message, Depend...

This log file contains all of the verbose messages sent to the Analytic log.  

Look for Event ID 4098 with a ‘Warning’ level. 

Warnings are represented with the value of 3. Unfortunately, not all event 4098 will be yours.  Take a look at this configuration:

# Create your configuration.
Configuration TestMessage
{
    Import-DscResource -ModuleName PSDesiredStateConfiguration

    $Message = "`n `nConfigEventID: 001`n"
    $Message += "Task XYZ Completed`n"
    $Message += "`nAdd Whatever else you need to add"
    Node "localHost"
    {

        Log TestMessage
        {
            # This will write a message to the event log with event
            # ID 4098.

            Message = "$Message"
        }
    }
}

You can see that I am creating a custom message that I want to make sure is visually separated from the rest of the metadata presented in the events message.  My next set of code allows me to filter out all of the other information and just see my message.

# Create a hash for Get-WinEvent
$EventHash = @{LogName = 'Microsoft-Windows-DSC/Analytic'
              ID = 4098
              Level = 3}

# View the log files for our message.
(Get-WinEvent -FilterHashTable $EventHash -Oldest |
    Where-Object Message -Like "*ConfigEventID: 001*" |
    Select-Object -ExpandProperty Message).Split("`n")[6..10]

The result is:
ConfigEventID: 001
Task XYZ Completed


Add Whatever else you need to add

This may be a bit easier to read than this:
PS C:\PS> Get-WinEvent -FilterHashTable $EventHash -Oldest


   ProviderName: Microsoft-Windows-DSC

TimeCreated            Id   LevelDisplayName Message                                                                                                                      
-----------            --   ---------------- -------                                                                                                                      
2/25/2016 3:20:07 PM   4098 Warning          Job {4D5478C7-DC16-11E5-80BA-00155D130217} : ...                                                                                     
2/25/2016 3:22:02 PM   4098 Warning          Job {92101197-DC16-11E5-80BA-00155D130217} : ...                                                                                    
2/25/2016 3:23:51 PM   4098 Warning          Job {CEA254D0-DC16-11E5-80BA-00155D130217} : ...                                                                                    
2/25/2016 3:23:51 PM   4098 Warning          Job {CEA254D0-DC16-11E5-80BA-00155D130217} : ...                                                                                     
2/25/2016 3:24:32 PM   4098 Warning          Job {EBAAF632-DC16-11E5-80BA-00155D130217} : ...                                                                                     
2/25/2016 3:38:38 PM   4098 Warning          Job {E4202499-DC18-11E5-80BA-00155D130217} : ...   

Or this:
Job {1791C5F3-DC1F-11E5-80BA-00155D130217} :
Displaying messages from built-in DSC resources:
        WMI channel 1
        ResourceID: [Log]TestMessage
        Message : [S1]:                            [[Log]TestMessage]

ConfigEventID: 001
Task XYZ Completed


Add What ever else you need to
Job {2930B945-DC1F-11E5-80BA-00155D130217} :
Displaying messages from built-in DSC resources:
        WMI channel 1
        ResourceID: [Log]TestMessage
        Message : [S1]:                            [[Log]TestMessage]

ConfigEventID: 001
Task XYZ Completed

Add Whatever else you need to add

Just remember to enable the analytic and debug logs first.  Also, this may not be the best way to log information.  Remember that all verbose information will be kept in this log as well.




Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...