Jump to content

JeffVandervoort

Members
  • Content Count

    89
  • Joined

  • Last visited

About JeffVandervoort

  • Rank
    IT Hero

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1334 profile views
  1. First, create a Scheduled Task to bump the service. (NET STOP "Service Name" && NET START "Service Name"). Then, in the Rules tab, create a Rule whose Condition is the service is using > 60% CPU or > 2GB RAM. The rule's Action would be Run a Task, and select your Scheduled Task.
  2. Typically, in a Remote Desktop hosting environment, we want to keep the per-user memory footprint as small as possible. 8 MB doesn't seem like much on a typical desktop or server, but on an RDSH, every byte counts, because RDSH capacity is generally determined by RAM. My understanding from another thread, here, is that PCMONTASK was added for the screen view feature, and that's all it's used for. Even at 8MB, this one task increases the memory footprint of an RDPINIT session here by about 50%, and is far larger than any of the other per-user "overhead" tasks we run here. By "overhead", I
  3. Another scenario: A Win 6.x file server has UAC enabled, and a shared folder has an ACL as follows: Administrators: Full SYSTEM: Full DOMAIN\SomeGroup: Modify Sysadmins are members of Local Administrators, but are NOT members of DOMAIN\SomeGroup. This is intentional. In this scenario, in order to access the folder, an admin either has to make himself a member of DOMAIN\SomeGroup, or by clicking "Click continue to gain access" when prompted. Either is an auditable security event, and Microsoft provided this functionality in UAC to protect against rogue admins. If it becomes necess
  4. Squeaking wheel gets the grease, they say. Push management was, IIRC, the first thing I posted about here, and it remains my number one unfilled need. If I can recruit others to "me too" the idea, perhaps it will become a higher priority. As Simon's request was push-management related; I couldn't miss the opportunity. Thanks for providing this forum for your customers to help shape PC Monitor, and for listening.
  5. "if you decide to "share" your account username/password with other users/devices then it is you that "makes every user an uber-admin"." Exactly, Marius. You've just crystalized the problem. That's why I'd have to stop using it. Because all PCM devices share one username & password, and the same (very elevated) privelege level. PCM users are admins, but systems of any size restrict admins to permissions that apply to their specialties, and nothing more. When my future (say) Exchange admin logs on and opens EMC, they can do whatever AD authorizes them to do, which will be pretty
  6. This might be useful to some, and would be easy to implement as an interim step: Allow certain devices to be "read-only" devices that could receive notifications but not issue commands.
  7. I'd like to be able to tell PCM to monitor all HDDs, instead of specifying one at a time. And as HDDs are added and deleted, automatically monitor them, too. It's pretty rare to find a disk I don't care about! HDD monitoring should also report Windows' storage Events (from NTFS, Disk, ATAPI, SMART...all the built-in stuff) without having to explicitly set up Event Log notifications for them. And since we're on the subject again, a repeat request for monitoring mount points and not just drive letters.
  8. I'm a big believer in principle of least permissions. AD includes several built-in levels of administrative permissions, and allows creation of many more through Delegation and Group Policy. PC Monitor makes every user an uber-admin, because it runs as LocalSystem, one of the most powerful accounts in a system. I'm a one-man shop at this point, but hope for big growth when I'm in production. There will come a time, possibly fairly soon, where I will no longer be able to use PC Monitor because it does not allow me to properly secure the system. I'd like for PCM to impersonate users, an
  9. Regarding why one shouldn't allow all devices, here are 2 good reasons off the top of my head: Mobile devices get lost and stolen, and employees get terminated. If all you have securing PC Monitor--a VERY powerful utility usable unsupervised and off-premises, access to which should not be granted lightly--is the username & password, you have to change that on every device and for the service itself. No thanks! <editorial>Unfortunately, Simon, PCM is not very enterprise-friendly when it comes to pushing changes. (Please join me in making noise about that!) Apparently the PCM ser
  10. That's great to hear...but it wasn't really what I was asking, so I guess I didn't explain it very well. And since then, I've rethought what I'm asking for anyway! So here's version 1.1 of my request: Here's one of several relevant scenarios: Dell OpenManage Server Administrator (OMSA) doesn't log very many events, but the ones it logs are usually related to storage problems. So if OMSA has anything to report, I want to hear about it. Therefore, I have set up Notifications to alert me to all OMSA events. Currently, in order to receive Critical notifications for Error events, Elevated
  11. Lots of admin types just about live in vRD. (If you've never heard of it, check it out: www.visionapp.com.) Happy to report that PC Monitor Dashboard 2.7 can be installed as an "External App", and 90% works. The 10% that doesn't is the menu bar. But I don't use the menu bar in Dashboard much after it's installed, so that works for me. My settings in the Dashboard external app properties' "Options": Wait for exit: On Max wait time: 2 Try to integrate: On Max wait time: 2 Start as shell process: Off [Edit] Since writing that yesterday, I've decided to go for the record for t
  12. In Desktop 2.7 or Manager 2.7, create or edit an Event Log Notifications. Grab a corner of the dialog box and gradually make it smaller, watching what happens as you do so.
  13. When creating a new Event Log Notification, typically I want the Notification to have a "Priority" that maps to its "Level". So, please make the Priority default to whatever is the highest Level of the checkboxes that are selected for the Notification, but still allow the user to select a Priority they prefer. By default, then: Error = Critical Warning = Elevated Information = Normal. Or Low. Not sure of the difference. What's the difference between Low and Normal in PCM Priorities?
  14. Agree with some of your points and could add a few...but was trying to avoid an OS war!
  15. Okay, loving Dashboard 2.7, and can check off items 3, 4 and 5 from my list, above. Still looking forward to 1 & 2, especially; 6 would be nice to have.
×
×
  • Create New...