Issues with SCOM 2012 Agent on Red Hat 5 Server

We are running SCOM 2012 server and have deployed the agent successfully to a number of Red Hat Linux servers. I am having an issue on about a quarter of the hosts, in that they appear as HEALTHY but are Grayed out and not green. When I look at the /var/opt/microsoft/scx/log/omiserver.log
file I see:
WARNING: wsman: authentication failed for user scom2012
I have verified that the system account is setup with the correct password and the runas account is setup with the correct password (i am able to deploy the agent from the SCOM server using it, so the passwords DO match).
Any ideas?
I've seen this on a few systems here when the agent has been upgraded but the old agent process does not die off. Just to rule it out, pick a node, make sure there are no instances of scxcimserver or scxcimprovagt and then start the agent and
see if the issue goes away. I've also seen wsman authentication failures related to the libssl issue that was fixed in yesterday's release.

Similar Messages

Issue with OHS (EPM) installation on Red Hat 6.4

Hello Gurus,
We are facing an issue with the installation of Oracle HTTP server which comes with EPM 11.1.2.2 using EPM Installer on Red Hat 6.4.
When I select the OHS product it says, that the Oracle software is not certified on the current operating system, however it does not happen with any other product in the suite
Is Red Hat 6.4 64 bit not a supported OS?
I have installed all the required libraries mentioned here: Oracle&#174; Fusion Middleware System Requirements and Specifications
Also my NPTL version is 2.12 which is higher than 2.3.4 as mentioned here: Oracle&#174; Fusion Middleware System Requirements and Specifications
Any help will be highly appreciated.

John,
My installation went smooth, however when I start the configuration (Oracle Database) I am getting the following error while configuring the shared service registry:
Failed to navigate from RegistryWizardState: Error while initializing registry. See logs for more details.
My DBA says that he has provided all the following privileges to the schemas.
CREATE SESSION
CREATE VIEW
CREATE TYPE
CREATE TABLE
CREATE CLUSTER
CREATE TRIGGER
CREATE SEQUENCE
CREATE INDEXTYPE
CREATE PROCEDURE
CREATE ANY SYNONYM
DROP ANY SYNONYM
UNLIMITED TABLESPACE
configTool has the following exceptions:
[2013-09-10T10:44:53.748+05:30] [EPMCMN] [WARNING] [EPMCMN-01001] [oracle.EPMCMN] [tid: 10] [ecid: 0000K46JlSgAXNIMyqqYMG1IBegW000002,0] [SRC_CLASS: com.hyperion.cis.utils.oui.OUIUtilImpl] Failed to determine home via OUI: [[
oracle.sysman.oii.oiii.OiiiInventoryDoesNotExistException: The inventory pointer location /etc/oraInst.loc is either not readable or does not exist
    at oracle.sysman.oii.oiii.OiiiInstallAreaControl.initAreaControl(OiiiInstallAreaControl.java:1855)
    at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:292)
    at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:231)
    at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:180)
    at com.hyperion.cis.utils.oui.OUIUtilImpl.inventoryTemplateMethod(OUIUtilImpl.java:289)
    at com.hyperion.cis.utils.oui.OUIUtilImpl.findEpmOracleHomeFromInventory(OUIUtilImpl.java:67)
    at com.hyperion.cis.utils.oui.OUIUtilLinkageErrorProtectionWrapper.findEpmOracleHomeFromInventory(OUIUtilLinkageErrorProtectionWrapper.java:18)
    at com.oracle.preconfig.impl.InventoryPreConfigCheck.executeCheck(InventoryPreConfigCheck.java:23)
    at com.oracle.preconfig.PreConfigCheckTemplate.execute(PreConfigCheckTemplate.java:9)
    at Main.runPreconfigChecksAndExitIfFail(Main.java:142)
    at Main.main(Main.java:90)
com.hyperion.hit.registry.exceptions.RegistryException: Unable to create registry.
    at com.hyperion.hit.registry.RegistryConnection.createRegistry(RegistryConnection.java:354)
    at com.hyperion.hit.registry.RegistryUtils.initUpgradeRegistry(RegistryUtils.java:272)
    at com.hyperion.hit.registry.RegistryUtils.initRegistry(RegistryUtils.java:105)
    at com.hyperion.hit.registry.Registry.createBasicComponents(Registry.java:2305)
    at com.hyperion.config.document.Storage.initRegistry(Storage.java:245)
    at com.hyperion.cis.config.ConfigRegistryUtils.initializeRegistry(ConfigRegistryUtils.java:384)
    at com.hyperion.config.wizard.impl.RegistryWizardState$1$1.commit(RegistryWizardState.java:228)
    at com.hyperion.hit.wizard.Wizard$NextClass.run(Wizard.java:544)
    at java.lang.Thread.run(Thread.java:662)
Caused by: java.sql.BatchUpdateException: error occurred during batching: ORA-01950: no privileges on tablespace 'HYPSS_DATA'
    at oracle.jdbc.driver.OracleStatement.executeBatch(OracleStatement.java:6390)
    at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:248)
    at com.hyperion.hit.registry.RegistryConnection.createRegistry(RegistryConnection.java:344)
    ... 8 more
Any help will be highly appreciated.

SCOM 2012 Agent - Best Practices with Base Images

I've read through the
SCOM 2012 agent installation methods technet article, as well as how to
install the SCOM 2012 agent via command line, but don't see any best practices in regards to how to include the SCOM 2012 agent in a base workstation image. My understanding is that the SCOM agent's unique identifier is created at the time of client installation,
is this correct? I need to ensure that this is a supported configuration before I can recommend it.
If it is supported, and it does work the way I think it does, I'm trying to find out a way to strip out the unique information so that a new client GUID will be created after the machine is sysprepped, similar to how the SCCM client should be stripped of
unique data when preparing a base image.
Has anyone successfully included a SCOM 2012 (or 2007 for that matter) agent in their base image?
Thanks,
Joe

Hi
It is fine to build the agent into a base image but you then need to have a way to assign the agent to a management group. SCOM does this via AD Integration:
http://technet.microsoft.com/en-us/library/cc950514.aspx
http://blogs.msdn.com/b/steverac/archive/2008/03/20/opsmgr-ad-integration-how-it-works.aspx
http://blogs.technet.com/b/jonathanalmquist/archive/2010/06/14/ad-integration-considerations.aspx
http://thoughtsonopsmgr.blogspot.co.uk/2010/07/active-directory-ad-integration-when-to.html
http://technet.microsoft.com/en-us/library/hh212922.aspx
http://blogs.technet.com/b/momteam/archive/2008/01/02/understanding-how-active-directory-integration-feature-works-in-opsmgr-2007.aspx
You have to be careful in environments with multiple forests if no trust exists.
http://blogs.technet.com/b/smsandmom/archive/2008/05/21/opsmgr-2007-how-to-enable-ad-integration-for-an-untrusted-domain.aspx
http://rburri.wordpress.com/2008/12/03/untrusted-ad-integration-suppress-misleading-runas-alerts/
You might also want to consider group policy or SCCM as methods for installing agents.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Issue with re-skilling agents in bulk

We tried to re-skill about 30 agents in bulk and change the competence level at the same time. Uccx took the change but, we noticed that agents were in a ready state even with calls were in the queue.
We went back and one by one re-skilled them again and at that point I'm told it worked...agents received calls.
Anyone ever had any issues with re-skilling agents in bulk?
We are on UCCX 8.5.1 SU3
Thanks,
Dan

Hi PARADOX-RED,
Based on the error messages that you provided, please remove the connector software from Control Panel completely. Then, in the problematic computer, please locate
to: Control Panel-> System-> select Change settings. And select the Computer Name tab in the System Properties dialog box, click
change button. Then in the Computer Name/Domain Changes dialog box, please take the computer out of the domain as a workgroup, and rejoin in new domain.
Please check if this issue can be solved. If it still exists, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Does the SCOM 2012 agent "look back" in the logs before the service was started?

Does the SCOM 2012 agent "look back" in the logs before the service was started?<o:p></o:p>
We raised this question to our Microsoft rep back when we migrated to SCOM 2007. We wanted to know if SCOM would alert on errors generated before the Heath Service started. For example, errors
logged before the service is started on reboot (which is when some critical errors are logged). We also wondered what happens when the service is restarted...would errors during the same window be missed?
If I remember correctly the MS response was that the agent looks back on startup/restart based on a timestamp of some kind. We did some testing that seemed to confirm this information. I've
recently encountered several instances of errors generated while the service was stopped (primarily during boot up) where SCOM failed to alert on the error.
Can anyone confirm how the SCOM 2012 agent deals with errors generated before the service starts on boot and during service restarts?

I would suspect it's with watermarks as it has been in the past. What you should look into is if these alerts you were expecting are event based, and if there are rules set to alert for these conditions. If so, and you don't get an alert,
then you can bring that up with your msft rep. However, they should be caught.
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.
There is a watermark. If the agent has been down for a significant period of time, the watermark may not apply, as the log would have rolled - but the entire log will still be processed regardless of what has already been discarded in the log. This may cause
some problems if a monitor picks up an unhealthy state, and the healthy state log entry has already been flushed. In this case, you need to reset health on that particular monitor, or just flush the cache on the agent to start anew.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

Dell server hardware component monitoring with scom 2012 R2.

hello ..
We have some dell poweredge r710 SFF 2X SIX CORE X5 SAS Servers ,I need to monitor its hardware components with scom2012 R2.I have installed os:windows server hyper-v server on this and windows server core OS management packs on scom and monitoring
working fine .next I want to know their is Latest Management pack available for this dell model server and what are hardware components can be monitored with scom 2012 R 2. I want to monitor Hardware failure such as Power failure ,cpu failure,disk
failure and NIC failure etc
Thanks
Richa

Hi,
Please refer to the User’s Guide of the DELL MP:
http://support.dell.com/support/edocs/software/smconect/msscom/40/en/ug/pdf/Dell_Server_Management_Pack_Suite_v4.0_UG.pdf
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Meanwhile, considering this is related to DELL products, if you need more information or further investigation, please also contact DELL support
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.

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

Scom 2007 and scom 2012 agent multi home

is there version limit for the agent multihom for scom 2007 and scom 2012?
In technet i found it for SCOM upgrade it mentioned need scom 2007 CU4 and above, how about for multihome approach for SCOM agent?
Besides that, instead of agent upgrade, could we perform agent uninstallation scom 2007 and reinstall scom 2012?
Thanks for your advice.

Hi Cylim,
You can upgrade your agents to SCOM 2012 only from SCOM 2007 R2 CU4. Please look at these helpful links:
http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
http://blogs.catapultsystems.com/cfuller/archive/2012/05/31/quicktricks-multi-homing-an-agent-to-opsmgr-2012-scom-sysctr.aspx
http://blogs.catapultsystems.com/cfuller/archive/2014/04/02/multihomed-migrations-in-operations-manager-lessons-from-the-field.aspx
As Scott mentioned, you can uninstall SCOM 2007 agent and install SCOM 2012 agent on one or a few servers, and see if they report properly to both management groups SCOM 2007 and SCOM 2012:
http://dynamicdatacenter.wordpress.com/2012/10/15/om-2012-agent-report-to-scom-2007-not-r2-scom-2012/
Natalya

OEM integration with SCOM 2012

Hi,
Can anyone help me out on the topic- OEM integration with SCOM 2012.

Are you refer to this document
Oracle® Enterprise Manager Installation and Configuration Guide for Microsoft System Center Operations Manager Connector
http://docs.oracle.com/cd/E24628_01/install.121/e28572.pdf
Roger

DPM failed to communicate with the protection agent on DPM 2010 SERVER because the agent is not responding. (ID 43 Details: Internal error code: 0x8099090E)

Hi everyone,
Backup jobs for protected members are intermittently failing with the following error on the DPM server:
DPM failed to communicate with the protection agent on <DPM 2010 SERVER> because the agent is not responding. (ID 43 Details: Internal error code: 0x8099090E)
Why does the DPM server failing to see it's own DPM agent cause the backup job for another server to fail? One day a backup will work fine, the next it may fail; and the next back to normal again...
The following error is recorded in the Service Control Manager event log on the DPM server just prior to the above error:
A timeout was reached (30000 milliseconds) while waiting for the DPMRA service to connect.
Thank you.
With regards,
Rob

Hello,
I have read these entire postings and see that my problems match most of the above problems.
I believe we have tried all of the ideas in this blog and lots of other ideas from other forums and internet searches.
We have about 80 small databases protected and set at 15 minute incremental and most will work but some fail. When they fail the most common, but not only error, is something like "DPM
failed to communicate with the protection agent on <DPM 2010 SERVER> because the agent is not responding. (ID 43 Details: Internal error code: 0x8099090E)". The alert is inactivated in the DPM Console, and the backups resume as normal."
Since later jobs are successful I thought all was well. All was well until I went to restore from incremental backups. We worked for two days (day and night work) to restore
from a corrupted virtual disk on our SQL Server 2008 R2. I suspect DPM had something to do with the corrupted virtual disk. All I know is that we never had this problem until installing DPM. Here is what we encountered when we went to restore
from the protection points:
* Restore jobs take a minimum of 15 minutes for jobs that are 45 MB or 2 GB.
* If you pick a backup from the list of recovery points that is not valid the job runs for 15 minutes and then "Failed".
* You cannot rerun the job because SQL Server 2008 has the table being recovered as <tablename> (recovering) and a retry will not work. Of course time is wasted while waiting
to see if it worked.
* Eventually you realize that even after dropping the table in the (recovering) mode in SQL that the restore point must be bad or possibly one of this failed recovery points.
* So begins the quest to start restoring recovery points one by one and 15 minutes by 15 minutes until you find one that actually restores to a SQL Instance.
* If you have 80 of these to do and you average trying three recovery points and each takes 15 minutes, not to mention the time to drop the table in SQL, well that time adds up to 3,600
minutes of trial and error. 60 hours of trial and error, wow not much of a savings using DPM over a SQL backup plan.
* And then you have to explain to your customers that their databases were restored but you do not know at what point the DB was restored.
All in all it seems like DPM concept is great but like many backups the backup plan looks good on paper but actually restoring a backup is quite a different matter.
I don't know if anyone has ever solved the problems presented in this forum but if they have then I wish they would post and if no one has solved the problem then shame on DPM.
Good luck everyone, but I for one have spent about two months on trying to protect and restore consistently. I have never had one day of consistent and reliable restore points. I
am going back to sql management plans for my backups. I have never, in 10 years had a sql generated backup fail me. Never.
gbl

Upgrade from SCOM 2007 R2 to SCOM 2012 R2 on a single server

we are planning to Upgrade from SCOM 2007 R2 to SCOM 2012 R2 on a single server.We are planning to do in place upgrade.

If you looking for a guide, check : http://blogs.4ward.it/how-to-upgrade-to-scom-2012-from-scom-2007-inplace-upgrade/
MS documentation for the upgrade is located at: http://technet.microsoft.com/en-us/library/hh476934.aspx
thx
Pranav

Issues with Monitoring Azure services with SCOM 2012 R2

Hi,
I'm trying to setup monitoring of our Azure subscriptions in a new installation of Operations Manager 2012 R2 which is running in-house as it is also monitoring our internal services. I've used the guide below:
http://blogs.msdn.com/b/walterm/archive/2013/04/13/first-impressions-on-system-center-management-pack-for-windows-azure-fabric-preview-for-scom-2012-sp1.aspx
This has all worked OK and I've been able to add the subscription into OP Manager and it's found the cloud service, storage and VM's. However when I try to add the monitoring and I go to create this When I select the Add option in the Add Monitoring
Wizard and click the Search button to list the components (Cloud Service, Storage and VM's) nothing is found despite me having already selected the subscription.
Has anyone else experienced this or can offer any advice?
Many Thanks
Colin

Hi,
Which version of RDP client you are using for your client?
Does more user login at same period of time?
As you have commented that after sticking the user can’t able to login in RDCB server, here I can suggest you to check the setting of connection broker. Also you can check that you have place the proper location path of UPD while configuring in collection configuration
wizard. You can take a look at below article foe virtual desktop configuration.
Deploying Virtual Desktops with Windows Server 2012
Are you trying to use same UPD for different collection then also it might happens to occur your issue. The fact of UPD is User profile disks are for a single collection only. A user connecting to two different collections will have two separate profiles. If
you want to synchronize settings, refer to Microsoft User Experience Virtualization. Go through this article for more understanding related to UPD.
Working with User Profile Disks on Session-Based Desktop Deployments
Hope it helps!
Thanks.

Issues with running controller-agent config on OLT .

Hi All,
I have 3 machines total. One is windows 2008 (controller / server) and other two are RHEL 5.2(agents). I have the same script in all 3 locations. Running the scripts individually in all 3 environments works fine. The scripts read the local databanks which is csv that has the paths for JAVA_HOME to execute jar and generate secret key. From controller(windows box) I clicked on Manage --> Systems and added the agent details and was successfully done. From controller, I added the script, set the system pointing to agent's name and ran the test, the scripts fail at the point where the secret key gets generated using the Jar. My guess is controller is able to read the local path from CSV and not able to generate the secret keys using local java_home and jar. Can anyone kindly comment on this issue.
Thanks,
Nags.

We are running SCOM 2012 server and have deployed the agent successfully to a number of Red Hat Linux servers. I am having an issue on about a quarter of the hosts, in that they appear as HEALTHY but are Grayed out and not green. When I look at the /var/opt/microsoft/scx/log/omiserver.log
file I see:
WARNING: wsman: authentication failed for user scom2012
I have verified that the system account is setup with the correct password and the runas account is setup with the correct password (i am able to deploy the agent from the SCOM server using it, so the passwords DO match).
Any ideas?
I've seen this on a few systems here when the agent has been upgraded but the old agent process does not die off. Just to rule it out, pick a node, make sure there are no instances of scxcimserver or scxcimprovagt and then start the agent and
see if the issue goes away. I've also seen wsman authentication failures related to the libssl issue that was fixed in yesterday's release.

Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2. I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
issues (that was a fun one to troubleshoot). Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
[14:46:47]: Always:
:LaunchMsiSetup: Complete: 2 seconds
[14:46:47]: Error:
:LaunchMsiSetup: Failed, return code: 1612
[14:46:47]: Error:
:Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
[14:46:47]: Error:
:Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
[14:46:50]: Error:
:LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
[14:46:50]: Error:
:ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
In the application log I am getting the following error:
"Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
Manager is already installed. These must be uninstalled to proceed."
I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
I am at a loss as to what to try next. Any suggestions?

Hi,
Check if you have the following registry. If so, please back it up first, then delete for a test.
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
http://technet.microsoft.com/en-us/library/dn249707.aspx
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: Agent Proxy not enabled.

I am seeing Critical Severity alerts on my SCOM 2012 Server stating:
"The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service ( 0C43A2D6-628F-D150-9553-8EABFECA600C ) should not generate data about this managed object ( 716D31EF-F34C-A4E3-1A16-3B8B75E85C0D
I have about 8 servers with this error. All of which have had Proxy turned on in SCOM ( Administration -> Agent Managed -> <agents in question> -> Properties -> Security Tab -> Checked "Allow this agent to act as a proxy...".
All of these servers are on the same domain as the SCOM server (we only have 1 domain).
Thanks,

For what it's worth I'm experiencing this issue. I've closed out the alerts and watched them pop back up later.
The agent was not able to submit data on behalf of another
computer because agent proxy is not enabled. Details:Health service (
774FAEE6-003E-7CAC-FC02-676C0D9F675E ) should not generate data about this
managed object ( 13354EE4-F0F9-DF55-88F0-271F30A70AAB ).
PS C:\> Get-SCOMAgent |Where-Object -Property id -eq '13354EE4-F0F9-DF55-88F0-271F30A70AAB'
PS C:\> Get-SCOMAgent |Where-Object -Property id -eq '774FAEE6-003E-7CAC-FC02-676C0D9F675E'
PS C:\>
This alert was generated about an hour ago, I have 160 agents installed.
My guess is...well I don't have a good guess. any help about this would really be appreciated.
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

Issues with SCOM 2012 Agent on Red Hat 5 Server

Similar Messages

Maybe you are looking for