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

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.