The available time and the deadline time are calculated based on the ADR rule run. So for available time, it should be 10th Aug+ 2 day that will take to 12th aug, deadline, 10 aug+3 days which will be 13th Aug.

Read the ADR process here https://docs.microsoft.com/en-us/mem/configmgr/sum/deploy-use/automatically-deploy-software-updates#bkmk_adr-process

Thanks,

Eswar
www.eskonr.com

Ok, thanks for the update and Your testing results are correct.

I did a closer look at the older versions (< 2203) and the recent released 2207 (op-in), i see there is clear indication on the ADR rules.

The following is old version of SCCM.

The following is the new version of SCCM (2207). you see the difference with clarity.

and the conclusion is, the deadline time is available time+ deadline days.

Thanks,
Eswar

For SSRS report, the co-management information is stored in SQL table ClientCoManagementState. You try something the SQL code something like below, but you can expand this further to get more data from various SQL views.

SELECT
sv.Netbios_Name0,
ClientCoManagementState.ComgmtEnabled,
ClientCoManagementState.CoMgmtWorkloadFlags,
ClientCoManagementState.MDMEnrolled,
ClientCoManagementState.ComgmtPolicyReceived,
ClientCoManagementState.LastMessageTime,
ClientCoManagementState.LastMessageStateID,
ClientCoManagementState.MDMRegistrationKind,
ClientCoManagementState.ScheduledEnrollTime,
ClientCoManagementState.EnrollmentBeginTime,
ClientCoManagementState.EnrollmentEndTime,
ClientCoManagementState.EnrollmentStatusCode,
ClientCoManagementState.EnrollmentErrorDetail
FROM
ClientCoManagementState
INNER JOIN v_R_System_Valid sv ON ClientCoManagementState.MachineID = sv.ResourceID

Thanks,
Eswar

DISM with cab files still valid and is documented at https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options?view=windows-11
There are multiple ways to deploy/update the drivers. You can use dell command integrated as stated https://www.dell.com/support/kbdoc/en-sg/000124139/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment
or you can use a community tool driver automation tool https://msendpointmgr.com/driver-automation-tool/

Thanks,
Eswar
www.eskonr.com

I hit this scenario couple of times and there is MS article documented on the MFA if you have CA policy created. Refer this article https://docs.microsoft.com/en-us/troubleshoot/mem/intune/troubleshoot-co-management-auto-enrolling#devices-fail-to-sync-after-auto-enrollment if you are match with this.

But can you check why the device is non-compliance and what settings are not compliant on the device?

Thanks,
Eswar
www.eskonr.com

no issues with the query syntax. it looks like you dont have any devices with the build number that you are looking for.
You can run the following SQL query if any records with the build number 19044

select top 10 * from v_gs_operating_system os where os.buildnumber0='19044'

Thanks,
Eswar
www.eskonr.com

you can try something like this, querying wmi directly

This is sample for adding the device to collection. https://eskonr.com/2022/01/how-to-add-device-to-collection-using-task-sequence-troubleshooting/

cmd /c powershell.exe -Command "&{$Me = $Env:COMPUTERNAME; Invoke-command -Computername "SCCMSERVERFQDN" -ArgumentList $Me -scriptblock {param($Me)Import-Module ConfigurationManager; cd SITECODE:; $Computer = Get-CMDevice -Name $Me; if ($Computer){Add-CMDeviceCollectionDirectMembershipRule -CollectionID 'COLLECTIONID' -ResourceId $computer.resourceid}}}"

Thanks,
Eswar
www.eskonr.com

you can try something like this http://eskonr.com/2010/01/sccm-report-for-installed-applications-excluding-software-updates/

Regards,
Eswar

some interesting thread for your information https://www.reddit.com/r/Intune/comments/na49yy/laps_in_administrative_templates_can_i_do/

Thanks,
Eswar

This looks like permission issue.
Make sure you have full administrator permissions and the scope is set to All.

Regards,
Eswar
www.eskonr.com
If the response is helpful, please click "Accept Answer" and upvote it.

if you have CA policies configured, it would be impossible for user to use work account on personal device for office 365 activation. Unless until the device meet the policies configured in CA/Intune.
OR

If your requirement is to allow the activation of office 365 proplus (Office 365 apps) on personal devices using corporate account, you will have to tweak the CA policies to bypass but this will have DLP issues doing so. There is no policy as such to allow the activation bypassing the conditional access.

Regards,
Eswar

Based on this documentation https://docs.microsoft.com/en-us/mem/configmgr/core/clients/manage/cmg/cloud-management-gateway-faq#example-2-multiple-tenants, the multi tenant is supported.

Regards,
Eswar
www.eskonr.com
If the response is helpful, please click "Accept Answer" and upvote it.

Hi,
you need a custom report to get the changes you have asked for.
Did you look at the default update compliance reports? anything useful?
if not, you will need to start creating a custom report for your requirement or hire a consultant who can help you.

Thanks,
Eswar
www.eskonr.com

when I try to the create a package with empty source files and use the command via SCCM, that process does not work out too

Did you check the execmgr.log for the status?

Thanks,
Eswar

If you need to know the version details that is available in updates and servicing node, then use the following syntax

select * from CM_UpdatePackages

Thanks,
Eswar