Skip to main content

New way to convert WMI time properties

I picked up new way to convert time that is retrieved from Get-WMIObject.  One of my past students, Zak Shupp from HP, sent me a function that we was working and it had a .NET object that I never seen before.  For those of you in a PowerShell V2 environment, you do not get to benefit from the Get-CIMInstance cmdlet.  Here is an example of the output of the same class with a focus on a DATETIME property:

PS C:\> Get-WmiObject Win32_Operatingsystem |

Select-Object -ExpandProperty InstallDate



PS C:\> Get-CIMInstance Win32_Operatingsystem |

Select-Object -ExpandProperty InstallDate


Wednesday, November 13, 2013 10:25:19 AM


The first command pulls a string of characters to represent the date and time of the operating system installation.  This is not exactly intuitive.  The last 3 digits are for the time zone.  Try explaining that one.  The second command pulls this data as a DATETIME object, which is what PowerShell cmdlets like.  To correct this with Get-WMIObject, a scriptmethod called ConvertToDateTime is provided by the Get-WMIObject cmdlet to all objects that it recovers for you.  Here is how it is used.

PS C:\> (Get-WMIObject Win32_Operatingsystem).ConvertToDateTime((Get-WmiObject Win32_Operatingsystem).InstallDate)




Wednesday, November 13, 2013 10:25:19 AM


Not cool.  Now, we will do it Zak’s way using the System.Management.ManagementTimeConverter object.

PS C:\> $OS = Get-WmiObject Win32_OperatingSystem

PS C:\> [System.Management.ManagementDateTimeconverter]::ToDateTime($OS.InstallDate)



Wednesday, November 13, 2013 10:25:19 AM


Much better! Ok, not as good as the CIM cmdlets, but Zak has simplified the process for those who need to use Get-WMIObject in their environments.  Remember, once all of your systems are at PowerShell V3 or better, start coding with Get-CIMInstance and begin to phase out Get-WMIObject.


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.