Diagnostic Agents: Update

Hello!
We installed for some times a Diagnostic Agent on satellite system and connected them to Solution Manager (7.1 SP10).
Now we can see that almost every week a new version of Diagnostic Agent will be released on Service Marketplace.
Question:
Do we need to update each time Diagnoctic Agent to the newest version by deinstallation and new installation with SWPM?

Hi Alex L,
Please check the below note attachment for upgrade process,
1365123 - Installation of Diagnostics Agents
Rule #5:
No need to upgrade Diagnostics Agents (in contrast to SAP Host Agent)
if the DA is having recent version, normally not required to DA upgrade using re-installation for ever latest release
Better upgrade JVM and SAP Kernal,
1774669 - Diagnostics Agent - How To Switch or Update SAP JVM
1707141 - Diagnostics Agent - How to upgrade SAP Kernel
Rg,
karthik

Similar Messages

IS Agent Update

Hi Guys,
I downloaded the latest IS Agent from SMP.
I have updated the ISAGENT using JSPM.
But when i open the URL for Byte code adaptor under Managed System system, it is still showing IS agent 8.X.X.X.
Am i missing something?
I want to update the IS agent version as i am getting error is RCA managed system in self diagnosis which asked to update the byte code agent to latest version 7.1 p9.
Regards
Abhishek

Hi Abhishek,
Undeploy IS agent.
Redeploy using SDM.
Restart your diagnostic agent on managed system.
Also, is possible, your java stack on managed system.
Divyanshu

DPM 2012 UR3 Agent Update Error: HRESULT E_FAIL...DCOM Error

My DPM Server is Windows 2008 R2 SP1 with a locally installed SQL and DPM Server and fully patched. My Workstations are all Windows 7 Ultimate x64, fully patched. I have manually installed the DPM RTM Agent and pushed the UR2 update from the DPM Server
without any challenges or issues. I have SCEP running with process exclusions for the DPM services on the WS and DPM Server. I’ve been running DPM 2012 RTM and then UR2 without any issues or challenges to-date.
I have recently updated my DPM 2012 Server from UR2 to UR3 and pushed out all the Agent Updates, which appeared to go successfully from the DPM Console perspective. I spot checked a few systems, 1 workstation (WS) and 1 server, everything looked good. A
couple of days after this I noticed 2 of my workstations failed backing up to Tape. I noticed the recovery options available for these WS’s have stopped updating hours after pushing the UR3 Agent update. The 2 WS’s I'm troubleshooting have a little different
scenario. I have 2 other WS’s that were updated in the same manner and are working perfectly.
Both WS cannot connect to the DPM Server and displays this DCOM Error:
"ERROR:ERROR HRESULT E_FAIL has been returned from a call to a COM component."
The 1st WS DPM Client has a Yelow Sign over-lay and "Administrator has not configured backups." when you hover over it.
The 2nd WS does not the Yellow Sign over-lay.
All the properties of the Local DPM Client Console 'Summary and Protected item' tabs are not updated on the 1st WS but are on the 2nd WS.
1st WS process:
The Recovery Tab shows the available recover dates to choice from.
I can expand one of the backup dates, folders and copy a file to this system.
I can view my previous recovery Points from the console dating back to when I updated the Agents.
I’ve validated the DCOM settings on both WS's compared to a WS that is working, they are the same.
I uninstalled the agent manually, then copied and reinstalled the new UR3 Agent Version with the same outcome.
I uninstalled the new version and reinstalled the previous version, same error.
I then proceeded with upgrading UR2 agent version installing the UR3 version over the top, same error.
I logged on to this WS as the Domain Admin, removed and reinstalled the UR3 version, same error.
I removed, applied and then re-added the DPM server to the local WS DPM and DCOM Groups.
I removed, applied and then re-added the WS from the Groups on the DPM Server.
I’m able to see, ping and view other backup folders presented on the DPM server on this WS.
In the DPM Console I am able to connect to this Workstation successfully from the Administrative, Agent Space.
The DPMClientProtectionCurr.errlog file shows this repeatedly:
0FC0
065C    10/13   05:02:32.499
03        service.cpp(298)
[000000000021FD90]
ACTIVITY
CService::AnnounceServiceStatus
0FC0
0D18    10/13   05:02:33.059
33        dlsclientprotection.cpp(778)
[00000000002BC850]
NORMAL
Connecting to DPM Server: (<Server.FQDN>)
0FC0
0D18    10/13   05:02:33.171
33        dlsclientprotection.cpp(861)
[00000000002BC850]
WARNING         Failed: Hr: = [0x80004005] : Failed to set client OS details - ClientName:<WS.FQDN>, ClientOSVersion:6.1.7601, OSType:2, AgentVersion: 4.0.1920.0
0FC0
0D18    10/13   05:02:33.171
33        dlsclientprotection.cpp(1490)
[00000000002BC850]
WARNING         Failed: Hr: = [0x80004005] : Failed to get connection to DPM server: lVal : ConnectToDPMServer(bstrClientMachineName, &pIUnknown, &fConnectionSuccessful, &dCurrentStatus,
exceptionResult)
The
DPMRACurr.eerlog show this for both WS's:
0EF0 1110 10/13 04:05:02.157 22 genericthreadpool.cpp(824) [000000000093C360]  NORMAL Hr: = [0x80070002] CGenericThreadPool::m_dwMaximumNumberOfThreads[20]
0EF0 1110 10/13 04:05:02.157 03 miscellaneousutils.cpp(918)   NORMAL Error:ERROR_UNKNOWN_PRODUCT, While detecting DPM version. Assuming DPM isnt installed.
And this one repeatedly:
0BE8 08EC 10/13 13:59:40.404 29 radefaultsubtask.cpp(382) [00000000002F1640] 4F801526-72F2-4460-8760-F9D6E127FECB WARNING Failed: Hr: = [0x809909b0] : CRADefaultSubTask: WorkitemID does not exist, {DB3F138D-DE37-414D-BADC-5A161C6E7E1C}
0BE8 08EC 10/13 13:59:40.404 05 defaultsubtask.cpp(546) [00000000002F1640] 4F801526-72F2-4460-8760-F9D6E127FECB WARNING Failed: Hr: = [0x809909b0] : Encountered Failure: : lVal : CommandReceivedSpecific(pCommand,
pOvl)
0BE8 08EC 10/13 13:59:40.404 05 defaultsubtask.cpp(751) [00000000002F1640] 4F801526-72F2-4460-8760-F9D6E127FECB WARNING Failed: Hr: = [0x809909b0] : Encountered Failure: : lVal : CommandReceived(pAgentOvl)
The 2nd WS Process:
I did not remove or touch the local agent installation because the information is populated on this client’s agent properties fields.
I can see the folder selections I’ve chosen to be backed up by the protection group configuration.
When i open the Agent UI I receive the sam DCOM error.
I also receive a different error message on this WS when I try and do a Sync Now from the General Tab: Failed to trigger synchronization.
I was able to perform a consistency check on this WS that completed successfully from the DPM server.
I’ve validated the networking configuration settings are correct.
I flushed local DNS cache.
Thanks,
Paul

Hi,
I have a Windows 7 x64 machine that exhibits this problem. It seems that it is not caused on the client side but on the server side.
In our case the server logs the following every time the client tries to connect:
WARNING   Verify disconnected client failed with exception: System.ArgumentException: Das Element wurde bereits hinzugefügt. Schlüssel im Wörterbuch: "<machinename>". Hinzuzufügender Schlüssel: "<machinename>".
(Translation: Element has already been added. Key in Table: "<machinename>". Key to be added: "<machinename>".
I have uninstalled the agent on the client several times. One time I have seen the following error message on the server side:
Deployment.cs(2815)           NORMAL   Removing all agent records for server[<machinename>] from table InstalledAgent.
ntlmutils.cpp(185)           WARNING   Failed: Hr: = [0x80070002] : Error trying to open key [HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0\NtlmAuthData\<machinename>]
SchedulerImpl.cs(166)           NORMAL   Entering DeRegister, JobDefID: bafe2b8b-53b2-4694-aa28-9e2c6c152d51
Catalog.cs(1006)           WARNING   No retry on exception The specified @name ('') does not exist. while executing sp_delete_alert
Catalog.cs(1013)           WARNING   SqlException encountered, SqlRetryCommand diag details - SqlCommandText => Name=msdb.dbo.sp_delete_alert, CommandType=StoredProcedure
Catalog.cs(1013)           WARNING   CommandDiagInfo => CanRetry=False, CommandTimeout=3600
Catalog.cs(1013)           WARNING   CommandParams   => Count=2, InTx=True
Catalog.cs(1013)           WARNING         Param[0]   => ParameterName=@name | Value= | Size=0 | DbType=NVarChar | Direction=Input | IsNullable=False
Catalog.cs(1013)           WARNING         Param[1]   => ParameterName=@RETURN_VALUE | Value=1 | Size=0 | DbType=Int | Direction=ReturnValue | IsNullable=False
EventManager.cs(98)           NORMAL   Publishing event from SchedulerImpl.cs(838): JobScheduleChange, [JobDefID=bafe2b8b-53b2-4694-aa28-9e2c6c152d51]
Errors on the client side appear the moment the agent is re-added to the DPM server (I use "connect agent" instead of "install agent"). After that moment I get the message "Error connection to the DPM server. Error: a COM-component returned E_FAIL" every time
I open the DPM client. This is mirrored by the Verify error mentioned above on the server side.
To me it seems that parts of the machine config are still in the MSDB after removal (maybe caused by the registry error). If this client is connected again, the orphaned database entries cause the Verify error
If that's true, how could we get rid of those entries? Would it help to rename the client?
Uwe

Can MOPZ be used without installing Diagnostic Agent.

Hi,
I need a clarification.
In Solution Manger 7.1 Version, can I use Maintenace Optimizer (MOPZ) to download SP's for a Managed System without prior installing Diagnostic Agent on the Managed System? If Yes, please write a brief procedure as below. (because my colleague was telling that one must install DA before using MOPZ).
In older Versions, to use MOPZ:
Send Managed System data with tcode RZ70 -------> The data will arrive in SLD of Solman -------> Assigning a Product and creating a Logical Component in SMSY -----> Assigning the Logical Component to a solution in DSWP --------> Now MOPZ can be used.
Thank you,
Mohan.

Hi Mohan,
Not required any agent for MOPZ setup.
Prerequisite:
*Initial, Basis and Managed system configuration setup( RFC creation, AISUSER assignment)
Open the MOPZ using 2 ways,
option 1. Using LMDB system landscape
option 2. In solman_workcenter -> Change Management -> New Maintenance Transcation ( for new MOPZ)
Prerequisite:
User ID is maintained in AISUSER
Configured Technical System in SMSY.
Follow the below documnet for MOPZ step.
http://scn.sap.com/docs/DOC-26893
Not required to create the solution as show in documnet , directly select the production version and start the MOPZ as show the document, remaining step are same.
Step by step how to Configure System for using MOPZ
Rg,
Karthik

DPM 2012 R2 agent update on Windows 2003 server x64 - Exchange

According to the release notes on http://blogs.technet.com/b/dpm/archive/2014/04/23/now-available-update-rollup-2-for-system-center-2012-r2-data-protection-manager.aspx the following workloads are supported on Win2K3 with DPM2012 R2 UR2:
SQL 2005
SQL 2008
SQL 2008 R2
SharePoint 2007
Does that mean protecting Exchange 2007 on Win2K3 is no longer an option after upgrading to DPM 2012 R2 (UR2)? It works on DPM 2012 SP1 but I need to know if it will continue to work after upgrading.
(This question follows on from this thread http://social.technet.microsoft.com/Forums/en-US/c425421b-b726-4125-82fc-beae8947722c/dpm-2012-r2-agent-update-on-windows-2003-server-x64?forum=dpmsetup which was marked as 'answered')

Hi,
Yes, Exchange 2007 backup will continue to work. I think that due to the timeframe of the UR2 release not all workloads were able to be re-certified, thus the limit in supported workloads.
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. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Error while Installing Diagnostic Agent

Hi Experts,
We are getting an error while installing Diagnostic Agent in Solman 7.1. Please find the attached Screen shot of error.
Can you please suggest us what was our error... So that we can move forward.
Thanks in Advance..
Regards,
Krishna.M

Hi,
After finshing of installation with that warning msg , u need to run the SMDSetup script manually in the server as like below.
1. Open a prompt command and navigate to the script folder inside of the agent path: usr/sap/<SID_AGT>/SMDAXX/script
2. Run the smdsetup script as the following examples:
Connection by Message Server:
- smdsetup managingconf hostname:"sapms://solman.full.qual.host.name" port:"81XX" user:"SMD_ADMIN" pwd:"XXXXXXXX"
Kindly refer the below link for the further information
http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents
Thanks & Regards,
Sandeep Alapati

Should I install Diagnostic Agent on managing system itself ?

Dear All,
I am using a solution manager as an managing system .
Should I install the Diagnostic Agent on the managing system , too ?
My solution manager is 7.01 EHP1 SPS22, I find there exist a directory /usr/sap/SMD , so it seems the Disgnostic Agent is installed during the solution manager installation . But in the Work Center -> Root Cause Analysis -> Agent Administration , it returns a "service cannot be reachable " error,
"URL https://<solution manager host >:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
And in the http://<solution manager host>:50000/smd , managed system -> setup wizard , I choose the solution manager SID , and next, it show the SMD agent hasn't been found.
I re-installed the SMD agent , but the result is the same, and I've tried to install the Diagnostic Agent 7.11 and still the same.
Anyone encounter the same problem as me ??
Thanks.

Hi, David,
In Solman_Setup , The initial and Basic configuration are finished without error ( green light).
And in managed system configuration , configure system, the first step check prerequisities failed with red light; the detail error messages is as below :
It seems some kind of service not activated in SICF , but not for sure.
Service cannot be reached
What has happened?
URL https://sapsolmgr.centurydsp.com:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
Note
The termination occurred in system SM2 with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-https-c:000-u:SAPSYS-l:E-i:SAPSOLMGR_SM2_00-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Thanks for your reply.
Enddy.

InTune - Agent Update Fail

I have one machine that's showing up in the InTune Portal under "with agents that are not installed" The machine is running Windows 8.1 Enterprise x64. Looking at the details of the client, I can see that an InTune Update failed: Update
for Microsoft Online Management (X64). It lists update ID a835e70f-490b-4548-830f-2e3acb5c9589 with error 0x80CF200B.
I went to the log files of the machine, and extracted the following, but still have no idea how to proceed to resolve the issue:
2015-02-27 13:08:08:886
16440 186c
Misc =========== Logging initialized (build: 5.0.3518.0, tz: -0500) ===========
2015-02-27 13:08:08:886
16440 186c
Misc = Process: C:\Program Files\Microsoft\OnlineManagement\Common\omsvchost.exe
2015-02-27 13:08:08:886
16440 186c
Misc = Module: C:\Program Files\Microsoft\OnlineManagement\Updates\Bin\omupdsrv.dll
2015-02-27 13:08:08:886
16440 186c
Service *************
2015-02-27 13:08:08:886
16440 186c
Service ** START ** Service: Service startup
2015-02-27 13:08:08:886
16440 186c
Service *********
2015-02-27 13:08:08:902
16440 186c
Service WARNING: Cannot start service now. AgentInstaller is installing updates. Silently exit.
2015-02-27 13:08:08:902
16440 186c
Service *********
2015-02-27 13:08:08:902
16440 186c
Service ** END ** Service: Service exit [Exit code = 0]
2015-02-27 13:08:08:902
16440 186c
Service *************
2015-02-27 13:08:12:937
10768 2b4c
Misc =========== Logging initialized (build: 5.0.2560.0, tz: -0500) ===========
2015-02-27 13:08:12:937
10768 2b4c
Misc = Process: C:\Program Files\Microsoft\OnlineManagement\Common\omsvchost2.exe
2015-02-27 13:08:12:937
10768 2b4c
Misc = Module: C:\Program Files\Microsoft\OnlineManagement\Common\AuthPlugin.dll
2015-02-27 13:08:12:937
10768 2b4c
EP SLS: Initializing for service ID 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2015-02-27 13:08:12:937
10768 2b4c
EP SLS: Reading from cache
2015-02-27 13:08:12:937
10768 2b4c
EP SLS: Successfully read service endpoints from cache.
2015-02-27 13:08:19:239
4932 d3c
Misc =========== Logging initialized (build: 5.0.3518.0, tz: -0500) ===========
2015-02-27 13:08:19:239
4932 d3c
Misc = Process: C:\Program Files\Microsoft\OnlineManagement\Updates\Bin\omupdclt.exe
2015-02-27 13:08:19:223
4932 d3c
UpdClt omupdclt.exe launched with command line "C:\Program Files\Microsoft\OnlineManagement\Updates\Bin\omupdclt.exe" /DailyTasks
2015-02-27 13:08:24:281
6868 2468
Misc =========== Logging initialized (build: 5.0.3518.0, tz: -0500) ===========
2015-02-27 13:08:24:281
6868 2468
Misc = Process: C:\Program Files\Microsoft\OnlineManagement\Common\omsvchost.exe
2015-02-27 13:08:24:281
6868 2468
Misc = Module: C:\Program Files\Microsoft\OnlineManagement\Updates\Bin\omupdsrv.dll
2015-02-27 13:08:24:281
6868 2468
Service *************
2015-02-27 13:08:24:281
6868 2468
Service ** START ** Service: Service startup
2015-02-27 13:08:24:281
6868 2468
Service *********
2015-02-27 13:08:24:296
6868 2468
Agent * Updates client version 7.12.3518.0
2015-02-27 13:08:24:296
6868 2468
Agent * Base directory: C:\Program Files\Microsoft\OnlineManagement\Updates
2015-02-27 13:08:24:296
6868 2468
Agent * Access type: No proxy
2015-02-27 13:08:24:296
6868 2468
Agent * Network state: Connected
2015-02-27 13:08:24:359
6868 2468
AgntUpd Searching for Asset Inventory Service: Not Found
2015-02-27 13:08:24:359
6868 2468
AgntUpd Searching for Microsoft Intune: Found
2015-02-27 13:08:24:374
6868 3430
Agent *********** Agent: Initializing Agent ***********
2015-02-27 13:08:24:374
6868 3430
DnldMgr Download manager restoring 0 downloads
2015-02-27 13:08:24:374
6868 3858
PeerDist Async IO monitor worker thread starting.
2015-02-27 13:08:24:390
6868 3430
Agent Task "Microsoft\OnlineManagement\Microsoft.OnlineManagement.UpdateEventReporter" was not found
2015-02-27 13:08:24:390
6868 3430
AgntUpd Agent requests client agent sync
2015-02-27 13:08:24:390
6868 3430
AgntUpd Asset Inventory Service is not installed; not scheduling agent sync
2015-02-27 13:08:24:390
6868 3430
Agent BeginFetchInstallStatus: Detected pending Agent Install Result
2015-02-27 13:08:24:390
6868 d70
Agent *************
2015-02-27 13:08:24:390
6868 d70
Agent ** START ** Agent: Installing updates [CallerId = Client Agents Sync]
2015-02-27 13:08:24:390
6868 d70
Agent *********
2015-02-27 13:08:24:390
6868 d70
Agent * Updates to install = 1
2015-02-27 13:08:24:390
6868 3430
AgntUpd Asset Inventory Service agent sync refreshing state
2015-02-27 13:08:24:390
6868 d70
Agent * Install Result Update Call: No actual installation will happen.
2015-02-27 13:08:24:390
6868 3430
AgntUpd Searching for Asset Inventory Service: Not Found
2015-02-27 13:08:24:390
6868 3430
AgntUpd Asset Inventory Service is disabled. Canceling agent sync timer
2015-02-27 13:08:24:390
6868 3430
AgntUpd Microsoft Intune agent sync refreshing state
2015-02-27 13:08:24:390
6868 3430
AgntUpd Searching for Microsoft Intune: Found
2015-02-27 13:08:24:390
6868 3430
AgntUpd Microsoft Intune is enabled. Initiating agent sync
2015-02-27 13:08:24:390
6868 2468
AgntUpd Received timeout event
2015-02-27 13:08:24:390
6868 2468
AgntUpd WARNING: Skipping Microsoft Intune sync request since a sync is already running
2015-02-27 13:08:24:390
6868 2468
Agent Agent servicing time window policy is not set
2015-02-27 13:08:24:390
6868 2468
Agent WARNING: Unable to read agent servicing time window policy, error = 0x80070002.
2015-02-27 13:08:24:390
6868 2468
AgntUpd WARNING: Failed to update task triggers, error = 0x80070002
2015-02-27 13:08:24:390
6868 d70
Agent * Title = Update for Microsoft Online Management (x64)
2015-02-27 13:08:24:390
6868 d70
Agent * UpdateId = {A835E70F-490B-4548-830F-2E3ACB5C9589}.503518
2015-02-27 13:08:24:390
6868 d70
Agent * Bundles 1 updates:
2015-02-27 13:08:24:390
6868 d70
Agent * {58FC1D2B-70F5-4B66-9D29-7FB3703D2B9F}.503518
2015-02-27 13:08:24:421
6868 884
AgntUpd >>## RESUMED ## AgntUpd: Install agents [UpdateId = {A835E70F-490B-4548-830F-2E3ACB5C9589}]
2015-02-27 13:08:24:421
6868 884
AgntUpd # WARNING: Install failed, error = 0x80CF200B
2015-02-27 13:08:24:468
6868 d70
Report *********** Report: Initializing static reporting data ***********
2015-02-27 13:08:24:468
6868 d70
Report * OS Version = 6.3.9600.0.0.65792
2015-02-27 13:08:24:468
6868 d70
Report * OS Product Type = 0x00000004
2015-02-27 13:08:24:468
6868 d70
Report * Computer Brand = Microsoft Corporation
2015-02-27 13:08:24:468
6868 d70
Report * Computer Model = Surface Pro 2
2015-02-27 13:08:24:468
6868 d70
Report * Bios Revision = 2.04.0950
2015-02-27 13:08:24:468
6868 d70
Report * Bios Name = 2.04.0950
2015-02-27 13:08:24:468
6868 d70
Report * Bios Release Date = 2014-05-12T00:00:00
2015-02-27 13:08:24:468
6868 d70
Report * Locale ID = 1033
2015-02-27 13:08:24:468
6868 3ff8
Report REPORT EVENT: {961FC6DE-7F1A-41C6-BBC9-D8B5986BDA17}
2015-02-27 13:08:24:468-0500 1
182 [AGENT_INSTALLING_FAILED] 101
{A835E70F-490B-4548-830F-2E3ACB5C9589}
503518 80cf200b
Client Agents Sync Failure
Content Install Installation Failure: Windows failed to install the following update with error 0x80cf200b: Update for Microsoft Online Management (x64).
2015-02-27 13:08:24:484
6868 d70
Agent Prompt user to reboot policy is not set. Client's default behavior is to prompt for reboot unless the policy specifies otherwise.
2015-02-27 13:08:24:484
6868 d70
Agent *********
2015-02-27 13:08:24:484
6868 884
AgntUpd #########
2015-02-27 13:08:24:484
6868 d70
Agent ** END ** Agent: Installing updates [CallerId = Client Agents Sync]
2015-02-27 13:08:24:484
6868 884
AgntUpd ## END ## AgntUpd: Install agents [Service = "Microsoft Intune", CallId = {BA0014E7-820E-483F-8F08-96D110F7A6EC}]
2015-02-27 13:08:24:484
6868 d70
Agent *************
2015-02-27 13:08:24:484
6868 884
AgntUpd #############
2015-02-27 13:08:24:484
6868 884
AgntUpd Agent sync completed
2015-02-27 13:08:53:972
10768 3930
EP SLS: Initializing for service ID 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2015-02-27 13:08:53:972
10768 3930
EP SLS: Reading from cache
2015-02-27 13:08:53:972
10768 3930
EP SLS: Successfully read service endpoints from cache.
2015-02-27 13:08:53:972
10768 3930
EP SLS: Contacting Location Service
2015-02-27 13:08:53:972
10768 3930
EP SLS: Contacting Location Service
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized binding name: DefaultBinding_UserAuthLocationServiceService
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized binding name: DefaultBinding_ServerAuthLocationServiceService
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized binding name: HttpsErrorEventWebService
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized binding name: DefaultBinding_SCCMConnector
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized binding name: DefaultBinding_SCCMUserSyncService
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized auth reqs: "AgentSTS"
2015-02-27 13:08:54:723
10768 3930
EP WARNING: SLS: Ignoring unrecognized auth reqs: "ConfigManagerConnectorSTS"
2015-02-27 13:08:54:723
10768 3930
EP SLS: Writing to cache
2015-02-27 13:08:54:723
10768 3930
EP SLS: Successfully wrote service endpoints to cache.
2015-02-27 13:08:54:723
10768 3930
EP SLS: Initializing for service ID 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2015-02-27 13:08:54:723
10768 3930
EP SLS: Reading from cache
2015-02-27 13:08:54:723
10768 3930
EP SLS: Successfully read service endpoints from cache.
2015-02-27 13:08:54:738
10768 3930
EP SLS: Initializing for service ID 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2015-02-27 13:08:54:738
10768 3930
EP SLS: Reading from cache
2015-02-27 13:08:54:738
10768 3930
EP SLS: Successfully read service endpoints from cache.
2015-02-27 13:08:54:738
6868 3ff8
Agent *************
2015-02-27 13:08:54:738
6868 3ff8
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-02-27 13:08:54:738
6868 3ff8
Agent *********
2015-02-27 13:08:54:738
6868 3ff8
Agent * Online = No; Ignore download priority = No
2015-02-27 13:08:54:738
6868 3ff8
Agent * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and
IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Detection'
and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Detection' and IsAssigned=1 and RebootRequired=1"
2015-02-27 13:08:54:738
6868 3ff8
Agent * ServiceID = Microsoft Intune
2015-02-27 13:08:54:738
6868 3ff8
Agent * Search Scope = {Machine}

I know this is old but I’m trying to clean up old posts. Did you ever solve this? If so it would be good if you could post the solution to assist others. If not, at this stage,
as nobody has answered, I would recommend that you call Intune support.
You will find your local Intune support number here
http://technet.microsoft.com/en-US/jj839713.aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to uninstall Remote Diagnostic Agent (RDA) 4

I am planning to try installing Remote Diagnostic Agent (RDA) 4 to development server to help diagnose/analyze the delay in login. I’ve done client-level tracing and have the trace file. This is a trace file related to network, so TKPROF, Trace analyzer, and other tools to analyze and tune SQL are not applicable. I just learned from Oracle Metalink that RDA can help analyze this kind of trace file. Before I install RDA, I’d like to know how to uninstall it so that if there are negative impact/results after the install, I can uninstall it. I tried to search the web and Oracle Metalink but I didn’t get any valuable information on how to uninstall RDA.
My question is: has anyone tried to uninstall this RDA tool? If yes, could you please show me how you did the uninstall?

user5470917 wrote:
I am planning to try installing Remote Diagnostic Agent (RDA) 4 to development server to help diagnose/analyze the delay in login. I’ve done client-level tracing and have the trace file. This is a trace file related to network, so TKPROF, Trace analyzer, and other tools to analyze and tune SQL are not applicable. I just learned from Oracle Metalink that RDA can help analyze this kind of trace file. Before I install RDA, I’d like to know how to uninstall it so that if there are negative impact/results after the install, I can uninstall it.There will be no negative impact/result. RDA is just a series of scripts/procedures. It is no more invasive of your database than a backup script. I wouldn't bother with an uninstall as you'll just have to re-install the next time you want to use it.
I tried to search the web and Oracle Metalink but I didn’t get any valuable information on how to uninstall RDA.
My question is: has anyone tried to uninstall this RDA tool? If yes, could you please show me how you did the uninstall?Just delete the files.

Problem using agent-update.bin to roll out SunMC agents

Greetings,
I want to use agent-update.bin to roll out SUNMC agents to solaris 9 and 10 hosts. I use the es-agentupdate.sh tool to create the installation package and the seed file on the SunMC server in /var/opt/SUNWsymon/agentupdate.
I copy the binary /opt/SUNWsymon/base/bin/agent-update.bin to the root on a test server.
I run the following commands - each fails - unable to find the seed file. Can anyone suggest an -f argument which might work as I need the rollout to occur without user intervention to enter secrets.
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f seed-file
or
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f ./seed-file
or
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f /var/opt/SUNWsymon/agentupdate/seed-file
Standard out from the last of these commands is as follows:
sbin_archive downloaded
SUNWessmu package installed
Running InstallClient : /tmp/agentupdate/DPI_BasicAgent/bin/sparc-sun-solaris/InstallClient -s oranc1 -p 8080 -u DPI_BasicAgent/upgrade-policy_sparc.xml -f /var/opt/SUNWsymon/agentupdate/seed-file
InstallClient started
upgrade policy downloaded
Argument file /var/opt/SUNWsymon/agentupdate/seed-file absent. Exiting...
Error: running InstallClient
Error: running InstallClient with error code 1
ERROR: information for "SUNWescom" was not found
ERROR: information for "SUNWescom" was not found
On the SUNMC server:
root@oranc1# pwd
/var/opt/SUNWsymon/agentupdate
root@oranc1# ls -l
total 6
drwxr-xr-x 4 root root 512 Feb 5 13:59 DPI_BasicAgent
-rw------- 1 root root 54 Nov 23 13:44 seed-file
drwxr-xr-x 4 root root 1024 Nov 23 12:46 SunMC36_Generic
I have also tried
-r-------- 1 root root 54 Nov 23 13:44 seed-file
Thanks in advance for your help
Tony

Greetings Mike,
I copied the seed-file from my SUNMC server to the host being updated and put it in the same directory as agent-update.bin. Ran the following:
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -s ./seed-file
The result is:
Error: getting sbin_archive
Web server is listening on port 8080 and accessible through a browser. Agent package directory name and seedfile name are OK.
any additonal help appreciated.
Regards
Tony

Agent update on VMM management server

Hi!
I just installed Update Rollup 3 for SCVMM 2012 R2. Updating the agents on all hosts in the fabric was smooth sailing, but the "Agent Version" on the VMM management servers (clustered) still shows 3.2.7510.0 (base R2 installation). Viewing
the Properties of the servers it shows that RU3 is installed, but I can't figure out how to update the VMM agent on these management servers.
Does anyone have ideas on how I can update the agents to the latest version? I am guessing that the management servers' agents also are supposed to be updated after rollup installations, not just the other servers in the fabric?

The SCVMM Server Agent should be updated on the SCVMM Server when the SCVMM Server UR is applied.
Past experience is that this is the expected behavior.
The Agent (being its own component) will have a different version from the SCVMM Server itself. If there was no need to update the agent in the UR, then it would not revise.
I know that UR2 included an agent update as I had to push new agents to my Hyper-V Servers - I have not updated to UR3 yet.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

SAP Host and Diagnostic agent

Dear Experts,
We are running ECC 6.6 and Portal on Net Weaver 7.31 ,and have Soution Manager 7.1,As I have read many places that host agent get installed automatically with Net Weaver Installation.
In My Portal server I am able to see hostctrl folder and SAPHostControl service related to host agent, but there is no such service or folder in R/3 server.So do I need to install Host Agent separately for R/3 system.
One more Question do I need to have Host agent mandatory for Diagnostic agent installation(SMD)?
Thanks
Chander

Hello
In our R/3 system Kernel release is 720 ,and we doesn't have SAP host agent,But for Java with same kernel release we have SAP host agent.
If this is an ECC system upgraded from an old R/3 system then you might have ignored to install SAP Host Agent as I have seen the upgrade guides suggesting to install SAP Host Agent starting from EHP5.
When we installed Net Weaver 7.31 for java portal SAP Diagnostic agent installed automatically and with that SAP host agent also came.
Read my previous reply. All new installation bring in SAP Host Agent.
My main purpose to install Diagnostic agent for R/3 for E2E analysis ,so i want more clarity regarding SAP host and diagnostic agent.
R/3 is on Net Weaver 7.31( ECC 6.6), So which version of diagnostic and host agent need to be installed and are they installed separately .
Follow the SAP note I have given above. The latest version is SAP HOST AGENT 7.20
Here is the SAP note once again 1031096 - Installing Package SAPHOSTAGENT
Regards
RB

ZENworks agent update from workstation.

Hi there,
Is there a way to get workstations to update themselves automatically with the latest version of the ZENworks agent. (ZCM 11.2.3.a is what we have)
We have a standard image which has a older version of the ZCM agent on it. Images are pulled down and the workstations are automatically built.
Various bundles are then installed automatically on the workstations. When we update the image with other changes etc, we will add the new agent to it.
But until we do that, instead of me having to manually check for all new machines built in the last week / month and then assign the agent update to them,
is there a process, script, bundle of something that can run on the workstation to update the agent itself to the latest version we have.
We are using ZCM 11.2.3a and we need to do this without having to manually visit 200-400 machines.
Thanks
Mark

While I (And Microsoft) recommends configuring your Router/Switches to
pass WOL packets from your trusted WOL Servers (Primaries in this case),
it is also possible to use WOL Proxies to allow this to happen across
your subnets.
There are also some Windows settings that may be necessary to allow WOL
to work from a deep sleep state. I would recommend researching those as
well.
If you are concerned about deploying updates when users are not using
the devices, WOL is something with which I recommend you become more
comfortable using.
On 2/10/2014 8:06 AM, gshaw0 wrote:
>
> craig_wilson;2305537 Wrote:
>> And ask folks to Leave PCs on as well as schedule a WOL task to run for
>> those missed. Then they should all be ready by start of the next school
>> day.
>>
>>
>> On 2/9/2014 3:00 AM, Shaun Pond wrote:
>>> Gshaw0,
>>>
>>> I can't say that it will be non-disruptive, no. Can you not schedule
>>> updates to happen out of hours?
>>>
>>
>>
>> --
>> --
>> Craig Wilson
>> Novell, Inc
>>
>> Any Comments or Posts are only my views and not Novell's
>> Accuracy Attempted but not guaranteed.
>
> 2500 PCs across 5 sites in a couple hundred different rooms, can't
> guarantee even half of them being on. WOL isn't routed across VLANs so
> that won't do the trick either, also not had great experiences with it
> in the past as it seems to rely on machines having had a clean shutdown
> and the socket not being turned off in between (once that happens WOL
> doesn't seem to have any effect until the machine gets a clean startup \
> shutdown cycle)
>
>
Craig Wilson
Novell, Inc
Any Comments or Posts are only my views and not Novell's
Accuracy Attempted but not guarenteed.

Client updates broken since last agent update

Immediately after the newest version of the Agent updates apply themselves, all the computers I administer can no longer update. When the Intune client is launched, it reports error code 0x80070057 and says Try Again. When Try Again is clicked
the error changes to 0x7007065b. Attempts to repair the System Updater, both with FixIT and manually, fail, and report falures.
This is happening on all of the over 250 machines I administer.

Hello
I confirm this problem.
Some Windows 7 machines that were not in the latest update group can still download Endpoint Protection updates.
The Windows 7 machines that are fully updated cannot update their protection definitions since May 14.
Error code I receive is 0x80072f76 (ERROR_HTTP_HEADER_NOT_FOUND)
Windows 8.1 machines are not affected.

CCMS agent update fails with an error

Hello All,
We are trying to update CCMS agent 700 unicode version on 640_REL unicode kernel.
But we are getting below error
./sapccm4x -v
Could not open the ICU common library.
   The following files must be in the path described by
   the environment variable "LIBPATH":
   libicuuc30.a, libicudata30.a, libicui18n30.a [nlsui0_mt.c 1557] pid = 860208
Please help.
Thanks,
Anu

If you use the Unicode version you need to install the Unicode libraries also.
You find them in the download area (where you got the CCMS patch) under "UCLIB". I assume this is AIX so you can also search for the file
UCLIB_3-20000978.SAR
extract it and put the files in the kernel directory.
Then logout and logon (the shell) and try again (or simply give a 'rehash' command).
Markus

Diagnostic Agents: Update

Similar Messages

Maybe you are looking for