Scom 2012 R2 Convert Manually installed Agents to Remotely managed

Hi
Need to convert manually installed agents to remotely managed.
Found this post :
http://damatisystemcenter.com/2013/01/25/convert-manually-installed-agents-to-remotely-managed/
The last Query converts one agent to remotely managed
How do I do if I want ALL my agents to be converted to remotely ?

Hi,
Setting Agents as Remotely Manageable in SCOM 2012 R2
http://daxsnippets.wordpress.com/2014/04/08/setting-agents-as-remotely-manageable-in-scom-2012-r2/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

Manually Installed Agent is not showing up in the Operations Manager Console Under Pending Management.

Hi Community,
I submitted this question because I'm a bit stuck with SCOM 2012 R2, I'll try to explain briefly what is happening right now in my environment, we have a DEV SCOM Deployment in which all the roles are installed in a single server, this servers is a
VMware machine running Windows Server 2008R2.
The Initial installation of the SCOM Operations Manager and all the other components was not performed by me but by a co-worker, unfortunately he doesn't remember much about the initial configuration. So i had to pickup where he left things about a year
ago, neither of us are SCOM experts, and we have almost no previous experience with previous versions of this application.
Now the problem that I'm facing is the following, all the DEV Servers are Domain Controllers and one of the indication within the "Guide for System Center Management Pack for Active Directory for Operations Manager 2012" states the following
Configuration
Supported?
Agent-less monitoring
No
After my first review I notice that our servers were being monitor by agent-less mode and given the above statement from the Operations Guide the only way that we could ever get those domain controllers monitor by SCOM would be by installing the agent on
each server, so I read somewhere (Can't remember where) that in order to install the agents in all the servers I should first remove them from the Agent-less node, which I did. Then I tried to use the discovery wizard to get the agent install in all of them
but it didn't matter how many times I try the servers never show up.
I read in a Tech Net Article that you had to modify the security settings so SCOM would let me decide if I wanted to approve it or not.
--> http://technet.microsoft.com/en-us/library/hh212853.aspx
I performed the suggested steps from the article but still the servers were not showing up, not even if I run the Discovery wizard, so I decided to go and perform the installation manually in a couple of servers I was able to install the agent in one of
the Domain Controllers, I configured the agent to use a service account that has Domain Admin rights. An hour after I installed the agent I went back to the Operations Console Manager and I check under Pending Action but the Server was not showing up. So i
went back to the Internet to try to find out if someone else had experience the same problem, and in one website some mentioned that if the servers were not showing up it was probably because they were still register in the SCOM Database, now I have no idea
of how i can check that or How can i remove them from there to have them available again, but what troubles me the most is that even after i installed the agent manually the server were not being recognize.
I went to the Event Viewer and I found one particular event that caught my attention, see below :
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          6/12/2014 12:48:19 PM
Event ID:      11551
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MyManagementServer
Description:
Computer verification failure for Machine Name: MyManagementServe is 0x800706BA. The RPC server is unavailable.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">11551</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-06-12T16:48:19.000000000Z" />
    <EventRecordID>1945680</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>MyManagementServer</Computer>
    <Security />
</System>
<EventData>
    <Data>MyManagementServe</Data>
    <Data>0x800706BA</Data>
    <Data>The RPC server is unavailable.</Data>
</EventData>
</Event>
Not sure if this is related to the problem that I'm facing right now, but , I make sure that the RPC Services were running and also the related dependencies too. There's no Firewall enable in any of the servers and DNS seems to be working properly.
Ports 135 / 5723 are open and listening so since I ran out of ideas, I would like to know if some of the experts in this field could perhaps give me some guidelines.
There's one caveat that I haven't mention yet and that is related to SQL, I checked and my user just has read access to SQL i'm not sure if that could affect this but i think is worth mentioning.
My main goal is to have all the servers showing up in the Operations Manager Console.
So thanks all in advance !
Oscar Loria

So you can ping and nslookup from your ms to these agents and vice versa right? I wouldn't do a manual install, I would push the agent from the management server. You can uninstall the agent manually, or use cleanmom to get rid of them. Then
do an install from the console. When you initiate the install from the console (management server), should it run into any issues it will dump out an error which will give you an idea of where the problem may be.
From Holmans post on this:
e MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
The MOM Server could not execute WMI Query "(null)” on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access. If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed. We need port 135 (RPC) and the DCOM port range opened for console push through a firewall.
3. Inspect WMI service, health, and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

Do manually installed Agents failover?

Hi, a very quick question that I can't find an answer for.
Does automatic failover work (once configured) for a SCOM agent that is manually installed?
I think they can't but would like confirmation.
Cheers

For SCOM 2012, all agents will automatic failover whether it is installed manually or not. you may also use the following powershell cmdlet to verify the auto failover of the agent
#Verify Failover for Agents reporting to MS1
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"--Failover MS :: " + ($managementServer.ComputerName);
Write-Host "";
Roger

SCOM 2012 Reporting Fails During Install

I am having issues installing the Reporting Module for SCOM 2012. Here is my environment:
Stand-alone SQL server with SQL 2012 (Default Instance and only is used for SCOM)
Reporting Services Installed and I am able to browse to the URL
Reader Account has access to both servers and both Report/OPM databases.
Stand-alone Management Server
Everything is running fine.
When I go to install Reporting on the SQL Server it fails during the Configuring Security phase and here are the logs:
Error:All retrys failed!!. Message:SetSRSSecurity Exception, now throwing:Cannot stop ReportServer service on computer '.'.
Error: :SetSRSSecurity failed: Threw Exception.Type: System.InvalidOperationException, Exception Error Code: 0x80131509, Exception.Message: Cannot stop ReportServer service on computer '.'.

I also see this error:
[12:50:50]: Error:
:StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingConfigurationHelper.ReportingConfiguration.ModifySRSServiceAccount(String userName, String userPassword, String sqlSRSServer, String srsServiceName, String sqlServerForSRSDatabase,
String srsDBName)
[12:50:50]: Warn:
:Message:SetSRSSecurity Exception Exception: The specified @job_name ('F5DDC431-93E3-41CF-8913-00EDFD457F99') does not exist.
The specified @job_name ('3AA30844-4417-479D-80EF-059C9CAAF84D') does not exist.
The specified @job_name ('A65C33A6-DC11-44AA-B8AD-077A7D94213D') does not exist.
The specified @job_name ('C9192EB7-87D8-475D-9826-100AF193F33F') does not exist.
The specified @job_name ('410DA81B-318F-4BD8-AA5B-14AC61AC82C3') does not exist.
The specified @job_name ('E26B57B7-72CE-449F-AA19-19B192CD10C0') does not exist.
The specified @job_name ('FF9BC31C-E6F9-4987-ABBC-1C20D41E0A7D') does not exist.
The specified @job_name ('BBE14DB5-E183-4F05-AC45-1CD147DD72BE') does not exist.
The specified @job_name ('D69172E5-4FD6-4FF2-9F98-1FA57C98B6B5') does not exist.
The specified @job_name ('566D3953-B305-43EC-9C08-2FA53CABA2FE') does not exist.
The specified @job_name ('B3D9B9B3-9C8A-4109-884B-36899D560A9B') does not exist.
The specified @job_name ('B47669F4-54A5-4F78-AEF4-40A9F40D9BC6') does not exist.
The specified @job_name ('97FA149B-5275-4A4D-A3C8-4E69B20C0D92') does not exist.
The specified @job_name ('86AEBFB5-CAA3-4D2A-859F-4E751B660257') does not exist.
The specified @job_name ('FE970B3F-D021-46A2-8387-4E989590A86D') does not exist.
The specified @job_name ('D6C2E45D-E677-4F2B-81AA-5103FB8E1B92') does not exist.
The specified @job_name ('7412F626-CAD9-48BE-8211-5145A3F51085') does not exist.
The specified @job_name ('17838236-691B-49D7-AD7C-553B1886AB58') does not exist.
The specified @job_name ('5445E14F-A22C-4014-9EB8-55C8BAF5A061') does not exist.
The specified @job_name ('C914C932-C350-404D-9CF4-575D108DDA82') does not exist.
The specified @job_name ('CB87B0AD-069A-4F07-BB62-580FBEF5C31B') does not exist.
The specified @job_name ('BC838396-DFE1-4BC5-8D24-58B194A7214E') does not exist.
The specified @job_name ('D58C71E8-A821-4A73-A0A7-5F5080BC6730') does not exist.
The specified @job_name ('49F42A35-15DA-4C9E-A95B-66F4040E139F') does not exist.
The specified @job_name ('F4F9400D-1212-4DD6-AAFF-671192BF2B25') does not exist.
The specified @job_name ('F0EFEFAA-F2D5-494E-B97E-6D075AC17F2F') does not exist.
The specified @job_name ('0721E6DF-0209-4874-B473-70E5026E8FF2') does not exist.
The specified @job_name ('B2AECE06-0F8F-4C5D-A04E-8148D8F6C255') does not exist.
The specified @job_name ('A9813C14-FB76-4461-80B9-8350CBE9E5BB') does not exist.
The specified @job_name ('71ABB496-3F2E-4D8D-8551-8650DBC45721') does not exist.
The specified @job_name ('EF1AAD40-47DA-41A2-A9F6-87A6AE140BB3') does not exist.
The specified @job_name ('B887666E-E580-427C-ADBA-8B605561E8E9') does not exist.
The specified @job_name ('A19772C9-CA88-455C-9CA7-8E11F960BB84') does not exist.
The specified @job_name ('CAFFEA4E-AE64-4B5F-9129-913272C5251D') does not exist.
The specified @job_name ('826AF562-C9D2-461B-AEEB-91B64FF3003A') does not exist.
The specified @job_name ('09458F97-C2ED-46B5-BB8E-91C4C54C22B4') does not exist.
The specified @job_name ('021AA26B-62EA-4C38-8ACF-975CE6B33FAD') does not exist.
The specified @job_name ('33EA5BB5-35A7-442F-8635-9FE560EDABBE') does not exist.
The specified @job_name ('E7405185-56A5-4C46-87AB-A1FA9FA4271B') does not exist.
The specified @job_name ('CEDDD21A-2E75-4BA6-BA99-A4E5B79073BC') does not exist.
The specified @job_name ('8A6E115B-616F-46D6-9A94-A7C22C94D11C') does not exist.
The specified @job_name ('30A0182B-0A70-4D33-A62F-AB277ABC4D63') does not exist.
The specified @job_name ('5B252CA0-FCFF-49FA-8B40-AD6667B345A1') does not exist.
The specified @job_name ('D0007E85-046E-4264-933A-AF662B8FECF7') does not exist.
The specified @job_name ('D1835177-4454-44C0-8134-B080AFD99B52') does not exist.
The specified @job_name ('B02F7A14-A658-420D-A2B0-B18577080FDD') does not exist.
The specified @job_name ('7CD641D9-C2C3-4907-88F9-BAED4FA93AAF') does not exist.
The specified @job_name ('23241CD1-4317-42EA-887E-C3F7441645D7') does not exist.
The specified @job_name ('9AB583BC-94AA-49BB-B4E4-CACE094A2764') does not exist.
The specified @job_name ('31EAC604-0DF5-4A9C-B510-CD6BEF72B608') does not exist.
The specified @job_name ('8412C87D-CC61-4FA0-9804-CFC8528DB66E') does not exist.
The specified @job_name ('314FBBDC-013B-4742-B65B-D122968AF014') does not exist.
The specified @job_name ('002B780F-351F-4345-9D97-D3DD370E2317') does not exist.
The specified @job_name ('F21C6C3D-5219-4917-BF29-D5AA1B315565') does not exist.
The specified @job_name ('34FCE497-498B-47EE-9A8B-D8EC2CFEC3AA') does not exist.
The specified @job_name ('1B356BC7-8300-4A6A-8E66-E036C1053C47') does not exist.
The specified @job_name ('6C94A462-3025-46AC-BD67-E7575ABBA4D9') does not exist.
The specified @job_name ('A79F3134-A3BC-470F-8D6C-F457C6114EBA') does not exist.

SCOM 2012 Powershell command to remove agent

Hello,
Has anyone had any luck removing agents via Powershell to mimic the delete agent from the console?
Blogs don't turn up anything useful for this task.
The 2012 Powershell covers how to approve agents, add proxy flag, and uninstall agent, but nothing to remove. Used the SQL stored procedure previously in 2007R2 (and same procedure exists in 2012 SP1.
Anyone aware of Powershell automate agent removal?
Thanks!
SCOM Power Shell to add SCOM 2012 agent
Get-SCOMPendingManagement | where {$_.AgentName -eq "ServernameFQDN"} | Approve-SCOMPendingManagement
Enable Proxy on newly added agent
Get-ScomAgent | where-object {$_.DisplayName -like "okcnmo*"} | where-object {$_.ProxyingEnabled.Value -eq $False} | Enable-SCOMAgentProxy
SQL Query to remove
http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/e413c030-509b-45e4-bcd4-b4ae1a649c73
Uninstall Agent
http://technet.microsoft.com/library/hh545186.aspx
Remove Unix agents
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerunixandlinux/thread/081f2801-7dfa-4db9-8c78-6adbc487a031/

We actually have used the stored procedure for 2007 and 2012
OperationsManager.dbo.p_TypedManagedEntityDelete
If you want to use Invoke-Sqlcmd to run the query.
Another way from SQL which can be put in PowerShell
--Grab GUID for that health service
select * from BaseManagedEntity
where FullName like '%<servername>%'
and IsDeleted = 1
Look for FullName with Microsoft.SystemCenter.HealthService:servername
-- Use this to test the entity delete for the healthservice GUID
DECLARE @EntityId uniqueidentifier;
DECLARE @TimeGenerated datetime;
-- change "GUID" to the ID of the invalid entity
SET @EntityId = '<GUID here>';
SET @TimeGenerated = getutcdate();
BEGIN TRANSACTION
EXEC dbo.p_TypedManagedEntityDelete @EntityId, @TimeGenerated;
COMMIT TRANSACTION
--Check what is in deleted
select * from BaseManagedEntity
where IsDeleted = 1

Scom 2012 r2 command line install

I want to pass the username and password as variable in the below command for datareader and datawriter accounts . The installation stops as its not able to validate the creds. Can some please help me correcting the script . If I hardcode the username and
password in the below script it works
$user = 'dpmain\me
$pass = 'passw'
Start-Process -FilePath C:\SCOM2012R2\setup.exe -ArgumentList '/install /InstallPath:"C:\Program Files\Microsoft System Center 2012 R2\Operations Manager" /components:OMServer,OMConsole /ManagementGroupName:OM2012SandBox /SqlServerInstance:. /DatabaseName:OperationsManager
/DWSqlServerInstance:. /DWDatabaseName:OperationsManagerDW /UseLocalSystemActionAccount /UseLocalSystemDASAccount /DatareaderUser: '$user' /DatareaderPasswod:'$pass' /DataWriterUser:'$user' /DatareadePassword:'$pass' /EnableErrorReporting:Never /SendCEIPReports:0
/UseMicrosoftUpdate:0 /AcceptEndUserLicenseAgreement:1 /silent'

The line below is taking care of the installation of you first management server. Change the parameters to first to your needs.
Start-Process-FilePathE:\setup.exe
-ArgumentList'/install /InstallPath:"C:\Program Files\Microsoft System Center 2012 R2\Operations Manager" /components:OMServer,OMConsole /ManagementGroupName:SCOMMgmt /SqlServerInstance:SQLSERVER\Instance /DatabaseName:OperationsManager
/DWSqlServerInstance:SQLSERVER\Instance /DWDatabaseName:OperationsManagerDW /ActionAccountUser:Contoso\Administrator /ActionAccountPassword:'XXXX' /DASAccountUser:contoso\Administrator /DASAccountPassword:'XXXX'
/DatareaderUser:domhome\Administrator /DatareaderPassword:'XXXX' /DataWriterUser:domhome\Administrator /DataWriterPassword:'XXXX' /EnableErrorReporting:Never /SendCEIPReports:0 /UseMicrosoftUpdate:0 /AcceptEndUserLicenseAgreement:1
/silent'
Also check below links
http://scug.be/christopher/2014/03/10/scom-2012-r2-unattended-installation-command-line/
http://technet.microsoft.com/en-us/library/hh416216.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 SP1- Getting Event ID 20070 on some agents and Event ID 200000 on management servers

On a significant number of my 2012 SP1 Agents, I am getting the following Event IDs in my OperationsManager event log:
20070
The OpsMgr Connector connected to XXXXXX.domain.net, but the connection was closed immediately after authentication occurred. The most likely
cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.
21006
The OpsMgr Connector could not connect to XXXXXX.domain.net:5723. The error code is 10060L(A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).
21015
OpsMgr was unable to set up a communications channel to XXXXXX.domain.net. Communication will resume when XXXXXX.domain.net is available and
communication from this computer is allowed.
On my various 2012 SP1 Management Servers, I am getting the following Event IDs in my OperationsManager event logs:
20000
A device which is not part of this management group has attempted to access this Health Service.
Requesting Device Name: servername.domain.com
Here are my settings and what I have tried:
We have agents assigned by AD-integration, and they are receiving their proper assignment
Agents are manually installed with SCCM 2012
“Automatically approve new manually installed agents” is selected
I have rebuilt the Health Service State folder and rebooted the service on the agent server
I have rebuilt the Health Service State folder on my management server and rebooted it to reset all services
On several agent servers that I am experiencing this issue, they are on the same network as their assigned management server, so there is no firewall issue.

Hi,
Here is a KB for your reference.
Troubleshooting gray agent states in System Center Operations Manager
http://support.microsoft.com/kb/2288515
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.

SCOM 2012 R2 installtion wizard not able to contact SQL server cluster

Hi,
This is about the error faced while installing SCOM 2012 R2.
My customer has SQL 2012 SP1 cluster installed. I am trying to install the SCOM 2012 R2 with this installed SQL cluster. The SQL cluster is installed with default instance and with AAG (Always on Availability Group).
The edition of SQL server is, SQL Server Enterprise edition with SP1
After check services on both the SQL nodes found that SQL Full text is not installed (as the related SQL Full text service not present in the services.msc) on any of the SQL cluster node & SQL Browser service is not running.
The running services for SQL are, SQL Server (MSSQLSERVER) & SQL Server Agent (MSSQLSERVER).
When I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, This SQL Server could not be found.
After installed SQL full text, the service is showing in services.msc as "SQL Full-text Filter Daemon Launcher (MSSQLSERVER)".
Now when I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, The installed version of SQL Server could not be verified or is not supported.
Followings test carried out for the connectivity between SCOM 2012 MS &SQL Cluster
Ping SQL Cluster successfully
Telnet SQL Cluster for port 1433 successfully
Tracert SQL Cluster – completed successfully with single hops.
The windows firewall is off on both sides
The SQL services running on the Active node 1 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Running & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL services running on the Passive node 2 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Stopped & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL Server Agent (MSSQLSERVER) service is not running on the second node. It is running only on first node which is active.
The account used to install SCOM has the local admin privilege on the SQL server
To ping the cluster use the cluster name & it solved the whole FQDN of cluster in ping result. When ping with IP address with -a it not resolve to name.
Is any one can provide their valuable inputs.
Regards,
SandeepK

Hi SandeepK,
Before Installing Operations Manager on an availability group, please
1. Make sure to use the Group listener Name and port when installing Operations Manager for the databases that are going to be added to the availability databases.
2. The first management server will use the Group listener to get the primary SQL instance, and will install the databases on that instance.
System Requirements: System Center 2012 R2 Operations Manager
http://technet.microsoft.com/en-us/library/dn249696.aspx#BKMK_ClusterConfig
Niki Han
TechNet Community Support

Recommendations for SCOM 2012 -- 2012 R2 migration

Hello to all. I have a customer that has SCOM 2012 in its IT environment but uses it barely and does not have any documentation. I proposed to install a new Manament Group (MG) and "reboot" to a paralell SCOM 2012 R2 considering the
use of new features present on 2012 R2.
Questions:
1- Does SCOM support a side by side migration strategy , like SCCM 2007 R2 --> SCCM 2012 R2 that takes its main source objects and bring them to the new separated Management Group (the SCOM 2012 R2)?
2- Considering that all regular member servers are monitored by SCOM 2012 (all have agents installed), what is the recommended way to to install SCOM 2012 R2 agents on them (multi homed deploy, deploy a new agent and it will upgrade/remove the
already existing SCOM 2012, etc)?
3- Does SCOM allows a approach to install a SCOM 2012 R2 on already existing SCOM 2012 MG and "migrate" its objects to new server and after that decomission SCOM 2012 (the old version)?
Your inputs and references will be very welecomed.
Regards, EEOC.

1- Does SCOM support a side by side migration strategy , like SCCM 2007 R2 --> SCCM 2012 R2 that takes its main source objects and bring them to the new separated Management Group (the SCOM 2012 R2)?
2- Considering that all regular member servers are monitored by SCOM 2012 (all have agents installed), what is the recommended way to to install SCOM 2012 R2 agents on them (multi homed deploy, deploy a new agent and it will upgrade/remove the
already existing SCOM 2012, etc)?
Yes. You can built SCOM 2012 R2 and do side-by-side migration.
High Level View of System Center 2012 R2 Operations Manager Upgrade Steps – Upgrading 2012 SP1 Agents to 2012 R2 and Running Two Environments:
1. Retain the original System Center 2012 Service Pack 1 (SP1), Operations Manager environment.
2. Set up an additional, new System Center 2012 R2 Operations Manager environment with management servers, gateway, Operations Manager Database, Operations Manager Data Warehouse, console, web console, and reporting server.
3. Upgrade the System Center 2012 Service Pack 1 (SP1), Operations Manager Agents to 2012 R2.
a. Push-Install option
b. Manual / Command Line option
3- Does SCOM allows a approach to install a SCOM 2012 R2 on already existing SCOM 2012 MG and "migrate" its objects to new server and after that decomission SCOM 2012 (the old version)?
The upgrade path is from SCOM 2012 --> SCOM 2012 SP1 --> SCOM 2012 R2
High Level View of System Center 2012 R2 Operations Manager Upgrade Steps – Upgrading a Distributed Management Group
1. Accomplish Pre-Upgrade Tasks
2. Upgrade the initial management server and then additional management servers (each management server must be upgraded)
3. Upgrade ACS (because the ACS server must be on same machine as a management server, we recommend you perform this step along with the upgrade of the management server on which ACS resides.)
4. Upgrade Gateway(s)
5. Upgrade Console
6. Push Install to Agent(s) / Upgrading Manually Installed Agents
7. Upgrade Web Console
8. Upgrade Reporting Server
9. Accomplish Post-Upgrade Tasks
For detail, pls. refer to
Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1
https://technet.microsoft.com/en-us/library/jj899854.aspx
Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
https://technet.microsoft.com/en-us/library/dn249707.aspx
Roger

How is called the Services "OpsMgr Health Service" in the SCOM 2012 and Client machine?

Hi,
Can anybody tell me how is called the Services of OpsMgr Health Service in the SCOM 2012?
I have installed the agent of scom2012 on my client computer. But I dont find any agent called "OpsMgr Health Service" on the Client machine?
Regards

Hi
If you look in the services.msc window then it is listed as the System Center Management Service. This is the display name.
The actual service name is HealthService
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
The Ayman answer is god, It is called "Microsoft Monitoring Agent"

SCOM 2007 R2 to SCOM 2012 SP1 upgrade issues.

We have SCOM 2007 R2 on one of our development Environment.
The plan was to upgrade to SCOM 2012 R2 so we installed the SCOM 2007 R2 CU5.
We are having issues to upgrade now from SCOM 2007 R2 CU5 to SCOM 2012 SP1.
While upgrading we received the below message:
Unable to Proceed
Setup is unable to proceed with installation for the following reason:
At least one of the following application is installed on the computer.Due to incompatibility with system center 2012 - operations manager,these applications must be uninstalled.
-System Center 2012 - operations manager beta
-system center operations manager 2007
-system center operations manager 2007 sp1
--system center operations manager 2007 r2
-system center service manager agent
--system center essentials agent

Hi,
You cannot upgrade from SCOM2007R2 to SCOM2012SP1, you must upgrade to SCOM2012 and the upgrade to SCOM2012SP1
Cameron Fuller has a blog:
http://blogs.catapultsystems.com/cfuller/archive/2013/02/11/can-you-upgrade-from-opsmgr-2007-r2-to-opsmgr-2012-sp1-scom-sysctr.aspx
Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1
http://technet.microsoft.com/en-us/library/jj899854.aspx
"The only supported upgrade path to System Center 2012 Service Pack 1 (SP1), Operations Manager is from System Center 2012 – Operations Manager. If you are upgrading from System Center Operations Manager 2007 R2, you must first upgrade to System Center 2012
– Operations Manager"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Is it possible to deploy 2 SCOM 2012 R2 reporting in a SQL server which already has SCOM reporting of a different management group but with 2 different reporting instance.

Hi Experts,
I have a typical situation in the LAB environment. Hope some one helps. I have Installed a SCOM 2012 R2 with SQL 2012 SP1 in a single server (Management group 1). I have installed another management group on another server using this SQL server for its database
so i have everything going fine.
The first management group has its reporting installed in the SQL server. For the second i created a new named instance for that. But i cannot run the SCOM setup in the SQL server (Also holding the Management group 1 MS) as 1 st reporting is already there.
When i run the setup it is asking me to repair it. I don't get the install option so i can install the reporting for management group 2 in the named instance.
Default instance is being used by the 1st management group.
Can any one figure a possibility for installing 2 SCOM reporting services for different management groups in a same SQL 2012 server please.
Gautam.75801

Hi Yan Li,
Thank you for the reply. So as you are aware If i need to instal reporting, i need to run the SCOM 2012 R2 setup in the SQL server and select reporting and select the
instance and then mention the management server there right. I am not getting that option there it is asking me to remove or repair the existing installation as there is already a SCOM entire setup including reporting there. As it is a lab there is no problem
in testing. I have 2 reporting instances. Any suggestions for me on how to overcome this issue and deploy the second reporting in the new named instance ?
Below is the screenshot of the error what i am talking about when i run SCOM 2012 R2 setup to install reporting in the SQL server
When i click on add feature reporting is greyed out (As already 1st management groups reporting is installed)
When i click on remove or repair it
uninstalls the existing one. But i want both SCOM 2012 r2 reporting to be there(For both Management group). Is it possible ? If yes What is the trick to run the setup ?
Gautam.75801

Update rollup 2 for SCOM 2012 R2 broke sharepoint and visio 2010 SCOM integration

I just applied UR2 to my test environment and I find that it has broken my SharePoint webpart, webconsole, and visio integration? What's the fix? I receive "Secure Store Service did not performed the operation."
from the dashboard web part, and "The server failed to process the request" from the VSW.
B. Wright

Hi,
Did you follow the article http://support.microsoft.com/kb/2929891 to install the UR2?
In the article:
We recommend that you install this update rollup package by following these steps in the given order:
Install the update rollup package on the following server infrastructure:
Management server or servers
Gateway servers
Web console server role computers
Operations console role computers
Apply SQL scripts (see installation information).
Manually import the management packs.
Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.
Please check whether your operation manager server works well. Please check the event logs for more related information to help to troubleshoot this issue.
Regards,
Yan Li
Regards, Yan Li

Upgrade Paths for SCOM 2012 R2

I looked through many forums and MS sites but can't find if it's possible to upgrade SCOM 2007R2 to SCOM 2012R2 directly. Or do you have to upgrade to the integrated SCOM 2012SP1 package first? or is even that supported? I'm trying to
upgrade to 2012R2 from 2007R2 and everything is on the same server.

Agree
The correct upgrade path is
SCOM 2007 R2 CU4 --> SCOM 2012
SCOM 2012 --> SCOM 2012 SP1
SCOM 2012 SP1 --> SCOM 2012 R2
1) blog for upgrade SCOM 2007 R2 to SCOM 2012
http://jeroennotebaertsblog.blogspot.hk/2012/01/upgrading-scom-2007-r2-to-scom-2012.html
http://www.vnext.be/2012/10/23/upgrade-guide-from-scom-2007-to-scom-2012/
2) blog for upgrade SCOM 2012 to SCOM 2012 SP1
http://kevingreeneitblog.blogspot.dk/2012/12/scom-2012-installing-service-pack-1-rtm.html
3) blog for upgrade SCOM 2012 SP1 to SCOM 2012 R2
http://www.systemcentercentral.com/upgrading-operations-manager-from-2012-sp1-to-2012-r2-step-by-step-upgrading-to-2012-r2-series/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28System+Center+Central+Rollup%29
Roger

SPN Registration clarification (in SCOM 2012 SP1 UR2)

Hi,
was looking some clarification of manual registration of SPN's - as is the requirement in my case were I am using a domain account for SDK and data access service.
I have read the Service Principle Names section of this Library document
http://technet.microsoft.com/library/hh487288.aspx and have also referenced Kevins post here
http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx and also reviewed the product knowledge from the scom rule that checks Data Access Service SPN registration. However I'm still a bit confused!!
I had the issue in my Preprod deployment which I resolved by manual registration which I completed as per following the product knowledge in the alert ie following this advice and syntax:
If the SPNs are not correctly registered, register them manually by running the following commands, using an account with domain administrator rights:
Setspn.exe -A MSOMSdkSvc/<MS NetBIOS Name> <MS NetBIOS Name>
Setspn.exe -A MSOMSdkSvc/<MS FQDN> <MS NetBIOS Name>
This I assume this is registering the SDK service for the computer account (where MS NetBIOS Name is mgmt Server netbios and MS FQDN is Mgmt Server FQDN).
However if I run Kevin's check,
C:\>setspn –L DOMAIN\sdkdomainuseraccount
I dont get any SDK SPN's for my account, the output is empty!
Can anyone advise if there should definately be output in the above command as per Kevins blog, or is the registration of machine account SPN's sufficient? Adding to the confusion is on other references to SPN's, they state NOT to use the -A switch
and instead use -S as that checks for duplicates (but the -A doesnt) - would be nice if the product knowledge could be updated to reflect the latest guidance!
Any advice much appreciated...

Alexis/Stefan - thanks both for the replies, that has clarified my confusion! Looks like I was incorrectly manually registering a machine account SPN, wereas I'm using a domain account and should be using the format below as per your replies:
Setspn.exe -S MSOMSdkSvc/<MS NetBIOS Name> <Domain\SDKAccount>
Setspn.exe -S MSOMSdkSvc/<MS FQDN> <Domain\SDKAccount>
I am now getting the output from setspn -L DOMAIN\sdkdomainuseraccount as expected from Kevins post - so all looks OK.
I notice I STILL get the alert for Data Access Service SPN registration in console after a server reboot - but I see the note in Kevins post that I can ignore it as below:
*Note – In SCOM 2012 – you might notice that every time your management server service is restarted, or rebooted, that we log an event (and create an alert) that the SPN’s are incorrect. This event/alert is in error, it is complaining the the SDK
SPN is missing from the management server COMPTUER account, which should ONLY be the case if you were using local system for the SDK service. Ignore this event and alert.
Is that the case - just the post I think was written for SCOM 2012, wereas I'm using 2012 SP1 UR2 - so wondered if this guidance for ignoring the alert is still valid incase the issue for this bogus alert had been resolved by SP1/UR2?

Scom 2012 R2 Convert Manually installed Agents to Remotely managed

Similar Messages

Maybe you are looking for