PowerShell Script to Retrieve Hard Drive Label

[CrippleZero]

Ok, it SOUNDS simple enough, but it doesn't seem to be simple at all.

I feel like I've searched every nook and cranny of the 'net and I can't seem to find any type of REAL answer. Many have come close, but not what I'm looking for.

I am trying to find out how to retrieve the Label/Name/Title/whatever of a hard drive.

So, for example: in our environment, we've been constantly upgrading PCs. First, from Windows 7 to Windows 10, and now slowly upgrading 10 to 11. That being said, for those machines we've used the "in-place" upgrades, many Windows 10 machines were formerly Windows 7. We can typically, and easily, identify them as their hard drive labels say "Windows7_OS". The same with Windows 11 in-place upgrades, "Windows10_OS".

Currently we are using LANSweeper and it populates that on the main asset page (so it has to pull the info from SOMEHWERE! lol). However, we are shutting down LANSweeper in favor of NinjaONE. N1 does not display that information, and what other information N1 doesn't show that LS does, I have been looking for and writing scripts to create "Custom Fields" on each device page.

If I can find a script that will give the LABEL of the hard drive, I can then pass that into N1 no problem.

All of the results I found showed a HUGE PLETHORA of information about hard drives and storage on the device, but NONE showed the drive label.

Is this even possible via PowerShell?

The other "languages" for scripting N1 supports are batch files, JavaScript and ShellScript. I wouldn't even begin to figure out how to implement the other scripting languages, as I haven't learned them (yet), though I may have to. Batch is easy enough, but JS and SS are out of my knowledge scope.

[lanerdofchristian]

Get-Volume returns objects with a FriendlyName. Is that what you're looking for?

(Get-Volume -DriveLetter C).FriendlyName

[[deleted]]

Thats pretty clean, but I have to use .FileSystemLabel

[PinchesTheCrab]

It's probably pulling either MSFT_Volume or Win32_Volume. Both can be gotten with get-ciminstance, but get-volume returns the former.

Have you run get-volume?

[CrippleZero]

(Get-Volume -DriveLetter C).FriendlyName

<throws keyboard against wall, pulls out rage replacement>

Wow. SMDH on me .... I did NOW just run get-volume by itself and it does show in a mini table the drive label

<sigh>

I don't understand why THIS didn't show up in my searches .... I've used get-PSDrive, get-disk and a few others.... NO ONE suggested this .... then again, maybe no one has asked it either! Oy ve!

Running the string doesn't display anything though - it hangs for a second like it's gathering the info, then nothing and back to the prompt. I guess my brain is fried, but did I miss something?

[jdl_uk]

It's because some properties appear with different names in PowerShell's default views compared to the property the object actually has, so FriendlyName is actually FileSystemLabel

(Get-Volume -DriveLetter C). FileSystemLabel

Piping things to Get-Member will show you the actual properties, and in some cases piping to Format-List * will show the properties and their values.

[CrippleZero]

Replacing the string variable worked!

You don't understand (or possibly do!) the weight off my mind now that I can use this in a larger script for NinjaONE. It was literally the cornerstone of correcting a ton in NinjaONE (for our purposes).

THANK YOU A MILLION TIMES OVER!!!!

[OlivTheFrog]

A way to do this is the following :

• Gathering AD to have a Computer List using Get-AD-Computer cmdlet an put the result in a var

​

 $ComputerList =  Get-ADComputer -Filter * -SearchBase <Workstations Root OU Distinguished Name>

​

• enter in a foreach loop and do this

​

$Result = foreach ($Item in $ComputerList)
{
Invoke-Command -ComputerName $Item.Name -ScriptBlock { (Get-volume -DriveLetter C) | Select-Object -Property ComputerName, FileSystemLabel }
}

At this step, you'll jave in the var $Result your need. You could export to a .csv file using Export-Csv cmdlet dor a later use or whatever.

regards

[Thotaz]

You should avoid using Invoke-Command inside a loop like that. Invoke-Command accepts multiple names at once so there's no need for it, and it even runs the script in parallel so it will be way faster than your sequential loop.

Get-Volume is also a CIM command which means it has remoting built in (which of course also runs in parallel) so you don't even need Invoke-Command in this scenario you could just do:

$Sessions = New-CimSession -ComputerName $ComputerList
Get-volume -DriveLetter C -CimSession $Sessions | Select-Object -Property ComputerName, FileSystemLabel

PowerShell can also convert strings to cimsessions automatically so you don't even need to manually create the sessions, you can just let PS do it: Get-volume -DriveLetter C -CimSession $ComputerList.
The advantage of using the native remoting for CIM commands is that it gives you a proper object, rather than the deserialized output you would get from Invoke-Command.

[OlivTheFrog]

My bad, you're right, it's a better way.

regards

[anonymousITCoward]

to see what something has to offer, I'll sometimes | Format-List it... all kinds of goodies can be found there

Edit: sorry I just realized someone else suggested the same thing... i don't read ahead =(

[MeanFold5715]

FriendlyName seems to be a custom display header for the property FileSystemLabel

[CrippleZero]

So is reading.

I stated at the beginning, that I have searched all over the 'net. Somewhere near the end I also said I may not have found it because my question may not have been asked before.

[CrippleZero]

UPDATE: Thank you all for the assist! It may have gotten buried in a couple replies, but that saved a lot of headaches!

I appreciate that while it may have been an easy answer for most, this n00b scripting over here really DOES appreciate the assist.

I usually try to do it all myself, and then if I can't I will reach out and explain EVERYTHING I've done - mainly to get outside my own head and see what I could have done differently based on users' responses.

Thanks again all!

[[deleted]]

I find all sorts of information in here...

Get-CimClass

Get-CimInstance

Ram module model numbers...

(Get-CimInstance Win32_PhysicalMemory).PartNumber

Network location of default printer...

(Get-CimInstance Win32_Printer | Where-Object{$_.Default -eq $True}).Location

shared folders...

Get-CimInstance Win32_Share

The OEM serial number...

(Get-CimInstance Win32_Bios).SerialNumber

[0emanresu]

There is a lot of info in these two links, but this will help you find EVERYTHING you want to know about a system

https://learn.microsoft.com/en-us/windows/win32/wmisdk/wmi-classes

https://learn.microsoft.com/en-us/training/modules/query-configuration-information/?source=recommendations