[Google mail call "Files" application and it bloc]

I think you need to add "com.google.android.documentsui" in Hidden apps tab of Launcher Layout settings as shown below.

 

[macOS Sequoia Blocker Profile]

And now that Sequoia is officially released, you can block the Sequoia installer by adding the following string to the array of “bundleid” section. (I checked in my test environment)
<string>com.apple.InstallAssistant.macOSSequoia</string>

[fling: Edge Services Observability]

Hi,

You can now download ESO on the Broadcom Flings page.

You need to login broadcom portal, but once you log in you can see download link of ESO applicance as shown in following image.

[Can’t Find the ‘Sensors’ Option in Workspace ONE Device Details View]

Hi,
According to the documentation, you can use the Sensors tab on the Device details page like Robin's screenshot even in the UEM2302 SaaS environment.
I think you need to create a support request to resolve this type of issue.https://docs.omnissa.com/bundle/Windows_Desktop_ManagementV2302/page/uemWindeskSensors.html#device_details_sensors

[Workspace One - Android Lost Mode and APIs]

Hi,

Lost mode API is mentioned in "What's New" section in 2402 release note.

I think you can not use this API if your UEM version is 2310 .(In our 2306 environment, same 404 error returned.)

https://docs.omnissa.com/ja-JP/bundle/Workspace-ONE-UEM-Release-NotesV2402/page/WorkspaceONEUEM-ReleaseNotes.html#whats_new

[Disable intelligent hub passcode requirement]

Hi,
You can disable Hub app passcode with following setting.

All Setting > Apps > Settings and Policies > Security Policies

-Authentication Type : Disabled

[Workspace One - problem with Provisioning packages on endpoints]

Hi,

Basically, "Queued" status means that device has not recieve product install command yet.

When I have same issue first action is running manual sync by right-clicking Hub icon intask tray and then click "Sync".

If that does not resolve issue, I think you need to do some trouble shooting like checking network conectivity or searching some error in log files.

Following URL is usefull guide when trouble shooting.
https://techzone.omnissa.com/troubleshooting-windows-devices-workspace-one-operational-tutorial#locating-log-files-and-registry-keys

[macOS Sequoia Blocker Profile]

Hi,

I could restrict to run Sequoia beta installer with following setting.
Try following setting.
-----------------

<dict>
   <key>Restrictions</key>
   <array>
      <dict>
         <key>Attributes</key>
         <dict>
            <key>bundleId</key>
         <array>
            <string>com.apple.InstallAssistant.Seed.macOS15Seed</string>
         </array>
         </dict>
         <key>Actions</key>
         <array>
            <integer>1</integer>
         </array>
         <key>Message</key>
         <string>You are currently not permitted to install macOS Sequoia.</string>
      </dict>
   </array>
   <key>PayloadDisplayName</key>
   <string>Restricted Software Policy</string>
   <key>PayloadIdentifier</key>
   <string>HubSettings.93f1655a-59fb-42dc-bc31-9571275cb12b</string>
   <key>PayloadOrganization</key>
   <string>VMware</string>
   <key>PayloadType</key>
   <string>com.vmware.hub.mac.restrictions</string>
   <key>PayloadUUID</key>
   <string>1D7F0D17-369B-4766-9CA0-D2B4537657C1</string>
   <key>PayloadVersion</key>
   <integer>1</integer>
</dict>

-----------------

 

-Result

 

If you still cannot restrict, the bundle ID in the profile may not match the installer for your device.
Check the bundle ID of the installer.
The bundle ID can be checked with the following command when the Sequoia installer is running. (I also checked “com.apple.InstallAssistant.Seed.macOS15Seed” in the same way.)
>lsappinfo

[macOS Sequoia Blocker Profile]

Hi,

When I install Sequoia in my environment, the bundle id of "Install macOS Sequoia Beta" app is "com.apple.InstallAssistant.Seed.macOS15Seed".
Try above bundle id in "bundleId" section in your profile.

 

[API command to Perform Enterprise Wipe a Windows machine with "Keep Apps On Device"]

Hi,
I have done the API command before with following command in API Explorer.

 

You can access API Explorer using following URL. ('cnXXXX' must be replaced with the console server hostname)

https://cnXXXX.awmdm.com/Api/help/

[Update SSL certificate for AWCM without full installer (no access to download)]

Hi,

Is this KB helpful?
https://kb.omnissa.com/s/article/2960970#Keytool

According to this KB, there are two ways to renew an AWCM certificate, and the Keytool method does not require an installer.

[Windows Autopilot - Microsoft Store for Business]

Hi, 
I have done the same procedure before, but when I check now, I get the same screen and cannot upload the csv file of the Autopilot device hash list.

According to MS documentation, MS store for Business is deprecated and Autopilot device hash registration must be done through another method, such as Intune Management Console.

https://learn.microsoft.com/en-us/autopilot/manual-registration#platforms-for-device-registration
>Device profile assignment will be retired from Microsoft Store for Business in the coming months.

[Onedrive configuration under Workspace ONE]

I don't think you can add certificate in OneDrive appconfig settings.
I think you need to publish certificate as profile if you need to use certificate when authenticate.

[On-Prem Cloud Connector Stopped]

Hi, 

Is there any error logs in the ACC log file?
The ACC log is located at the following path:
C:\VMware\AirWatch\Logs\CloudConnector\CloudConnector.log

If there are no error logs, you can further investigate by setting the log level to "Verbose" using the steps mentioned in following document:
https://docs.omnissa.com/ja-JP/bundle/TroubleshootingandLoggingGuide/page/IntegratedServicesLogging.html#vmware_airwatch_cloud_connector_acc
>Change ACC log level

After changing the log level, reproduce the error and check the error log again.

[Protect Exchange Online]

Hi,

Powershell integration can also work with ACC, but ACC is not a required component for Powershell integration to work.

The ACC advanced settings allow you to choose whether Powershell communication goes through ACC or not.

So if you're using Exchange Online, I think Powershell integration with "Exchange Powershell" setting disabled in ACC is the best way to manage MEM.
https://docs.omnissa.com/ja-JP/bundle/WS1UEM_PowerShell_Integration_GuideVSaaS/page/EnablePowerShellIntegrationinWorkspaceONEUEM.html

[Onedrive configuration under Workspace ONE]

Hi,

There isn't a lot of configuration in the OneDrive app configuration.
According to the MS documentation, all you can do is "Allow organizational accounts only".
https://learn.microsoft.com/en-us/mem/intune/apps/app-configuration-policies-use-android#allow-only-configured-organization-accounts-in-apps

This setting is preset on the Application Configuration tab of Assignment Settings.

 

This configuration requires setting the value to match the user's Microsoft account and you can use lookup values such as {UserPrincipalName}, {Email}, etc.

[Force BIOS Password Rest -Save Failed]

Hi,

In our environment, a similar error screen has appeared on other settings screens before, but no errors were displayed in the console log etc.
At that time, I had to open a support request because the error was recorded in a log that only the support team could see, so I recommend you to open support request.
Support team may check and investigate debug log.

[OS optimization tool]

HI,

Is this what you are looking for?

https://customerconnect.omnissa.com/downloads/info/slug/desktop_end_user_computing/windows_os_optimization_tool_for_vmware_horizon/1_0

 

Other useful tools are also published on this page.

https://techzone.omnissa.com/utilities#horizon-tools

[Devices enrolled but not deploy applications.]

Hi,
Console logging is limited, but more detailed logging is recorded in the device log file or registry.
The troubleshooting guide on the following page may be helpful.
https://techzone.omnissa.com/troubleshooting-windows-devices-workspace-one-operational-tutorial#troubleshooting-msi-apps