A user asked if it is possible to run the monitor cmdlets in a remote session. The answer was no, as it is a limitation of WCF and the use of named pipes. Process Monitor and Process Explorer were suggested to help, but this is only a temporary solution. Dennis Geerlings was mentioned – it is jokingly said that every day is Dennis Geerlings day at ControlUp.
Read the entire ‘Is it Possible to Run Monitor Cmdlets Remotely?’ thread below:
Question – is it possible to run the monitor cmdlets in a remote session? Seems like I can only get them to work when I am logged onto the monitor itself.
I don’t think so. I recall confirming this.
It’s a explicit design limitation of the framework (WCF) we use:
> User tokens that are marked with an impersonate flag are placed in the NETWORK USER group, its SID is explicitly denied access to WCF named pipes, as a security design concept*
Ignore the impersonate bit. The important bit is that identities that are part oft he NETWORK USER group, get explicit deny permissions on WCF named pipes. Well, the monitor cmdlets use named pipes.
You can see this in process monitor.
And also the groups you are a member off when you use something like enter-pssession.
You might be able to mess with the permissions via process explorer. But that’s obviously not a sustainable solution
Thanks Dennis. Out of curiosity, what day is Dennis Geerlings day at ControlUp? 😉
Every day. They give me chocolate covered almonds in the office.. so that’s good
Or bad? idk
Continue reading and comment on the thread ‘Is it Possible to Run Monitor Cmdlets in a Remote Session?’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers