How to parse data in an XML file.

PowerShell gives us many options for working with different types of data. One of the questions from class was how to parse through data in an XML file. Before we explore parsing through an XML file, we need to first create one.

Get-Process | Export-Clixml C:\xmlfile.xml

If you double click the xmiFile.xml, it will open to show you the contents of the file in XML.

Now we need to import this file into a variable so we can work with it.

$a = import-Clixml c:\xmlfile.xml

We can view the contents of the file by typing $a.

Since we exported an object to the XML, the import will have properties. Go ahead and type $a | gm. The data was also entered into the variable $a as an array. Type $a.count to get the number of cells in the array. Since the variable is an array with properties, we can enumerate the values of each item. For example, type $a[0].name. Using this information we can parse the data for what we are looking for.

Let's filter the data:

$a | where {$_.cpu -gt 20}

By filtering, you can isolate the information that you are interested in. For Example, $A | FL Name, CPU. To find out all the properties that you can call up, type: $A | gm - MemberType Property

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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...

Jason Yoder, MCT

Search This Blog