typicaltim/get-hddinfo

Grabs the hostname for the machine that the HDD was installed with and gives a list of users that were logged into it.

get-hddinfo's Issues

User list limitations in the CSV file

Problem

When the first HDD is scraped, however many users are found on that drive will be the maximum number of users that will be cataloged for every subsequent drive regardless of how many are found.

Example

$Drive1 is the first to be scraped for info, $userA and $userB were found. So $Drive1 will be cataloged as such:

HDDIndexNumber : 1
Hostname : $Hostname1
User1 : $userA
User2: $userB

$Drive2 is scanned second; $userC, $userD, and $userE were found. Unfortunately $Drive2 will be cataloged in this way:

HDDIndexNumber : 1
Hostname : $Hostname1
User1 : $userC
User2: $userD

Proposed Solutions

A.) When the Catalog file is first created, write all of the headers beforehand and create space for 100 users. This is in no way a perfect solution. If for some reason more than 100 users are found on a drive, users 101+ will not be cataloged. Also, querying the CSV for information might be slightly more annoying if 80% of the user columns are null.

B.) Figure out a way to create a new column(s) if the user count is greater than the number of user columns when a drive is scraped and written to the catalog.

Empty drives do not return property information before user prompt

Problem

If a drive is empty/non-existent when scanned, for some reason he script will not show the $SavedHDDInformation variable before prompting the user if it's okay to save. It prompts before showing the variable, which means the user can't verify the data is accurate and approve it.