Tuesday, August 12, 2008

Couldn't get process information from remote machine

Sometimes our customers install one of our end-user apps on Terminal Server, or Citrix. In these environments, individual users are not typically machine administrators.

There's functionality in our app that requires it to launch some external third-party applications, which we then integrate with -- syncing data back and forth.

Before our app launches the other program, it needs to know if that other program is already running. It looks for an already-running process with the other app's name.

Problem is, on Windows 2003 Server, standard users don't have the authority to look at other processes. We see an error:

Couldn't get process information from remote machine

When this happens, we advise our customer's IT department to add their end users to the Performance Monitor Users Group. This gives them the right to query running processes, without giving them the unwanted rights that making them machine administrators would.

1 comment:

Anonymous said...

I was having this problem publishing out an app in Presentation server and I added the local "Terminal Server User" to the Performance Monitor Users group