JeffVandervoort

Actually, Services Policy doesn't work, because the Services CSE runs before the GPSI CSE. This means the PCM service hasn't been installed when GP tries to launch it. So I used Group Policy Preferences/Services module to launch the service, set it to run only once (in case I want to set PCM agent to Manual start for some reason) and used ILT to target only computers where the program has been installed (I used a file match) so the run once wouldn't be used up before the software was installed. Incidentally, the PCM Service doesn't need to be installed on a DC to appear in the Services list...it needs to be installed on the computer on which you run GPMC. I've invested a fair amount of effort (correction: an unfair, large amount of effort!) on deployment in the last few days. Am considering posting a home-brew "PC Monitor Enterprise Installation Kit" to give others a jumping off point until things are smoothed out. But I can't stress enough to MMSoft that enterprise deployment is a CRITICAL need for the success of your product. It's surprising and disappointing how little attention this has received; while the agent and client are loaded with Enterprise features of little or no interest to SOHOs, it looks kinda like you never expected anyone with any more than the 3 free computers to use it! BTW, downloading the new Windows Phone PCM client as I type this. (A Mango version? Just got Mango today so I gather that's it.) Looking forward to whatever Mango goodness you've baked in! WP7 rocks. Mango rocks harder. And I'm VERY pleased that PCM supports both, and does it so well.

The app is fine. I can launch it from the .exe or create a non-MSI shortcut to it and run that. The MSI shortcut is the problem. I just realized that now that I'm installing by GPSI Computer Configuration, I won't have that problem, any more...the shortcut will be placed in All Users. So there's another workaround!

The PC Monitor agent does not start automatically after it is installed. You've agreed elsewhere that PC Monitor installation isn't yet enterprise-friendly, but the impact of this is that even after installing by GPSI, we have to come up with a method to launch the service. If it's a bug, fixing it would be one step closer to being enterprise-ready. If this is by design, is there a way to make the service launch with an MST file?

Normal users don't have access to servers. And a shortcut that doesn't work isn't a good idea, either!

In this system, (all Win 6.1) we redirect ALL possible folders, including Start Menu. It appears that the PC Monitor Start Menu shortcut is machine specific. When I launch PC Monitor from the shortcut on any machine other than the one on which the shortcut was originally installed, I get this error: [Window Title] Problem with Shortcut [Content] The parameter is incorrect. [OK] I suspect the same problem will occur if you DON'T redirect folders but DO use roaming profiles...but I haven't tested that. Probably the best and easiest fix: Install the shortcut to the All Users Start Menu.

And the "Count" registry value has to go. I've written software, too, and I know how convenient it is to store the upper boundary, but it makes it tough on the end user. My current plan is to push the settings I'm interested in by Group Policy Preferences, but my comments apply to the ADM/ADMX files I very much hope you furnish soon. This needs some rethinking by MMSoft. As much as I like MPCM (from my 3-computer trial), my one negative comment (now that I've bought a larger license) would be that it is not very well designed for enterprise deployment, whether by GPSI or SCCM.

Thinking it through further, to be useful... I need to be able to set a config that will work on ANY machine. Unlike "secure by default", where we only want to install services we need, in monitoring, we want MPCM to monitor EVERYTHING that's installed, and ignore anything that's not. Is that how MPCM works? For example, if I enable IIS monitoring on a machine where IIS is not installed, do bad things happen? In particular, I notice unique IDs for network connections and hard disks. Those sure won't be usable globally. Don't know what all the possible ramifications are of this, but it sounds like settings that monitor "All Adapters" and "All Disks", with per-machine exceptions, would make a lot of sense.

Cool! That'll work.

I'd like to push the Agent to my WS2008 R2 servers via SCCM 2007. Is there a way to furnish the credentials info from the command line, or an answer file?

Having a tray icon AND a taskbar icon is redundant. MUCH prefer a tray icon. I've added Dashboard to my Startup group to run minimized. Preference would be to have an option to launch on logon AS A TRAY ICON. Tray icon (get the theme here?<g>) should post a balloon as new notifications arrive. Tray icon should flash (or something) when a new notification comes in, and keep flashing until I've seen and dismissed it (not necessarily deleted it). Minor, and if it never changed it would be OK with me. But that stock traffic light icon has been around for at least 15 years! A desktop Gadget that summarizes system status and scrolls notifications would be cool. Great product; looking forward to all the new functionality you're adding.