Hdd ap

Detect HDD or SSD plus SMART Health

Drive type detection and drive health.


This agent procedure detects the type of hard drive the Windows OS is using. Either HDD, SSD, or Virtual. It also gets the health (for HDD and SSD), the SSD Wear and Power on Hours, and any HDD Read Errors.

This script uses PowerShell commands only available to Windows 8 and above including Windows Server 2012 and above. It is important to mention that this script is designed for the C drive but you can edit the script to check other drives. Also, this has not been tested on RAID arrays... Any feedback would be greatly appreciated.

This Agent Procedure requires Custom Fields to be created exactly as they appear in the included Documentation PRIOR to importing the Agent Procedures. Most of the times the Custom Fields will match so you do not have to edit the Agent Procedure. There is a possibility that the import doesn’t detect the Custom Fields and you will have to edit the Agent Procedure.

  • Name: Sidney Sahdala
  • Company: Kaseya
  • Website: http://www.kaseya.com
  • Contact Developer
  • Summary
  • Detect HDD or SSD plus SMART Health
  • Version: 1.0
  • Released on August 19th, 2019
  • Reviews

    Detect HDD or SSD plus SMART Health has no reviews.

    Gravatar for Sidney Sahdala
    Sidney Sahdala 29 days ago

    This Agent Procedure together with the Windows System Stability Index Agent Procedure (https://automationexchange.kaseya.com/products/619will be very helpful in judging the reliability of a system.

    Gravatar for Dmitrij Kondrasov
    Dmitrij Kondrasov 24 days ago


    I've got an errors:

    Failed THEN in step 34 (Line 51)

    Failed ELSE in step 2 (Line 60)

    Tried several times.

    Firstly I've created Custom Fields and run procedure. Tried on two computers with SSD disks.

    Gravatar for Kevin Saunders
    Kevin Saunders 14 days ago

    I am getting the same errors that Dmitrij is getting.

    Gravatar for Dale
    Dale 14 days ago

    I am also getting the same errors and I have tried on around 15 machines which all have different specs. Not once has it done a successful run.