Terms, Requirements and Installation of AD Health Profiler

Article provides information on various terms used in the AD Health Profiler. Article explains terms associated with the AD Health Profiler such as Target, Health Profile, and Dynamic Packs and also explain the requirements before using AD Health Profiler. We recommend that you read this article before you start using the product.

Terms Used in AD Health Profiler

What is Active Directory Health Profiler?

Active Directory Health Profiler, sometimes referred to just AD Health Profiler, tool is designed to perform complete assessment of multiple Active Directory Forests. It has the ability to perform health check of different components of Active Directory and provides Recommendations to fix the issues. Each component of Active Directory is checked based on the Dynamic Packs availability. You can create multiple health profiles and each health profile can include same or different Active Directory Forest or all or selected Dynamic Packs.

Let us understand terms being used in AD Health Profiler before we start using the application.

What is a Target?

AD Health Profiler supports Active Directory Forest as a target. Currently, application does not support any other targets other than Active Directory. You must register an Active Directory Forest with AD Health Profiler before you start to use the tool.

What is a Dynamic Pack?

AD Health Profiler is dynamic in nature. We always believe in designing Dynamic Solutions. AD Health Profiler Execution SubSystem and Dynamic Packs work together to check components of Active Directory. For example, we provide Domain Controllers FSMO Test Dynamic Pack to check FSMO placement in Active Directory. The Execution SubSystem is responsible for executing the Dynamic Pack and Dynamic Pack is responsible for checking the component (FSMO in this case) and reporting back to Execution System.

A Dynamic Pack consists of PowerShell code. We offer 71 Dynamic Packs with the purchase of Active Directory Health Profiler and many are in the queue. Once new Dynamic Packs are available those can be imported from within the tool.

What is a Health Profile?

In AD Health Profiler, a Health Profile is a management unit. Health Profile contains an Active Directory Forest and Dynamic Packs. You can create multiple Health Profiles and have each Health Profile manage the same or different Target. For example, if you create three Health Profiles, you can add three or different Active Directory Forests as illustrated in below example:

  1. TestHealthProfile1: This health profile contains DPTest.Local as AD Forest Target and 71 Dynamic Packs.
  2. TestHealthProfile2: This health profile contains DPTest.Local as AD Forest Target BUT only 30 Dynamic Packs.
  3. TestHealthProfile3: This health profile contains Ossisto365.Local as AD Forest Target and 71 Dynamic Packs.
Requirements for AD Health Profiler

You need to be meeting some of the requirements highlighted in this section before you start to use the product.

  • Administrator account: You must run the installation as an Admin and also be able to run the AD Health Profiler Execution SubSystem “As An Administrator”. This is the requirement before AD Health Profiler can execute Dynamic Packs.
  • Operating Systems: We have tested AD Health Profiler on Windows Server 2012 and Windows Server 2012 R2 Operating Systems. However, as long as you are running RSAT for Windows Server 2012/R2 on a supported Windows Operating System, you can try running AD Health Profiler on Windows Operating Systems other than Windows 2012 and R2.
  • PowerShell Modules: Since AD Health Profiler uses PowerShell-based Dynamic Packs, you are required to install following PowerShell Modules and Tools on the computer:
    • AD DS Tools
    • Active Directory PowerShell Modules
    • DNS Server PowerShell Modules
    • GPMC PowerShell Modules

Tip: Please note AD Health Profiler Execution SubSystem can try to install above PowerShell Modules and Tools automatically, in case it fails to do so please install manually from the Server Manager.

When AD Health Profiler runs it checks above PowerShell Modules and creates a log file. The log file is located under

C:ProgramDataDynamicPacksTechnologiesADHealthProfilerLog folder. As you can see it reports “Ok Found” for each PowerShell Module it checks. In case it does not find the PowerShell Module on the computer, it will say “NOT Found”.

So it is very important to install these modules before proceeding with the AD Health Profiler.

Once you have met the above requirements, you can proceed with the AD Health Profiler installation.

Installation of AD Health Profiler

It’s quite easy to install the AD Health Profiler. If you have downloaded the tool just double click on the MSI file and follow the on-screen steps. Once application is setup, you will see two desktop icons as shown in the screenshot below:

AD Health Profiler V3 shortcut is the Execution SubSystem and AD Profiler Reporter tool is to be used to generate reports in Word and Excel formats.

Important: AD Health Profiler Execution SubSystem must be run “as an Administrator”.


If you need to understand the capabilities of AD Health Profiler in detail please contact us at support@Ossisto365.com.

If you wish to see a complete a demo on AD Health Profiler let us know your convenient time.

Schedule a Demo