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

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...