Adserverdownexception Powershell

I am currently using vRO 6.0 along with the PowerShell plug-in 1.0.5 and am having issues running workflows executing active directory command powershell scripts. My plug-in and powershell host are set up using kerberos authentication http. I am able to successfully execute vRO powershell workflows for using the vSphere powercli to connect to ESXi hosts to do certain things and that works fine. I need to create powershell scripts though so I can connect to multiple different domain controllers to create objects on specific servers to overcome replication times. My scripts work fine, if I execute them locally on the host then everything is successful. If I try and execute the same script calling it through vRO I get the error stack below from the logs window on the workflow and it fails within seconds. I have seen some posts about using CredSSP but supposedly that is just if you can't use kerberos. The host I am using is just a domain member not a DC but has the AD powershell modules loaded on it and as I said the script executes perfectly fine as long as it is not executed through vRO. Any ideas would be greatly appreciated.

Download File

One specific note is that it is actually not working with the powershell plug-in but the article explains why and also how to work around it. I just went through this whole issue and have mentioned this to VMware product management, please take the time to let VMware know you would like this fixed also.

So your article helped me out a lot. I've setup a client/host in separate domains and am able to invoke powershell scripts and external scripts. I'm just stuck at using CredSSP to authenticate to run powershell scripts against active directory.

But still I did not understand, why this difference for WMI based Test and Agent based test method? In WMI in order to run a powershell script we need to select Remote connection while for Agent based we need to use Local connection?

38c6e68cf9