scom 2012 r2 agent installation · waleed mostafa blog: 1 introduction the below are the deferent...
TRANSCRIPT
SCOM 2012 R2 AGENT INSTALLATION
FOR WINDOWS
Waleed Mostafa [email protected]
http://waleedmostafa.wordpress.com
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
table of contents
1 Introduction .................................................................................................. 2
2 SCOM 2012 R2 Agents Supported Operating System ................................................ 3
3 Agent Push ................................................................................................... 4
4 Agent manual installation ................................................................................. 7
4.1 MSXML 6.0 installation steps if you install on Windows 2003 if not please skip. ......................... 7 4.2 Agent Installation steps ................................................................................................................ 9
5 Certificates configuration .............................................................................. 13
6 Agent approval ............................................................................................ 14
7 Agent act as proxy configuration ..................................................................... 15
8 Agent failover configuration ........................................................................... 16
9 Active Directory Management Pack Helper Object ............................................... 17
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
1 Introduction
The below are the deferent type of the SCOM agent deployment/installations.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
2 SCOM 2012 R2 Agents Supported Operating System
Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2003 SP2, Windows 8, Windows 8.1, Windows Embedded POSReady 2009, Windows Embedded Standard 7 SP1.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Processor Architectures: x64, x86.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is
required when installing on Windows Server 2003.
Windows PowerShell 2.0 or Windows PowerShell 3.0 --- > required to run OpsMgr
MPs that use PowerShell Scripts.
Microsoft .NET Framework 3.5 or later.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
3 Agent Push
Agent push can only be performed for computers located in the same domain as the Management Servers or in fully trusted domains (bi-directional).
Note that agent push from the console are automatically updated if the Management Servers has been updated.
Open the console with a
SCOM administrator account.
Go to the Administration
panel, right-click on Device
Management and select
Discovery Wizard.
Select Windows computers
then click next.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Check Advanced discovery,
select Servers Only or Client
Only or both and select the
Management Server or
Gateway on which the
agent(s) will be attached.
Check Browse for, or type-in
computer names and enter
the list of computers (FQDN)
you want to deploy agent on.
Enter the information of an
account that has administrator
privileges on the target
machines and click on
Discover.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Select the agent that have
passed the discovery checks
and select Agent as
Management Mode.
Leave the default parameters
and click on Finish.
Agent has been successfully
installed.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
4 Agent manual installation
The following steps have to be done locally with an administrator account. The agent’s sources are available.
4.1 MSXML 6.0 installation steps if you install on Windows 2003 if not please skip.
Double-click on msxml6.msi.
This is the version for x64
servers; there is also an x86
version available of msxml6
on the SCOM media if
needed.
This pop-up may appear,
click on Yes.
Leave the welcome screen.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Select I agree the terms in
the license agreement.
Enter a Name and a
Company name.
Click on Install.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Once installation is finished,
close the wizard.
4.2 Agent Installation steps
First, make sure the agent can resolve the gateway FQDN. If not you will need to modify the %WINDIR%\System32\Drivers\etc\hosts file as follow. This example is for an agent on workgroup.
Run CMD as Administrator.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Type cd <Source location>, type MOMAgent.msi This is the x64 version of the msi, there is also a x86 version available on the gateway.
Leave the welcome screen.
Click I agree.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Use the default parameters.
Check Specify Management Group information.
Enter the Management Group Name, SCOM-MG, the Management Server name, GW001 and validate.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
Use Local System as the Action Account.
Click on Install.
Once installation is complete, close the wizard.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
5 Certificates configuration
At this time the agent is not able to communicate with its Gateway. Please refer to this link for certificates configuration.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
6 Agent approval
Once certificates are configured and the agent is able to communicate with its parent, we need to approve it.
An entry should appear in the SCOM console for our agent in the Administration pane in the Pending Management folder. Right-click on it and select Approve.
Click on Approve.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
7 Agent act as proxy configuration
Most of the SCOM Management packs need to enable agent act as proxy.
On the agent Properties check
the allow agent to act as proxy
option then click ok.
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
8 Agent failover configuration
To configure agent failover, connect to the Management Server using a SCOM administrator account and launch the Operations Manager Command Shell. Run the following commands (The agent must already have its primary server configured with the right one:
Open OpsMgr PowerShell as administrator, run the PS command.
$primaryMS = Get-SCOMManagementServer | where {$_.Name –eq ‘GW001’} $failoverMS = Get-SCOMManagementServer | where {$_.Name –eq ‘MS003’}
$agent = Get-SCOMAgent | where {$_.Name -eq ‘RS007’} Set-SCOMParentManagementServer -Agent: $agent -PrimaryServer:
$primaryMS Set-SCOMParentManagementServer -Agent: $agent -FailoverServer:
$failoverMS
Verify the configuration PS command
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq ‘GW001’}
$Agents | sort | foreach { Write-Host "";
"Agent :: " + $_.Name; "–Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers(); foreach ($managementServer in $failoverServers) {
"–Failover MS :: " + ($managementServer.ComputerName); } }
Write-Host "";
Waleed Mostafa Blog: http://waleedmostafa.wordpress.com
9 Active Directory Management Pack Helper Object
If the agent is installed on a domain controller, we need to install the Active Directory Helper Object.
Right-click on OOMADs.msi, then install, This is the x64 version of the tool. An x86 version is available in the SupportTools folder on the SCOM media.
Once installation is over close the window.