make sure that winrm is started and localhost is seen as trusted
winrm get winrm/config/client should list the localhost as TrustedHosts
If not add the host as trusted :
Set-Item WSMan:\localhost\Client\TrustedHosts localhost
and most important configure the policy with the same user in my case is sentry\arif as the one which allowed you to add the localhost as trusted
To be safe I 've been also using the same account as the Patrol Agent default account
just in case you have the Monitoring X Plugin in TSPS, you can directly cross lauch the powershell session and test the command from them.
cross launch MS X console from TSPS -> Tools-> >_Shell
There just type powershell, and you'll get the real powershell within a 'patrol' session and test your script
Then configure the script using Patrol Scripting KM.
Isn't nice to have a powershell Session from TSPS
If he had MSX, he would have used that instead of Scripting KM
Yes I know. What I show previously was just the console MSX which can be cross launched from TSPS.
It's not really the MSX km feature.
The powershell script is configured with scripting KM via the infrastructure policy.
I think, the cross launch of MSX console doesn't require the monitoring studio 10.1.01 KM to be loaded , does it ?
Yes, it does.
Von meinem iPhone gesendet
Am 20.03.2020 um 07:45 schrieb Arif Alibay <firstname.lastname@example.org>:
BMC Communities <https://communities.bmc.com/?et=watches.email.thread>
PATROL for Scripting - local PowerShell-Script
reply from Arif Alibay<https://communities.bmc.com/people/alibababay.fr?et=watches.email.thread> in TrueSight Operations Mgmt - View the full discussion<https://communities.bmc.com/message/865282?et=watches.email.thread#865282>
I know it's hard to believe, but the cross launch of the MS X console from TSPS doesn't require the X.kml to be loaded.
it needs to be installed though but you can leave it unloaded and use only console features.
in TSPS , you need to import the Monitoring X plugin.
See as well the article : How The TrueSight PATROL Agent UI Works
Anyway from TSPS on localhost , Status attribute, what messages do you see as annotation message ?
Should you have any issue , you should see the full error message in the Status graph annotation details.
Technically if they do not own the license, they should not use it.
I believe you can still use the MSX for free but then you won't have the support from Sentry Software.
But I can't imagine customer using such product without acquiring the license.
Product license and support license are two different things. You need to have product license to install and use it. And support license to avail tech support.
I'll explain to you one to one. But MS X is a little bit different as it has the console from TSPS and the Studio part provided by the KM itself.
And again I can't imagine a "real" customer using the MS X feature console side and KM side without paying the license
Back to the original Post , I was able to reproduce an issue with Powershell Scripting KM and have an annotation message in the graph.
Note here , I am using Patrol for Scripting KM (Scriptpowershell) and NOT Monitoring Studio KM , have configured Patrol for Scripting from CMA with a infrastructure policy
And I am just viewing the Scriptpowershell\Localhost\Status instance graph from TSPS MS X console - cross launched from TSPS in just one click.
You can do the same from classic console, PCO or TSPS device graph view.
Hi Arif Alibay
I am well aware of the capabilities of the MSX KM and I would use it if I could. But the customer doesn't have support or licenses for the KM and therefore the KM is not a feasible solution.
I must say I am a bit annoyed that every discussion is becomming a marketing/sales event for MS. I have explicit written that the KM is cannot be used in this situation.
I must have a solution with the KMs licensed by the customers and for the moment this is the Scripting KM.