Forum Discussion
MicrosoftWhat's New in Windows Autopatch: September Edition
Also, under Release management, the "Date Available to Update Group" and "Target Completion Date" are showing "Invalid Date". Harman_Thind
Microsoftbernathe - I can't say for sure without knowing which tenant is yours specifically but I strongly suspect that the default Windows Autopatch policies have been modified. As mentioned in our documentation if those policies are modified devices will be rendered ineligible for management and there won't be an appropriate release schedule shown in the Release Management blade. If my assumption is correct, please raise a support ticket and we can work with you to bring your tenant back into compliance or if I'm wrong I'd love to get some more details!
As an aside, I totally understand the need for custom quality update schedules and we're working on that and a whole bunch of other cool features as a part of the service but we just aren't quite there! Stay tuned for future announcements š
Chris_Tulip thanks for the reply. I had opened a ticket with support and they replied that
āour Dev team has identified a bug with Autopatch readiness check and fixed it. The service automatically runs these checks once a day so it may take 24 hours for devices to appear in the "Ready' tab. Feel free to contact us in case of follow-up questions or queries.ā
It appears to be working now.
- Chris_TulipGreat - addresses the issue you were mentioning on the Device Registration page, glad you got it sorted out! My previous comment was regarding your second screenshot on the Release Management page - are you still seeing issues there or did that get addressed int he same ticket?
Chris_Tulip - Sorry about that, I missed the reference to the release schedule. That issue is still outstanding as is the ticket. The first step was to get systems reporting correctly and now that that is resolved we are moving onto the release schedule invalid date issue.
I'm quite certain none of the default autopatch policies have been modified (this is a brand new autopatch enablement) and when I review the "Update rings for Windows 10 and later" the last modified date matches the creation date for all. The "Feature updates for Windows 10 and later (preview)" policies creation and modified do not match but they are all the exact same for all ring groups.
Looking forward to further developments!