Skip to main content

Convert my Get-HDSizeInfo Cmdlet Output to a CSV File

Earlier this morning I posted some code that will extract hard drive information from other clients on your network.  I got this idea from a user on the LinkedIn group PowerShell Power Users.  His request was for a CSV file where my code sent objects into the pipeline that would not translate well into a CSV.  Below is the code that will convert the output of that cmdlet into a CSV. 

To use this code:

  1. Copy the Get-HDSizeInfo code from my previous post into the PowerShell ISE. 
  2. Paste the code below directly under the Get-HDSizeInfo code
  3. On line 81, provide the names of the clients that you want to pull the hard drive information from.
  4. On line 82, update the Path parameter to where you want the output file to be.
  5. On line 82, adjust MaxDrives to the highest number of drives you expect any 1 client to report.  It defaults at 3.
  6. Run the script.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

80

81

82

83

84

85

86

Function ConvertTo-HDInfoCSV

{

Param (

   

            [parameter(Mandatory=$true,

                      ValueFromPipeline=$true)]

            $HDInfo,

           

            [parameter(Mandatory=$true)]

            $Path = "C:\Temp\Out.CSV",

           

            [Int]

            $MaxDrives = 3               

)

 

BEGIN

{

    # Create the first row of the CSV file.

    # If you anticipate more than 3 drives being returned, then add a new

    # Set of place holders for them.

    $DriveHolders = $Null

    For ($X=1;$X -le $MaxDrives; $X++)

    {

        $DriveHolders += "Drive_$X,SizeGB_$X,UsedGB_$X,FreeGB_$X,"

    }

    $DriveHolders = $DriveHolders.Remove($DriveHolders.LastIndexOf(","))

 

    $Row1 = "ComputerName,$DriveHolders"

    $Row1 | Out-File -FilePath $Path

} # END: BEGIN BLOCK

PROCESS

{

    ForEach ($HD in $HDInfo)

    {

   

        # NULL out the output string

        $String = $Null

       

        # Add the Computer name.

        $String += "$($HD.ComputerName),"

 

        # Get all the hard drive information from the object.

        $Drives = $HD | Select-Object -ExpandProperty Drives | Sort-Object -Property Drive

 

        # Cycle through the Hard Drives and add them to the Output.

        ForEach ($D in $Drives)

        {

            # This will add the Hard Drive information in the correct

            # order for the CSV.

            $String += "$($D.Drive),"

            $String += "$($D.SizeGB),"

            $String += "$($D.UsedGB),"

            $String += "$($D.FreeGB),"

        }

 

        # Remove the last "," from the string.

        $String = $String.Remove($String.LastIndexOf(","))

        $String | Out-File -FilePath $Path -Append

 

    }

 

} # END: PROCESS BLOCK

END {}

 

 

} # END: Function ConvertTo-HDInfoCSV

 

 

# Used the Get-HDSizeInfo code from yesterday to get hard drive information.

# Just past that code as the above the code above.

Get-HDSizeInfo -ComputerName lon-dc1, lon-cl1, LON-ex1 -Fixed | Where Online -eq $True |

ConvertTo-HDInfoCSV -Path "C:\Temp\Out.CSV" -MaxDrives 3

 

 

# You can import the CSV into Excel or import it into PowerShell with the line below.

import-csv -Path "C:\Temp\Out.CSV"

 

 

 

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.