tasklist /svc /fo list
If you're using Sysinternals's Process Explorer, just hover over a svchost instance to see what it's hosting.
You can't drill down into the individual services, but that should help track down errant services which are consuming lots of CPU and/or memory.
Taken from this CodeProject thread in The Lounge.
08 December 2009
01 December 2009
Handling meetings
Business meetings are almost always a waste of time, and this is usually because like so many other business activities, there is no process, no structure. However, we are engineers and we can fix things and make them better, so let's see what we can do with meetings.
Every meeting must have an agenda. Seems like a simple enough idea, but most meeting notices consist of a subject, a time, a place, and a list of attendees. An agenda is usually absent. Although you might be tempted to simply turn down agenda-less meeting requests with a curt "No agenda." response - as I have done on occasion - it is usually better to tentatively accept the meeting and send a polite response asking about the agenda. Eventually, people will get the idea.
Every meeting must have a scribe. Again, this seems obvious, but what usually happens is everyone takes their own notes (if they take notes at all; more on this below) and everyone has a Rashomon-like perspective on what was discussed and what decisions were made. The scribe should mail out meeting minutes (or email a link to their location in the wiki or SharePoint) as soon as possible once the meeting ends.
Every meeting should result in one or more action items. The purpose of a meeting is usually to resolve issues or bring all the attendees into alignment on a particular topic. If the meeting is purely informational, you probably shouldn't have it: instead, email a link to a document or video containing the information you would have shared. If the meeting is to resolve issues, every issue should have one or more action items, and each action item must have an attendee's name attached to it. You can't assign action items to people who didn't attend, and you can't assign action items to a group of people.
A digression on "we": I read something recently where someone outlawed the use of "we" in meetings, because "we" never get anything done.
Every meeting must have an agenda. Seems like a simple enough idea, but most meeting notices consist of a subject, a time, a place, and a list of attendees. An agenda is usually absent. Although you might be tempted to simply turn down agenda-less meeting requests with a curt "No agenda." response - as I have done on occasion - it is usually better to tentatively accept the meeting and send a polite response asking about the agenda. Eventually, people will get the idea.
Every meeting must have a scribe. Again, this seems obvious, but what usually happens is everyone takes their own notes (if they take notes at all; more on this below) and everyone has a Rashomon-like perspective on what was discussed and what decisions were made. The scribe should mail out meeting minutes (or email a link to their location in the wiki or SharePoint) as soon as possible once the meeting ends.
Every meeting should result in one or more action items. The purpose of a meeting is usually to resolve issues or bring all the attendees into alignment on a particular topic. If the meeting is purely informational, you probably shouldn't have it: instead, email a link to a document or video containing the information you would have shared. If the meeting is to resolve issues, every issue should have one or more action items, and each action item must have an attendee's name attached to it. You can't assign action items to people who didn't attend, and you can't assign action items to a group of people.
A digression on "we": I read something recently where someone outlawed the use of "we" in meetings, because "we" never get anything done.
Subscribe to:
Posts (Atom)