Deployment SCOM

Finally i decides to send the problem, after having hard time 1 week, sure that you can help me now i tried my best coming through all the prerequisites on both the servers SQL server and SCOM server: save my days plz
thank u
Alex
[15:49:46]: Always:
[15:49:46]: Always:
Application Started
[15:49:46]: Always:
:Machine on which Operations Manager is being installed: ASP186-OPSMGR
[15:49:46]: Always:
:Current setup user: SATURN\administrator
[15:49:46]: Always:
:Current setup version: 7.1.10226.0
[15:49:46]: Always:
:Begin: Parse command line.
[15:49:46]: Debug:
:Collected a path value of: E:\Setup\AMD64\
[15:49:46]: Always:
:Begin: Parse command line.
[15:49:46]: Always:
:End: Parse reporting command line switches.
[15:49:46]: Always:
:End: Parse data reader account command line switches.
[15:49:46]: Always:
:End: Parse command line.
[15:49:46]: Always:
:Begin: System State detection.
[15:49:46]: Info:
:Info:CheckIfOpsMgrComponentsInstalled: component - OMCONSOLE
[15:49:46]: Info:
:Info:Component OMCONSOLE is not installed
[15:49:46]: Info:
:Info:CheckIfOpsMgrComponentsInstalled: component - OMSERVER
[15:49:46]: Info:
:Info:Component OMSERVER is not installed
[15:49:46]: Info:
:Info:CheckIfOpsMgrComponentsInstalled: component - OMWEBCONSOLE
[15:49:46]: Info:
:Info:Component OMWEBCONSOLE is not installed
[15:49:46]: Info:
:Info:CheckIfOpsMgrComponentsInstalled: component - OMREPORTING
[15:49:46]: Info:
:Info:Component OMREPORTING is not installed
[15:49:46]: Always:
:End: System State detection.
[15:49:46]: Info:
:Beginning evaluation of rule 'Upgrade rules for SCOM setup.'
[15:49:46]: Debug:
:Condition wasnt defined for rule 'Upgrade rules for SCOM setup.'.
[15:49:46]: Info:
:Beginning evaluation of rule 'UpgradeRulesForAllSKUs'
[15:49:46]: Debug:
:Condition wasnt defined for rule 'UpgradeRulesForAllSKUs'.
[15:49:46]: Info:
:Beginning evaluation of rule 'BlueUpgradeRules'
[15:49:46]: Debug:
:Condition wasnt defined for rule 'BlueUpgradeRules'.
[15:49:46]: Info:
:Info:OM12RTMServer is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMServer failed.
[15:49:46]: Info:
:Info:OM12RTMConsole is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMConsole failed.
[15:49:46]: Info:
:Info:OM12RTMWebConsole is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMWebConsole failed.
[15:49:46]: Info:
:Info:OM12RTMReporting is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMReporting failed.
[15:49:46]: Info:
:Info:OM12RTMServer is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMServer failed.
[15:49:46]: Info:
:Info:OM12RTMConsole is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMConsole failed.
[15:49:46]: Info:
:Info:OM12RTMWebConsole is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMWebConsole failed.
[15:49:46]: Info:
:Info:OM12RTMReporting is installed: False
[15:49:46]: Info:
:Info:Product check for OM12RTMReporting failed.
[15:49:46]: Info:
:Finished evaluation of rule 'BlueUpgradeRules'
[15:49:46]: Info:
:Finished evaluation of rule 'UpgradeRulesForAllSKUs'
[15:49:46]: Info:
:Finished evaluation of rule 'Upgrade rules for SCOM setup.'
[15:49:46]: Always:
:This is not an upgrade
[15:49:46]: Always:
:No OM component is installed on this machine and it's interactive run.
[15:49:46]: Error:
:Error:User did not accept EULA.
[15:49:47]: Always:
:We don't have a path entry in the registry or from command line so using default install path as C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[15:49:47]: Info:
:SetInstallPath: installpath has a value of C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[15:49:47]: Info:
:Info:SetComponentSwitches: component list not specified
[15:49:47]: Always:
:Begin: Rationalize components.
[15:49:47]: Always:
:Begin: Rationalize command line arguments (first run).
[15:49:47]: Always:
:RationalizeCommandLineArguments succeeded.
[15:49:47]: Always:
:End: Rationalize command line arguments (first run).
[15:49:47]: Always:
:Begin: Rationalize final steps.
[15:49:47]: Info:
:Beginning evaluation of rule 'Block Unsupported MOM versions.'
[15:49:47]: Debug:
:Condition wasnt defined for rule 'Block Unsupported MOM versions.'.
[15:49:47]: Info:
:Beginning evaluation of rule 'PreOM12RTMRulesGroup'
[15:49:47]: Debug:
:Condition wasnt defined for rule 'PreOM12RTMRulesGroup'.
[15:49:47]: Info:
:Info:MOMSelect is installed: False
[15:49:47]: Info:
:Info:MOMAEM is installed: False
[15:49:47]: Info:
:Info:MOMEval is installed: False
[15:49:47]: Info:
:Info:MOMOEM is installed: False
[15:49:47]: Info:
:Info:MOMAgent is installed: False
[15:49:47]: Info:
:Info:MOMGW is installed: False
[15:49:47]: Info:
:Info:MOMReporting is installed: False
[15:49:47]: Info:
:Finished evaluation of rule 'PreOM12RTMRulesGroup'
[15:49:47]: Info:
:Beginning evaluation of rule 'BlockPre2012SP1'
[15:49:47]: Debug:
:Condition wasnt defined for rule 'BlockPre2012SP1'.
[15:49:47]: Info:
:Info:OMServer is installed: False
[15:49:47]: Info:
:Info:OMConsole is installed: False
[15:49:47]: Info:
:Info:OMReporting is installed: False
[15:49:47]: Info:
:Info:OMWebConsole is installed: False
[15:49:47]: Info:
:Finished evaluation of rule 'BlockPre2012SP1'
[15:49:47]: Info:
:Finished evaluation of rule 'Block Unsupported MOM versions.'
[15:49:47]: Info:
:Beginning evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[15:49:47]: Debug:
:Condition wasnt defined for rule 'Check that Unsupported SKU does not exist for SCOM setup.'.
[15:49:47]: Info:
:Info:MOMAEM is installed: False
[15:49:47]: Info:
:Info:MOMEval is installed: False
[15:49:47]: Info:
:Finished evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[15:49:47]: Always:
:End: Rationalize final steps.
[15:49:47]: Always:
:End: Rationalize components.
[15:49:47]: Error:
:Error:IsReportingValidToInstall failed SRS instance not provided
[15:49:47]: Info:
:Start adding DataItems
[15:49:47]: Info:
:Initial Configuration
[15:49:47]: Info:
:Database Configuration
[15:49:47]: Info:
:Data Warehouse Configuration
[15:49:47]: Info:
:Management Server
[15:49:47]: Info:
:Operations console
[15:49:47]: Info:
:Web Console Server
[15:49:47]: Info:
:Reporting Server
[15:49:47]: Info:
:Final Configuration
[15:49:47]: Info:
:Done adding DataItems
[15:49:47]: Info:
:Adding Page StartPageTrack
[15:49:47]: Info:
:Adding Page UpgradeInvalidStartPage
[15:49:47]: Info:
:Adding Page UpgradeInvalidRootPage
[15:49:47]: Info:
:Adding Page ARPStartPageSwitch
[15:49:47]: Info:
:Adding Page ARPAddRemovePage
[15:49:47]: Info:
:Adding Page UpgradePageSwitch
[15:49:47]: Info:
:Adding Page UpgradePage
[15:49:47]: Info:
:Adding Page UpgradeManagementGroupPageSwitch
[15:49:47]: Info:
:Adding Page UpgradeManagementGroupPage
[15:49:47]: Info:
:Adding Page UpgradeEulaPage
[15:49:47]: Info:
:Adding Page RegularStartPageSwitch
[15:49:47]: Info:
:Adding Page ComponentsPageCleanInstall
[15:49:47]: Info:
:Adding Page ComponentsPage
[15:49:47]: Info:
:Adding Page InstallationLocationPage
[15:49:47]: Info:
:Adding Page PrerequisitesProgressPage
[15:49:47]: Info:
:Adding Page AdditionalPrerequisitesPage
[15:49:47]: Info:
:Adding Page InstallScenario
[15:49:47]: Info:
:Adding Page ShortEulaPage
[15:49:47]: Info:
:Adding Page SecondServerOperationalDb
[15:49:47]: Info:
:Adding Page EulaPageCleanInstall
[15:49:47]: Info:
:Adding Page FirstServerOperationalDb
[15:49:47]: Info:
:Adding Page DbPageDataWarehouse
[15:49:47]: Info:
:Adding Page SelectManagementServerForReporting
[15:49:47]: Info:
:Adding Page SelectReportingInstance
[15:49:47]: Info:
:Adding Page SelectManagementServerForWebConsole
[15:49:47]: Info:
:Adding Page WebConsoleSitePage
[15:49:47]: Info:
:Adding Page WebConsoleAuthorizationMode
[15:49:47]: Info:
:Adding Page AccountsInformationPage
[15:49:47]: Info:
:Adding Page ImproveUserExperiencePage
[15:49:47]: Info:
:Adding Page MSFTUpdatePage
[15:49:47]: Info:
:Adding Page ConfigurationSummaryPage
[15:49:47]: Info:
:Adding Page ProgressPage
[15:49:47]: Info:
:Adding Page BlockPage
[15:49:47]: Info:
:Adding Page FinishPage
[15:49:48]: Info:
:Beginning evaluation of rule 'Block Unsupported MOM versions.'
[15:49:48]: Debug:
:Condition wasnt defined for rule 'Block Unsupported MOM versions.'.
[15:49:48]: Info:
:Beginning evaluation of rule 'PreOM12RTMRulesGroup'
[15:49:48]: Debug:
:Condition wasnt defined for rule 'PreOM12RTMRulesGroup'.
[15:49:48]: Info:
:Info:MOMSelect is installed: False
[15:49:48]: Info:
:Info:MOMAEM is installed: False
[15:49:48]: Info:
:Info:MOMEval is installed: False
[15:49:48]: Info:
:Info:MOMOEM is installed: False
[15:49:48]: Info:
:Info:MOMAgent is installed: False
[15:49:48]: Info:
:Info:MOMGW is installed: False
[15:49:48]: Info:
:Info:MOMReporting is installed: False
[15:49:48]: Info:
:Finished evaluation of rule 'PreOM12RTMRulesGroup'
[15:49:48]: Info:
:Beginning evaluation of rule 'BlockPre2012SP1'
[15:49:48]: Debug:
:Condition wasnt defined for rule 'BlockPre2012SP1'.
[15:49:48]: Info:
:Info:OMServer is installed: False
[15:49:48]: Info:
:Info:OMConsole is installed: False
[15:49:48]: Info:
:Info:OMReporting is installed: False
[15:49:48]: Info:
:Info:OMWebConsole is installed: False
[15:49:48]: Info:
:Finished evaluation of rule 'BlockPre2012SP1'
[15:49:48]: Info:
:Finished evaluation of rule 'Block Unsupported MOM versions.'
[15:49:48]: Info:
:Beginning evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[15:49:48]: Debug:
:Condition wasnt defined for rule 'Check that Unsupported SKU does not exist for SCOM setup.'.
[15:49:48]: Info:
:Info:MOMAEM is installed: False
[15:49:48]: Info:
:Info:MOMEval is installed: False
[15:49:48]: Info:
:Finished evaluation of rule 'Check that Unsupported SKU does not exist for SCOM setup.'
[15:49:48]: Debug:
:OMForwardToStartPageTrackPageHandler: Moving to page RegularStartPageSwitch
[15:49:48]: Always:
:Entering Page: ComponentsPageCleanInstall
[15:49:48]: Info:
:Server Installed:False InstallingNow:False
[15:49:48]: Error:
:No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[15:49:48]: Error:
:The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
[15:49:48]: Info:
:Server Installed:False InstallingNow:False
[15:49:48]: Error:
:No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[15:52:26]: Info:
:The user canceled setup
[15:52:26]: Always:
:Begin: Property bag dump.
[15:52:26]: Always:
:SetupStartTime = 21.01.2014 15:49:46
[15:52:26]: Always:
:Collection ProtectedProperties (System.Collections.ArrayList):
[15:52:26]: Always:
: [0] = ActionAccountPassword
[15:52:26]: Always:
: [1] = DASAccountPassword
[15:52:26]: Always:
:DefaultLogName = C:\Users\administrator.SATURN\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[15:52:26]: Always:
:DefaultLogPath = C:\Users\administrator.SATURN\AppData\Local\SCOM\Logs
[15:52:26]: Always:
:path = E:\Setup\AMD64\
[15:52:26]: Always:
:setupexepath = C:\Users\administrator.SATURN\AppData\Local\SCOM\Setup
[15:52:26]: Always:
:ArchitectureIs64Check = True
[15:52:26]: Always:
:Collection ListOfSupportedComponents (System.Collections.ArrayList):
[15:52:26]: Always:
: [0] = OMCONSOLE
[15:52:26]: Always:
: [1] = OMSERVER
[15:52:26]: Always:
: [2] = OMWEBCONSOLE
[15:52:26]: Always:
: [3] = OMREPORTING
[15:52:26]: Always:
:install = 1
[15:52:26]: Always:
:installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[15:52:26]: Always:
:EulaFilesPath = C:\Users\administrator.SATURN\AppData\Local\SCOM\Setup
[15:52:26]: Always:
:HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[15:52:26]: Always:
:hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[15:52:26]: Always:
:ScreensLoaded = 1
[15:52:26]: Always:
:UserCanceledInstall = 1
[15:52:26]: Always:
:InstallSuccess = 1
[15:52:26]: Always:
:End: Property bag dump.
[15:52:26]: Debug:
:CEIP disabled. CEIP data will NOT be sent.
[15:52:26]: Always:
:Application Ended: Successful

Hi
Could you please give some more details? It seems the error is somewhere here.
[15:49:48]: Error:
:No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
[15:49:48]: Error:
:The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.
[15:49:48]: Info:
:Server Installed:False InstallingNow:False
[15:49:48]: Error:
:No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.
What exactly are you trying to do?
Cheers,
Stefan
Blog: http://blog.scomfaq.ch

Similar Messages

How to deploy SCOM Dashboard solution to sharepoint online

i have come through many articles saying how to deploy scom dashboard solution to sharepoint server,
but how do i deploy SCOM WSP solution to sharepoint online office 365.
i need to show my SCOM dashboards on sharepoint online.
Can anyone help me in doing this?
Thanks & Regards, Suresh Gaddam

Yes i did the same thing but when i hit activate it threw some error saying you cannot deploy farm solution to sharepoint
This solution
contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'c125f6b7-8c1e-40ae-86e2-bd2d5e568ca2' failed validation, file manifest.xml, line 14, character 4: The element 'Solution' in namespace
'http://schemas.microsoft.com/sharepoint/' has invalid child element 'RootFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'ActivationDependencies, FeatureManifests' in namespace 'http://schemas.microsoft.com/sharepoint/'.
TECHNICAL
DETAILS
Thanks & Regards, Suresh Gaddam

Deploy scom 2012 r2 on server 2012 r2

Going to deploy scom 2012 r2 on server 2012 r2 with sql 2012 sp1. a few questions before starting:
1. roles placement: server1 - management server, operation console;
                             server2: database server, reporting server;
                             Not sure where to place web console - server1 or server2?
2. what are the least privileges to have for the installation account - domain user with local administrators?
    should the servers' system account need to be member of local administrators?
3. what about other SCOM specific accounts? what least privileges they need?
Thanks in advance.

1. You can place it on the 1st server. do note however the downside doing all in one box SCOM components.
2. It would be best to use a domain user account with local admin rights on the box
3. Its all in the SCOM deployment docs..
You might want to check this link
http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.aspx (same as
Blake Mengotto)
Hope this helps.
Thanks,

Deploying SCOM 2012 Agents to untrusted Forests/Domain

Can we deploy SCOM 2012 agents to untrusted forest/domain? I don't want to use SCCM 2012 for installing agents via package deployment. Pls suggest.
Regards,
Ravi

Yes, You can deploy SCOM Agent to untrusted domain manually and using Certificate.
For deployment scom Agent, you can refer below links
http://www.toolzz.com/?p=279
http://jimmoldenhauer.blogspot.com/2012/11/scom-2012-deploying-agents-to-untrusted.html
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

Deploying SCOM 2012 R2 on a high availability

I I am deploying scom 2012 r2 in high availabilty my question is that i need a witness resource disk or file share witness disk for the sql 2012 high availabilty or not and also share the steps of making the scom 2012 r2 high availability through
screen shots.with sql server 2012 high availability

Looks like you asked this twice?
I replied on the later thread:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/3b69afd0-db93-436e-84a7-caee7b79a5a6/deploying-scom-2012-r2-on-a-high-availability?forum=operationsmanagerdeployment
John Joyner MVP-SC-CDM

Deploy SCOM 2012 R2 Agents to Domain Servers on Perimeter Network using SCOM Gateway on different Domain

Hi, I have a bit odd situation on a SCOM 2012R2 deployment.
I have a MS on the internal network, and a Gateway Server on the perimeter network. Each server is connected to different Active Directory Forests and there are no trust relationships between them. I configured the communication between the two using certificates.
I have already connected some servers through the Gateway using certificates because there are on Workgroups, they are already approved on the MS and reporting their status.
However, I have some servers that are member servers of the internal AD domain but are located on the perimeter network.
So I've tried to configure one of them for testing to connect to the Gateway Server using a certificate using manual agent installation. Initially it didn't report on the SCOM, but then I ran the get-scompendingmanagement and saw that it showed there,
so I ended up approving the agent using Powershell and then it was reported on the Console as "Not Monitored"
First the agent was running as local system and then tried using a local admin account on the server, neither options have worked.
I get the following errors:
The OpsMgr Connector connected to scomgateway.externaldomain.com, 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. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
OpsMgr was unable to set up a communications channel to scomgateway.externaldomain.com and there are no failover hosts. Communication will resume when scomgateway.externaldomain.com is available and communication from this computer is allowed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Is this configuration possible? Or do I need to open communication ports from the agents to the MS inside the corporate network and not use the Gateway?
Any ideas if someone else has done this are appreciated.
Thank you.
Regards.
Eduardo Rojas

I'm sorry, maybe I didn't explained myself correctly, I already have the gateway up and running with some Workgroup machines connected to it using certificates, so the Gateway is indeed working. These Workgroup machines are in fact reporting back to the
Management Server on the internal network through the Gateway.
My problem is with Domain Member machines that are on the perimeter network. This machines are joined to the Active Directory inside the corporate firewall, not the Active directory from the perimeter network (where the Gateway is joined). So my question
is, can I connect these machines through the Gateway (even if the Gateway is on a different domain) or do I need to open ports and connect them directly to the management server (which is on the same active directory domain)?
Let me know if I made myself clear.
Thank you.
Regards.
Eduardo Rojas

I get this error when i deploy SCOM 2012 in my Lab server

When i install SCOM 2012 i get this error "
The version of SQL Server on this computer is either not supported or could not be validated"
I tried performing as per this article but still i have the same issue.
Below is the screen shot of the error.
I also tried the steps in the below article. The command completes success fully but still i get the below error.
http://social.technet.microsoft.com/wiki/contents/articles/13954.opsmgr-2012-the-version-of-sql-server-on-this-computer-is-either-not-supported-or-could-not-be-validated.aspx
Can some one please help on this.

Hi,
look at this two blog:
http://www.scom2k7.com/fix-scom-2012-install-error-the-version-of-sql-server-on-this-computer-is-either-not-supported-or-could-not-be-validated-because-of-an-issue-connecting-to-the-wmi-provider/
http://kevingreeneitblog.blogspot.com/2013/06/scom-2012-sp1-install-error-with-sql.html
Regards.
Ivan

SCOM POC deployment

As a POC deployment of SCOM2012R2, I have just built up a management server and a gateway server. Now both MS and GW servers appear in the console as healthy. I haven't installed agent on any other systems, nor have management packs imported.
I am thinking the next step, should I discover and deploy scom agent to computers first or should I import basic management packs before deploying agents? Or the order does not matter.
Thanks in advance

For which is first deploy agent or import MP, It won't matter what's first. but most popular and usage Deploy Agent then Import Management Pack then configure Tuning, rules and security.
Also you can refer to below link
http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.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).

SCOM 2012 R2 deployment on Amazon Cloud VM

Hi,
I am planning to deploy SCOM 2012 R2 on VM hosted on Amazon Cloud, is this supported deployment??
Also is any impact after the MAC address of SCOM VM`s changed??
i have deploy all the System center 2012 R2 Components on Amazon Cloud only ..
Shailendra Dev

Hi,
Please refer to the link below:
Hardware Requirements for System Center 2012 R2
https://technet.microsoft.com/en-us/library/dn726764.aspx
These computers can be physical servers or virtual servers.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Is SCOM security compliant (ISO and HIPAA ) to deploy in health care environments

Hi All,
We have a requirement to deploy SCOM 2012 and a questioned arise.
is SCOM security compliant (ISO and HIPAA ) to deploy in health care environments.
I would appreciate if you can clarify me on this regards.
Thanks in advance.
Raj
raj

Hi Raj,
As we know, SCOM is used to monitor objects healthy based on monitors or rules created within management packs. After searching the internet, it seems like that few article take ISO and HIPAA together with SCOM.
What do you want to achieve with SCOM?
Regards,
Yan Li
Regards, Yan Li

SCOM agent install fails Error 80070035 - the network path was not found

I have deployed SCOM 2012 agents to most servers (2008, 2008 R2, 2012, 2012R2) in our estate but some either fail to install or are not monitored. I assume the two problems are related, but for now I am concentrating on the servers that fail completely.
Installation is from the Discovery Wizard and I have about 20 servers that fail of various server versions.
So looking at one specific server that is failing to install the agent - a 2008 standard service pack 2
The firewall in on and file and printer sharing is enabled for domain, remote administration is enabled for domain
I added a specific rule to allow TCP 5723 and 5724
DCOM is enabled
I can Ping the target server from the SCOM server by both name and FQDN - both return the same IP and our DNS server has only one entry for this server
I can browse to the admin share \\server\C$ from the SCOM Server, using the same account that I specify for the agent install that is a domain admin with rights on this server (and on the other servers the agent
did install to) and the server has plenty of disk space available
I am not sure what else to look at so would welcome any ideas
Thanks

Hi Petro,
I have a Agent installation failure cheat sheet, For your error 80070035 it is said to perform a manual installation.
So i would like to understand which version of SCOM is this ? 2007 R2 or 2012 or 2012 r2 ?
Also check if your agents have the WMI service started and enabled ?
Also if yours is a SCOM 2007 R2 do you have a RMS & MS in your management group ? If yes then Pushing the agent installation from MS may cause such issue. So would suggest you push the installation from RMS.
Also check if your Network connectivity meets the minimum requirement as recommended by SCOM. Below is applicable for Both SCOM 2007 R2 & SCOM 2012 & 2012 R2.
Component A
Component B
Minimum Requirement
Root management server or management server
Agent
64 Kbps
Root management server or management server
Agentless
1024 Kbps
Root management server or management server
Database
256 Kbps
Also check if you have any Anti virus / Firewall which is blocking the install / communication. If yes disabe or add the "Monitoringhost.exe to the safe list or what your feature is.
Check if you have another IP assigned to the NIC card and remove it tempraurly andchecl.
Also post the event logs of the Agents which are in not monitored state for analysis.
SCOM Agent installation failure error codes
Error
Error Code(s)
Remediation Steps
The MOM Server could not execute WMI Query "Select * from Win32_Environment where
NAME='PROCESSOR_ARCHITECTURE'" on computer server.domain.com
Operation: Agent Install
Install account: domain\account
Error Code: 80004005
Error Description: Unspecified error
80004005
1. Check the PATH environment variable. If the PATH statement is very long, due to lots of installed third party software - this can
fail. Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary.
2. The cause
could be corrupted Performance Counters on the target Agent.
To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command
prompt. Press ENTER after each command.
cd
\windows\system32
lodctr /R
Note /R is uppercase.
Windows Server 2003 rebuilds all the counters because it reads all the .ini files in the C:\Windows\inf\009 folder for the English operating system.
How to manually rebuild Performance Counter Library values
http://support.microsoft.com/kb/300956
3. Manual agent install.
The 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.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access
3. Inspect WMI health and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
The MOM Server failed to open service control manager on computer "servername.domain.com". Access is Denied
Operation: Agent Install
Install account: DomainName\User Account
Error Code: 80070005
Error Description: Access is denied.
80070005
80041002
1. Verify SCOM agent push account is in Local Administrators group on target computer.
2. On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin.
Disable McAfee antivirus during push
The MOM Server failed to open service control manager on computer "servername.domain.com".
Therefore, the MOM Server cannot complete configuration of agent on the computer.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
800706BA
1. Firewall blocking NetBIOS ports
2. DNS resolution issue. Make sure the agent can ping the MS by NetBIOS and FQDN. Make sure the MS can ping the agent by NetBIOS
and FQDN
3. Firewall blocking ICMP
4. RPC services stopped.
The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding
on this computer, please retry the Push Agent operation after some time.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 80072971
Error description: Unknown error 0x80072971
80072971
This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer:
%windir%\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2
When you install or remove a management agent, the Operations Manager 2007 management server copies temporary files to the remote computer. One
of these files is named LockFileTime.txt. This lock file is intended to prevent another management server from performing a management agent installation at the same time as the current installation. If the management agent installation is unsuccessful and
if the management server loses connectivity with the remote computer, the temporary files may not be removed. Therefore, the LockFileTime.txt may remain in the folder on the remote computer. When the management server next tries to perform an agent installation,
the management server detects the lock file. Therefore, the management agent installation is unsuccessful.
http://support.microsoft.com/kb/934760/en-us
The MOM Server detected that the following services on computer "(null);NetLogon" are not running. These services are required for push
agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Remote Computer Name: servername.domain.com Install account: DOMAIN\account
Error Code: C000296E
Error Description: Unknown error 0xC000296E
C000296E
1. Netlogon service is not running. It must be set to auto/started
The MOM Server detected that the following services on computer
"winmgmt;(null)" are not running
C000296E
1. WMI services not running or WMI corrupt
The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer "servername.domain.com". This service is
required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to "Manual" or "Automatic", or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: C0002976
Error Description: Unknown error 0xC0002976
C0002976
1. Windows Installer service is not running or set to disabled – set this to manual or auto and start it.
The Agent Management Operation Agent Install failed for remote computer servername.domain.com.
Install account: DOMAIN\account
Error Code: 80070643
Error Description: Fatal error during installation.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameAgentInstall.LOG
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameMOMAgentMgmt.log" on the Management Server.
80070643
1. Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired.
Call was canceled by the message filter
80010002
Install latest SP and retry. One server that failed did not have Service pack installed
The MOM Server could not find directory \\I.P.\C$\WINDOWS\. Agent will not be installed on computer "name". Please verify the required
share exists.
80070006
1. Manual agent install
Possible locking on registry?
http://www.sysadmintales.com/category/operations-manager/
Try manual install.
Verified share does not exist.
The network path was not found.
80070035
1. Manual agent install
The Agent Management Operation Agent Install failed for remote computer "name". There is not enough space on the disk.
80070070
1. Free space on install disk
The MOM Server failed to perform specified operation on computer "name". The semaphore timeout period has expired.
80070079
NSlookup failed on server. Possible DNS resolution issue.
Try adding dnsname to dnssuffix search list.
The MOM Server could not start the MOMAgentInstaller service on computer "name" in the time.
8007041D
80070102
NSlookup failed on server. Possible DNS resolution issue.
Verify domain is in suffix search list on management servers.
The Agent Management Operation Agent Install failed for remote computer "name"
80070643
1. Ensure automatic updates service is started
2. Rebuild WMI repository
3. DNS resolution issue
The Agent Management Operation Agent Install failed for remote computer "name". Another installation is already in progress.
80070652
Verify not in pending management. If yes, remove and then attempt installation again.
The MOM Server detected that computer "name" has an unsupported operating system or service pack version
80072977
Install latest SP and verify you are installing to Windows system.
Not discovered
Agent machine is not a member of domain
Ping fails
1. Server is down
2. Server is blocked by firewall
3. DNS resolving to wrong IP.
Fail to resolve machine
1. DNS issue
The MOM Server failed to perform specified operation on computer "name". Not enough server storage…
8007046A
1. This is typically a memory error caused by the remote OS that the agent is being installed on.
There are currently no logon servers available to service the logon request.
8007051F
1. Possible DNS issue
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version
of the Windows Installer service.
8007064D
1. Install Windows Installer 3.1
The network address is invalid
800706AB
Possible DNS name resolution issue.
Tried nslookup on server name and did not get response.
Verify domain is in suffix search list on management servers.
The MOM Server failed to perform specified operation on computer servername.domain.com
80070040
1. Ensure agent push account has local admin rights
The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com.
80072979
1. Correct DNS/WINS issue.
2. Try pushing to NetBIOS name
Gautam.75801

SCOM 2012 R2 HA design but using SQL 2014 Standard edition

Hi All,
I want to deploy SCOM 2012r2 with a HA design (but have constraints!)
Plan is two management servers with all roles to each (fresh deployment so 2012r2 RU5)
SQL servers need to be 2014 standard edition due to licensing and cost constraints.
Design is to be split between two datacentres that are fibre connected and sub 3ms latency
Plan was to have a Management Server and a SQL server at each location.
Each location has a dedicated SAN but SAN replication is not an option.
What are my SQL options for the DB??
AlwaysOn FCI is not preferable as it gives a single point of failure due to shared storage requirement.
I read Database mirroring is not a supported config but this isn't Microsoft direct info just blog post, is this correct.
Which leaves me with log shipping, is this supported and the best option??
Would be great to get advice on what works well in the field with a contraint of having to use SQL Standard edition!
Thanks
James

Hi,
No additional licenses are needed for management servers or SQL Server technology.
System Center 2012 R2 licensing
http://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx#tab=2
Reference:
SCOM 2012 R2 HA options with Server 2012 and SQL 2012
https://gallery.technet.microsoft.com/SCOM-2012-R2-HA-options-540beb95
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Reporting doesn't show the newly installed SCOM Agents

Hello,
I am running SCOM 2012 SP1 on Win2008 R2.
I recently deployed scom agent to couple of machines the agents are showing up healthy and i can see the performance and health data from Monitoring tab but when i try to run report i can't find these new agents in the objects to add to report.
Report
it doesn't even query the agents.
and on the SCOM manamgent server i see this error in event viewer not sure if it is related.
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
Exception 'SqlException': Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 368, Message: Violation of UNIQUE KEY constraint 'UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime'. Cannot insert duplicate key in object
'dbo.ManagedEntityProperty'. The duplicate key value is (528, Aug 25 2013 8:52AM).
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.ManagedEntity
Instance name: 08eb00a2-e227-4472-a368-a6e42a2bc502
Instance ID: {EEFCB078-6517-97CD-FA4F-8FCAB54E4930}
Management group: OPSMGR
Regards,
Maqsood
Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

Ok, so at this point, without enabling logging and going to the extremes, I would attempt an uninstall and reinstall of the agents. One at a time. So remove the agents. Reinstall one, and monitor what is happening on that server, and investagate
it in the ops console.
If you know what applications are on the box, and being discovered, look for the server in discovered inventory for those classes, etc.
Before you do that, you can try to run this against the DW to see if there are any alerts associated with these two servers, that is if they ever raised alerts:
USE OperationsManagerDW
SELECT Alerts.AlertName, SUM(1) AS 'Alert Instances', SUM(Alerts.RepeatCount + 1) AS 'Alert + Repeat Count',
CASE Alerts.MonitorAlertInd WHEN 1 THEN vMonitor.MonitorDefaultName WHEN 0 THEN vRule.RuleDefaultName ELSE 'Not found' END AS 'Rule or Monitor Name',
CASE Alerts.MonitorAlertInd WHEN 1 THEN 'Monitor' WHEN 0 THEN 'Rule' ELSE 'Not Found' END AS 'Rule or Monitor', vManagedEntity.Path,
vManagedEntity.DisplayName
FROM Alert.vAlert AS Alerts INNER JOIN
vManagedEntity ON Alerts.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId LEFT OUTER JOIN
vRule AS vRule ON Alerts.WorkflowRowId = vRule.RuleRowId LEFT OUTER JOIN
vMonitor AS vMonitor ON Alerts.WorkflowRowId = vMonitor.MonitorRowId
WHERE (Alerts.RaisedDateTime BETWEEN DATEADD(day, - 180, GETDATE()) AND GETDATE()) AND
(Alerts.AlertName like '%Hub Servers In Retry Error%') and path like '%servername%'
GROUP BY Alerts.AlertName, Alerts.MonitorAlertInd, vMonitor.MonitorDefaultName, vRule.RuleDefaultName, vManagedEntity.Path, vManagedEntity.DisplayName
ORDER BY 'Alert Instances' DESC
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.

SCOM 2012 R2 Agent Issue: Error 25211.Failed to install performance counters.. Error Code: -2147024809

Hi All,
I'm trying to deploy SCOM 2012 R2 agent onto a domain controller and I get the following error "Product: Microsoft Monitoring Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.)."
I've installed the agent successfully onto 4 other domain controllers with out any issues.</p><p>The domain controllers are all VM's running on VMWare and are Windows Server 2012 R2.
I've rebuilt the Perfmon Counters based on this article: https://support.microsoft.com/en-us/kb/2554336?a=wsignin1.0
I've also enabled verbose logging on the msi installation:
InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft Monitoring Agent\Agent\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
Any help on this would be great.

Hi Stefan,
I've successfully installed the agent. The server needed a reboot after fixing the corrupt perfmon counters.
I know have a issue with the agent on the domain controller. It kkeeps on greying out and have used hslockdown to allow the local system access by using the following command.
HSLockdown.exe "ManagementGroupName" /A "NT AUTHORITY\Authenticated Users"
Further digging into the issue I see in the SCOM Management Server the following error "The entity servername is not heartbeating"
Written a SQL query to gather more information. SQL query I used is:
SELECT
ME.FullName,
HSO.StartDateTime AS OutageStartDateTime,
DATEDIFF (DD, hso.StartDateTime, GETDATE()) AS OutageDays,
HSO.ReasonCode,
DS.Name AS ReasonString
FROM vManagedEntity AS ME
INNER JOIN vHealthServiceOutage AS HSO ON HSO.ManagedEntityRowId = ME.ManagedEntityRowId
INNER JOIN vStringResource AS SR ON HSO.ReasonCode =
REPLACE(LEFT(SR.StringResourceSystemName, LEN(SR.StringResourceSystemName)
– CHARINDEX(‘.’, REVERSE(SR.StringResourceSystemName))), ‘System.Availability.StateData.Reasons.’, ”)
INNER JOIN vDisplayString AS DS ON DS.ElementGuid = SR.StringResourceGuid
WHERE (SR.StringResourceSystemName LIKE ‘System.Availability.StateData.Reasons.[0-9]%’)
AND DS.LanguageCode = ‘ENU’
AND ME.FullName like ‘%SERVER NAME%’ –Change name here or leave %% for ALL SERVERS
ORDER BY OutageStartDateTime
This gives me the following reason behind the failure : "The heartbeat from System Center Management Service is missing."
Have I missed anything? The agent is running fine, however SCOM is reporting that the heartbeat is missing.
Any help on this would be great.

System center data access service crashes with event id 26339 ad 26380 in SCOM 2012 Sp1 RTM

hi all,
I have deployed scom 2012 sp1 rtm on Os 2012 std and database is on another VM Machine having SQL 2012 sp1 with OS 2008 R2 SP1 std, suddenly sql vm get stopped and unable to start , so I have delete it from hyper-v 2012 console and imported the VM again
in Hyper-0S 2012 cluster.
Now, System centre data access service get crashed again and again with mentioned events
event 26339, OpsMgr SDKService
event 26380, opsmgr SDkService
An exception was thrown while initializing the service container.
Exception message: Initialize
Full exception: HTTP could not register URL
http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application.
The System Center Data Access service failed due to an unhandled exception.
The service will attempt to restart.
Exception:
System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application. ---> System.Net.HttpListenerException: The process cannot access the file
because it is being used by another process
   at System.Net.HttpListener.AddAllPrefixes()
   at System.Net.HttpListener.Start()
   at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
   --- End of inner exception stack trace ---
   at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
   at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
   at System.ServiceModel.Channels.HttpChannelListener`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.EnterpriseManagement.ConnectorFramework.ServiceDataLayer.ConnectorFrameworkDataAccessChannel.Initialize()
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.Initialize(InProcEnterpriseManagementConnectionSettings configuration)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.InitializeRunner(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
Kirpal Singh

Hi Kirpal
Can you try this it might help as its an known issue of getting event id 's 26361,26380 try out & lets see if it helps.
The manifest files are located on the RMS at the \Program Files\System Center Operations Manager 2007\ root directory. The manifest files will need to be edited for the config and sdk service on affected RMS. The file names are:
Microsoft.Mom.Sdk.ServiceHost.exe.config
Microsoft.Mom.ConfigServiceHost.exe.config
In between the EXISTING <runtime> and </runtime> lines – you need to ADD a NEW LINE with the following:
<generatePublisherEvidence enabled="false"/>
This solution disables CRL checking for the specified execute-ables, permanently.

Deployment SCOM

Similar Messages

Maybe you are looking for