1. On the ControlCenter VM, click the Google Chrome icon.

2. You can also enter https://{labid}.us0.wss.workspaceone.com in the address bar to access the Omnissa Access administration console.

3. Log in to the Omnissa Access console.

   • User name: admin

   • Password: Pa$$w0rd

4. In the Omnissa Access console, click each tab in the menu bar and review the available controls.

5. In the upper-right corner of the page, click the catalog menu (looks like a 3x3 grid) and review the available controls.

• User Portal: Changes to the User Portal view.

6. In the upper-right corner of the page, click the Tenant Admin drop-down menu and review the available controls.

   • Profile: Review the administrator account details.

   • Logout: Logs the current user account out of the Omnissa Access console.

7. From the navigation pane, click Accounts and review the available controls. You explore and configure some of these settings later in this course.

   • Users

   • User Groups

   • Roles

7. In the navigation pane, across the top, click Resources and review the available controls. You explore and configure some of these settings later in this course.

   • Web Apps

   • Virtual Apps

   • Horizon Cloud Services Next-Gen

   • Virtual Apps Collections

   • Policies

   • Global Launcher Preferences

8. From the navigation pane, across the top, click Integrations and review the available controls. You explore and configure some of these settings later in this course.

   • Authentication Methods

   • Connectors

   • Directories

   • Connector Authentication Methods

   • Hub Configuration

   • Identity Providers

   • Magic Link

   • Okta Catalog

   • People Search

   • UEM Integration

   • SIEM

9. From the navigation pane, across the top, click Settings and review the available controls. You explore and configure some of these settings later in this course.

   • Branding

   • Login Preferences

   • OAuth 2.0 Management

   • Password Policy

   • Password Recovery

   • User Attributes

   • Support Access

1. From the Omnissa Access console menu bar, select Settings > Branding.

2. Under the Workspace ONE Browser Tab section, you can customize the sign-in page browser tab display preference.

   • Company Name: Enter the text that appears in the web browser page title.

   • Product Name: Enter the text that appears in the web browser page title after your company name.

3. Under the Sign-In Screen section, you can customize the UI preference for the login screen.

   • Logo: Upload the logo that is displayed on your login page.

   • Screen Background: Select a background image for your login page.

   • Sign-in dialog background: Select the background color of your login page.

   • Sign-in button background: Select the background color of your login button.

   • Sign-in Button Text: Select the color of the login button text.

You can use the preview box to determine if you are satisfied with the changes.

4. Click Save to store your custom branding.

5. Open a new Incognito window in Google Chrome.

6. Log in to the Omnissa Access console.

   • You should see the Omnissa Access sign-in page with the new branding scheme if you changed any branding element in the previous steps.

7. Close the Incognito window.

8. Return to the Omnissa Access console. Keep the Workspace ONE UEM and Omnissa Access consoles open for later labs.

1. If the Workspace ONE UEM console is logged out due to inactivity, log in to the Workspace ONE UEM administration console.
   1. From the ControlCenter VM, click the Google Chrome icon and open a new tab.
   2. From the bookmarks bar, select Workspace ONE UEM. You can also enter https://omnissatraining.com/Airwatch in the address bar to access the console page.
2. Log in to Workspace ONE UEM.
   • User name: studentadmin{labid}
   • Password: Pa$$w0rd
3. In the navigation pane at the top, select Groups & Settings. Then, select All Settings and expand System > Enterprise Integration > Cloud Connector.
   • You should see that AirWatch Cloud Connector is enabled.
4. Click Test Connection to validate connectivity.
   • A "Reached Cloud Connector running version 25.#.#.# at WS1-Connector (192.168.110.95)" message appears.
5. In the navigation pane on the left, select System > Enterprise Integration > Directory Services.
   • You should that see Directory Services integration is configured.
6. Click Test Connection to validate connectivity.
   • A test connection dialog box opens, and you should see a message, saying, "Connection successful with the given server name, bind username, and password."
7. Close the Test Connection dialog box.
8. Select Devices & Users and then expand General > Enrollment.
9. On the Authentication tab, click Override next to Current Setting.
10. Next to Authentication Mode(s), select the Basic and Directory check boxes.
11. Next to Source of Authentication for Intelligent Hub, click WORKSPACE ONE ACCESS.

12. Click Save.

1. Using the VM Swticher menu, switch to the WS1-Connector VM.
2. On the WS1-Connector VM desktop, open Google Chrome. If an Enhanced ad Privacy in Chrome window opens, click More, and then Got it.
3. Enter https://{labid}.us0.wss.workspaceone.com/ in the address bar.
4. Log in to the Omnissa Access console.
   • User name: admin
   • Password: Pa$$w0rd
5. Click in the top right TA button and click Access Console.
6. From the Omnissa Access console navigation bar, click the Integrations tab, and in the left pane, click Connectors.
7. If the Add New Connector screen does not appear automatically, click New.
8. On the Download Installer screen, click Next.
9. Enter Pa$$w0rdPa$$w0rd in the Password text box.
10. Enter Pa$$w0rdPa$$w0rd in the Reenter password text box.
11. Click Download Configuration File.
    • The es-config.json file downloads to the Downloads folder of the WS1-Connector VM.
12. Click Next and then click Close.

13. From WS1-Connector VM desktop taskbar, click the File Explorer icon, and navigate to the Desktop\Software\Access folder.
14. In the Access folder, Right-click the Workspace-ONE-Access- Connector-Installer-24.12.1.0.exe file and select Copy.
15. Navigate to the WS1-Connector VM's Downloads folder.
16. Right-click inside the folder, and select Paste.
    • The Omnissa Access Connector installer is copied to the VM's Downloads folder.
17. In the Downloads folder, right-click the Workspace-ONE-Access-Connector-Installer-24.12.1.0.exe file and select Run as administrator.
18. Click Next. If you are prompted with a security warning, click Run to proceed with the installation.
19. If you are prompted to install Microsoft .NET Framework 4.8 Web, click Install to complete that installation.

The Omnissa Access connector installation wizard appears.

20. Select I accept the terms in the license agreement and then click Next.
21. Click Next to accept the service selection and default install path.
22. If you are prompted to update the Java Runtime Environment (JRE) version, click Yes.
23. On the Specify Configuration File page, click Browse.
24. Navigate to the Downloads folder and select the es-config.json configuration file.
25. Click Open.
26. Enter Pa$$w0rdPa$$w0rd as the configuration file password. Ensure that Enable FIPS is NOT selected.
27. Click Next.
28. On the Select Default or Custom Installation page, select Default and then click Next.
29. On the Specify Service Account page, enter the service account information.
    • User name: omnissatraining.com\WS1Access
    • Password: 0Mnissa1!
30. Click Next.
31. Click Install.

32. On the Installation Wizard Completed page, click Finish.
33. If you are prompted to restart the server, click Yes and wait for the WS1-Connector VM restart process to finish.

34. In the Omnissa Access console, select Integrations > Connectors from the navigation.

You see a Omnissa Access connector entry with the ws1-connector.omnissalearninglabs.com host name. The following services should be running on the WS1-Connector VM:

• Directory Sync
• Kerberos Auth
• User Auth
• Virtual Apps Sync

1. On the ControlCenter VM, log into the Omnissa Access administration console.
   • User name: admin
   • Password: Pa$$w0rd
2. Click in the top right TA button and click Access Console.
3. From the navigation bar, across the top, click the Settings tab and then from the left-hand side of the page, click User Attributes.
4. Verify that the email check box is selected as a required attribute.

5. Click Save.
6. From the navigation bar, across the top, click the Integrations tab and then from the left-hand side of the page, Click Directories.
7. Click Add Directory and select Active Directory. The Add Active Directory dialog box appears.
8. Enter omnissatraining in the Directory Name text box.
9. Click Next.
10. Next to Directory Sync Hosts, verify that the WS1-connector.omnissalearninglabs.com (Active) check box is selected.
11. Next to User Auth Hosts, verify that the WS1-connector.omnissalearninglabs.com (Active) check box is selected.
12. From the User Name drop-down menu, verify that sAMAccountName is selected.
13. Under Server Location, verify that the This Directory supports DNS Service Location check box is selected.
14. Under Encryption, verify that the STARTTLS required for all connections check box is not selected.
15. Under Bind User Details enter:
    • Base DN: dc=omnissatraining,dc=com
    • Bind User DN: cn=administrator,ou=corp,dc=omnissatraining,dc=com
    • Bind User Password: Pa$$w0rd
16. Click Save.
17. On the Select Domain(s) page, click omnissatraining.com check box is selected.
18. Click Save.
19. The Map User Attributes dialog box appears.
20. From the email drop-down menu, verify that mail is selected.
21. From the firstName drop-down menu, verify that givenName is selected.
22. From the userName drop-down menu, verify that sAMAccountName is selected.
23. Leave the default values for all other user attribute mappings.
24. Click Save.
25. Click +ADD in the Select the group you want to sync page.
26. In the Name field type dc=omnissatraining,dc=com and click Add.
27. Scroll down and click SAVE.
28. In the the Select the Users you would like to sync page, edit the syntax so it reads: ou=corp,dc=omnissatraining,dc=com.
29. Click Test.
30. Click SAVE.

31. In the Sync Frequency page click Every hour.
32. Click Save & Sync to finish the directory synchronization.

You are returned to the Directories page in the Omnissa Access console.

33. Refresh the browser page to reflect the directory synchronization result.
34. From the Navigation bar, across the top, click the Accounts tab and make sure the Users section is selected. Then, verify that the new user accounts are imported from Active Directory. (This may take a few minutes.)

1. From the Omnissa Access console navigation bar, across the top, click the Integrations tab, and in the left pane, click Identity Providers.
2. To edit the settings for the IdP, click IDP for Omnissatraining.com.
3. You see the sections, General Information, Users, Connector Authentication Methods, Authentication Methods, Network, and KDC Certificate Export.  Password (cloud deployment) is selected. Leave all settings at their default values.
4. Click Save.

1. From the Omnissa Access console navigation bar, click the Resources tab, and in the left pane, click Policies.

2. Click Edit on the Default Policy.
3. Click Next.
4. The Configuration page appears.  To edit the access policy rule, click ALL RANGES next to the Workspace ONE App or Hub App device type policy rule.
   • The browser might obscure the values. You can point to a value to see the full text.
5. Verify the configuration of the rule. The correct configuration should be, as follows:
   • If a user’s Network Range is: ALL RANGES
   • and the user accessing content from: Apps on Workspace ONE Intelligent Hub
   • Then perform this action: Authenticate using
   • then the user may authenticate using: Password (cloud deployment)
   • If the preceding method fails or is not applicable, then: Password (Local Directory)

6. Leave the default values for the other settings and click Save.
7. Repeat the same steps for the Web Browser policy rule to ensure that Password (cloud deployment) authentication is set as the primary authentication method.

8. On the Configuration page of the Edit Policy, click +Add Policy Rule.
9. Configure a new policy rule as follows.

10. Click Save.
11. Drag the vertical 6-dot icons to reorder the policy rules.
12. Drag the macOS rule to the bottom.
13. Drag the Workspace ONE App or Hub App rule to the middle.
14. Drag the Web Browser rule to the bottom.  Their order, from top to bottom, should be macOS, Workspace ONE App, then Web Browser.
15. To view the Summary page, click Next.
16. Click Save to commit your changes to default_access_policy_set.