Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

NET (Agent, Installation)

Powershell Official Cmdlets Return Unexpected Result


Powershell Official Cmdlets Return Unexpected Result

Greetings. I am testing the appdynamics.psm1 official module, attempting to poll my servers for the presence and version of the AppD agent. Module sourced from:


Using the Get-Agent cmdlet on

1) A live server with an appd agent, and

2) A live server without an appd agent


I get the same answer: Version


The reason is that the function Get-Agent *assumes* that any server that can be pinged (Test-ComputerConnection) must therefore have a valid AppD registry entry. However, the test server I used actually both has a working AppD agent AND does not have a valid registry entry. The code does not account for this, and returns a value. I am going to have to change the official code to get any use out of it. Could an AppD developer please add further resilience to their official cmdlet?



By replying you agree to the Terms and Conditions of the AppDynamics Community.
Powershell Official Cmdlets Return Unexpected Result
AppDynamics Team

Re: Powershell Official Cmdlets Return Unexpected Result

Hi David,


Thanks for contacting AppDynamics. Please let us know which agent version is installed in your servers. The commandlet is looking for the registry key 

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall with a Displayname value equals to AppDynamics .Net Agent. If it can't find that entry, is returned, which means no agent is installed. 


So, in a machine where no agent is installed, the response you got is expected. However, in the machine where the agent is installed, these registry entries must be present. So, we have to understand why those registry entries are not created. If the registry entries are corrupt, they can be fixed by launching the Appdynamics configuration wizard (from start menu).




Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.