Updates Deployment - Assignment already in progress state

Hello,
Can anyone shed any light on what is happening during this following process? It occurs in our UpdatesDeployment.log file right after a Software Update Group has been deployed to a client. The client is healthy and can get normal application,
task sequence, etc. deployments. However, some software update deployments don't seem to get past the acknowledgement step.
Assignment {a1ce0350-5328-4519-ab93-5e0c9f563c1e} has total CI = 303
Deadline received for assignment {{a1ce0350-5328-4519-ab93-5e0c9f563c1e}}
Detection job {{D2824A10-684E-4C08-BBFA-F00140ED0117}} started for assignment {{a1ce0350-5328-4519-ab93-5e0c9f563c1e}}
Assignment {{a1ce0350-5328-4519-ab93-5e0c9f563c1e}} already in progress state (AssignmentStateDetecting). No need to evaluate
We've tracked the assignment GUID back to the deployment unique ID and can confirm that this deployment is deadlined and should be installing on clients that need some of the updates contained within. We have similar deployments that do work just fine
and don't throw the "already in progress state" message, so it isn't a universal issue that would prevent all software update deployments.
We just have several deployments in our environment that will not even appear to evaluate on our clients and I'd like to rule out that the above message is not an indication as to why. We are feeling like the client thinks something is in progress with
evaluating/downloading/installing updates from this deployment, but something is hung or broken in the SUP or WSUS somewhere.
Any thoughts?
Thank you,
Ryan

I just restarted the client to flush the client cache and re-ran the Scan Cycle so I could watch it in the ScanAgent.log/UpdatesDeployment.log files. Here's what I see...
Sources are not current
ScanAgent 5/24/2013 3:46:11 PM
3600 (0x0E10)
ScanJob({EDF944F2-83BD-42F2-A963-25D7B25E6380}): - - - - - -Locations requested for ScanJobID={EDF944F2-83BD-42F2-A963-25D7B25E6380} (LocationRequestID={1B97D959-CAEA-4A7B-9701-AE3737019D0E}), will process the scan request once locations are available.
ScanAgent 5/24/2013 3:46:12 PM
3600 (0x0E10)
Sources are not current
ScanAgent 5/24/2013 3:46:12 PM
3604 (0x0E14)
ScanJob({307E771E-A265-4E30-8ED9-8A5DADF291A9}): - - - - - -Locations requested for ScanJobID={307E771E-A265-4E30-8ED9-8A5DADF291A9} (LocationRequestID={B4C91219-3F2F-45D4-9668-4FCFD511096D}), will process the scan request once locations are available.
ScanAgent 5/24/2013 3:46:12 PM
3604 (0x0E14)
Message received: '<?xml version='1.0' ?>
<UpdateSourceMessage MessageType='ScanByUpdateSource'>
<ForceScan>TRUE</ForceScan>
<UpdateSourceIDs>
<ID>{409A9C41-D015-4A14-BB54-CE29CC557D4E}
</ID>
</UpdateSourceIDs>
</UpdateSourceMessage>'
ScanAgent
5/24/2013 3:46:30 PM
3604 (0x0E14)
*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800
ScanAgent 5/24/2013 3:46:30 PM
3604 (0x0E14)
Sources are current and valid. TTLs are however, invalid.
ScanAgent 5/24/2013 3:46:30 PM
3604 (0x0E14)
User logon system task
UpdatesDeploymentAgent
5/24/2013 3:46:31 PM
4048 (0x0FD0)
ScanJob({508932A1-1742-4395-AB81-DC1820271CAE}): - - - - - -Locations requested for ScanJobID={508932A1-1742-4395-AB81-DC1820271CAE} (LocationRequestID={65308859-0F27-462A-BF63-748EA5901321}), will process the scan request once locations are available.
ScanAgent 5/24/2013 3:46:32 PM
3604 (0x0E14)
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT START Event
UpdatesDeploymentAgent
5/24/2013 3:46:41 PM
4004 (0x0FA4)
No current service window available to run updates assignment with time required = 1
UpdatesDeploymentAgent
5/24/2013 3:46:41 PM
4004 (0x0FA4)
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT MODIFY Event
UpdatesDeploymentAgent
5/24/2013 3:46:41 PM
3708 (0x0E7C)
No current service window available to run updates assignment with time required = 1
UpdatesDeploymentAgent
5/24/2013 3:46:41 PM
3708 (0x0E7C)
*****WSUSLocationUpdate received for location request guid={65308859-0F27-462A-BF63-748EA5901321}
ScanAgent 5/24/2013 3:46:43 PM
4048 (0x0FD0)
Sources are current and valid. TTLs are however, invalid.
ScanAgent 5/24/2013 3:46:43 PM
4004 (0x0FA4)
ScanJob({508932A1-1742-4395-AB81-DC1820271CAE}): Performing Full Scan.
ScanAgent 5/24/2013 3:46:43 PM
4004 (0x0FA4)
ScanJob({508932A1-1742-4395-AB81-DC1820271CAE}): Scan Succeeded, Resetting Source to Current and TTLs to Valid
ScanAgent 5/24/2013 3:47:00 PM
4048 (0x0FD0)
ScanJob({508932A1-1742-4395-AB81-DC1820271CAE}): CScanJob::OnScanComplete - Scan completed successfully, ScanType=1
ScanAgent 5/24/2013 3:47:00 PM
4048 (0x0FD0)
ScanJob({508932A1-1742-4395-AB81-DC1820271CAE}): CScanJobManager::OnScanComplete -ScanJob is completed.
ScanAgent 5/24/2013 3:47:00 PM
4048 (0x0FD0)
ScanJob({508932A1-1742-4395-AB81-DC1820271CAE}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...
ScanAgent 5/24/2013 3:47:00 PM
4048 (0x0FD0)
- - Calling back to client on Scan request complete...
ScanAgent 5/24/2013 3:47:00 PM
4048 (0x0FD0)
CScanAgent::ScanComplete- Scan completion received.
ScanAgent 5/24/2013 3:47:00 PM
4048 (0x0FD0)
EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0
UpdatesDeploymentAgent
5/24/2013 3:47:09 PM
3580 (0x0DFC)
My hunch is that the line "No current service window available to run updates assignment with time required = 1" may be the culprit but I'm not sure. I'm just not certain what this means exactly. I want to say from other forum posts this has
to do with maintenance windows, but I had this client's collection set to two hours from 3am-5am. I just reset the maintenance window on the client's collection to 23 hours of every day for testing purposes, but I didn't have a successful test. I
had the same log results, but maybe I didn't wait long enough between the change and the test.

Similar Messages

Software Update Deployment - Job error (0x80072f0c) received for assignment

I'm deploying a software update to my test clients but half of them failed with error below;
UpdateStore.log -
Failed to refresh sync message. Error = 0x87d00310.
WUAHandler.log
OnSearchComplete - Failed to end search job. Error = 0x80072f0c.
Scan failed with error = 0x80072f0c.
Updates Deployment
Job error (0x80072f0c) received for assignment ({0F2CA22F-BB7A-4ED8-9794-15AB24B83E09}) action
Do you have any recommendation ?

Since no one has replied to this post, I recommend that you contact Microsoft Support (CSS) directly, they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Validation Error when updating Feature work item to completed state?

We are on the latest version of TFS 2013 and have customized process templates based off of the Scrum template.
We have a custom workflow for the Feature work item type. I get an error when trying to update the state to custom done state of "Prod Deployment Successful". The error I receive is below:
TF237165: Team Foundation could not update the work item because of a validation error on the server etc etc.
I have TFS Admin rights as well as project and project collection Admin rights.
Custom States:
Planned
Canceled
On Hold
In Progress
Ready For QA
QA Deployment Failed
QA Deployment Successful
Ready For Stage
Stage Deployment Failed
Stage Deployment Successful
Ready For Prod
Prod Deployment Failed
Prod Deployment Successful
Custom Workflow:
" " TO    Planned
Planned TO Canceled
Planned TO On Hold
Planned TO In Progress
In Progress TO On Hold
In Progress TO Ready For QA
On Hold TO In Progress
Ready For QA TO QA Deployment Failed
Ready For QA TO QA Deployment Successful
QA Deployment Failed TO Ready For QA
QA Deployment Failed TO In Progress
QA Deployment Successful TO Ready For Stage
QA Deployment Successful TO Ready For Prod
Ready For Stage TO Stage Deployment Failed
Ready For Stage TO Stage Deployment Successful
Stage Deployment Failed TO Ready For Stage
Stage Deployment Failed TO In Progress
Stage Deployment Successful TO Ready For Prod
Ready For Prod TO Prod Deployment Failed
Ready For Prod TO Prod Deployment Successful
Prod Deployment Failed TO Ready For Prod
Prod Deployment Failed TO In Progress
I have also updated the Process Configuration file to map the states to the meta states so I can show the custom states on the Feature board. The section in the process configuration file that relates to Feature is below:
<States>
        <State type="Proposed" value="Planned" />
        <State type="InProgress" value="Canceled" />
       <State type="InProgress" value="On Hold" />
       <State type="InProgress" value="In Progress" />
       <State type="InProgress" value="Ready For QA" />
       <State type="InProgress" value="QA Deployment Failed" />
       <State type="InProgress" value="QA Deployment Successful" />
       <State type="InProgress" value="Ready For Stage" />
       <State type="InProgress" value="Stage Deployment Failed" />
       <State type="InProgress" value="Stage Deployment Successful" />
       <State type="InProgress" value="Ready For Prod" />
       <State type="InProgress" value="Prod Deployment Failed" />
        <State type="Complete" value="Prod Deployment Successful" />
      </States>
The error ONLY happens when I try to update a Feature state to "Prod Deployment Successful". I have looked at other posts and searched the internet and have found no help for my exact issue in TFS 2013. For some
reason, I can't update the state from "Ready For Prod" to "Prod Deployment Successful". Does anyone have any ideas of what could be wrong or causing my issue?
Thanks in advance!

I finally figured out my issue and fixed it.
I had to update a reference name in the WIT xml file to Common.BusinessValue instead of Closed.

Parent fail/aborted. Transaction is already in progress.

I cant patch my SLES11 server, i've added the installationmedia from
zypper and can install and modify my packages from zypper install etc.
But I cant patch this server. I've rebooted and ONLY assign
SLES11-Updates bundle to the machine. I tried restart novell-zmd but it
doesnt work patching....
Can someone help me out?
04 Feb 2010 14:42:14 INFO BundleManager Executing preprepare
scripts for patch-slessp0-yast2-instserver_SLES11-Updates-1
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
A transaction is already in progress
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO BundleManager Bundle preparation
failed: A transaction is already in progress
04 Feb 2010 14:42:14 ERROR ScheduledActionsModule
Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR:
Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR
Novell.Zenworks.Zmd.Public.ZenException: Failed to prepare bundles for
install: A transaction is already in progress
04 Feb 2010 14:42:14 INFO BundleManager Executing preprepare
scripts for patch-slessp0-yast2-ldap-client_SLES11-Updates-1
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
A transaction is already in progress
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO BundleManager Bundle preparation
failed: A transaction is already in progress
04 Feb 2010 14:42:14 ERROR ScheduledActionsModule
Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR:
Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR
Novell.Zenworks.Zmd.Public.ZenException: Failed to prepare bundles for
install: A transaction is already in progress
04 Feb 2010 14:42:14 INFO BundleManager Executing preprepare
scripts for patch-slessp0-yast2-ldap-server_SLES11-Updates-1
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
A transaction is already in progress
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO Progress Progress.Stop Message:
Parent failed/aborted
04 Feb 2010 14:42:14 INFO BundleManager Bundle preparation
failed: A transaction is already in progress
04 Feb 2010 14:42:14 ERROR ScheduledActionsModule
Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR:
Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR
Novell.Zenworks.Zmd.Public.ZenException: Failed to prepare bundles for
install: A transaction is already in progress
Technical Consultant
Kerfi AB Stockholm Sweden

Anders,
one of this should solve that problem:
# rug restart --clean --force
or
# rug shutdown --force
# rm /var/lib/zmd/zmd.db
# rczmd start
Rainer

Software Update Deployment - Compliance Status = Unknown - Client Check passed/active

Hi,
First I want to say, that I found many Forum-Posts which describes a similar issue, but it is not exactly my issue...
I have a ADR (Auto Deployment Rule) which creates every Month a Windows Update Package, and deploys it. The Deployment starts from a custom day, and ends 14 days later (Deadline). Now I have the issue, that the compliance chek in the deployment status is
"reseted" every day (at 0:00) - (at least after the Deadline!)... The Compliance Check starts every day at 0:00 and then tries to reach every Computer again! So if the Computer-object is powered on and responding, it turns over to compliant (because
it is already compliant - the Windows Update Installation works fine...). But if the Computer is not powered on / not responding the next day, it turns over to "Unknown - Client check passed/active" instead of staying in the Status "compliant"
until it is powered on / respinding again, then it changes over to compliant again... Why is that?
Is there a issue with the Client Settings?:
- Software Update Scan (every day)
- Software Update Re-Evaluation (every day)
- Compliance Settings (every day at 0:00) -> but is this not for the Configuration Baselines?
any other ideas?
Patrik

As soon as the computer get the Software Update configuration items, it will start compliance checking, then send the compliance check result to MP.
From your description, the powered on computers sent the state message to the MP when they got the deployment policy. And the frequency of Status Summarizers of updates deployment for a deployment that was modified in the last
30 days is 60 minutes. Because the site server had not recieved the state message from the powered off computers so that the compliance state was changed to Unknown.
Juke Chou
TechNet Community Support

Change Software Updates deployment priority

Hi
We use SCCM 2012 R2 CU2.
whenever a new client is being installed and registered it gets its policies and deployments.
our problem is that there are many software updates that being deployed and it takes a very long time until they finish their installation.
while what is more important for us is the clients to get software deployments
before the software updates.
I know I can change packages priority but as I understand - it only changes the priority between the software packages.
is there any way to make the software deployments to be installed before the software updates for new clients?
even if there's no build-in solution, I'd be happy to get a friendly workaround.
I thought about auto-adding the clients to a software update deployment collection only after all the packages are being deployed, but maybe some of you can come up with something better
thanks!

You can't prioritize in policy for a client. The first policy that arrives is the first that's being served..
If you're talking about the first thing after the OS deployment, then I would try to update my clients completely during the deployment already. That would solve your problem already. In that same scenario, you could also think about installing
computer or user targetted applications during the task sequence. For examples about both scenario's see:
Computer-targeted:
http://www.petervanderwoude.nl/post/install-computer-targeted-application-during-os-deployment-via-powershell-and-configmgr-2012/;
User-targeted:
http://www.petervanderwoude.nl/post/install-user-targeted-applications-during-os-deployment-via-powershell-and-configmgr-2012/.
If you're not talking about an OS deployment, your only option is indeed to add the clients later to the software update collection(s). In that case you could also try to automate it via PowerShell by using the
Add-CMDeviceCollectionDirectMembershipRule.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Most Service Requests are in a In Progress state??

I started looking through all our SR and about 80% of them are "In Progress". Some go back almost a year. Looks like the Completed and Closed links were greyed out so they just left them like that.
One user called me about today saying the Complete and Closed links were greyed out. I was able to force it to completion with the following PS command:
cd C:\program files\Microsoft System Center 2012\Service Manager\Powershell
import-module .\System.Center.Service.Manager.psd1
(get-scsmclass -name "System.WorkItem.ServiceRequest" | get-scsmclassinstance) | where {$_.ID -eq 'SR11157'} | %{ $_.Status = "Completed" ; $_ } | update-scsmclassinstance
What is the normal life cycle of a SR? I noticed on many of the SR's, the Activity tab is blank. Why would a SR stay in the "In Progress" state with the Completed and Close links greyed out. I checked the status on the workflows and did not see
any errors.

all SRs should be created as new. The out of the box workflows will run and examine the activities.
if there are no activities, the status is set to Submitted, and the SR waits for an analyst to act upon it.
If there are activities, the status is set to In Progress, and the first activity is set to In Progress.
When an activity is added the SR workflows will again examine the SR. If the status is Submitted, and an activity was added, the SR will be set in progress, and the first activity will be set in progress
If the status is In Progress, and an activity was completed, the next activity will be set in progress. if it was the last activity was completed, the SR will be set completed.
If the status is In Progress, and an activity was Failed, the SR status will be set failed.
If the SR status is changed to Hold, then each activity will be set to hold.
an analyst can complete SRs that are in the Submitted status.
an analyst can close SRs that are in the completed status.
consider a visual:

How to calculate the compliance for an software update deployment

Hi All,
I am trying to find as how do we calculate the compliance for an software update deployment.
Scenario, We have about 4000 machine in the domain. but we have some stale records in the domain which is about 1200. The AD cleanup for the stale records is planned for sometime in March.
So total number of machines in a collection (including the stale machines) are 5200.
The current compliance of that deployment shows the following status:
Complaint : 1156
In Progress : 1724
Error : 38
Unknown : 2462
And in the unknown, we have :
Client check failed/Active: 2
Client check failed/Inactive: 6
Client check passed/Active: 732
Client check passed/Inactive: 1722
Can you please suggest in understanding the formula that should be followed to get the compliance.

Your Compliancy, should be based solely off of the number of computers within CM12.
There are no “if”, “and” or “but” able it. This is the only way to truly and reliably provide numbers to management.
Again it should be very simple calculation:
(Total outstanding Security SU, Total outstanding
Critical SU, Total outstand Service packs, Total outstand Update Rollups, Total outstand Updates, Total outstand Definition Updates, Total outstand tools, Total outstand Feature packs) Vs Total applied SU (all Classifications)
Or
Total # of 100% patched PCs vs Total # of PCs as seen by CM12.
If you use any other calculation then you MUST include a disclaimer that you are filtering out computers because they might be invalid. Or you MUST define exactly how you are calculating the number. Therefore any compliancy rate that your calculate maybe
invalid too or at least it will change once you clean up AD.
I will never hide low compliancy numbers to management, I will always show it to them.
In many case I will ask to give a presentation to Management to explain why the numbers are so low.
Provide them with a list of action items that need to be done in order to bring up the number to more reasonable level. I also set their expectation on what a reasonable level is.
100% is unachievable; there is no exception to this!
95-99% Very excellent but expect to spend lots of $$$s to obtain these percentages.
90-95% is really, really, good; expect to spend $$s in this range.
85-89% is good; expect to set strict procedures
81-84 is ok but you could do better
Below 80% is bad
In your case, I would start by saying AD is dirty and need to be clean up, this has been schedule for March 2015. I would follow up this to say, in order to keep AD clean the follow procedures need to be define / updated / followed. You should also define
exactly what you are doing to ensure that all computers are management by CM12.
IMO these is no simple answer of this.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Windows Update Agent rebooting systems after Software Update deployment

I have a software update deployment that is configured to install software updates on a collection of servers at 4:00 AM with a suppressed reboot. The updates get deployed and no reboot occurs as expected. Then ~8 hours later WUA starts up and the
servers get rebooted.
There is a maintenance window applied to the collection from 4:00 AM to 6:00 AM to allow the updates to install.
I've read a few forum and blog posts on this issue and have implemented some settings via GPO, but the reboots are still occurring. The settings that were applied are referenced in the link below.
https://support.microsoft.com/kb/2476479?wa=wsignin1.0
Here is a snippet from the WindowsUpdate.log:
2014-10-22 12:00:26:153 1428 8a88 AU Received AU Resume timeout
2014-10-22 12:00:26:153 1428 8a88 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
2014-10-22 12:00:26:153 1428 8a88 AU Can not perform non-interactive scan if AU is interactive-only
2014-10-22 12:02:08:512 1428 8a88 AU AU received policy change subscription event
2014-10-22 12:16:43:463 1428 8a88 AU ########### AU: Uninitializing Automatic Updates ###########
2014-10-22 12:16:43:479 1428 8a88 WuTask Uninit WU Task Manager
2014-10-22 12:16:43:697 1428 8a88 Service *********
2014-10-22 12:16:43:697 1428 8a88 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-10-22 12:16:43:697 1428 8a88 Service *************
2014-10-22 12:19:29:728 1428 e584 Misc =========== Logging initialized (build: 7.8.9200.16604, tz: -0400) ===========
2014-10-22 12:19:29:728 1428 e584 Misc   = Process: C:\WINDOWS\system32\svchost.exe
2014-10-22 12:19:29:728 1428 e584 Misc   = Module: c:\windows\system32\wuaueng.dll
2014-10-22 12:19:29:728 1428 e584 Service *************
2014-10-22 12:19:29:728 1428 e584 Service ** START ** Service: Service startup
2014-10-22 12:19:29:728 1428 e584 Service *********
2014-10-22 12:19:29:744 1428 e584 Agent   * WU client version 7.8.9200.16604
2014-10-22 12:19:29:744 1428 e584 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2014-10-22 12:19:29:744 1428 e584 Agent   * Access type: No proxy
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2014-10-22 12:19:29:744 1428 e584 Agent   * Network state: Connected
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2014-10-22 12:19:29:791 1428 e584 Agent *********** Agent: Initializing global settings cache ***********
2014-10-22 12:19:29:791 1428 e584 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS server:
http://Internal-WSUS.Domain:8530
2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS status server:
http://Internal-WSUS.Domain:8530
2014-10-22 12:19:29:791 1428 e584 Agent   * Target group: (Unassigned Computers)
2014-10-22 12:19:29:791 1428 e584 Agent   * Windows Update access disabled: No
2014-10-22 12:19:29:791 1428 e584 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2014-10-22 12:19:29:806 1428 e584 WuTask WuTaskManager delay initialize completed successfully..
2014-10-22 12:19:29:822 1428 e584 Report CWERReporter::Init succeeded
2014-10-22 12:19:29:822 1428 e584 Agent *********** Agent: Initializing Windows Update Agent ***********
2014-10-22 12:19:29:822 1428 e584 DnldMgr Download manager restoring 0 downloads
2014-10-22 12:19:29:838 1428 e584 AU ########### AU: Initializing Automatic Updates ###########
2014-10-22 12:19:29:838 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
2014-10-22 12:19:29:838 1428 e584 AU AIR Mode is disabled
2014-10-22 12:19:29:838 1428 e584 AU   # Policy Driven Provider:
http://Internal-WSUS.Domain:8530
2014-10-22 12:19:29:838 1428 e584 AU   # Detection frequency: 22
2014-10-22 12:19:29:838 1428 e584 AU   # Approval type: Disabled (User preference)
2014-10-22 12:19:29:838 1428 e584 AU   # Auto-install minor updates: No (User preference)
2014-10-22 12:19:29:838 1428 e584 AU   # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Pre-install notify)
2014-10-22 12:19:29:838 1428 e584 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2014-10-22 12:19:29:838 1428 e584 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2014-10-22 12:19:29:853 1428 e584 AU AU finished delayed initialization
2014-10-22 12:19:29:884 1428 e584 AU #############
2014-10-22 12:19:29:884 1428 e584 AU ## START ## AU: Search for updates
2014-10-22 12:19:29:884 1428 e584 AU #########
2014-10-22 12:19:29:884 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
2014-10-22 12:19:30:416 1428 e584 Report *********** Report: Initializing static reporting data ***********
2014-10-22 12:19:30:416 1428 e584 Report   * OS Version = 6.2.9200.0.0.197008
2014-10-22 12:19:30:416 1428 e584 Report   * OS Product Type = 0x00000008
2014-10-22 12:19:30:416 1428 e584 Report   * Computer Brand = HP
2014-10-22 12:19:30:416 1428 e584 Report   * Computer Model = ProLiant BL460c Gen8
2014-10-22 12:19:30:416 1428 e584 Report   * Platform Role = 1
2014-10-22 12:19:30:416 1428 e584 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Revision = I31
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Name = Default System BIOS
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Release Date = 2014-02-10T00:00:00
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Sku Number = 641016-B21
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Vendor = HP
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Family = ProLiant
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Major Release = 255
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Minor Release = 255
2014-10-22 12:19:30:431 1428 e584 Report   * Locale ID = 1033
2014-10-22 12:19:30:431 1428 e584 AU <<## SUBMITTED ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:431 1428 dae0 Agent *************
2014-10-22 12:19:30:431 1428 dae0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:30:431 1428 dae0 Agent *********
2014-10-22 12:19:30:431 1428 dae0 Agent   * Online = No; Ignore download priority = No
2014-10-22 12:19:30:431 1428 dae0 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-22 12:19:30:431 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-10-22 12:19:30:431 1428 dae0 Agent   * Search Scope = {Machine & All Users}
2014-10-22 12:19:30:431 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
2014-10-22 12:19:30:494 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
2014-10-22 12:19:30:494 1428 dae0 Agent *********
2014-10-22 12:19:30:494 1428 dae0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:30:494 1428 dae0 Agent *************
2014-10-22 12:19:30:509 1428 d158 AU >>## RESUMED ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:509 1428 d158 AU   # 0 updates detected
2014-10-22 12:19:30:509 1428 d158 AU #########
2014-10-22 12:19:30:509 1428 d158 AU ## END ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:509 1428 d158 AU #############
2014-10-22 12:19:30:509 1428 d158 AU All AU searches complete.
2014-10-22 12:19:30:525 1428 e584 AU #############
2014-10-22 12:19:30:525 1428 e584 AU ## START ## AU: Search for updates
2014-10-22 12:19:30:525 1428 e584 AU #########
2014-10-22 12:19:30:525 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
2014-10-22 12:19:30:525 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
2014-10-22 12:19:30:525 1428 e584 AU <<## SUBMITTED ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:525 1428 dae0 Agent *************
2014-10-22 12:19:30:525 1428 dae0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:30:525 1428 dae0 Agent *********
2014-10-22 12:19:30:525 1428 dae0 Agent   * Online = Yes; Ignore download priority = No
2014-10-22 12:19:30:525 1428 dae0 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-22 12:19:30:525 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-10-22 12:19:30:525 1428 dae0 Agent   * Search Scope = {Machine & All Users}
2014-10-22 12:19:30:525 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
2014-10-22 12:19:30:525 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2014-10-22 12:19:30:541 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:541 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:556 1428 dae0 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab"
2014-10-22 12:19:30:588 1428 dae0 Agent Checking for updated auth cab for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 at
http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab
2014-10-22 12:19:30:588 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
2014-10-22 12:19:30:603 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:603 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:775 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
2014-10-22 12:19:30:791 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:791 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:791 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
2014-10-22 12:19:30:806 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:806 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:822 1428 dae0 EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-10-22 12:19:30:978 1428 dae0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-10-22 12:19:30:978 1428 dae0 PT   + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL =
https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-10-22 12:19:31:025 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
2014-10-22 12:19:31:025 1428 dae0 Agent *********
2014-10-22 12:19:31:025 1428 dae0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:31:025 1428 dae0 Agent *************
2014-10-22 12:19:31:025 1428 d158 AU >>## RESUMED ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:31:025 1428 d158 AU   # 0 updates detected
2014-10-22 12:19:31:025 1428 d158 AU #########
2014-10-22 12:19:31:025 1428 d158 AU ## END ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:31:025 1428 d158 AU #############
2014-10-22 12:19:31:025 1428 d158 AU All AU searches complete.
2014-10-22 12:19:31:025 1428 d158 AU AU setting next detection timeout to 2014-10-23 14:19:28
2014-10-22 12:19:36:025 1428 e214 Report REPORT EVENT: {E04012FD-8FFD-4259-96D5-A5A34127F0A0} 2014-10-22 12:19:31:025-0400 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2014-10-22 12:19:36:025 1428 e214 Report CWERReporter finishing event handling. (00000000)
2014-10-22 12:29:29:914 1428 e584 AU AU invoking RebootSystem (OnRebootNow)
2014-10-22 12:29:30:055 1428 e584 AU Allowing auto firmware installs at next shutdown
2014-10-22 12:29:30:102 1428 e584 Misc WARNING: SUS Client is rebooting system.
2014-10-22 12:29:30:102 1428 e584 AU AU invoking RebootSystem (OnRebootRetry)
2014-10-22 12:29:30:367 1428 e584 Shutdwn Checking to see whether install at shutdown is appropriate
2014-10-22 12:29:30:367 1428 e584 Shutdwn user declined update at shutdown
2014-10-22 12:29:30:367 1428 e584 AU AU initiates service shutdown
2014-10-22 12:29:30:367 1428 e584 AU ########### AU: Uninitializing Automatic Updates ###########
2014-10-22 12:29:30:399 1428 e584 WuTask Uninit WU Task Manager
2014-10-22 12:29:30:445 1428 e584 Agent Sending shutdown notification to client
2014-10-22 12:29:30:445 5788 8084 COMAPI WARNING: Received service shutdown/self-update notification.
2014-10-22 12:29:30:461 1428 e584 Report CWERReporter finishing event handling. (00000000)
2014-10-22 12:29:30:539 1428 e584 Service *********
2014-10-22 12:29:30:539 1428 e584 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-10-22 12:29:30:539 1428 e584 Service *************
Any assistance is appreciated.
-Tim

Hi,
Any update?
Best Regards,
Joyce
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.

Migrate To Mac "Installation already in progress"

I got a Mac Book Air yesterday - and just tried to transfer all my files from my Sony Vaio just now. After restarting and updating my computer it still says that I am already installing the program which I am not.
"Windows Migration Assistant: Another installation is already in progress. You must complete that installation before continuing this one."

I was in safe mode with networking and now got this message. Is it because I'm in safe mode?
That's my guess. It tells us the Windows Installer is being used. That service is apparently not loaded in Safe Mode. See KB2642495. You've never seen that message after booting in normal mode, right?
Do the System Restore as far back as you can.
Also, uninstall the Norton stuff. Tear it out by the roots.
Download and run the Norton Removal Tool to uninstall your Norton product
Replace it for now with Microsoft's program, which interferes with nothing.
Microsoft Security Essentials
-Jerry

Software Updates Deployment Evaluation.

Hi,
I would like to get some clarification around the Software Updates Deployment Eval. cycle. (SCCM R2 CU3)
Example scenario:
I have a Software Update Group that contains 200 updates. This SUG includes updates that are prerequisites for other updates in the same SUG. So, when scanning occurs. Only one of these updates are at that particular time considered applicable.
The software update deployment deadline is reached. The update is installed, as expected. The then agent reports compliance against the update deployment.
Then comes the Software Update Scan schedule, when a new scan is made against the SUP more updates are now detected as required because of the previously installed update - from the same SUG which are deployed.
This leaves me in a situation where the agent is compliant against the Software Update deployment and non-compliant in regards to the actual Software Update Group.
I can of course just hit the schedule for Software Update Deployment Evaluation manually on the agent or simply do something (adding an update or whatever) that modifies the actual software updates deployment policy. This would in turn cause a new evaluation
to occur at the client.
Bottom line. Is my conclusion correct or have i missed something here?
If i'm correct, a good thing would be to add scheduling options available for the actual "software update deployment evaluation".
That would really come in handy in situations like above scenario.
Br,
Chris

The next scheduled scan cycle will pick up the newly applicable but non-compliant updates in the deployment.
However, note that update compliance at the client level is done against the entire update catalog as this is actually done by the Windows Update Agent (WUA) which knows nothing about ConfigMgr. Thus, the fact that an update is in a deployment or not is
completely irrelevant as far as compliance and compliance reporting goes (which is part of the reason why compliance reporting in ConfigMgr is tricky).
Updating the policy of an update deployment will kick off a scan cycle (just like creating a new deployment will) on the clients which is why you are probably seeing this behavior as addressing the scenario.
Jason | http://blog.configmgrftw.com | @jasonsandys
Thanks Jason,
What you are describing exactly matches the point I’m trying to make here. There is no correlation what so ever between update scans and actual software update deployments. The logic just isn't there. Which is a logic that is lacking
– in my opinion.
I really do think there is room for improvement here.
Case:
A customer wants to minimize the spread of reboots (a maint. window overnight should be sufficient for the agent to get the server fully up to date). The admin – who also wants to minimize effort in regards to worrying about MS bundling\prereq
requirements – simply wants it all to be taken care of by the updates deployment agent.
Example:
Software update deployment contains required updates as well as updates that will not be detected as required - until the deployment has been run – and a new update scan cycle has taken place.
The server reboots and updates deployment agent says all is fine – with regards to the deployment in it's current state, of course.
But it's not.
The server then issues a new scan (maybe 4 hours later and way behind the end of the maint. window) according to the software updates scan schedule, and suddenly 10 more updates are applicable, but still within the same deployment.
What happens? Nothing, sadly. Next maint. window? Nothing.
Not even a (client agent set – and scheduled) software update deployment re-eval takes care of this since – according to my findings – the deployment will never really be evaluated against again without administrative intervention.
Suggestion:
Whenever a software update deployment has been run, succeeded and passed the "after reboot" detectjob. Initiate a new evaluation of this deployment in full – of course including a pre-eval software updates scan. Just add
a few steps to the logic of updates deployment.
Evaluate.
Apply.
Initiate a new scan.
Re-Evaluate.
Apply again (if needed)
Reboot
Initiate a new scan.
Re-evaluate
Isn’t this the way WAUA has always worked? Why shouldn’t this method be adopted here as well? Why should ConfigMgr not honour the procedure?
Result:
Administrative relieve. Since I know that a software update deployment will always do the job, in full. No need for manual triggers or policy modifications.
Caveats:
I do realize the fact that – if this would be the scenario - the admin sometimes will not be aware of what might happen during the nightly maint. window since he cannot solely rely on compliance data.
Anyways:
This should at least be a deployment option in future releases.
"Force rescan and deployment re-evaluation after first run." Simple.
Would make life easier and keep the spread of reboots concentrated to one night and to a minimum. (Given the appropriate length of maint. windows of course)
Consider things like KB2919355 and how WUAU agent handles that against Windows Update.
Br,
Chris

App Store not letting me download free games or even let me update apps I already have!

Ok, so I tried purchasing a item in a game I have (not knowing how much I have in my bank account). App Store denied it so I'm like ok whatever I don't care. Well now whenever I try to download free apps or eve. Update apps I already have the store makes me sign in, and wants me to update my billing information because there was an error with my last purchase because it didn't go through. Ok why is it doing this? It didn't go through I don't care I just wanna update my apps and be able to download free Apps without having to update my information then apple charging for something I don't want anymore.... Can anyone tell me how to fix this? I already tried removing the card! I don't have a "none" option when I try to remove it so... Yeah

You must have a valid form of payment on your account even for updates and free apps.

Error message: can't install update, firefox is already running, but it is not

second request
an auto update failed a few days ago and now everytime I open FF I get an error message that says can't install update, firefox is already running, but it is not!
the parent.lock file is not open when FF is closed
in addition to this message, a box opens asking looking for a file
Help!

hi
I had the same problem (update failed for normal user, update worked for administrator, but then normal user still got asked about installing the update even though it was already done).
Following the advice on http://kb.mozillazine.org/Software_update#Software_Update_not_working_properly worked for me, in particular to remove the update-related xml files.
good luck
kris

Error while updating the Assignment details using 'hr_assignment_api'

An exception message is thrown while updating the assignment details through 'hr_assignment_api.update_emp_asg'.
The message is 'ORA-20001: HR_FLEX_VALUE_MISSING: N, COLUMN, ASS_ATTRIBUTE6, N, PROMPT'.
Even though a valid value is being passed to the segement,the error is thrown.
I have tested the API in one instance and it is working fine. Recently I have migrated the codes to nother instance and encountered this error. The only difference is that in the newer instance, the segment is mandatory.
One interesting thing is that, When I update the Assignment through application it is successfully saving the record. Then if I use the API to correct the Assignment, it is working fine. The API is not able to update only when the mandatory segment is null.
Please help
Thanks in advance
Kumar

Pl post details of OS, database and EBS versions, along with HR RUP level. It may be a bug, as outlined in MOS Doc 429169.1 (When Calling the Assignment API To Update Position, It Errors in Required Segment)
HTH
Srini

Notification: "The report deployment process in in progress"

Hi All,
We're implementing Service manager and we have an issue with the reporting management packs.
Upon opening the Service manager console we're getting the error:
"The report deployment process in in progress. To determine when management pack deployment is complete, see the procedure in the service manager deployment guide. You can view reports after management packs have been deployed."
I've consulted the guide and the MPsyncjobs tasks runs and completes in under 1 minute, the Get-SCDWJob command returns the following:
BatchId Name Status CategoryName StartTime
6490 MPSyncJob Not Started Synchronization
6482 DWMaintenance Not Started Maintenance
6488 Load.Common Not Started Load
6484 Load.OMDWDataMart Not Started Load
6485 Load.CMDWDataMart Not Started Load
6492 Extract_DW_SBCSMDW Not Started Extract
6486 Transform.Common Not Started Transform
In the GUI under "data warehouse jobs" the job MPSyncJob is Not started but in the details section under Job Progress it's stuck at 48/48 and looks like it's running.
I'm new to System Center so if anyone could point me into the right direction to work out how to get reporting working that would be great.
Thanks.

Modified the required files as per the specifiacation in both xml and properties files .
Deployed the service successfully.
But problem is it's not picking the file from the source server.
Please guide me how to test the service...in the bpel after deploying the service...
how the check the service log ?

Updates Deployment - Assignment already in progress state

Similar Messages

Maybe you are looking for