Skip to main content

Why are Objects so Important?

We are in day 1 of a PowerShell class here in Phoenix.  I’ve been keeping an eye on PowerShell.com and PowerShell.org to try and find questions that we can help with.  Right before we started our topic on saving and retrieving objects from disk, an IT pro asked a question concerning getting and processing information about their virtual machines.

Get-VM | Out-File C:\ps\VMS.txt

$VMs = Get-Content -Path C:\PS\VMS.txt
ForEach ($VM in $VMs)
{
    $VM | Select-Object -Property Name
    Get-VM $VM | Get-DatastoreCluster
}

Do you see the problem here?

The IT Pro is correctly getting his virtual machine objects.  The problem is he is saving them to a text file.  Let’s look at the text file.
PS C:\> Get-Content -Path C:\ps\VMS.txt

Name  State   CPUUsage(%) MemoryAssigned(M) Uptime             Status             Versi
                                                                                  on  
----  -----   ----------- ----------------- ------             ------             -----
CL1   Off     0           0                 00:00:00           Operating normally 7.0 
CL2   Off     0           0                 00:00:00           Operating normally 7.0 
DC    Running 0           1132              1.22:38:46.2550000 Operating normally 6.2 
EX1   Off     0           0                 00:00:00           Operating normally 7.0 
S1    Running 0           512               1.22:38:45.3760000 Operating normally 7.0 
S2    Running 0           512               1.22:38:45.1660000 Operating normally 7.0 
SVR1  Off     0           0                 00:00:00           Operating normally 6.2 
SVR2  Off     0           0                 00:00:00           Operating normally 6.2 
Test1 Off     0           0                 00:00:00           Operating normally 7.0 

It looks just like what you would expect if you executed Get-VM.  Let’s look at the objects produced by Get-VM and Get-Content.
PS C:\> Get-Content -Path C:\ps\VMS.txt |
    Get-Member |
    Select-Object -first 1 -ExpandProperty Typename
System.String

PS C:\> Get-VM |
    Get-Member |
    Select-Object -First 1 -ExpandProperty Typename
Microsoft.HyperV.PowerShell.VirtualMachine

The object types are different.  If you want to save your objects to disk, a text file will not work.  Consider using Export-CliXml.  Yes, I know.  It is harder to read.  If you are not planning on automating a process, go ahead and save it as a text file.  You will then have to manually read it and manually execute your actions. This IT Pro was trying to automate a process.  A text file was not working.  This will:

Get-VM | Export-Clixml -Path c:\ps\Vms.xml

$VMs = Import-Clixml -Path C:\ps\Vms.xml
ForEach ($VM in $VMs)
{
    $VM | Select-Object -Property Name
    #Get-VM $VM | Get-DatastoreCluster
}

You may have noticed that I commented out the Get-VM $VM line.  Well, that is another error in his code, but that is for another time.


Comments

Popular posts from this blog

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.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

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