Agent Versions Incorrect?

Good Afternoon,
I have recently been given control of our SCOM infrastructure as the person before me has left and I've been given the reigns. We are currently running SCOM 2012 Service Pack 1 and have Cumulative Update 8 installed which is the latest CU available from
Microsoft.
I have been doing a bit of housekeeping today and noticed that the agent version that is installed on all of our clients is version 7.0.9538.0 which is the version that came pre-installed with 2012 SP1 when it was first released.
The only server that does seem be on the latest build number is the Management Server which CU8 was installed on to manually. The build number is now 7.0.9538.1123.
I know for a fact that our previous owner of SCOM installed every CU that has been released and I also remember that he went through the process of updating the clients on all our servers (almost 400).
I have gone through the process of uninstalling some of the agents and reinstalling but I am unable to update it. We do also have a few servers that are running version 6.1.7221.49. This version is from May 2009 and was part of the SCOM 2007.
I've noticed that if I log on to one of the servers that an agent is installed on after we ran the update for CU8 I can see that the file versions of the dll files do have the correct build number for CU8 (7.0.9538.1123)
So from what I see it looks as though this is potentially a bug with SCOM. I'm not sure. How can I update the agent versions within the SCOM console to reflect the correct agent version.
As you can see in the screenshot1 above the version for the servers with an agent here are still on 7.0.9538.
In screenshot2 this is from one of the servers with an agent installed in the path of 'C:\Program Files\System Center Operations Manager\Agent'. As you can see the latest version is there but you can also see older versions too.
Finally if I log on to the SCOM management server and open operations manager shell and run the command get-scomagent it gives me the same incorrect version.
I hope someone can help me with this.
Regards,

Yes, it´s normal and as expected. The version number 7.0.9538 reflects System Center 2012 SP1 Operations
Manager and doesn´t change when applying a Update Rollup. If you were to upgrade to R2 then the version would be 7.1.10226.0 instead.
If there were older agents from a SCOM 2007 etc, the version number would match the SCOM version.
Regards,
Daniel
IT Consultant at Viridis IT

Similar Messages

Agent version 10.1.0.6.0 DB Control version 10.2.0.4 - Is this ok?

Hi,
dbconsole is failing to startup. We have already tried rebuilding the repository and still it won't start.
The agent does come up. One thing to point out is that the agent version that is reported by emctl status agent is 10.1.0.6.0
with a protocol version of 10.1.0.2.0
while dbcontrol(and the database are on version 10.2.0.4). Can the 10.1.0.6 agent work with 10.2.0.4? This setup
did work before but I think the repository rebuild may have caused some problems. The db was installed as 10.1.0.6
and then upgraded to 10.2.0.4 so the original repository build was likely on a consistent version.
Thanks

I see lots of connection refused messages in the emagent.trc file
Messages are of the form:
WARN snmehl_connect: connect failed to....
ERROR pingManager: nmepm_pingReposURL: Cannot connect to...
This isn't to surprising since dbconsole is not running.

DPM 2012 R2 UR2 and Windows 2003 SP2 Agent Version Issue

Hi All, I have UR2 installed on my DPM 2012 R2 server and have followed Mike's guide on getting them protected:
http://blogs.technet.com/b/dpm/archive/2014/06/11/details-on-protecting-windows-server-2003-computers-using-data-protection-manager-2012-r2.aspx
The agents now show in the DPM console but display as needing an update and showing as agent version 4.1.3313.0 instead of 4.1.3441.0, which is odd.
Servers have:
.Net 3.5 Sp1 Full
Visual C++ 2008 Redistributable - x86 9.0.30729.17
From the DPM server:
C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\agents\RA\4.2.1235.0\i386\1033\DPMAgentInstaller_Win2K3_i386.exe
Executed:
setdpmserver.exe -dpmservername DPMserverName
From the DPM server:
Attach-ProductionServer.ps1 script on the DPM server and refreshed twice
What have I missed?

Hi.
Reboot your 2003 Server
Run DPM Setup again on Server 2003
Run setdpmserver.exe again
click refresh in DPM Server
worked for me
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

How to find installed SMD Agent version?

Hi,
Please let me know how to find the installed SMD agent version in managed system.
Thanks,
Kavitha Rajan.

Hello,
Something really easy to differentiate the agents installed:
- 7.01-> /usr/sap/SMD/JXX
- 7.11 or 7.20 -> /usr/sap/DAA/SMDAXX
Regards,
Allam

Agent version differs from LMService

Hi ,
I am connecting a NW 7.31 Java system with solman 7.1 SP10 with SMD diagnostic agent for Manage system config set up
I have installed the SMD agent and connected with central SLD & solman.
In the agent connectivity it can be seen that the diagnostic agent is in pending status with the message " 7.10.1.0.2011070611153 Agent version differs from LMService"
what could be the reason and what is LMService here.
The system kernel version is 720_EXT.
Please guide and provide a solution
Thanks in advance

Hi Daniel,
Can you check LM-Service SP and Patch level.
Also Refer the guided process as per these 2 KBAs.
1962333 - Responsibility of individual steps in transaction SOLMAN_SETUP
1931100 - "Agent version differs from LMService" Error in Solution Manager 7.1 Agent Administration
Divyanshu

IS Diagnostics Agent Version 7.01 SR1 available?

Hi,
We have solution manager version Versions 7.0 EHP1 < SP20 so Diagnostics Agent Version 7.01 SR1 complies with the version of the Solution Manager system.
But I can not find dowload available on market pla

Looks like it is required. My version is 1.6

Search for all deployed agents version

Hi,
I want to list all (recent) deployed zcm agents to find out which computers need to be updated manually to the latest version. The reporting:
Type Software Applications, focusing on General Software
Columns Product Manufacturer
Product Name
Product Version
Instances (Summary)
Product
Machine Name
Criteria Device Is Retired = No and
Product Is Deleted = No and
Product <= Novell ZENworks Adaptive Agent 11.3.2.47407 and
Product >= Novell ZENworks Adaptive Agent 11
==> doesn't show correct results as some devices are reported as old version but in fact the latest agents version has been installed. What option are useful to find the installed agents versions?
All the best, Ralf

Is your Zone Setup to Auto-Rename Devices when the machine name changes?
I wonder if the issue is that the "Machine Name" may not match "ZCM Device Object Name"
You may even have Dupe "Machine Names" so that while you think it is updated, it is not because it is actually a different machine than you expected.

Report Agent version

Hi all,
is it possible that I can get a report about the ZCM Agent version from my clients? I want to know how many clients are online with the old (10.1.0) version....
GerritRoss

Originally Posted by gerritross
Hi all,
is it possible that I can get a report about the ZCM Agent version from my clients? I want to know how many clients are online with the old (10.1.0) version....
GerritRoss
For all how have the same question: You can create dynamic groups in the workstation section. There you can choose Workstation Agentversion. So it is easy to get these information!
Greets

11g: New agent versions at download-area

Hello,
how can i put new agent versions at our download area on grid control server?
Acutally we have a grid control server verison 11.1.0.1.0 and all agent versions for deployment are 11.1.0.1.0 or older. But i want to install agent version 11.1.0.7.0. What i have to do therefore?
Regards,
Heike

The staging area in <OMS_HOME>/sysman/agent_download/<version> is only for staging base versions of the agent.
If you want to deploy an agent with patches (e.g. agent version 11.1.0.1.0 with PSU 5 applied), you can apply the desired patches to an existing agent and then clone it. For more information on cloning an agent, please see:
http://docs.oracle.com/cd/E11857_01/install.111/e16847/clone_agent_usng_zip.htm#BABHBJJA
By the way, agent version 11.1.0.7.0 is not available.
Regards,
- Loc

Cisco Secuirty agent version 5.2

I installed the cisco security agent version 5.2 on my windows xp machine, i am not in a server enviroment only at home. i go to control panel and try to remove it does nothing and then i try from the program files and try there nothing how do i get this off my system

I started it and right click and yes i can turn it off and i can also just disabled the service under services? but that is not what i wnat to do i want to remove it off my system. i was simply curious about what this was and i really dont understand what it does, i know its for a client server architecture but what else is it for.

ISE 1.2 Profiling - User Agent attribute incorrect

Hi all,
Just troubleshooting some profiling issues and have found that multiple devices are profiling incorrectly eg MAC OSX profiling as Apple-Device. Basically the issue is the user-agent string profiled by ISE is incorrect meaning that only the OUI is matched. During the BYOD onboarding process, non Internet Browser, applications and services (games and OCSP Daemons etc) are presenting their specific user-agent strings eg "OCSPD\1.0.2" to ISE resulting in incorrect profiling.
Does anybody have any suggestions on how to resolve this issue as it is resulting in about 50% of devices been profiled at the "top level" ie Apple-Device or Windows Workstation (anything based on User-Agent). Can any one explain whether profiler works on the basis of first agent received, last agent received and why it doesn't hold onto a list of presented agents to make a decision? In my mind this is a pretty big issue in that some of the more popular device profiling policies are based on a user-agent string thus potentially preventing you from defining tight Authz policies eg IPAD only etc

"Unless you have suppression configured, ISE will continue to collect profiling data and will re-profile a device as long as a rule with higher certainty factor is hit. However, if the certainty factor is the same the device will remain at its originally profiled group."
The suppression feature will not affect the re-profiling of a device. The suppression only affects the logging on the MnT node. Since the Profiling is a PSN function the suppression has no affect on the outcome of a profiling event.
You are correct in that a rule with a higher certainty factor "wins" and this is the profile that is chosen. Again, an understanding of how profiles work is not the issue here.
For example say only the RADIUS and HTTP probes are being utilized for an endpoint. There are two endpoints one is a iPad and the other an iPhone. The endpoint attributes that are known about the device are the MAC OUI and the useragent.
Based on the default profiling rules there are two three things that need to be identified either an iPhone or an iPad. The first common item is that the MAC OUI is identified as apple. This increases the certainty factor by 10. The second is either the HTTP User agent containing either iPad/iPhone or the DHCP hostname containing either iPad/iPhone. Both of those conditions would increase the certainty factor by 20 for a total of 30. Since DHCP is not being used in this example we can remove that for a possibility and say that for an iPhone to be profiled as an iPhone it must both have a MAC OUI of apple and the useragent must contain iPhone. Same goes for iPad, but iPad in the useragent.
Like smcbridebpc stated every application that uses HTTP will have a useragent string. The profiler rules assume that the useragent that is being used contains either the word iPhone or iPad to distinguish these types of devices. If an application on the device sends a useragent string such as "OCSPD\1.0.2" which is obviously the OCSP Daemon. This useragent string is "stuck" on the endpoint and no other usable useragents can be used to profile the device. Therefore a race condition exists and depending on the application that wins determines if the profiler will be accurate or not.
The only two solutions that I can think of would be to have a useragent filter that would allow you to manually filter out useragents like "OCSPD\1.0.2" (or the ISE developers could filter known unusable user agents out on the backend) OR everytime a new useragent is presented to the profiler for a device the useragent is joined to a list of useragents.
If the useragent was overwritten everytime a new useragent was presented then it would cause the device to be reclassified everytime the different applications presented useragents which would not be good.
It does look like a bug may have been filed and marked as fixed in release pending, but the bug notes do not list enough information to identify if this is the same issue that we are seeing.
https://tools.cisco.com/bugsearch/bug/CSCuj45373

Cannot start SQL Server Agent (Version 2014 enterprise core)?

The SQL Server Agent log file has the following information. I already set the firewall for inbound 1433.
2014-11-04 11:59:43 - ? [100] Microsoft SQLServerAgent version 12.0.2000.8 (X64 unicode retail build) : Process ID 6108
2014-11-04 11:59:43 - ? [495] The SQL Server Agent startup service account is ......
2014-11-04 11:59:43 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2014-11-04 11:59:43 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to
allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2014-11-04 11:59:43 - ? [098] SQLServerAgent terminated (normally

Is this new SQL Server installation or originally it was working fine ?
Below message makes me think you might as well need to repair your installation
>SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
Please see below link
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d2a97cf4-54b2-40b7-836a-b9f146442855/unable-to-open-sql-server-logs?forum=sqlsetupandupgrade
Without errorlog it would be difficult to say why this happened but as errorlog says it has found registry inconsistent so repairing installation would help
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Cisco Agent Desktop incorrect stats Agent Statistics Display

Hi,
I have a very strange problem with a cisco agent desktop user. The times/numbers as displayed in the Agent Statistics Display are incorrect. As you can see from image 1, the agent was presented with 14 calls. The total talking time is 7:22. However if you look at the actual times from image two, and add those numbers you will have a total of 54:42 minutes:seconds. Also the Max talking is incorrect since this filed should display the longest call which has a length of 14:22 min:sec. Also the ready times max/avg and so are incorrect. It's like it's displaying numbers from a different agent however the number of calls presented is correct. If i look at this specific user from the supervisor tool the numbers are correct, see image 3. (in this image a 15th call was placed) I have reinstalled the agent desktop software but this has not solved this problem. I've done some googling but can't seem to find anyone with the same issue and/or a way to troublshoot this. Anyone have a clue?
Image 1:
Image 2:
Image 3:

Hi Anand,
I've looked at the historical reports. Nothing weird there. The 14 minute call came directly from outside, no transfeer or anything. And even if this was the case then the 2nd longest inbound call is 8:30 and not 3:08. Also if you take the sum of all inbound call times you get almost 55 minutes. The difference is too much as the Toal Talking time displayed is 7:22. Also from the supervisor tool I do see the correct numbers.
Thanks again.
Regards,

Why SCOM 2012 R2 Agent version for Service Manager servers is 6.1.7221.49, why not 7.1.10184.

Hi ,
In SCOM 2012 R2 console if i look at all of my agent managed servers have agent builds of 7.1.10184 but my two service manager servers have agent builds of 6.1.7221.49
Can anyone let me know is this known issue or how can we upgrade the agent to correct version.
Thanks in advance
Bharath

Hi,
SCOM and SCSM are built on the same structure, Management Servers and DAta Warehouse etc. This means that when you install the SCSM Management Server, the Microsoft Monitoring Agent is also installed. When
you want to monitor Service Manager and the server it´s installed on, you need to configure the SCOM parameters from the control panel at the SCSM management server.
If you were to try and install the SCOM agent at the SCSM server, it would fail and tell you that you can´t install the agent on a server where Service Manager is installed. The agent will be upgraded when
you upgrade Service Manager so this is all expected and It´s as it should be :)
Regards,
Daniel
IT Consultant at Viridis IT

OMS vs Agent version

Is it possible to run OMS Oracle Enterprice Grid Control Version 10.2.0.1.0 with enterprice agents of higher version like 10.2.0.2.0?
- Tommy

Your Enterpise Manager will always come (whether downloaded or CD) with the Installation Guide. In the installation guide for each release, it states the Certified Platform, Respository, Management Service, Managed targets etc.
Anything outside of those stated in the guide and release note is a hack around that you deal with on your own.
So I would suggest you read the Installation Guide for your Release because what works for Ugonic's platform outside the certified ones may not work for Tommy.

Agent Versions Incorrect?

Similar Messages

Maybe you are looking for