- #RHEL 7 WINDOWS INTEGRATION GUIDE INSTALL#
- #RHEL 7 WINDOWS INTEGRATION GUIDE PASSWORD#
- #RHEL 7 WINDOWS INTEGRATION GUIDE DOWNLOAD#
If you made a mistake in editing the file, you can close without saving your work by entering :q!. To save and close the sudoers file, enter :wq. This setting allows the service account to elevate without requiring a password.ģ. Move down the file until you find the line root ALL=(ALL) ALL, and enter opsmgrsvc ALL=(root) NOPASSWD: ALL just after it. This setting allows the service account to login without requiring a TTY session.Ģ. Move down the file until you find the line Defaults requiretty, and enter Defaults:opsmgrsvc !requiretty just after it. While still logged into the Linux SSH session as root, open the sudoers file editor by typing visudo and then:ġ.
#RHEL 7 WINDOWS INTEGRATION GUIDE PASSWORD#
Next you will configure the sudoers file, giving the opsmgrsvc account the ability to elevate and execute privileged commands without requiring a password (this is a SCOM requirement). You will be prompted to enter the password after issuing the command. Create the opsmgrsvc account using the following command: Login with an account that has privileges to add user accounts and modify the sudoers file, or login with root. Launch Putty and connect to the Linux host by entering the host name or IP address of the RHEL system and clicking Open. The most common is Putty, which can be downloaded at. There are several free tools you can use to establish a SSH session to a Linux system. In this example, SCOM will leverage a single Linux account to perform all activities: opsmgrsvc. Most out-of-box monitoring activities are performed using low privileges on the Linux system, but some activities do require elevation using sudo.
#RHEL 7 WINDOWS INTEGRATION GUIDE INSTALL#
Here are the tasks that will be addressed in this walk-through:ġ: Create a Linux user account for the OpsMgr serviceĤ: Verify DNS – forward and reverse lookupĥ: Create a cross-platform monitoring resource poolĦ: Install certificates on resource pool membersīefore attempting to discover and install the SCOM agent, an account needs to be created on the Linux system and the sudoers file must be configured to allow the account to execute certain commands. RHEL 6 Evaluation (download the rhel-server-6.3-x86_64-dvd ISO)
#RHEL 7 WINDOWS INTEGRATION GUIDE DOWNLOAD#
If you do not have an SCOM environment or a RHEL system in your lab, you can download evaluation versions from the links below (these links may be outdated at the time you are reading this). There may be better practices or methods for configuring Linux – comments are welcome.
This is intended to familiarize SCOM administrators with the entire process. Windows Firewall is not turned on, and the RHEL system is running with default IPTABLES configuration.ĭisclaimer: I do not claim to be an experienced Linux admin. It is also assumed there are no firewalls between the SCOM management servers and the RHEL system. Everything in this demonstration assumes a new installation of RHEL6 with no additional configuration. This is a step-by-step article on installing the SCOM agent on a RHEL6 system, both from an SCOM and Linux administrator perspective.