SCOM 2012 design plan

Hi
Am designing SCOM2012 R2 for monitoring 300 servers and 50 network devices . Client asks me to install server monitoring, network monitoring,ACS in only two servers since the monitored devices are very less . I would to know that enabling all this 3
services in two servers will work smoothly. What would be the best design solution for this requirement ?
All monitored servers are 2012 R2 and there is a separate high end DB server is hosting SCOM DBs'.All servers are running from single cloud location.

For SCOM Design, you can check below links
http://technet.microsoft.com/en-us/library/jj593271.aspx
http://blogs.technet.com/b/momteam/archive/2012/04/13/opsmgr-2012-design-guide.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Similar Messages

SCOM 2012 Design including DR

I have been spending quite a bit of time researching HA in SCOM 2012 and have seen other posters being pointed in the direction of best practice docs etc but none seem to talk about hyper-v replica. My initial implementation will consist of about 300
servers to be monitored, the sizing tool recommends 2 MS and a single SQL server hosting the OPS and DW SQL DB.
This seems a reasonable configuration but I need to incorporate a DR solution into this. We have a Hyper-V 2008 cluster in DC1 which is replicated to DC2 which is out DR site. I am proposing hosting all of the servers on the Hyper-V cluster,
in the event of DC1 going down my plan is to bring the replicated servers up in DC2.
Does this seem like a reasonable solution or am I missing something? Are there any limitations to this design that I am not seeing or any problems I am likely to run into?
Thanks

A good idea is to backup the operational database daily, and ship that backup using whatever tool or process you want. If you care about historical data, then I suggest setting up log shipping or similar for the data warehouse database.
In terms of DR for the MG, my preferred way to go about this is to have warm MS's in another DC, completely installed and ready to go. Depending on how "mission critical" monitoring is, this is about as good as it gets for DR. If monitoring is
number 1 priority mission critical to your business, then I suggest 2 MG's - one in each DC - and multi-homing your Windows agents and monitoring all other devices (network, UNIX/Linux) from both MG's at all times. When one fails, there is literally no outage
for those monitored instances in the DC that is still alive, and no additional DR procedures are really necessary in this case.
In my experience, monitoring is not mission critical. This is not my opinion, but the opinion of all the organizations I've worked with. There is a cost to DR, and having a completely HA scenario with absolutely no down time for those instances that are
still "alive", usually it simply isn't worth the cost and administrative overhead.
A simple backup and move job of the operational database, and a "seed" management server in another DC is typically the design I would suggest.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

SCOM 2012 Design questions?

While design SCOM 2012 , what are important things to be noticed ? like Environment to be monitored , Budget , Network Bandwith , Application to be monitor ..etc
Like this any other important things to be noticed.

For SCOM Design, you can check below links
http://technet.microsoft.com/en-us/library/jj593271.aspx
http://blogs.technet.com/b/momteam/archive/2012/04/13/opsmgr-2012-design-guide.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCOM 2012 design document

HI team,
can any one please share the design document.

Hi,
I would like to share this document with you. Hope it helps.
SC2012_OpsMgr_Design_and_Planning_Guide.docx
http://blogs.technet.com/cfs-filesystemfile.ashx/__key/telligent-evolution-components-attachments/01-4616-00-00-03-49-19-33/SC2012_5F00_OpsMgr_5F00_Design_5F00_and_5F00_Planning_5F00_Guide.docx
Niki Han
TechNet Community Support

SCOM 2012 R2 HA design but using SQL 2014 Standard edition

Hi All,
I want to deploy SCOM 2012r2 with a HA design (but have constraints!)
Plan is two management servers with all roles to each (fresh deployment so 2012r2 RU5)
SQL servers need to be 2014 standard edition due to licensing and cost constraints.
Design is to be split between two datacentres that are fibre connected and sub 3ms latency
Plan was to have a Management Server and a SQL server at each location.
Each location has a dedicated SAN but SAN replication is not an option.
What are my SQL options for the DB??
AlwaysOn FCI is not preferable as it gives a single point of failure due to shared storage requirement.
I read Database mirroring is not a supported config but this isn't Microsoft direct info just blog post, is this correct.
Which leaves me with log shipping, is this supported and the best option??
Would be great to get advice on what works well in the field with a contraint of having to use SQL Standard edition!
Thanks
James

Hi,
No additional licenses are needed for management servers or SQL Server technology.
System Center 2012 R2 licensing
http://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx#tab=2
Reference:
SCOM 2012 R2 HA options with Server 2012 and SQL 2012
https://gallery.technet.microsoft.com/SCOM-2012-R2-HA-options-540beb95
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 R2 Upgrade Plan Discussion

Dear Experts,
Currently I have a RMS and one MS Server with SCOM 2007 R2 in my Test Environment (Windows 2008 R2).
Now, The Upgradation plan is below and please correct me if I am wrong.
SCOM 2007 R2 CU4 --> SCOM 2012
SCOM 2012 --> SCOM 2012 SP1
SCOM 2012 SP1 --> SCOM 2012 R2.
So we need to purchase of three types of SCOM 2012 versions S/W or else we can simply download those versions from Microsoft ?
Please provide me the complete process of this Migration cycle.
Saravana Raja

Hi Saravana:
Upgrading to System Center 2012 – Operations Manager is supported from Operations Manager 2007 R2 CU4, or from the latest available CU. See
http://technet.microsoft.com/en-us/library/hh476934.aspx.
As for upgrading from SCOM 2012 to SCOM 2012 SP1 to SCOM 2012 R2, MVP Marnix Wolf is clear that you need to perform each upgrade step separately:
http://thoughtsonopsmgr.blogspot.com/2013/07/upgrade-paths-to-system-center-2012-r2.html. The "complete process" would consists of performing the upgrade for each version one after the other, again, just as you put in your plan.
You do not need to purchase any additional software, but you will need to download the 3 versions as you described from Microsoft volume license site or other media source.
John Joyner MVP-SC-CDM

Windows 2012 upgrade plan to R2 hosted with SCOM 2012 SP1

Dear Experts,
Currently we are hosting SCOM 2012 SP1 on Windows 2012 Operating System and the Server team plan to upgrade Windows server OS 2012 to Windows OS 2012 R2.
So, Is there any Potential road blocks and things to take care for SCOM 2012 SP1 if we want to upgrade the Windows 2012 R2 OS.
Thanks,
Saravana
Saravana Raja

Hi,
I have seen this a couple of times without any issues.
Just make sure you backup all SCOM related (databases if local, management packs etc).
www.coretech.dk - blog.coretech.dk

SSRS for SCOM 2012 need separate instance of SQL

Hi All,
My customer has planned to install SCOM 2012 R2 in their environment. I designed for them as followings:
Planned 3 MS servers namely, MS1, MS2 & MS3
The rolls planned on those MS servers as follows:
MS1 – Management Server,
Operation console & Web console
MS2 – Management Server,
Operation console & Web console
MS3 – Management Server,
ACS, SQL Reporting services & SCOM Reporting server
Customer has their existing SQL cluster database configured. This existing SQL database is also utilized by other applications.
I am planning to keep all the SCOM databases (Operation Manager DB, Operation DW DB, Reporting DB & ACS DB) on the central location on SAN storage of the SQL cluster.
For this, I requested to customer for a new instance of SQL to install SCOM DBs & SQL Server Reporting services.
Customer raised a concern on Why would need to install the databases & SQL Server Reporting services on a separate instance.
I replied as, The new instance requested will host the databases along with the SQL Server reporting services (SSRS).
The installation of SQL server report server will integrate the security of selected SSRS instance with Operation Manager role based security. Any reports that were previously installed on this
SQL server instance might become inaccessible. No other applications that are using SQL Server Reporting Services can be installed on this instance of SQL Server.
On this, Customer says if SSRS is planning to install on the MS3 server then there would not need to create a separate instance on SQL cluster. We can go with the existing instance for installation
of SCOM databases on SQL cluster and SSRS on MS3 server.
I need your inputs on this, as can I still require the new instance of SQL on SQL cluster or can go with the existing instance for installation of SCOM databases on SQL cluster and SSRS on MS3 server.
Kindly provide your inputs.
Regards,
SandeepK

Although SCOM can share a single instance running SQL Server to store data, this is not a recommended configuration. The SSRS is the same, no document says that it can be shared with others.
Also, refer to
http://social.technet.microsoft.com/Forums/en-US/84e89021-6794-421e-b41c-5da1186aae2e/sccm-and-scom-reporting-on-the-same-sql-instance?forum=configmgrreporting
Juke Chou
TechNet Community Support

SCOM 2012 Global Architecture, One management group or multiple?

Hi Folks,
I work for a global firm, we have multiple data caters in different regions. America, UK, Australia, China etc etc. We are looking to roll out SCOM 2012 for monitoring all systems. Our environment
1,000 Windows servers
All servers on the same Active Directory domain
10 Mbps links between data centers.
My question is around whether to use multiple management groups or one? I’ve seen recommendations for both. For example
In the Infrastructure Planning and Design guide for SCOM 2012 it is stated:
“A centralized management model with large remote locations works best with a management group in each region and a local management group (which provides a consolidated view of alerts and status) in the parent location. In this case, the centralized management
group connects through the software development kit (SDK) and functions as an additional console on each of the connected management groups.”
However moderators in this forum have stated
“Each management group has its own set of SQL Servers and Management Servers \ Gateways. It also adds considerably to administrative overhead. I'd try to avoid
multiple management groups where possible.”
” It will get expensive in terms of hardware and software with multiple management groups and you will duplicate a lot of work with regards to overrides”
“If you go with multiple Management Groups then you would need to add on a fair number of SQL licenses plus additional hardware. “
“Presumably if I have multiple management groups will that mean I will have to
create rules for each Management Group- correct. Same
with overrides. It could add a lot of administrative overhead. “
It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance. I’ve heard
stories about SCOM deployments architected in this way not performing well because of network latency. i.e admins from all regions besides the region local to the SCOM deployment not wanting to use SCOM because application performance is too slow.
What would the SCOM experts recommend for this scenario?
MH

1) My question is around whether to use multiple management groups or one?
Factors to consider in determine the number of Management group
• Scaling
• Agents separated from their management server by WAN-speed network links
• Political, administrative or security requirements within the organization requiring separate management groups.
• A view of AD DS topology required across multiple forests.
• A dedicated management group required for auditing purposes.
• Disaster recovery functionality required.
• Consolidated views of connected management groups required in Operations Manager.
• Operations Manager integration with the VMM console.
With refer to your situation
a) 1,000 Windows servers
b) All servers on the same Active Directory domain
c) 10 Mbps links between data centers.
It is suggest that one Management group is required.
2) It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance
It is recommend that you should deploy Gateway server in region office which has more than 10 agents.
• Gateway server reduce network bandwidth utilization. Agents located across WAN links consume network bandwidth, potentially affecting service delivery to and from the remote location. A gateway server can consolidate the traffic.
Roger

How to create a group in SCOM 2012 R2 based on SCCM Collection?

Is there a way to create a group in SCOM 2012 R2 based on sccm collection? I am planning to use that group for maintenance mode.
Thanks, Samer

Hi,
I think you could query all the collectin members from SCCM database then use powershell to add them to a specific OU.
How to Create Groups in Operations Manager
http://technet.microsoft.com/en-us/library/hh298605.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Can overrides from SCOM 2007 R2 be used in a new SCOM 2012 R2 installation?

Hi All,
I'm wondering if we can "easily" use our overrides/configuration from our current SCOM 2007 R2 implementation and use them in a new SCOM
2012 R2 environment that we plan on standing up. We are using SCOM to monitor approx. 400 servers (physical and virtual).
We have been using 2007 R2 for a few years and we'd like to start using 2012 R2. Instead of using the update path (2007 R2 to 2012
to 2012 SP1 to 2012 R2), we are planning on setting up a new 2012 R2 environment and configuring our servers to start reporting to 2012 R2 (after it has been configured in such a way as to "mimic" our 2007 R2 environment).
Ideally, we'd like to avoid going through the upgrade path. (We'll leave our 2007 R2 environment running so that we can still access "historical
data" until the new 2012 R2 environment has had a chance to build up its own "historical data".)
So ... I was thinking we could export our overrides from 2007 R2 and import them into 2012 R2, but I'd like to verify that this approach makes
sense. We haven't done extensive customizations to 2007 R2 in terms of Distributed Applications or Management Pack Objects (although we have made some changes - which I guess we could manually configure in 2012 R2 to offer the same "experience").
The following are some of the Management Packs that we are using in 2007 R2:
Microsoft Windows Active Directory
Active Directory Certificate Services
EMC Storage Monitoring
IBM Hardware
Microsoft Exchange Server 2010
McAfee
Microsoft Forefront Server Protection 2010
Microsoft Office SharePoint Server 2007
Microsoft SQL Server
Microsoft Windows DNS Server
Microsoft Windows WINS
Microsoft Windows Hyper-V
Microsoft Windows Internet Information Services
Microsoft Windows Server
Microsoft Windows DHCP
NetBackup Operations Manager
Office Communications Server
OpsLogix (BlackBerry)
Service Level Dashboard for OpsMgr 2007 R2
SolarWinds Orion
Schedule Maintenance Mode
Team Foundation Server 2010
Virtual Machine Manager
Microsoft Windows Cluster
Operations Manager 2007 R2
I appreciate all feedback and the sharing of you expertise.
Thanks, Joe.

As long as the base pack works and you wish to retain the customisation then you should be ok, there’s a good article
here which explains how to perform the migration and some of implication/things to check.
There will be complications if you’ve stored anything in the default mp but this is explained in the above article.

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Logical Disk space on a virtual Computer (not a Server) in SCOM 2012

Hello all-
   I have a sort of unique situation for our SCOM environment. We are already doing logical disk space monitoring on all of our SERVERS with no issues. Now we have one user who requires monitoring on their computer. This is really
a virtual workstation, as opposed to a real computer.   Since it's virtual, it's really online all the time.    Whether its right or wrong, they are using this virtual workstation sort of as a server. Anyway, they want me to
monitor the disk space for the C drive on this virtual computer. I'm having difficulty setting up such a monitor on a computer like that...
I got the SCOM agent installed onto the computer. SCOM is reporting it as being "Healthy".   Now how can I define a logical disk space monitor for it?   I attempt to create a monitor:   Windows Performance Counters,
Static Thresholds, Single Threshold. Then how can I direct the monitor at the C drive on the computer? I have to fill in the Object, Counter and Instanace. Normally I would click on the
Select button, then I would type in the server name and hit Enter and it would bring up all the objects it will allow me to monitor. Unfortunately it doesn't let me type in the computer name and hit enter in the same way. When I
do so, it says "The network path was not found". If I click on the
... button next to the Computer field, it brings me to a Select Computer screen. In here, I am type in the computer name and then I click
Check Name and it does appear to find it, and it underlines the computer's name.    So I then click
OK to bring me back to the previous screen where it presents me with the same "The network path was not found" error immediately. So I can't seem to navigate to the computer in SCOM and select the C drive, as I would be able
to for a server.
I tried to sort of force it in, instead of browsing for the computer and selecting the C drive. I simply put
LogicalDisk in for the Object then Free Megabytes for the Counter, then
C: for the Instance (as shown in the attached screen print.
Then I just applied my new rule to the computer via SCOM. I don't get any error messages when setting it up that way, but it certainly doesn't work.
So with all that said, can anyone help me out setting up a logical disk space monitoring for a COMPUTER in SCOM 2012 SP1 please? Please let me know if you need any more information!

Thanks, that would probably do it, I'm going to keep that as my backup plan. However, my current feeling is that it might be a bit overkill to install a whole management pack, when all I want to do is monitor a single C drive on a single workstation.
The rest of the monitors in the management pack I wouldn't have any interest it.   Let me ask you a question maybe you will know the answer to... Shouldn't I be able to monitor that drive even without that management pack installed?   I
mean some combination of settings for the Logical Disk Space rule in that management pack works for computers/workstations. Shouldn't I be able to reproduce that one single rule without the management pack? Does anyone have that management pack
installed? Could you possibly look at the Client OS Logical Disk Space rule and send me some screen shots or something?   Or am I missing something? Is the management pack needed for other reasons in order to monitor this?

Performance of Network Monitoring in SCOM 2012 SP1

Hi all!
I´ve problems with performance of the network monitoring feature in SCOM 2012 SP1.
According to the
guide the following should be adeqate:
•1000 network devices (approximately 12,500 monitored ports) managed by a resource pool that has three or more management servers
•500 network devices (approximately 6,250 monitored ports) managed by a resource pool that has two or more gateway servers
We have 800 network devices with a total of 24000 ports,
BUT only 1500 of them are monitored. This is basically what happens automatically after discovery, since only ports between monitored devices are monitored by default.
For this setup I first used only one management server dedicated to the Network Pool,
based on my assumption that if two servers could monitor 6250 ports, one server would be more than enough for 1500. I found this configuration working very poorly so I added another server. I now have two servers
dedicated for the Network Resource Pool. (They are NOT members of the “All management servers resource pool”)
Still, I get constant alerts regarding Health Services Private Bytes on these servers. They vary between 1-2Gbytes. Furthermore, if one of the servers goes offline, the network devices that was monitored by that server becomes grey for
several hours. Even if the server only is rebooted it takes forever to get everything online and green again.
I don´t really know what I should do now. I had a plan to replace our current network monitoring system (SNMPc) which easily handles this load on only one server. They are of course completely different beasts, but still. SCOM seems to
require a massive back-end to produce equivalent real life results.
Any suggestions or reflections from the field are highly appreciated!
Regards
Peter

Hi,
Try to overide the monitor Health Services Private Bytes by the following steps.
◾Go Authoring space – Management Pack Objects – Monitors
◾Go to change scope – select clear all – look for Health Service – tick it and press OK.
◾Expand Health Service – expand Entity Health – expand Performance – expand Health Service Performance
◾Select the Health Health Service Private Bytes Threshold.
◾Right click the mouse and choose to overide the monitor for a group
◾Select the group called Management Server Computer Group and press OK
◾Select the Agent Performance Monitor Type – Threshold and change the value 104857600 to ex. 2610612736.
◾Select to store the overide in a management pack you have created and press OK
Juke Chou
TechNet Community Support

Which type of SQL DB do I need for SCOM 2012?

Hello everyone,
We would like to install a SCOM 2012 Server for reporting and alerting of our Exchange and Lync Server.
Our guys from database management asks me, what type of SQL DB do I need. "An SQL DB with 100GB" shouldn't be enough :-( I'm not very familiar with SQL.
So, which informations could be missing?
Thanks in advance and best regards
Daniel
Beste Grüße

Daniel,
usually Standard Edition is enough and included in the SCOM (agent) license.
Here you find more about requirements:
https://technet.microsoft.com/en-us/library/dn249696.aspx
SQL specific:
Check for updates and hotfixes for Microsoft SQL Server. See
SQL Server in System Center 2012 R2.
Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
For SQL Server collation settings, see
SQL Server in System Center 2012 R2
The SQL Server Agent service must be started, and the startup type must be set to automatic.
The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
For information about how to resolve the issue, see
System Center Data Access Service Start Up Failure Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 R2 Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
You should have a look at the sizing calculator:
http://download.microsoft.com/download/C/A/6/CA60425C-950B-456E-986C-C5F2FCD5668D/System%20Center%202012%20Operations%20Manager%20Sizing%20Helper%20Tool%20v1.xls
Good luck,
Patrick
Please remember to click “Mark as Answer” on the post that helped you.
Patrick Seidl (System Center and Private Cloud)
Website: http://www.syliance.com
Blog: http://www.systemcenterrocks.com

SCOM 2012 design plan

Similar Messages

Maybe you are looking for