Tag Info

Hot answers tagged

4

1) Yes. You will need an Active Directory infrastructure available. SCOM is heavily tied into those services. It is described further in the Infrastructure section of the Environmental Prerequisites. 2) Yes, but you may need a newer version of SCOM 2007. The original release version of SCOM does not support SQL 2008 because it didn't exist when it came ...


4

System Center is a suite of different monitoring, configuration management, and automation tools Microsoft sells for the Windows operating system. Collectively they achieve Systems Management. SCOM, System Center Operations Manager, is the monitoring component of that suite. SCCM, System Center Configuration Manager, handles configuration management. HP ...


4

None of these products will be impacted by the raising of the forest or domain functional levels. I can't think of a single application that would be impacted by this, as it typically only increases the number of features present in Active Directory.


3

Answer found, and it's a bit unpleasant (at least if you were expecting the people creating management packs to actually know what they are doing). Extracted from the monitor's description: This monitor verifies forwarder availability by performing an NSLOOKUP on the targeted forwarder. The script executes nslookup -timeout=<value> ...


3

SQL 2008 R2 is now supported for migrations if you install SCOM 2007 R2 Cumulative Update 4. KB Article: http://support.microsoft.com/kb/2449679/en-us Download Link: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=39a871e0-d996-4568-be5d-2edb6f539330&displaylang=en Upgrade Procedure (I think this will still be updated): ...


3

I've got these bookmarked... http://technet.microsoft.com/en-us/systemcenter/om/bb498235 http://technet.microsoft.com/en-us/library/bb310604.aspx (I'm a new member here, it wouldn't let me post more than two links)


3

To the best of my knowledge, the OpsMgr agent can only send data to one server; it cannot 'serve two masters', so to speak. Actually the agent can absolutely report to two different management groups. It's called "Agent Multihoming". Basically you just find the agent in Add/Remove programs and modify the install, it will bring up a dialog that will ...


3

This is entirely policy related and there's nothing you can do except suggest it if you're not in charge. If you want an admin to do something and they don't, then discipline if the only way. If you're not in a position to discipline anyone, then it's not your decision to make. You could always present your case to their manager and hope for the best, but ...


2

SCOM 2007 R2 still does not support SQL 2008 R2 for existing installations. The latest cumulative update for SCOM (CU#3) was just released November 15 and didn't include support, so you will have a while to wait for a CU to cover it. You may be able to contact Microsoft Support and see if a hotfix is available through that route instead.


2

Jmeter is great for this. It's not 100% obviously how to use as it's quite flexible, but there are plenty of load-testing tutorials out there for it.


2

Microsoft's Documentation: How to move a site database in SCCM You must have SCCM 2007 SP1 installed with Hotfix KB955262 to use SQL 2008. For SCOM you must have SP2 installed. Then you get to move the three databases separately: Warehouse, Database, and Reporting.


2

The maths add up for me. 55 > 2 > 1 > ? = SCOM Also, to be honest, the amount of stuff there is to monitor on a Windows machine, with all the various flavors of Microsoft software sitting on them, for me, would make a tool specialized in monitoring that product a priority. Lastly, I believe SCOM 2007 can monitor several *nix flavours, ESX, and any SNMP ...


2

According to the documentation, you can easily place a whole server in maintenance mode: In the Operations console, click the Monitoring button. In the Monitoring pane, expand Monitoring, and then click Computers. In the Computers pane, right-click the computer that you want to place into maintenance mode, click Maintenance Mode, and then click ...


2

This is a known issue that is solved when installing upate rollup 2. See http://support.microsoft.com/kb/2706783/en-us Issue 2 The Set-SCOMLicense cmdlet fails if the management group evaluation expiration time-out has expired. So install update rollup 2 en retry inserting the license key.


2

If powershell is installed on the RMS or RMSe then I would write a script that would check that the healthservice, cshost and omsdk services are running. I would also try to identify a concrete event message that indicates that your SCOM environment has lost connectivity to the database; the OpsMgr log will surely show this but I can't recall one off the ...


2

Since 2008, SQL Server answers on dynamic ports by default. You can set static ports in SQL Server Configuration Manager. To turn Dynamic Ports off, erase the 0 that appears on the right side, above the port number (in this case, 1433). Once you have static ports, you'll need to enable access to 1433 TCP and 1434 UDP.


2

I had to configure the static ports for IP1, IP2, IPAll, Erase the 0 at Dynamic Ports and set TCP Ports to 1433, however, Im using a named instance. also open firewall ports Once you have static ports, you'll need to enable access to 1433 TCP and 1434 UDP. (Katherine Villyard) See Screen Shots for configuration details.


2

Of course it can. There are also a lot of neat hardware vendor-specific packages for it.


1

You might find this helpful: Managing Allowed List for the CI Connector


1

There is no difference. "Close Alert" updates the resolution state of the alert to 255 - so does "Set Resolution State -> Closed"


1

What Microsoft says - Because of the limited communication between an ACS forwarder and an ACS collector you only need to open the inbound TCP port 51909 on a firewall to enable an ACS forwarder, separated from your network by a firewall, to reach the ACS collector. You can check if default port is not changed from 51909: On the ACS Collector server run ...


1

If you need to check that SCOM agent is installed on this machine (which literally means that this machine is monitored by SCOM) - it's enough to check that the following Windows service is installed: - HealthService (it's display name different for different versions of SCOM and might be a "Microsoft Monitoring Agent" or "System Center Management ") If ...


1

Instead of trying to push the agent from the SCOM server, try running the agent installer manually from the target server. The installer GUI may give you a better idea of why the install failed. In my case the problem was that the System Center Advisor Agent was installed, which can not co-exist with the SCOM agent.


1

This is not a false alert. It shows disc latency in excess of 40ms. Whether or not that is a PROBLEM is your definition - and you should adjust things. Acceptable disc latency really depends on whether the systems get too slow and it is a broad topic and one that has to be defined by you. On secondary VMs I accept 50 or even 100ms at times, on my main ...


1

Which version of SCOM are you using? In my 2007 install, its a view not a table. Use adtServer.dvAll5 which contains only the first 5 event params, or adtServer.dvAll which has ALL params, but it slower.


1

You can write a script that can place the monitored objects in Maintenance Mode. Best way to do this is to create either a dynamic or static group of the objects you do not want to alert on. Then you can create a powershell script that runs prior to your reboot windows that places the group into maintenance mode for a duration that is acceptable.


1

If Nagios is making that information available somewhere (e.g. in logs), SCOM can query it and generate alerts. You may just have to write your own management pack. Here is a solution that looks promising: http://www.mbaeker.de/category/tools/scom2nagios/ If that doesn't work for you, then you should read up on management pack authoring so you can write ...


1

It doesn't matter. MPs are pushed to agents very soon after they are imported. From my experience, most people install SCOM without any additional MPs at first, then add them in an orderly fashion. If you just install a whole slew of MPs at one time, you might get alert floods that are difficult to pinpoint. When installing MPs, be sure to read the ...



Only top voted, non community-wiki answers of a minimum length are eligible