Agent removal
Hello,
I want to remove the Zenworks Asset Inventory agent version 7.5 from all machines. They are not installed by an application object.
Can anyone tell me how to get this done?
Thanks in advance,
Peter
9195010,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/
Similar Messages
-
I am trying to upgrade my Zen agent install from Zen 6.5sp2 agent to Zen
7sp1 agent. There appears to be a problem with my current install of the Zen
6.5 agent that prevents the install from automatically removing it pryor to
the Zen 7 install. I have tried uninstalling the 6.5 agent manually through
add/remove programs but the uninstall fails.
My question is this....
How do I remove the Zen 6.5 agent manually so that all traces are gone from
my machine? Thanks...
MikeRolf Lidvall wrote:
>> How do I remove the Zen 6.5 agent manually so that all traces are gone
>> from my machine? Thanks...
>
> It's not easy doing that manually because it's installed
> with MSI-technology. The safest way is to use this tool,
> download link is in the document:
> "Windows Installer CleanUp Utility"
> http://support.microsoft.com/kb/290301
That tool doesn't remove zen-agent. It just can remove installer
configuration for it. In order to really remove agent you should use
msiexec /X package.msi or msiexec /X{package_GUID}. In Zen 6.5 case that
would be MsiExec.exe /X{51E7C053-8ED5-4BB8-AEA7-69AECED4A282} (or
something like that. Right line can be found in
/HKLM/Software/Microsoft/Windows/CurrentVersion/Uninstall) .
Cleaning installer configuration might help solving
installation/uninstallation problems though, so if those above lines
don't work, then use CleanUP utility and try again.
Timo Pietil -
Sourcefire newbie here...I have to remove FireAMP agents from computers, but I would like to do this from the FireAMP management console. I know that if you navigate to Management>Computers and you highlight the computer in question you have the option to "Delete" from actions window on the right. After executing the deletion, the computer will re-appear since the actual agent was never removed from the client side. How can this process be done from within Sourcefire FireAMP console without actually "touching" the actual computer?
Currently there is no method to uninstall the connector from the amp console. This requires touching the computer or some other mechanism.
-
SCOM R2 agent removed but stays in Computer field under monitoring
We have servers that needs retired, so I uninstall from the console and the servers disappear from the agent managed view. But if you look under computers in the monitoring view the server is still there. When we were on SP1 we had a similar issue and i contacted MS and we got a script to clear it out out of the database (Orphaned Servers)
now that we are on R2 it seems the script doesnt work because it can not locate the name..any suggestion on this
agent manage and computers are off by 22 when they should be the sameHi I have the same problem.
I have lot of machines in the computer view which are not available in the Agent managed view. that machine was deleted more than 2 weeks ago.
We found the following on the net:
http://www.experts-exchange.com/Microsoft/Server_Applications/Q_26893576.html
You will need to remove the objects from the Database. This is fairly easy to do. Here are the steps that i use when i have this issue.
System Center Operations Manager 2007 stores all "entities" it "manages" in the BaseManagedEntity table in the Operational database (named "OperationsManager", by default). This is the place where we will be manually telling SCOM that this computer does
not exist anymore. There's a column called "IsDeleted" that stores if the agent was removed.
1. Connect to the SCOM SQL server and open SQL Management studio
2. Right click on OperationsManager database and select new query
3. Run the following query in the right window to see the status of
ALL computers in SCOM
SELECT * FROM dbo.[BasemanagedEntity] where FullName Like '%Windows.Computer%'
4. To see the status of a specific computer in SCOM (replace the text "fqdn" with the server name)
SELECT * FROM dbo.[BasemanagedEntity] where FullName Like '%Windows.Computer%' and Name Like '%FQDN.of.my.computer%'
5. In the results scroll to the right to find the "IsDeleted" column. 0(Zero) means the database does not know the computer has been deleted. If it is zero then we will run the next command to change it to 1 (one)
replace the text "fqdn" with the server name
UPDATE dbo.[BasemanagedEntity] SET IsDeleted = 1 where FullName Like '%Windows.Computer%' and Name Like '%FQDN.of.my.computer%'
Going back to the Operations Console to the Monitoring & Computer section, shows us that the computer does not show in the list already. It will still take some time before it really gets deleted in the database, but visually you are already set.
(Do note that the machine and its child objects like disk and CPU are still there in the Data Warehouse. This will stay there until that expired there also; which is 360 days by default). -
SCOM 2012 Powershell command to remove agent
Hello,
Has anyone had any luck removing agents via Powershell to mimic the delete agent from the console?
Blogs don't turn up anything useful for this task.
The 2012 Powershell covers how to approve agents, add proxy flag, and uninstall agent, but nothing to remove. Used the SQL stored procedure previously in 2007R2 (and same procedure exists in 2012 SP1.
Anyone aware of Powershell automate agent removal?
Thanks!
SCOM Power Shell to add SCOM 2012 agent
Get-SCOMPendingManagement | where {$_.AgentName -eq "ServernameFQDN"} | Approve-SCOMPendingManagement
Enable Proxy on newly added agent
Get-ScomAgent | where-object {$_.DisplayName -like "okcnmo*"} | where-object {$_.ProxyingEnabled.Value -eq $False} | Enable-SCOMAgentProxy
SQL Query to remove
http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/e413c030-509b-45e4-bcd4-b4ae1a649c73
Uninstall Agent
http://technet.microsoft.com/library/hh545186.aspx
Remove Unix agents
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerunixandlinux/thread/081f2801-7dfa-4db9-8c78-6adbc487a031/We actually have used the stored procedure for 2007 and 2012
OperationsManager.dbo.p_TypedManagedEntityDelete
If you want to use Invoke-Sqlcmd to run the query.
Another way from SQL which can be put in PowerShell
--Grab GUID for that health service
select * from BaseManagedEntity
where FullName like '%<servername>%'
and IsDeleted = 1
Look for FullName with Microsoft.SystemCenter.HealthService:servername
-- Use this to test the entity delete for the healthservice GUID
DECLARE @EntityId uniqueidentifier;
DECLARE @TimeGenerated datetime;
-- change "GUID" to the ID of the invalid entity
SET @EntityId = '<GUID here>';
SET @TimeGenerated = getutcdate();
BEGIN TRANSACTION
EXEC dbo.p_TypedManagedEntityDelete @EntityId, @TimeGenerated;
COMMIT TRANSACTION
--Check what is in deleted
select * from BaseManagedEntity
where IsDeleted = 1 -
SCOM 2012 R2 agent upgrade fails crippling agents
Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
******* Action:
******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid. Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
KeithHi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
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. -
How to protect both access (http and https) with a Policy Agent
Hi,
During the installation of a web Policy Agent (i.e. Policy Agent for IIS) we have to choose the protocol (and port) of the web server we want to protect.
If we have an IIS with secure (https) and non secure (http) applications, how we manage this scenario with the policy agent?
Regards,Hi,
Finally, i have installed the agent in IIS5 in the non secure port (http) and in fact it detects both access (http and https) fine.
The problem now is that if i try to access to a non secure url ( http://mynonsecureapp.com ) all works fine, the agent redirects to https://myaccessmanager.com:443/amserver/UI/Login?goto=http://mynonsecureapp.com but when i try to access to a secure url ( https://mysecureapp.com ) the agent try to redirects me to: https://myaccessmanager.com:443/amserver/UI/Login?goto=http://mysecureapp.com (notice that the agent removes the 's' in the url).
The amAgent log file shows:
+2008-07-17 09:44:08.296MaxDebug 656:d8f6b0 PolicyAgent: am_web_is_notification(), https://sigcit.agp.gva.es:443/fullcitriweb is not notification url http://sigcit.agp.gva.es:80/amagent/UpdateAgentCacheServlet?shortcircuit=false.+
+2008-07-17 09:44:08.296 Warning 656:d8f6b0 PolicyAgent: OnPreprocHeaders(): Access Manager Cookie not found.+
+2008-07-17 09:44:08.296 Debug 656:d8f6b0 PolicyAgent: am_web_is_access_allowed(): url 'https://sigcit.agp.gva.es:443/fullcitriweb' path_info ''.+
+2008-07-17 09:44:08.296MaxDebug 656:d8f6b0 PolicyAgent: am_web_is_access_allowed(): processing url http://sigcit.agp.gva.es:80/fullcitriweb.+
+2008-07-17 09:44:08.296 Debug 656:d8f6b0 PolicyAgent: am_web_is_access_allowed(): client_ip 172.27.65.62 not found in client ip not enforced list+
Any ideas?
Regards,
Edited by: idm_oceanic on Jul 17, 2008 1:33 AM -
Unable to delete agent assignment from Standard Task 8267 DECISION
Hi All
In transaction PFTC_CHG I'm trying to Delete Agent Assignment (Shift + F2), the screen simply refreshes and the action is not performed - the user is not deleted from the Demo Workflows parent folder? I'm not sure how to change or remove this entry? Authorisations check out fine.
Regards,
AdrianHi ,
Go through below links ..i am sure you will find something helpful.
How to delete agents
remove assigned agents
Regards,
Himanshu Joshi -
SCOM 2012 UR2 - Flush health service state causes infinite agent resets
Appearing on several of our 2008R2 servers from our SCOM 2012 UR2 environment, set up with several management servers:
If I select a monitored servers agent in the Operator Console and click the task
Flush health service state and cache, the selected agent will restart as intended.
However, it will restart again every 2-3 minutes forever ever after, unless you stop the agent service and delete the health service cache folder on the monitored server.
This is visible via the eventlog:
event 103, Healthservice. A task to reset the health service store has been submitted. The service store will be deleted and re-created.
This was never the case with our SCOM2007R2 setup and started appearing with 2012.
Have anyone seen this before? Any ideas?
Regards / JonMight save someone some time....
Stopping the agent, removing the "Health Service State" directory + restarting doesn't appear to help. I did this *and* deleted some agents from the console (then re-added them. We turned auto approve off) and it appears
it might have fixed it. I'll know more in the morning if this actually does the trick besides doing a full uninstall/reinstall of the agent.
If you don't know what agents are constantly restarting, search all management servers for *many* file transfers (Event ID 2110 in Ops manager event log) all to the same Instance/GUID. Execute this powershell on a managemnt server: "get-SCOMClassInstance
-Id <GUID>" to get the affected agent. Alternatively, make a SCOM rule to catch event 103 and look for many repeats from the same server/agent:
Event Type: Warning
Event Source: HealthService
Event Category: Health Service
Event ID: 103
Description:
A task to reset the health service store has been submitted. The service store will be deleted and re-created. -
How to fix "A 32-bit agent is installed on 64-bit operating system" alerts
Hi
We have installed SCOM 2007 R2 CU1 in our environment (by properly following installation sequence given on the CU1 web page). After manually installing agent update of CU1 on 64 bit servers, we are getting alerts "A 32-bit agent is installed on 64-bit
operating system" and the status of these 64-bit servers remains in Warning state. We have manually uninstalled and reinstalled 64-bit agent as well as 64-bit CU1 agent update but still the status is in Warning state. We can not completely uninstall cluster
node agent, remove it from the console and reinstall agent from scratch because SCOM R2 is not allowing to do clean uninstall and reinstall of agent on cluster nodes.
If anyone faces similar problem and have fixed it then please let me know the solution so i can also fix the issue.
Thank you
HRP
Thanks & regards, H R ParikhThis new(er) monitor is set to generate when the registry key "HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft
Operations Manager\3.0\Setup" is found on a 64-bit Windows server. We have several alerts like this as well, but found it had little to do with the CU1 patch and
more to do with rolling out the updated Operations Manager management pack (v6.1.7599.0) at around the same time as well as the server having had a 32-bit agent previously installed at one point or another. We are looking into simply removing the 32-bit
key, but have not done so just yet as we need to test this theory on a dev server first. Of course, to be safe, we could always uninstall the agent and patch, delete the keys manually, and then reinstall.
Hope that helps.
Larry -
We did a trial of ZCM about a year ago for the patch management piece of it and ended up selecting another vendor so the server VM we were testing it on is no longer available. We loaded the agent on a handful of workstations at the time and forgot about them after the trial.......fast forward to now and I'm having an awful hard time getting them removed. I've tried unregistering (zac unr -f -s) and doing a local only uninstall with no luck because I don't know the password. I've tried running the cleanup tool as well but again the lack of the password is holding me up. Is there any way to get these agents removed without completely hosing the systems? I've seen some mention of using msiexec /x guid but I'm unaware if self defense was enabled when these agents were deployed or not and don't want to run the risk of making the situation worse.
Originally Posted by Phillip E. Thomas
I've also struggled with this issue. Using the syntax
AgentCleanup -silent -casa
with the zenworks cleanup tool seems to bypass the password prompt,
while still removing everything, including ZESM.
I made a little progress with this.....running that command did remove casa but I was still left with ZESM. I don't have anything Novell Agent related listed in Add/Remove programs, but the ZESM service is still active. -
12c Cloud Control - Agent Unreachable
Hello,
I am quite new to 12c cloud control and I am unable to resolve an "Agent Unreachable" issue.
I could find Agent does not upload to OMS in OEM 12c as relevant
but nothing in that worked for me.
The setup is as follows:
1) 12c cloud control is installed on a box and is up and running (both OMS and agent)
2) The agent on the same host as OMS can talk to OMS and the agent status is shown as "available" in OMS console
3) There is another box that has a 11.2 database installed as well as 12c agent installed (called as DEVBOX for convenience)
4) DEVBOX has database up and running and 12c agent also up and running. In the past, it was probably being able to "talk" to OMS but I can't remember
However, at present, on OMS console, this agent is shown as "unreachable". I tried few things but only possible issue I could find is
when I try to use Setup -> Add Target -> Add Targets Manually -> Add non-Host targets using guided process, on the "specify Host" page
when I click on "Select Host" option, the hostname in the agent URL for the DEVBOX is different than the actual host name.
As the agent URL for DEVBOX is not reachable (because the hostname is invalid), I can't do anything with this agent.
Can somebody please help?Loc Nhan wrote:
To remove an agent from the console:
- Go to the homepage of the host where the agent reside
- From the Host menu under the host name, select Related Targets
- Remove all non-agent targets
- Remove the host target by selecting Host > Target Setup > Remove Target
- Stop the agent
- Remove the agent target by going to the agent homepage and selecting Agent > Target Setup > Remove TargetLoc,
Once again thanks for looking into this. I followed your advice above and removed the host and the agent from OMS console.
Now, with the 12c agent already running on the DEVBOX, I was hoping that OMS will automatically detect the agent but I
can't find it in OMS console.
On DEVBOX:
[oracle@devbox agent_inst]$ ./bin/emctl status agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
Agent Version : 12.1.0.1.0
OMS Version : 12.1.0.1.0
Protocol Version : 12.1.0.1.0
Agent Home : /u01/app11g/oracle/agentHome12c/agent_inst
Agent Binaries : /u01/app11g/oracle/agentHome12c/core/12.1.0.1.0
Agent Process ID : 8945
Parent Process ID : 8893
Agent URL : https://devbox.dev.abc.com:3872/emd/main/
Repository URL : https://gridbox.prd.abc.com:4901/empbs/upload
Started at : 2012-08-17 09:47:30
Started by user : oracle
Last Reload : (none)
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 17.52%
Collection Status : Collections enabled
Last attempted heartbeat to OMS : 2012-08-17 09:48:51
Last successful heartbeat to OMS : 2012-08-17 09:48:51
Agent is Running and Readyon OMS box:
[oracle@gridbox middleware]$ ./oms/bin/emctl status oms -details
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : gridbox.prd.abc.com
HTTP Console Port : 7789
HTTPS Console Port : 7801
HTTP Upload Port : 4890
HTTPS Upload Port : 4901
OMS is not configured with SLB or virtual hostname
Agent Upload is locked.
OMS Console is locked.
Active CA ID: 1
Console URL: https://gridbox.prd.abc.com:7801/em
Upload URL: https://gridbox.prd.abc.com:4901/empbs/upload
WLS Domain Information
Domain Name : GCDomain
Admin Server Host: gridbox.prd.abc.com
Managed Server Information
Managed Server Instance Name: EMGC_OMS1
Managed Server Instance Host: gridbox.prd.abc.comAs I mentioned earlier, gridbox and devbox can communicate with each other on necessary ports.
I would prefer to resolve this issue without having to re-install the agent.
Would appreciate some help.
Thanks. -
Software Update Point Switching is not working for some Clients
Hi there,
I found nothing similar here and I hope this is the right section.
I´m running ConfigMgr 2012 R2 where one of the Site Systems from one of the Primaries is located in an untrusted Forest in a perimeter Network. The Site System there has the MP, SUP and DB Roles. In general it works great. The Systems in that untrusted Forest
get the SCCM Agent pushed, see and can install published Software packages and receive Windows Updates. But there are a few systems where everything works, except Windows Updates.
So I had a deeper look at what is happening and found out that the SUP switching is not working for them. They always try to contact the SUP from the Primary, which they cannot reach (this is intended).
From how I understand SUP switching as described here
http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx#pi140062=1
the Windows Update Agent tries to connect to a SUP every 30 minutes and after 4 failed attempts he will try to connect to the next one until he finds one which works.
As I said before, this seems to work for most systems in the untrusted forest, but some do not make any intentions to switch the SUP.
So my next step was to find out from where the Update Agent can get the information of the available SUPs. I think they either don´t receive the information that other SUPs exist, or if the Information is there, they don´t realize that there´s an error and
make no attempt to switch.
I used the System Center Support Center to gather all Information from some of the systems with that problems (Log Files, WMI information, registry information, policies etc.) but I cannot find where SCCM or the Update Agent store the information which SUPs
are available in my environment.
I´m sure the problem is on the Systems which fail to connect to the right SUP and not in the SCCM infrastructure itself, because for most of the systems everything is working just perfect. Unfortunately in the Blog Post above there´s also no information
where this information is stored and how it is obtained by the clients. In the comments there´s even one post which describes the same problem I have here, but there was no answer. I hope someone can point me into the right direction, because I´m stuck currently.
Things I tried additionally to all the log file / WMI / registry sniffing:
Removing the Software Distribution Folder and restarting the Windows Update Agent
Removing the WindowsUpdate Registry folder in the HKLM\SOFTWARE\Policies\Windows section in the Registry and restarting the Windows Update Agent.
Tried to reset the WUAgent with wuauclt /Resetauthorization additionally to the steps above.
I also tried to manually set the WUServer and WUStatusServer Keys in the registry to the new Server, but as soon as the next Update Scan cycle runs, the value is set back to the URL of the Primary Sites SUP
Is someone having additional ideas? It seems to me older systems are more affected (which were configured for a standard WSUS before SCCM 2012 was deployed) than newer ones which were installed when SCCM was in place already. But I don´t know what else to
"reset" on those machines without reinstalling them.Thank you very much for your response. I must have missed that one by looking through numerous Logfiles. In this, there´s indeed a list of all available SUPs. So according to the LocationServices.log the machine should have a choice.
The WMI Key however, contains just one entry and this is the URL of the Primaries SUP which is not reachable in the untrusted forest. Is it OK that the WMI entry includes only one entry? If yes, what process is putting the results from the LocationServices
into WMI? It seems like the Windows Update Agent is feeded from the WMI Key then. If this is the case my problems seems to be the "communication path" between these two components.
Is this the job from the SCCM Agent, the Windows Update Agent or maybe some third component I´m not aware of? I wonder how I can fix this. -
Server 2012 R2 - WSUS - Win 7 reporting status, Win 8 not
Hi,
We have WSUS running in Server 2012 R2 standard. I have a handful of Win 7 PCs reporting status successfully. All other Win 7 and Win 8/8.1 have "not yet reported".
Looked at the windowsupdate.txt to compare a Win 7 working PC to a Win 8.1 non-working PC. Found this difference: Win7 is using
http://hccsus01:8530/ClientWebService/client.asmx and Win 8.1 is using
https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
Windows 7
2014-08-13 12:35:25:886 452 c64 Agent *************
2014-08-13 12:35:25:886 452 c64 Agent ** START ** Agent: Finding updates [CallerId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2014-08-13 12:35:25:886 452 c64 Agent *********
2014-08-13 12:35:25:886 452 c64 Agent * Online = Yes; Ignore download priority = No
2014-08-13 12:35:25:886 452 c64 Agent * Criteria = "(IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains 'a38c835c-2950-4e87-86cc-6911a52c34a3' and CategoryIDs contains 'e0789628-ce08-4437-be74-2495b842f43b')"
2014-08-13 12:35:25:886 452 c64 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-08-13 12:35:25:886 452 c64 Agent * Search Scope = {Machine}
2014-08-13 12:35:26:369 452 c64 PT +++++++++++ PT: Starting category scan +++++++++++
2014-08-13 12:35:26:369 452 c64 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://hccsus01:8530/ClientWebService/client.asmx
2014-08-13 12:35:27:085 452 c64 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-08-13 12:35:27:085 452 c64 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://hccsus01:8530/ClientWebService/client.asmx
2014-08-13 12:35:27:101 452 c64 PT WARNING: Cached cookie has expired or new PID is available
2014-08-13 12:35:27:101 452 c64 PT Initializing simple targeting cookie, clientId = f1921f0f-c420-4d01-b0f3-24c64a786102, target group = , DNS name = snbk-t13-04.hillcrest.qld.edu.au
2014-08-13 12:35:27:101 452 c64 PT Server URL =
http://hccsus01:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-08-13 12:35:27:677 452 c64 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-08-13 12:35:27:677 452 c64 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://hccsus01:8530/ClientWebService/client.asmx
2014-08-13 12:35:27:927 452 c64 Agent * Found 0 updates and 4 categories in search; evaluated appl. rules of 64 out of 80 deployed entities
2014-08-13 12:35:27:942 452 c64 Agent *********
2014-08-13 12:35:27:942 452 c64 Agent ** END ** Agent: Finding updates [CallerId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2014-08-13 12:35:27:942 452 c64 Agent *************
2014-08-13 12:35:27:942 452 c64 Report REPORT EVENT: {31C51F1C-F783-4DF0-A59D-B1DEFC6E91EF} 2014-08-13 12:35:21:646+1000 1 190 101 {ACF78076-4EB1-4AA2-B7A8-1FD495789486} 200 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2846960)
2014-08-13 12:35:27:942 452 c64 Report REPORT EVENT: {165FE843-CA58-43B1-BAFC-F3EDDBF1D624} 2014-08-13 12:35:21:662+1000 1 190 101 {1A4BBD72-9048-4E79-842F-4AD9A6114195} 200 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following update: Security Update for Windows 7 for x64-based Systems (KB2862973)
2014-08-13 12:35:27:942 452 c64 Report REPORT EVENT: {C3FAA8E2-AAF2-469C-900A-9824B6EBB36C} 2014-08-13 12:35:21:677+1000 1 190 101 {55028D69-EF9F-4949-8C2A-8FDEFBBC754F} 200 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following update: Security Update for Windows 7 for x64-based Systems (KB2871997)
2014-08-13 12:35:27:942 452 c64 Report REPORT EVENT: {A460D377-1182-4784-9E98-921FC7A7AD97} 2014-08-13 12:35:21:693+1000 1 190 101 {CED3293C-2613-41FF-BD6A-D8525504C035} 201 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following update: Security Update for Windows 7 for x64-based Systems (KB2957503)
2014-08-13 12:35:27:942 452 c64 Report REPORT EVENT: {A6D60884-0AFD-483A-A9CF-273892E5D2F1} 2014-08-13 12:35:21:693+1000 1 195 101 {6C60D018-A24B-46E0-820A-3C317F085D41} 201 80242016 AutomaticUpdates Failure Content
Install Installation Failure: Windows failed to install the following update with error 0x80242016: Cumulative Security Update for Internet Explorer 9 for Windows 7 for x64-based Systems (KB2962872).
2014-08-13 12:35:27:942 1236 5c4 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2014-08-13 12:35:27:942 1236 5c4 COMAPI - Updates found = 0
2014-08-13 12:35:27:942 1236 5c4 COMAPI ---------
2014-08-13 12:35:27:942 1236 5c4 COMAPI -- END -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2014-08-13 12:35:27:942 1236 5c4 COMAPI -------------
Windows 8.1
2014-10-07 15:33:23:740 936 186c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line Id = 70]
2014-10-07 15:33:23:740 936 bfc Agent * Caller SID for Applicability: S-1-5-18
2014-10-07 15:33:23:740 936 186c Agent *********
2014-10-07 15:33:23:740 936 bfc Agent * RegisterService is set
2014-10-07 15:33:23:740 936 186c Agent * Online = Yes; Ignore download priority = No
2014-10-07 15:33:23:741 936 186c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-10-07 15:33:23:741 936 186c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-10-07 15:33:23:741 936 186c Agent * Search Scope = {Machine & All Users}
2014-10-07 15:33:23:741 936 186c Agent * Caller SID for Applicability: S-1-5-18
2014-10-07 15:33:23:741 936 186c Agent * RegisterService is set
2014-10-07 15:33:23:741 936 bfc EP Got WSUS Client/Server URL: "http://hccsus01:8530/ClientWebService/client.asmx"
2014-10-07 15:33:23:743 936 186c EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "117cab2d-82b1-4b5a-a08c-4d62dbee7782"
2014-10-07 15:33:23:747 936 186c EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-10-07 15:33:23:755 936 186c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-10-07 15:33:23:755 936 186c PT + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL =
https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-10-07 15:33:23:756 936 186c Agent Reading cached app categories using lifetime 604800 seconds
2014-10-07 15:33:23:756 936 186c Agent Read 0 cached app categories
2014-10-07 15:33:23:756 936 186c Agent SyncUpdates adding 0 visited app categories
2014-10-07 15:33:24:021 936 186c IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 10001; does use network; is at background priority
2014-10-07 15:33:24:483 936 bfc PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-10-07 15:33:24:483 936 bfc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://hccsus01:8530/ClientWebService/client.asmx
2014-10-07 15:33:24:491 936 bfc Agent Reading cached app categories using lifetime 604800 seconds
2014-10-07 15:33:24:491 936 bfc Agent Read 0 cached app categories
2014-10-07 15:33:24:491 936 bfc Agent SyncUpdates adding 0 visited app categories
2014-10-07 15:33:25:038 936 186c IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 10001) stopped; does use network; is at background priority
2014-10-07 15:33:25:038 936 186c Agent Reading cached app categories using lifetime 604800 seconds
2014-10-07 15:33:25:038 936 186c Agent Read 0 cached app categories
2014-10-07 15:33:25:038 936 186c Agent SyncUpdates adding 0 visited app categories
2014-10-07 15:33:25:056 936 186c PT + SyncUpdates round trips: 1
2014-10-07 15:33:25:142 936 bfc IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 10002; does use network; is at background priority
2014-10-07 15:33:25:193 936 bfc IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 10002) stopped; does use network; is at background priority
2014-10-07 15:33:25:193 936 bfc Agent Reading cached app categories using lifetime 604800 seconds
2014-10-07 15:33:25:193 936 bfc Agent Read 0 cached app categories
2014-10-07 15:33:25:193 936 bfc Agent SyncUpdates adding 0 visited app categories
2014-10-07 15:33:25:221 936 bfc IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 10003; does use network; is at background priority
2014-10-07 15:33:25:235 936 bfc IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 10003) stopped; does use network; is at background priority
2014-10-07 15:33:25:235 936 bfc PT + SyncUpdates round trips: 2
2014-10-07 15:33:29:220 936 186c Agent * Added update {3F0C7A2A-336A-4D59-B38A-0C36D63B0DB2}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {EC9994ED-440F-4AFC-A0FA-CB90285A1226}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {DE323AF5-28CA-4BAB-A85B-B074001783BF}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {E44E8654-728E-49D5-A3A3-4BCFCBEF56C0}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {B7E8218C-20B2-4F04-B7E8-D3228A9B8546}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {2DDF83CB-B38E-443E-8BD9-A92D564A2851}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {E94B5DA8-C4D4-48BE-A54F-76AFB13A318F}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {B3411B62-63F7-44F2-999B-BCDFF13306B9}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {D87FA2B6-A04D-4920-92AE-7C6586F98ED4}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {00563009-B9BF-43A4-8B4E-5ACE3172912B}.2 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {D73327BD-8697-4486-9AFC-70C59746203D}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {CE28408E-E7D6-4846-A8EA-A195793146B2}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {2FA08060-64AE-4346-AC95-242853B9F810}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {ED11C6E2-F7CB-4A7F-8802-7EE5133526A9}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {9E03B879-90B1-48D6-9865-5595F857EE9F}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {A281593D-85FC-43C1-B66C-8D7031952489}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {EEEC4FAF-41B2-467D-BE87-7617505E92B6}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {57D48F6B-2C9E-468C-9BFC-4D3E090A0BC6}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {63872F34-415D-4C31-BD17-013E892F1358}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {EA8829A8-226D-409A-A17C-1A2E2BF0BF2D}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {65BC05C5-944E-4685-B961-91B8ED14E09E}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {B8AA2946-F586-47B1-A953-07D15B64446F}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {BD56C6B6-5467-42ED-A1A3-75FD751815B0}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Added update {BB57D17A-B3DC-4D85-BF6C-EE3D304D5737}.1 to search result
2014-10-07 15:33:29:220 936 186c Agent * Found 24 updates and 40 categories in search; evaluated appl. rules of 105 out of 137 deployed entities
2014-10-07 15:33:29:221 936 186c Agent *********
2014-10-07 15:33:29:221 936 186c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line Id = 70]Sorry if I am posting too much of the log file:
2014-10-23 09:34:35:207 936 1ff4 Agent *************
2014-10-23 09:34:35:207 936 1ff4 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 25]
2014-10-23 09:34:35:207 936 1ff4 Agent *********
2014-10-23 09:34:35:207 936 1ff4 Agent * Online = No; Ignore download priority = No
2014-10-23 09:34:35:207 936 1ff4 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-10-23 09:34:35:207 936 1ff4 Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-10-23 09:34:35:207 936 1ff4 Agent * Search Scope = {Current User}
2014-10-23 09:34:35:207 936 1ff4 Agent * Caller SID for Applicability: S-1-5-21-2026328644-1534031742-38565284-21128
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {C21E26AB-BFEE-425B-BD0B-C0043B81B034}.1 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {F944750C-BED6-4116-BFC4-91361F87CE97}.1 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {AE53F50B-1F53-4E10-93A2-7005AD671608}.100 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {17A599BB-6485-4405-89C1-77A260C078D9}.100 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {1E536662-7256-42FA-9373-7A009A14400B}.100 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {BB8EED48-5EB9-481D-A043-D8BE51942055}.1 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Added update {4849182B-70A4-4A3F-9FF9-054D8BCDCDDD}.1 to search result
2014-10-23 09:34:35:821 936 1ff4 Agent * Found 7 updates and 40 categories in search; evaluated appl. rules of 95 out of 158 deployed entities
2014-10-23 09:34:35:821 936 1ff4 Agent *********
2014-10-23 09:34:35:821 936 1ff4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 25]
2014-10-23 09:34:35:821 936 1ff4 Agent *************
2014-10-23 09:34:35:821 936 1ff4 Agent Removing per user update {EC9994ED-440F-4AFC-A0FA-CB90285A1226} from search result since it applies to no users
2014-10-23 09:34:35:821 936 1ff4 IdleTmr WU operation (CSearchCall::Init ID 25, operation # 179) stopped; does not use network; is at background priority
2014-10-23 09:34:35:821 936 1ff4 IdleTmr WU operation (CSearchCall::Init ID 4, operation # 153) stopped; does not use network; is at background priority
2014-10-23 09:34:35:837 936 1db0 AU >>## RESUMED ## AU: Search for updates [CallId = {FD3E1275-77A9-486E-966C-356F504EECA3} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-23 09:34:35:837 936 1db0 AU # 25 updates detected
2014-10-23 09:34:35:837 936 1db0 AU #########
2014-10-23 09:34:35:837 936 1db0 AU ## END ## AU: Search for updates [CallId = {FD3E1275-77A9-486E-966C-356F504EECA3} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-23 09:34:35:837 936 1db0 AU #############
2014-10-23 09:34:35:837 936 1db0 AU All AU searches complete.
2014-10-23 09:34:35:837 936 1db0 AU Adding timer:
2014-10-23 09:34:35:837 936 1db0 AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 20 SID {S-1-5-21-2944061896-1139597750-3336218179-1001} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-31239} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 11 SID {S-1-5-21-2026328644-1534031742-38565284-2061} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-2065} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 13 SID {S-1-5-21-2026328644-1534031742-38565284-8465} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 15 SID {S-1-5-21-2026328644-1534031742-38565284-11034} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 11 SID {S-1-5-21-2026328644-1534031742-38565284-13341} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-24355} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-2026328644-1534031742-38565284-18802} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 15 SID {S-1-5-21-2026328644-1534031742-38565284-14209} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-20353} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-10627} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 1 SID {S-1-5-21-2026328644-1534031742-38565284-22425} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 15 SID {S-1-5-21-2026328644-1534031742-38565284-24256} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 13 SID {S-1-5-21-2026328644-1534031742-38565284-13251} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:837 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-14279} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:853 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2026328644-1534031742-38565284-30666} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:853 936 1db0 AU # Publishing WNF Per user update count event Count: 11 SID {S-1-5-21-2026328644-1534031742-38565284-500} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:853 936 1db0 AU # Publishing WNF Per user update count event Count: 14 SID {S-1-5-21-2944061896-1139597750-3336218179-500} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:853 936 1db0 AU # Publishing WNF Per user update count event Count: 2 SID {S-1-5-21-2026328644-1534031742-38565284-30713} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:34:35:853 936 1db0 AU # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-2026328644-1534031742-38565284-21128} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-10-23 09:36:57:217 936 1b6c Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 1, GetLastError=2250
2014-10-23 09:36:57:999 936 1b6c Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 1, GetLastError=2250
2014-10-23 09:36:58:233 936 1b6c Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 1, GetLastError=2250
2014-10-23 09:37:05:023 936 1b6c Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 1, GetLastError=2250
2014-10-23 09:43:11:935 936 151c SLS Retrieving SLS response from server using ETAG "rb8COOsTDgXFc0zxoL6zacOQpaa9aiTtEjb2yq2aUaA=_1440"...
2014-10-23 09:43:11:998 936 151c SLS Making request with URL
HTTPS://sls.update.microsoft.com/SLS/{117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}/x64/6.3.9600.0/0?CH=454&L=en-US&P=&PT=0x4&WUA=7.9.9600.17336&AM=0&SCV=788
2014-10-23 09:43:16:243 936 151c EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-10-23 09:43:16:321 936 151c EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Reporting URL: "http://statsfe2.ws.microsoft.com/ReportingWebService/ReportingWebService.asmx"
2014-10-23 09:43:16:321 936 151c Report OpenReportingWebServiceConnection, reporting URL =
http://statsfe2.ws.microsoft.com/ReportingWebService/ReportingWebService.asmx
2014-10-23 09:43:16:321 936 151c IdleTmr WU operation (CLegacyEventUploader::HandleEvents) started; operation # 290; does use network; is at background priority
2014-10-23 09:43:16:321 936 151c Report Uploading 1 events using cached cookie.
2014-10-23 09:43:16:947 936 151c Report Reporter successfully uploaded 1 events.
2014-10-23 09:43:16:947 936 151c IdleTmr WU operation (CLegacyEventUploader::HandleEvents, operation # 290) stopped; does use network; is at background priority
2014-10-23 09:51:16:954 936 151c Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2014-10-23 09:53:16:960 936 1108 AU Earliest future timer found:
2014-10-23 09:53:16:960 936 1108 AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 09:53:17:960 936 1b6c AU ########### AU: Uninitializing Automatic Updates ###########
2014-10-23 09:53:18:960 936 1b6c WuTask Uninit WU Task Manager
2014-10-23 09:53:19:288 936 1b6c WuTask WARNING: SessionConnectHandler, could not validate and register task, error = 0x80070534
2014-10-23 09:53:19:288 936 1b6c Agent Sending shutdown notification to client
2014-10-23 09:53:19:288 936 1b6c AU Earliest future timer found:
2014-10-23 09:53:19:288 936 1b6c AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 09:53:19:491 936 1b6c AU Earliest future timer found:
2014-10-23 09:53:19:491 936 1b6c AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 09:53:19:788 936 1b6c Service *********
2014-10-23 09:53:19:788 936 1b6c Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-10-23 09:53:19:788 936 1b6c Service *************
2014-10-23 11:49:51:818 936 1dac Misc =========== Logging initialized (build: 7.9.9600.17336, tz: +1000) ===========
2014-10-23 11:49:51:818 936 1dac Misc = Process: C:\Windows\system32\svchost.exe
2014-10-23 11:49:51:818 936 1dac Misc = Module: c:\windows\system32\wuaueng.dll
2014-10-23 11:49:51:818 936 1dac Service *************
2014-10-23 11:49:51:818 936 1dac Service ** START ** Service: Service startup
2014-10-23 11:49:51:818 936 1dac Service *********
2014-10-23 11:49:51:833 936 1dac IdleTmr Non-AoAc machine. Aoac operations will be ignored.
2014-10-23 11:49:51:833 936 1dac Agent * WU client version 7.9.9600.17336
2014-10-23 11:49:51:833 936 1dac Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2014-10-23 11:49:51:833 936 1dac Agent * Base directory: C:\Windows\SoftwareDistribution
2014-10-23 11:49:51:833 936 1dac Agent * Access type: No proxy
2014-10-23 11:49:51:833 936 1dac Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2014-10-23 11:49:51:833 936 1dac Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-10-23 11:49:51:833 936 1dac Agent * Network state: Connected
2014-10-23 11:49:51:833 936 1dac Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2014-10-23 11:49:51:833 936 1dac Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-10-23 11:49:51:849 936 1dac Agent *********** Agent: Initializing global settings cache ***********
2014-10-23 11:49:51:849 936 1dac Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-10-23 11:49:51:849 936 1dac Agent * WSUS server:
http://hccsus01:8530/
2014-10-23 11:49:51:849 936 1dac Agent * WSUS status server:
http://hccsus01:8530/
2014-10-23 11:49:51:849 936 1dac Agent * Target group: (Unassigned Computers)
2014-10-23 11:49:51:849 936 1dac Agent * Windows Update access disabled: No
2014-10-23 11:49:51:849 936 1dac WuTask WuTaskManager delay initialize completed successfully..
2014-10-23 11:49:51:849 936 1dac AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 11:49:51:849 936 1dac AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2014-10-23 21:44:50, not idle-only, not network-only
2014-10-23 11:49:51:849 936 1dac AU Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2014-10-23 21:44:46, not idle-only, not network-only
2014-10-23 11:49:51:849 936 1dac AU Timer: E25CADF6-86A6-4569-BCDF-89BE66B0CA66, Expires 2014-10-24 21:33:11, not idle-only, not network-only
2014-10-23 11:49:51:849 936 1dac Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2014-10-23 11:49:51:849 936 1dac Report CWERReporter::Init succeeded
2014-10-23 11:49:51:849 936 1dac Agent *********** Agent: Initializing Windows Update Agent ***********
2014-10-23 11:49:51:849 936 1dac DnldMgr Download manager restoring 0 downloads
2014-10-23 11:49:51:849 936 1dac AU ########### AU: Initializing Automatic Updates ###########
2014-10-23 11:49:51:849 936 1dac AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2014-10-23 11:49:51:849 936 1dac AU AIR Mode is disabled
2014-10-23 11:49:51:849 936 1dac AU # Policy Driven Provider:
http://hccsus01:8530/
2014-10-23 11:49:51:849 936 1dac AU # Detection frequency: 22
2014-10-23 11:49:51:849 936 1dac AU # Approval type: Scheduled (Policy)
2014-10-23 11:49:51:849 936 1dac AU # Auto-install minor updates: Yes (User preference)
2014-10-23 11:49:51:849 936 1dac AU # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Scheduled)
2014-10-23 11:49:51:849 936 1dac AU # Will interact with non-admins (Non-admins are elevated (User preference))
2014-10-23 11:49:51:865 936 1dac AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070032
2014-10-23 11:49:51:974 936 1dac AU AU finished delayed initialization
2014-10-23 11:49:52:287 936 2340 DnldMgr Asking handlers to reconcile their sandboxes
2014-10-23 11:59:52:061 936 2338 AU Earliest future timer found:
2014-10-23 11:59:52:061 936 2338 AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 11:59:53:061 936 1dac AU ########### AU: Uninitializing Automatic Updates ###########
2014-10-23 11:59:53:123 936 1dac WuTask Uninit WU Task Manager
2014-10-23 11:59:53:232 936 1dac WuTask WARNING: SessionConnectHandler, could not validate and register task, error = 0x80070534
2014-10-23 11:59:53:232 936 1dac AU Earliest future timer found:
2014-10-23 11:59:53:232 936 1dac AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 11:59:53:311 936 1dac AU Earliest future timer found:
2014-10-23 11:59:53:311 936 1dac AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-10-23 15:43:33, not idle-only, not network-only
2014-10-23 11:59:53:436 936 1dac Service *********
2014-10-23 11:59:53:436 936 1dac Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-10-23 11:59:53:436 936 1dac Service ************* -
SCCM 2012 R2 - Distribution Point untrusted domain - Not acknowledging Network Access Account (FYI)
Hello!
Scenario
Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
errors indicate that this software can'tbe downloaded.
In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
Problem
The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
were reinstalled. A fresh install didn't detect the NAA.
Solution
After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
domains aren't approved automatically (by default).
In this case something as simple as an Approving the client fixed these issues.
The DataTransferService.log highlights the issue:
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="1" thread="3136" file="dtsjob.cpp:3501">
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
<![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="3" thread="3136" file="dtsjob.cpp:3513">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.h:166">
<![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
{38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download. Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="2" thread="3136" file="dtsjob.cpp:3652">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.cpp:3205">
<![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
thread="3136" file="netaccessaccount.cpp:288">
<![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
type="1" thread="3136" file="netaccessaccount.cpp:858">
<![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
(0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
The IIS server logs u_ex150219.log captures the request:
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 2 5 1509 2
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 4
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 3
2 x Domains: DomainA and DomainX
- Single domain forests
- No trusts between domains/forests
DomainA\PRIMARYSERVER
- Primary Site Server, MP, DP, IIS, all roles
DomainX\DP1
- Distribution Point, IIS, etc
- CCM client installedBased on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
Jason | http://blog.configmgrftw.com | @jasonsandys
Maybe you are looking for
-
Cannot delete messages from the Drafts folder in Mail.
I am running Mail 2.1.3. For some reason I am no longer able to delete draft messages from my Drafts folder. It is by no means a serious problem, just annoying! Can anyone figure this out? Thanks.
-
i need my private information like accounts and other can anyone help me out please it would help alot
-
Tab Strip Selection Screen in ALV Report
Hi All, I want to create a ALV report with TABStrip selection screen. How to proceede. Is there any necessary to create dailog program for the screens. Please advise. Thank You, ANu.
-
Help, please, with iphoto 9.4.3 crash
Hi, On a recent month-long vacation I tried to transfer images from my camera to iPhoto via a cable, but my hard drive didn't have room. I haven't been able to get iPhoto 9.4.3. to launch again, even without my camera connected. I tried one recommend
-
MY POSSIBLE FIX for Time Machine preparing for ages every hour
Like many others, i have had problems with Time Machines backups - ever since upgrading to 10.5.2. Every hour it would say 'preparing' for ages, and then, when it did finally backup, the data transfer was incredibly slow. Not to mention the amount of