Found while doing forensics on some rediscovered loose flash drives.

      • skilltheamps@feddit.de
        link
        fedilink
        arrow-up
        16
        arrow-down
        3
        ·
        8 months ago

        Yes, if it was as object based as it claims, Get-WmiObject would subtract WmiObject from Get. Instead it is like having all the clutchy drawbacks from being object based without reaping any of the potential bemefits.

        If you want anything that actually is object based, just use xon.sh - sane and familiar syntax with insane amounts of power just like that

      • Carighan Maconar@lemmy.world
        link
        fedilink
        arrow-up
        6
        arrow-down
        3
        ·
        8 months ago

        It’s from the beginning meant to be fully scripted though. You’re not supposed to be putting in these commands manually, it’s meant to be used in an environment where the 5-50 commands you or your company needs constantly have aliases and script files defined and on PATH.

    • OfficerBribe@lemm.ee
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      8 months ago

      Get-Disk would have sufficed here, no real need to use WMI here. That said, you would still need to filter USB device and select properties you want to retrieve.

      And unrelated, but if WMI class needs to be queried, Get-CimInstance is the preferred method instead of Get-WmiObject for quite some time.