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

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.

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