Advanced Threat Analytics (ATA) Sizing tool

This tool moved to a new location, please use

4.9 Star
Add to favorites
E-mail Twitter Digg Facebook
  • Failure running tool
    2 Posts | Last post February 14, 2017
    • Hi,
      After having the tool running for a few hours I receive the following errors after which the process stops:
      NextValue failed on server 'FQDN' for 'Memory\Available MBytes\'.
      NextValue failed on server 'FQDN' for 'Network Interface\Packets/sec\vmxnet3 Ethernet Adapter'.
      NextValue failed on server 'FQDN' for 'Processor\% Processor Time\_Total'.
      System.UnauthorizedAccessException: Access to the registry key '238' is denied.
      Any ideas?
    • It appears like the performance counter queries of machine FQDN aren’t working properly at all or remotely from the machine running the sizing tool.
      Try manually accessing the mentioned counters of the machine FQDN from the machine running the tool using PerfMon. 
      If that fails, you might want to investigate that failure.
      In any case it might be worth trying the tool again after restarting the computer which was used to executed the sizing tool and the FQDN DC (if possible).
      You can try and work around the problem by skipping the problematic DC by creating a DC list file (-GenerateDCListFile can help), removing the problematic FQDN DC, and running the tool again with all other DCs using -InputDCListFile.
  • Enumerate AD Sites?
    2 Posts | Last post July 24, 2016
    • Any plans to enumerate which AD sites the DCs are a part of?
    • We just released update version (2.5.8) which include the below request.
  • More infor on Output
    2 Posts | Last post July 13, 2016
    • Is there any possibility to provide more details on the output xls file and the format of it?
    • We are working on publishing more details about the tool and it will be published in the regular documentation site (
  • Empty report file when tool fails
    1 Posts | Last post July 06, 2016
    • When the tool fails to run (due to insufficient permissions or being run an a non-domain joined computer), an Excel report file called ATASizingToolResults.xlsx is still created, but the file cannot be opened with Excel, since it only contains two dashes (--) and is therefore interpreted as corrupted. Perhaps the tool should remove this file in these scenarios, or even better, writing the reason of the failure in Excel-readable format?
  • Run on DC?
    2 Posts | Last post July 06, 2016
    • Can this tool run on a DC, or is it better if it runs on some other domain joined computer?
      Tom Aafloen, Onevinn
    • Better run on other domain member machine, as it connect to all DCs on the domain...