Hi,
I am working on a requirement where SN will try to make a remote connection to a server and perform a cleanup of few folders.
I have a custom action built for it with PowerShell script sitting on a file in MID server(agent\scripts\Powershell\CleanLogFolder.ps1). However this action works only on the MID server host, i.e. it works/cleans up the folders when tested against the MID server itself. But when i try to clean up on some other server for which MID has access and can communicate, it gives me credential error when the action is tested.
Steps below are already in place:
- MID Server is able to ping the server "akash-vm" and run WMI commands and get the information
- Relevant ports 135, 5989,3389, DCOM ports 49152-65535 are already opened
- PS remoting is enabled to server "akash-vm" from the MID server.
- SN Instance has valid credentials to this VM and credential test is also working fine.
Action steps and error message when the credential is tested via action is attached. Please let me know if anyone has faced this issue and were able to resolve it.
Hello, a quick update - I was able to resolve this by following steps.
- Create a credential alias record and specify the credential you want to use for remote login
- Add a "Get Connection Info" step in your action and ensure "Type" = Credential Alias & select the one you created in above step. Make sure to select the same credential alias in the powershell step as well.
Now, when you test the credentials it will get validated successfully.
Updated Action
Hello, a quick update - I was able to resolve this by following steps.
- Create a credential alias record and specify the credential you want to use for remote login
- Add a "Get Connection Info" step in your action and ensure "Type" = Credential Alias & select the one you created in above step. Make sure to select the same credential alias in the powershell step as well.
Now, when you test the credentials it will get validated successfully.
Updated Action
