Ruhul Azad

Recently, we have encountered some issues with devices that were being updated to Windows 11 24H2. These issues include the removal of wallpaper, Chrome crashes, device slowness, and VPN connectivity problems. In some cases, rolling back to 23H2 has resolved the issues. However, it should be noted that after the rollback, other issues such as Chrome crashes have emerged. Does anyone have any updates ?

I would recommend WS1 as we have been managing all our Windows devices through WS1 only. You will get more details on below article https://brookspeppin.com/2022/10/17/intune-vs-workspace-one-15-pros-and-cons-2022-edition/

I would like to suggest the creation of a Restriction profile for OS Updates, which will allow us to set Delay OS Updates (Days) from 1 to 90 days according to your testing requirements. By selecting the appropriate number of days, you will be able to allocate sufficient time for thorough testing.

E3 was assigned for those users and later we encountered a stale entry of another Airwatch app in Azure. After removing it using the graph export function, the issue was resolved. Please find below the topic and solution:

May be this link might help. https://docs.omnissa.com/bundle/SoftwareDistributionManagementVSaaS/page/SoftwareDistributionofWin32Applications.html

YAY

Done

Done

I have added all the details in above topic

Done

I would like to bring to your attention an issue we have encountered with the OOBE configuration. Although we followed the documentation provided, it appears that the requests are not reaching the DS server, and the device is not being enrolled in UEM. Upon consulting with MSFT, we were informed that there is a stale entry for a second app in Azure, which is preventing the requests from being sent. To verify if there are any stale entries, you may use the following URL in the graph explorer: GET https://graph.microsoft.com/beta/policies/mobileDeviceManagementPolicies If you come across any apps with blank or false values in the Discovery URL and Terms and Conditions URL fields, it suggests that these are stale entries. To delete these entries, please use the following command in the graph explorer. Before proceeding, please ensure that you have the necessary access to modify the policy. If not, please make the required modifications: DELETE https://graph.microsoft.com/beta/policies/mobileDeviceManagementPolicies/APP ID

We have received an update from MSFT regarding a stale Airwatch entry with another app ID. Could you please clarify if you have already removed this entry? Alternatively, if there is any support required from MSFT or Omnissa, please let us know.

With Hub v24.4.12 this issue has been addressed. https://docs.omnissa.com/bundle/intelligent-hub-windows-rn/page/ws1-intelligent-hub-windows-rn.html

Can some help me for creating MS Office polices, as I don't see any option in Baseline or BETA profile.

I am also having the same issue where devices are not getting enrolled in UEM. As currently working with MS support for the same and it looks like requests are not hitting to T&C and enrollment URL.