Install Scom Agent Manually Reset

Earlier this week I did some tests around Ubuntu Server and Operations Manager 2012. I did the same in Operations Manager 2007 R2 and the way to get the monitoring to work is almost the same in both products. All challenges that I meet was the same in both products.

Before we continue I would like to remind you that Ubuntu is not support by Microsoft in Operations Manager 2007 or 2012. The management pack and the agent I am using is community projects and is not supported either. I installed a X86 Ubuntu Server version 10.04.3. I configured it with a static IP-number (sudo vi / etc/network/interfaces (you might need to remove DHCP client to get that setting static sudo apt-get remove dhcp-client)), DNS settings (sudo vi / etc/resolv.conf) and restarted networking (sudo / etc/init.d/networking restart). Note there is a space in front of etc, due to some security setting in the blog platform:) ) If you are in a sandbox and don’t care about the firewall you can disable it by running sudo ufw disable.

Discussion Problems after Microsoft Monitoring Agent. Problems after Microsoft Monitoring Agent. By the SCOM agent. So when you install SCSM it is.

I would not recommend that for production servers but I would not recommend using a un-supported agent either 🙂 The first discovery result in this error Second try, after updated the forward and reverse DNS zones, result in this error As I didn’t had a management pack for Ubuntu or a Ubuntu agent I thought that could be a good next step. There is a Ubuntu and a Ubuntu at Codeplex that you can download and extract. You will notice there is two GetOSVersion.sh files, according to instruction at Codeplex you should use these files and replace the default file on your management server (C: Program Files System Center Operations Manager 2012 Server AgentManagement UnixAgents). Operations Manager copies this file over to the Linux/UNIX machine (/ tmp/scx-username) during discovery and executes the script.

The script will get what kind of Linux/UNIX it is and report back to Operations Manager, that decides if it has a management pack or not for the version. The challenge is that we had two files, to decide which one to use you can copy them over to your Ubuntu machine and manually run the, You will then see that only the GetOSVersion.sh that came with the management pack returns valid XML. In other word copy the GetOSVersion.sh from the agent folder to your UnixAgents folder on the management server. After that I still had some problem with the discovery, so I installed the agent manually on the Ubuntu machine (sudo dpkg -i scx-1.0. Antivirus Test Results 2009 Chevy there. 4-265.Ubuntu.10.x86.deb) and restarted the server (sudo reboot). After reboot I verified that Microsoft SCX CIM server was running (ps –ef grep scx). Then I ran the discovery again and a new error showed up. As you can see in the picture below there seems to be a problem with the certificate that the Ubuntu machine is trying to use.

Normally the Linux machine will get a certificate signed by the management server, during the discovery. But in this example we installed the agent manually so the certificate is self-signed by the Ubuntu machine. If you copy the certificate file (/ etc/opt/microsoft/scx/ssl/scx-host-ubuntu02.pem) to a Windows machine and rename it to.cer you can open it and look at it.

To solve this certificate issue, copy the certificate from your Linux box to your management server, run scxcertconfig -sign scx-host.pem scx_new.pem. Then rename scx_new.pem to the name of your Linux generated certificate and replace it on your Linux box. Restart the SCX service (sudo scxadmin -restart). After that the discovery worked fine and the Ubuntu machine showed up healthy in the console. Don’t forget to configure accounts and profiles for your Ubuntu machine Please note that this is un-supported by Microsoft and provided “as is” with no warranties at all.

Welcome to contoso.se! My name is Anders Bengtsson and this is my blog about Azure infrastructure and system management. I am a principal Premier Field Engineer (PFE) at Microsoft.

Contoso.se has two main purposes, first as a platform to share information to the community and then second as a notebook for myself. Everything you read here is my own personal opinion and any code is provided 'AS-IS' with no warranties. MVP awarded 2007,2008,2009,2010 My Books Search Contoso.se Search for: Top posts last month • • • Random Posts • • • Categories • (21) • (24) • (2) • (5) • (26) • (8) • (95) • (1) • (1) • (24) • (15) • (70) • (2) • (2) • (60) • (8) • (15) • (12) • (6) • (208) • (68) • (7) • (7) • (2) RSS Feeds Here are some Azure news: • ( System Center Operations Manager Team Blog) • ( System Center Operations Manager Team Blog) Recent Comments • on • on • on • on • on.

There are a few posts out there that talk about this issue: • • As SCSM was built by the SCOM team, a lot of the underlying code is SCOM at heart. So much so that the workflows within SCSM are run by the SCOM agent.

So when you install SCSM it is already installing a SCOM agent and you don't need to install a new one. All you have to do is configure it to report to your SCOM gateway server. Here is a post regarding this: However, if you DO install SCOM on a server with SCSM already installed, it will overwrite the Uninstall registry key and therefore the SCSM installation will look like it disappeared.

Here is the definitive Microsoft Technet article on the subject. (v=sc.12).aspx Hope this has answered your question.

There are a few posts out there that talk about this issue: • • As SCSM was built by the SCOM team, a lot of the underlying code is SCOM at heart. So much so that the workflows within SCSM are run by the SCOM agent. So when you install SCSM it is already installing a SCOM agent and you don't need to install a new one. All you have to do is configure it to report to your SCOM gateway server. Here is a post regarding this: However, if you DO install SCOM on a server with SCSM already installed, it will overwrite the Uninstall registry key and therefore the SCSM installation will look like it disappeared. Here is the definitive Microsoft Technet article on the subject.

(v=sc.12).aspx Hope this has answered your question. CIRESON COMMUNITY WEB SITE TERMS OF USE AGREEMENT BETWEEN USER AND CIRESON The Cireson Community Web Site is comprised of various web pages operated by Cireson, LLC (collectively, the web pages are referred to herein as the “ Cireson Community Web Site”). The Cireson Community Web Site is offered to you conditioned on your acceptance of the terms, conditions, and notices contained herein without modification or exception. Your use of the Cireson Community Web Site constitutes your agreement to all such terms, conditions, and notices contained in these Terms of Use. MODIFICATION OF THESE TERMS OF USE Cireson reserves the right to change the terms, conditions, and notices under which the Cireson Community Web Site is offered, including but not limited to the charges associated with the use of the Cireson Community Web Site upon written notice. LINKS TO THIRD PARTY SITES The Cireson Community Web Site may contain links to other Web Sites (“ Linked Sites”).

The Linked Sites are not under the control of Cireson and therefore Cireson is not responsible for the contents of any Linked Site, including, without limitation, any link contained in a Linked Site, or any changes or updates to a Linked Site. Cireson is not responsible for webcasting or any other form of transmission received from any Linked Site. Cireson is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Cireson of the site or any association with its operators. NO UNLAWFUL OR PROHIBITED USE As a condition of your use of the Cireson Community Web Site, you warrant to Cireson that you will not use the Cireson Community Web Site for any purpose that is prohibited by law, rule regulation or by any of these terms, conditions, and notices, including, without limitation the export of any Software or technical data to any country prohibited by law. You may not use the Cireson Community Web Site in any manner which could damage, disable, overburden, or impair the Cireson Community Web Site or interfere with any other party’s use and enjoyment of the Cireson Community Web Site. You may not obtain or attempt to obtain any materials or information through any means not intentionally made available or provided for through the Cireson Community Web Site. USE OF COMMUNICATION SERVICES The Cireson Community Web Site may contain bulletin board services, chat areas, news groups, forums, communities, personal web pages, calendars, and/or other message or communication facilities designed to enable you to communicate with the public at large or with a group (each a “ Communication Service,” and collectively, “ Communication Services”).

You agree to use the Communication Services only to post, send and receive messages and material that are appropriate, proper and related to the particular Communication Service. By way of example, and not as a limitation, you agree that when using a Communication Service, you will not: • Defame, abuse, harass, stalk, threaten or otherwise violate the legal rights (such as rights of privacy and publicity) of others. • Publish, post, upload, distribute or disseminate any inappropriate, profane, defamatory, infringing, obscene, indecent or unlawful topic, name, material or information. • Upload files that contain software or other material protected by intellectual property laws (or by rights of privacy of publicity) unless you own or control the rights thereto or have received all necessary consents. • Upload files that contain viruses, corrupted files, or any other similar software or programs that may damage the operation of another’s computer.

• Advertise or offer to sell or buy any goods or services for any business purpose, unless such Communication Service specifically allows such messages. • Conduct or forward surveys, contests, pyramid schemes or chain letters. • Download any file posted by another user of a Communication Service that you know, or reasonably should know, cannot be legally distributed in such manner.

• Falsify or delete any author attributions, legal or other proper notices or proprietary designations or labels of the origin or source of software or other material contained in a file that is uploaded. • Restrict or inhibit any other user from using and enjoying the Communication Services. • Violate any code of conduct or other guidelines which may be applicable for any particular Communication Service. • Harvest or otherwise collect information about others, including e-mail addresses, without their consent. • Violate any applicable laws, rules or regulations. Cireson has no obligation to monitor the Communication Services. However, Cireson reserves the right to review materials posted to a Communication Service and to remove any materials in its sole discretion.

Cireson reserves the right to suspend or terminate your access to any or all of the Communication Services at any time without notice for any reason whatsoever. Cireson reserves the right at all times to disclose any information as necessary to satisfy any applicable law, rule, regulation, legal process or governmental request, or to edit, refuse to post or to remove any information or materials, in whole or in part, in Cireson’s sole discretion. Always use caution when giving out any personally identifying information about yourself or your children in any Communication Service.

Always use caution when giving out any information concerning your employer or customers, if any. Cireson does not control or endorse the content, messages or information found in any Communication Service and, therefore, Cireson specifically disclaims any liability with regard to the Communication Services and any actions resulting from your participation in any Communication Service.

Managers and hosts are not authorized Cireson spokespersons, and their views do not necessarily reflect those of Cireson. Materials uploaded to a Communication Service may be subject to posted limitations on usage, reproduction and/or dissemination. You are responsible for adhering to such limitations if you download the materials. MATERIALS PROVIDED TO CIRESON OR POSTED ON THE CIRESON COMMUNITY WEB SITE Cireson does not claim ownership of the materials you provide to Cireson via the Cireson Community Web Site (including feedback and suggestions) or post, upload, input or submit to the Cireson Community Web Site or its associated services (collectively “ Submissions”). However, by posting, uploading, inputting, providing or submitting your Submission you are granting Cireson, its affiliated companies and sublicensees permission to use your Submission in connection with the operation of their Internet businesses including, without limitation, the rights to: copy, distribute, transmit, publicly display, publicly perform, reproduce, edit, translate and reformat your Submission; and to publish your name in connection with your Submission. No compensation will be paid with respect to the use of your Submission, as provided herein.

Cireson is under no obligation to post or use any Submission you may provide and may remove any Submission at any time in Cireson’s sole discretion. By posting, uploading, inputting, providing or submitting your Submission you warrant and represent that you own or otherwise control all of the rights to your Submission as described in this section including, without limitation, all the rights necessary for you to provide, post, upload, input or submit the Submissions. LIABILITY DISCLAIMER THE INFORMATION, SOFTWARE, PRODUCTS, AND SERVICES INCLUDED IN OR AVAILABLE THROUGH THE CIRESON COMMUNITY WEB SITE MAY INCLUDE INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. CIRESON (OR ITS SUPPLIERS) MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE CIRESON COMMUNITY WEB SITE AT ANY TIME.

ADVICE RECEIVED VIA THE CIRESON COMMUNITY WEB SITE SHOULD NOT BE RELIED UPON FOR PERSONAL, MEDICAL, LEGAL OR FINANCIAL DECISIONS AND YOU SHOULD CONSULT AN APPROPRIATE PROFESSIONAL FOR SPECIFIC ADVICE TAILORED TO YOUR SITUATION. NEITHER CIRESON NOR ANY OF ITS SUPPLIERS MAKE ANY REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, AVAILABILITY, TIMELINESS, AND ACCURACY OF THE INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS CONTAINED ON THE CIRESON COMMUNITY WEB SITE FOR ANY PURPOSE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, ALL SUCH INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS ARE PROVIDED “AS IS” WITHOUT WARRANTY OR CONDITION OF ANY KIND.

CIRESON AND/OR ITS SUPPLIERS HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT.

Hello Alex, We do not want to reach a point where we have to worry about querying the DW to find out if an alert has been closed manually over 14 days ago. There are several ways to avoid ever having to deal with this issue, but the easiest resolution is to import Tao Yang’s Self-Maintenance management pack and enable the Manually Closed Alert’s rule which runs every 24 hours by default and triggers an alert when a monitor based alert has been closed manually. Alternatively, you can configure your own alert using this script. Both methods are great candidates for automation using Orchestrator’s Monitor Alert activity or SMA to ensure that you never miss one of these issues. Thanks, Shawn Tierney Like.