SCOM scales up to 15,000 agents.

The perceived performance at this scale is HIGHLY dependent on the number of 
management packs in place, the number of classes, relationships, and workflows. 
 And scale is impacted highly by the sizing of the hardware and I/O throughput 
capabilities provided (i.e… physical vs virtual, shared resources vs dedicated, 
disk, CPU, and memory I/O)

In the case of typical client OS monitoring, the number of classes is very 
small, as is the number of important monitoring workflows.  This allows a 
client OS monitoring environment to scale very well.


Client OS monitoring is fairly common.  We have customers who take the scale to 
the maximum supported numbers…. especially common in cases where the client OS 
is a POS machine, ATM, Kiosk, etc.  Even on standard user laptops and desktops, 
this can provide benefit for ACS scenarios, proactive disk failure monitoring, 
or performance reporting.



From: [email protected] [mailto:[email protected]] On 
Behalf Of Marcum, John
Sent: Friday, January 8, 2016 8:15 AM
To: [email protected]
Subject: RE: [msmom] SCOM Desktop monitoring

We own the license actually. We own all of Sys Center for all workstations, 
desktops and users. It’s part of a suite we bought.

I was thinking someone told me SCOM doesn’t scale well past a couple thousand 
machines though.

________________________________
        John Marcum
            MCITP, MCTS, MCSA
              Desktop Architect
   Bradley Arant Boult Cummings LLP
________________________________

  [H_Logo]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Garth Jones
Sent: Wednesday, January 6, 2016 1:01 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [msmom] SCOM Desktop monitoring

I have always thought the cost was nuts. ( I haven’t looked at the cost in 
years, truth be told) Yes, there are time where it make sense but for the 
average PC, is the cost worth it?



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Casey Robertson
Sent: Wednesday, January 6, 2016 1:32 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [msmom] SCOM Desktop monitoring

Wow – I ran into one guy that ran it just for Excel.  Their traders relied so 
heavily upon it they needed to know right away if Excel was borked and needed 
fixing/reloading.

From: <[email protected]<mailto:[email protected]>> 
on behalf of "Marcum, John" <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, January 6, 2016 at 10:15 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: RE: [msmom] SCOM Desktop monitoring

Seriously? Every time I’ve even thought about doing that all the SCOM guys and 
MS folks tell me it’s insane to even think about doing it. I only have 1000 
desktops where I am now and I was told it was an insane idea.

________________________________
        John Marcum
            MCITP, MCTS, MCSA
              Desktop Architect
   Bradley Arant Boult Cummings LLP
________________________________

  [H_Logo]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jeremy Pavleck
Sent: Wednesday, January 6, 2016 11:57 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [msmom] SCOM Desktop monitoring

I will get back to you in more detail when I can, but yes I have experience. In 
fact, we just rolled out SCOM monitoring to 13,000 desktops.

On Wed, Jan 6, 2016 at 12:07 PM, Steven Peck 
<[email protected]<mailto:[email protected]>> wrote:
I am beginning some research into monitoring desktops with SCOM.  Does anyone 
know of a good best practices document or write up on doing this?  Currently 
all my experience is with server monitoring.  The request is typically vague at 
this point but I want to at least get an overview.  Checking on the current 
sources now (TechNet docs) but figured I would ask if anyone knew of something 
more specific.  Like is it even a good idea to mix server and client monitoring 
in a mid sized environment?  (~1300 servers monitored currently)

Thanks,
Steven Peck
http://www.blkmtn.org<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.blkmtn.org&data=01%7c01%7ckevin.holman%40microsoft.com%7ce39d723af0364acf5de008d31836be49%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ts9xnYUH8apoGty1Ea7LV905cNSyTJg6i6fnJ3JYV5s%3d>




________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.





Reply via email to