Workspace One UEM Tips And Tricks

/ October 20, 2020/ Uncategorised, Workspace One

This blog contains a few Workspace One UEM Tips and Tricks to make your IT-project to a great success!

  1. While configuring the Unified access gateway, use a domain service account to establish to connection between the UAG Service (tunnel) and the Workspace One console. While using a local system account, which has been created within the UEM console. By default the password expires after 90 days. After rebooting the Unified access gateway, connections will be dropped.
  2. Make always a child organization group and configure company settings within this organization. While facing problems, you can always change the above setting (parent)
  3. Applications created in the child organization cannot be shared with other organizations.
  4. Applications created from the highest level (parent) can be enrolled or assigned to child organizations or groups
  5. You need a Azure AD Premium P1 License to provide OOBE (out of the box experience) in combination with Windows 10
  6. Use the same password policies within your profile and the default domain policy
  7. Use the Workspace One UEM Enterprise App Repository to create the most common applications. This app Repository uploads automatically the right installer with additional parameters. A Great tool!
  8. Make sure that the “When to call install complete” condition has been set correctly. While not set, the install of the application will be failed.
  9. Chrome OS device profile will be listed after integrate your google account with workspace One
  10. Since the new release, applications and Weburls can be combined within the Workspace one HUB.
  11. While using multiple Organization groups, map the right domain within Workspace One Access, otherwise web apps will not be showing, see my blog about it

Tricks

Enroll Office 365 With UEM
Make first your configuration XML at the website https://config.office.com/

Due the maximum size deployment of installers are limited to 200 MB, The best way to deploy Office 365 would be local. With the additional parameter “/configure” installation files would be downloaded directly from Microsoft.

!Ask VMware Support to increase the upload limit to a maximum of 500MB

Install ContextUser
Admin PrivilegesYes
Install Commandsetup.exe /configure configuration.xml
Uninstall Commandsetup.exe /configure uninstall.xml
When to call install completeFile exists – C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE

Run a powershell script

In order the run a powershell script, specify if the script must be executed from the user or device. In order to satisfy the “When to call complete Value” you can create a registry key from your script. This is quite important when using the auto deploy option from UEM. The next application will not be installed if the current hasn’t completed.

Install ContextUser or Device
Admin PrivilegesYes or no
Install Commandpowershell -executionpolicy bypass -nologo -NoProfile -file virtualblog.ps1

Leave a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>
*
*