Updates Deployment - Assignment already in progress state

Question

_{Thursday, May 16, 2019 10:12 AM}

We have created all the deployments for this month Software Updates on Client and Server. But the deployments doesn't start at the deadline. In the UpdatesDeployment.log the following line is found:

Assignment({8871DB1D-0BD0-4C1D-AA92-3E5EE4F0471C}) already in progress state (AssignmentStateDetecting). No need to evaluate UpdatesDeploymentAgent 16.05.2019 11:53:35 21388 (0x538C)

I have deleted the Update Deployment and recreated with the same result. The Updates are not showing in Software Center. 

On clients, we have no MW defined and in the Deployment, the setting to install and reboot outside the MW is set. 

I already have restarted the client, deleted the SoftwareDistribution folder and evaluated the Scan cycle multiple times. All of the assets still staying as Unknown of the deployment with the category Client Check passed/Active. 

I found another forum entry, but without any solution. Hope somebody can help me.

Kind regards Stefan Somogyi

All replies (5)

_{Tuesday, May 21, 2019 1:07 PM ✅Answered}

We could figure out the cause of this problem. We use Updates Group with many Updates included. During analyzing of the problem, we have found the following repeating lines in the DataTransfer.log:

DTS job {1888A263-A0C4-4BCF-ACD5-E09A94D7F8E5} BITS job {68CC4CA1-96E9-4030-A9CC-F1A3918007D9} failed to download source file http://{MP_Server}:80/SMS_MP/.sms_dcm?Id&DocumentId=1626f790-4b16-4758-af2c-c74984046ae2/PROPERTIES&Hash=9977A6BE450E511B5870A061D017C5FFBD5226FC0EABD412E91AC537083C2CED&Compression=zlib to destination C:\WINDOWS\CCM\CIDownloader\Staging\FEADB409-BBA2-45BD-A706-C3C7FBC277AD}_2.zip with error 0x80190194             DataTransferService       5/19/2019 12:15:07 PM 2560 (0x0A00)

I then searched with the DocumentID "1626f790-4b16-4758-af2c-c74984046ae2" the corresponding Update and have found the Update "2019-05 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 and Server 2012 R2 for x64 (KB4499408)". 

Removing this Update from the deployed Update Group, deleted the Deployment of the Group and recreating the deployment has solved the problem. The .Net Update was then separately deployed as an own Update Group.  

There must have been something with the download of the .Net Framework Updates. The exactly cause could not be found.

Kind regards Stefan Somogyi

_{Friday, May 17, 2019 6:57 AM}

Hi,

Based on your scenario, please first double check that the boundary and boundary group are configured properly.

Also, there is a good post for a similar issue, here is link for your reference, hope it helps.
https://www.linkedin.com/pulse/total-actionable-updates-0-gabriel-alicea-mcts

Best Regards,
Tina

Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, May 17, 2019 7:39 AM}

Thanks Tina for the link. It was promising. But the MinVersion was correct. I also double checked the Boundaries and Boundary Groups, there is all right defined. 

Kind regards Stefan Somogyi

_{Friday, May 17, 2019 8:43 AM}

Try checking your client policy - Software Updates and schedule deployment re-evaluation schedule. From my experience the deadlines arent always the best in kicking off before the time so may have to change the scheduling times of your deployment

Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

_{Friday, May 17, 2019 9:29 AM}

I have done that multiple times, including recreating the deployment. Special is, that some clients get the deployment and the patches was installed. But only a few (10%) and the OS are Windows 7, Windows 10 1803 and Windows 10 1809. 

Kind regards Stefan Somogyi