question

karthikpalani-9530 avatar image
1 Vote"
karthikpalani-9530 asked saldana-msft edited

SCCM upgrade from 1709 to 1903/1909 X64 en-us

Hi All,

I have SCCM CB 2006 in which we are trying to upgrade 1709/1809 machines using Windows 10 feature updates.
Seems after deploying 1903/1909 consumer edition on 1709 machine, it trigger the status as compliant in SCCM. But no installation started on the end-user machine

Validated wuahandler, updatesdeployment, updateshandler, updatesstore etc... unable to find any error message. All looks fine

No download happen in ccmcache. Is there anything i need to verify to upgrade 1709/1809 machines. Please advice

mem-cm-generalmem-cm-osdmem-cm-updates
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

There shouldn't be any issue.
Verify you have deploy all other required updates and you may check log files in the client side.

0 Votes 0 ·
karthikpalani-9530 avatar image
0 Votes"
karthikpalani-9530 answered Amandayou-MSFT commented

Dear All,

Thanks for your support

Issue seems to be in co-management settings. Under workload, update policies are pointed to PILOT INTUNE which offloaded the update feature to MDM.

After changing back to configuration manager, Issue got fixed

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Thank you very much for the update and we're glad the problem is solved now. If you have any questions in future, we warmly welcome you to post in this forum again.

Have a nice day!

Regards,
Amanda

0 Votes 0 ·
RahulJindal-2267 avatar image
0 Votes"
RahulJindal-2267 answered

Consumer edition would mean that the devices are running home edition? Are you managing them as workgroup devices?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered RahulJindal-2267 commented

Hi @karthikpalani-9530,

After deploying the feature update, there might be seven steps to troubleshoot the common issues.

Step 1: We could check Policyagent.log. When policy is received, the following entry is logged in PolicyAgent.log:
93174-4301.png

We could check if Deployment Unique Id on the console is consistent with policy id displayed in PolicyAgent.log.
93164-4302.png

Step 2: Software update would be checked if it is required by client, kindly check UpdatesStore.log. UpdateStore.log would record updates as missing if they are required. If it is not required or has been installed by client, there is no record in this log.

Step 3: If the update is required, the content could be detected before downloading. We could refer to UpdatesDeploymentAgent.log.

Step 4: The content could be downloaded. we could refer to UpdatesHandler.log, CAS.log, and ContentTransferManager.log.

Step 5: After the download is completed, detection could be followed before installation. We could refer to UpdatesHandler.log,ScanAgent.log, UpdateStore.log, WindowsUpdate.log and WUAHandler.log.

Step 6: Software update could be installed. We could refer to Windowsupdate.log and UpdatesDeployment.log.

Step 7: After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot, and then it notifies the user if client settings are configured to allow such notification. We could refer to UpdatesDeployment.log and UpdateStore.log.

Here is an article about some detailed log screenshots.
Using log files to track the software update deployment process



If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



4301.png (20.2 KiB)
4302.png (9.4 KiB)
· 8
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Just checking in to see if there is any update. May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

Thanks and regards,
Amanda

0 Votes 0 ·

Thanks Amanda for your followup

No still the issue persist, i dont see any error in wuahandler and other updates logs. I found an warning message in policyagent.log in all user machines

94806-iiserror.jpg


94807-pol2.jpg



I followed the steps mentioned in http://blog.configmatt.com/2018/03/resolving-issues-with-user-policy.html and restarted the server too but still upgrade package is not starting to install. Even tried reinstalling the sccm client, any other suggestions please

0 Votes 0 ·
iiserror.jpg (81.4 KiB)
pol2.jpg (38.7 KiB)

Hi,

Thanks for your reply.

I research Microsoft docs, it says we increased the values of MaxFieldLength and MaxRequestBytes on the IIS server from the default of 16384 to 32768 (may vary according to ticket size) and this fixed the issue. And we could try to configure it again.

Detailed information could be referred to this article:
https://docs.microsoft.com/en-us/archive/blogs/ashishsingh/windows-authentication-for-accounts-with-large-kerberos-tickets-may-not-work-despite-having-maxtokensize-in-place

0 Votes 0 ·
Show more comments