I am trying to launch 4 simultaneous gauges for users on my Windows 2003 Terminal Server. Launching them as 4 individual PGF files works beautifully, but results in each user running 4 instances of P.P.exe (which is using 195MB of memory per user). This is not a level of memory overhead I can justify given the additional gauges we would like to deploy in the near future.
I read that you can get all of the gauges to run in a single P.P.exe instance by launching them using a script. I spent a couple days writing and refining the script to do this (clearly scripting is not my strong suit - hence the initial PGFs) and it works great......but there's another catch. When PowerShell is allowed to launch P.P.exe it will only launch one instance per server. So the first user that logs in sees all of the gauges and is happy; the next and subsequent users who log in to the same server get nothing. There is no error for the user, no event in the event log - just nothing happens. If you try to manually launch the gauges (instead of using the login script), you get the same result - nothing. If the first user closes their gauges (or I kill the P.P.exe process for that user), then one person can launch the gauges successfully, but not a second person.
To eliminate my script or complicated gauges as the problem, I logged in as 2 different users, opened PS for both, added the PG snap-in for both, and then just ran "out-gauge" (with no options). The first user got a generic gauge -- the second user got nothing.
Any suggestions? Thank you!
