Jump to content

Akito Ogushi

Tech Insider
  • Posts

    347
  • Joined

  • Last visited

  • Days Won

    37

8 Followers

About Akito Ogushi

Areas of Interest

  • Areas of Interest
    Horizon 8
    Horizon Cloud
    Workspace ONE
    Digital Employee Experience (DEX)
    Security

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Akito Ogushi's Achievements

  1. A KNOX license may be required, but the KnoxService Plugin app allows you to configure screen timeout settings. Assignment > Application Configuration > Device and Settings customization profile (Premium) -Configure values in settings menu -Name of the Setting item :Display > Screen timeout Explanations of each settings can be found in Samsung's documentation. https://docs.samsungknox.com/admin/knox-manage/kbas/kba-412-how-to-configure-screen-timeouts-knox-manage/
  2. Hi, Devices from some manufacturers, such as Zebra, allow screen timeout settings in the OEM configuration as follows: Which manufacturer's devices does your organization use? Some manufacturers offer OEM configuration apps like Zebra that allow you to configure advanced settings.
  3. I tested in my environment and it's possible to run directory sync using the API with following parameters: -Request URL: https://[YOUR TENANT]/SAAS/jersey/manager/api/connectormanagement/directoryconfigurations/[Directory GUID]/sync/v2 -HTTP Method: POST -Request Headers: -Content-Type: application/vnd.vmware.horizon.manager.connector.management.directory.sync.trigger.v2+json -Accept: application/vnd.vmware.horizon.manager.connector.management.directory.sync.trigger.v2+json -Body: {"ignoreSafeguards":false} And you can obtain the directory GUID that you need when running the directory sync API by accessing the directory settings page for your target directory.
  4. I checked in my environment and confirmed the same thing happened. Search in the test connection failed, but I was able to add the group in the group list view. This behavior is a little weird, but it seems fine since you can actually add groups and sync member users of the group.
  5. Hi, I have tested in my environment and have successfully imported groups from Onelogin by setting "Base DN" in the directory settings of the UEM console as follows. Except for the Base DN, the rest of the settings are same as shown in the Onelogin documentation. -Base DN: ou=groups,dc=[TENANT],dc=onelogin,dc=com
  6. There should be AppXInstaller logs at the following path in affected devices. ProgramData%AirWatch Related Pages LogsVMware.Hub.Win32Agent.AppXInstaller-YYYYYYYMMDD.log”. Is there any error log? In our case, we have seen that there is an error log stating that the prerequisite package does not exist for the affected device. (It matched the situation described in the KB) But you may have different error logs, given that the simple method doesn't work.
  7. Have you tried updating the Hub app? In our case, updating the Hub app to a fixed version (v24.04.08 or later) has also solved this problem. By distributing the Hub app as an internal app, you can remotely update the Hub app to a specific version.
  8. I assume your problem is the one described in the following KB. https://kb.omnissa.com/s/article/6000119 We resolved this issue by distributing a Powershell script containing the commands described in the KB's “Workaround” section. >Add-AppxPackage "C:\Program Files (x86)\Airwatch\AgentUI\Resources\Hub.UI.Package\HubWinUi\Microsoft.WindowsAppRuntime.1.4_4000.1227.1637.0_x86__8wekyb3d8bbwe.msix" The script was distributed and executed using the product provisioning feature. Once the fixed version of the Hub was released, we took action to update the Hub remotely using the app distribution feature.
  9. Hi, I'm not sure what value is required by Ascom app, but accroding to description in app config setting screen, how about using "{PhoneNumber}". >Set the identity to register with at the SIP PBX (use the phone number or name). {PhoneNumber} is described in Omnissa docs. https://docs.omnissa.com/ja-JP/bundle/WorkspaceONE-UEM-Managing-DevicesV2310/page/LookupValues.html#full_listing_of_uem_lookup_values
  10. You can add any app identifier by following these steps: 1. Click "Miscellaneous" in Quick Filters. 2. Click the "Add New" button. 3. Enter app name in "App Name" and App Identifier in "App ID" and then click "ADD"
  11. I think you need to add "com.google.android.documentsui" in Hidden apps tab of Launcher Layout settings as shown below.
  12. 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>
  13. 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.
  14. 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
  15. 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
×
×
  • Create New...