QuickTrick: Adding AdtAdmin tool path to environment path variable


Today I installed Audit Collection Services (ACS) in my demo environment and after installing the ACS Collector and ACS Forwarder I wanted to start the AdtAdmin.exe tool. But where is AdtAdmin.exe installed?

And how do I run it next time from any location Iā€™m in my (PowerShell) Command prompt?

AdtAdmin.exe is installed in: C:\Windows\System32\Security\AdtServer folder.

Now I knew the path I just added the path the path environment variable using Powershell.

$env:path = $env:path + ";C:\Windows\System32\Security\AdtServer"

Result:

image

Have fun Auditing your security events!

But would not it be cool to have a PowerShell wrapper around AdtAdmin.exe? Smile Anybody?

Comments (3)

  1. Anonymous says:

    Hi Kevin,

    Thanks for commenting on my question šŸ™‚ If I've some time I'll try to do some wrapper testing and keep you posted.

    /Stefan

  2. Kevin says:

    An issue you run into pretty quick when trying to do that is that adtadmin doesn't handle comma decimals.  It simply joins all of it's data with commas without taking into account the possibility of comma decimals in the numeric fields.

    In a previous life, this made things quite painful when trying to deal with both US/Western European and Eastern Eruopean (where the comma decimal seemed more prevalent) environments. We ended up doing a bit of assumption based on field counts to try to guess the right way to interpret the stats data we got back.

    Aside from that issue it wouldn't be terribly hard to put together a nice wrapper around it since so much of the data returned is in CSV format.

  3. Rem-8 says:

    If I just knew how to write powershell cmdlets to handle exe files or commands (is this what is called wrapping?) I might give it a try too šŸ™‚