EUCHorizon Cloud Services Advanced Integrations (For Self Paced Learning in the VLP) Day 1Introduction to the Horizon Cloud Services Advanced Integration Labs

Introduction to the Horizon Cloud Services Advanced Integration Labs

Welcome to the EUC Livefire: Horizon Cloud Services Advanced Integration session. The scenario you will be working on this week is a company called EUC-Livefire. They are a very dynamic Organization and have traditionally been an in house Organization that has been required to get all their users to work from home. They need a secure solution that offers a user experience on par with working in the office.

Manageability and ease of access is a key requirement

During this course, you will be integrating the following solutions with Horizon Cloud Services Control Plane. These will include two on-premises  VMware Horizon PODS. Access to will be delivered using VMware NSX-AVI and VMware Unified Access Gateway.

We will look at the integration of Workspace ONE Access, Workspace ONE Hub services and Workspace ONE UEM and how we can move away from Password based authentication

In addition to  securing access we will also look at how we can manage the user experience when a user logs in to their VMware Horizon Desktop and then possibly logs in to their windows 10 laptop afterwards. We will look at how VMware Dynamic Environment Manager now integrates with Workspace ONE UEM , Workspace ONE Intelligence and Microsoft OneDrive

Your Resource Information

Colour Code Convention

  • Everything in BOLD BLACK is something to look for, it could be a heading or title providing you context to an area you need to configure or launch
  • Everything in BOLD GREEN is an area to select or click on
  • Everything in BOLD BLUE is something to type in

Account information

On starting your lab, you will require the following and these resources are not automated and will have to be setup manually

If you have already attended this course. Do not use the resources ID and POD ID specified in the Microsoft Teams interface when attending the course.

On your Laptop or Desktop

  • Create a dummy email account with a fictitious name
    • This will be helpful when you do your Azure lab on Day 4.
      • The Developer account has to have a unique email and phone number that is not associated with any other Azure Accounts.
      • If either are associated with another Azure account you might not be able to register
    • Go to GMAIL.com  and create yourself a fictitious account.
  • In your Document sheet.
    • Do not forget to document your account and URL information

The objective of this chapter is to introduce to class resources.

It is imperative that you document your urls and also fulfil certain pre-requisite work before you start with regular lab

Failure to complete this chapter will result in you not being to able to complete certain labs going forward

Part 1 : Accessing the VMware Learning Platform (VLP)

Timings

  • This individual Self-paced learning Lab access will be available for 7 days.
    • Please ask for an extension and we will see if this is possible
Part 1 : Accessing the VMware Learning Platform (VLP)
  1. On your Laptop / Desktop
    • Open a Browser and enter the following URL
      • https://vmwarelearningplatform.com/livefire
      • Select LOGIN/REGISTER
      • Next to Username
        • enter your registered username with the Livefire teams
      • Next to Password
        • Enter your VLP password,
          • If you dont know your VLP Password, select Forgot Password?
      • Select LOGIN
  1. In the Labs area
    • Under Horizon Cloud Advanced Integration
      • Select ENROLL
  1. In the Enrollments area
    • Expand LAB DETAILS
      • Take a moment to Read the details
      • Select START THIS LAB
    • In the RESOURCE AVAILABILITY window
      • Select CONTINUE
  1. Accessing your resources
    • You have two choices as to how you will access your labs (Both are acceptable)
      • The first option is direct access using the VLP Admin Console
        • comes with the lab manual
        • might be slower
        • might be more challenging when doing cut & paste work
      • The second option is RDP .
        • This option performs better
        • requires you to use an external link for your lab manual
      • Check your email for the following
        • You should receive and email entitled Livefire-HaaS-VRO (DO NOT REPLY)
          • Open the email and notice there is an attachment
          • Download the attachment
        • Please Note in YOUR email the details
          • To connect to the RDP server
          • Login to the VM (This will be your ControlCenter server)
          • Ignore the [email protected] login information in the email
  1. In your Downloads folder
    • Select and right-click the Livefire Desktop.rdp shortcut
      • Open with your preferred RDP client
    • In your username area : enter
      • YOUR email details to connect to the RDP server Username
      • YOUR email details to connect to the RDP server Password
    • Select OK
  1. In your RDP client session
    • If the login to the ControlCenter fails
    • Ensure the username is [email protected]
    • Ensure the password is VMware1!
    • Select the Sign In arrow
  1. In the VLP interface
    • On the left of the page, select CONSOLES
    • Note the Tier1 virtual machines as mentioned earlier in the LAB Architecture

Part 2: Overview of our On-premise and SaaS resources

This section breaks down all the virtual machines and resources you will have access to in this course .

You can read this conjunction with your Architectural drawing

Part 2: Overview of our On-premise and SaaS resource

On-premise resources

  • The following resources in your lab environment are representative of what the EUC-Livefire organisation "On-premise' resources.
  • This is a multi-site vAPP representing two sites and two of the following:
  • Site 1 (Bangalore) and Site 2 (Seattle)
    1. Active Directory Domain Controller and DNS services.
      • An Active Directory Domain is EUC-Livefire.com
        • ControlCenter.euc-livefire.com is your Site 1 domain controller DNS server and Root CA server
          • Its also your primary landing desktop into your assigned vAPP
        • DC2.euc-livefire.com is your Site 2 domain controller and DNS server
    2. Connector Server
      • A dedicated Windows server called ws1.euc-livefire.com, this is dedicated for the Workspace ONE Access & UEM AirWatch connector.
        • This is a site 1 resource
    3. Horizon Infrastructure
      • Site 1
        • Horizon-01a .euc-livefire.com (Installed and Configured)
        • TrueSSO-01a.euc-livefire.com (installed and Configured)
          • You will deploy your own RDS server farm
          • You will deploy your own Instant Clone Desktop Pool
      • Site 2
        • Horizon-02a .euc-livefire.com (Installed and Configured)
        • TrueSSO-02a.euc-livefire.com ( Installed and Configured)
          • You will deploy your own RDS server farm
          • You will deploy your own Instant Clone Desktop Pool
    4. Unified Access Gateway servers
      • Site 1
        • UAG-HZN-01a.euc-livefire.com
        • UAG-HZN-01b.euc-livefire.com
      • Site 2
        • UAG-HZN-02a.euc-livefire.com
        • UAG-HZN-02b.euc-livefire.com
    5. VMware NSX ALB Server
      1. Site 1
        • AVI SE Server
      2. Site 2
        • AVI Controller Server
        • AVI SE Server
    6. Client resources
      1. Windows 10 desktops .
        • Site 1
          • W10Ext-01a.euc-livefire.com           (TEST CLIENT)
            • the test user account for this desktop will be Jill
          • W10Client-01a.euc-livefire.com        (TEST CLIENT
            • the test user account for this desktop will be Mark
        • Site 2
          • W10Ext-02a.euc-livefire.com           (TEST CLIENT)
            • the test user account for this desktop will Tom
          • W10Client-02a.euc-livefire.com     (TEST CLIENT
            • the test user account for this desktop will be Fernando
      2. Android Device
        • You will be asked to enroll an Android Device, you can either bring your own version of Android or deploy the Android Emulator on a physical laptop. This deployment is optional and we offer a step by step guide on how to do this
        • All your client resources will be enrolled into Workspace ONE UEM

Cloud SaaS resources

In the following section you will validate your access to the following

  • A SaaS Instance of WorkspaceONE UEM
  • A Saas Instance of Workspace ONE Access
  • A Horizon Cloud Account to Horizon Cloud Services
  1. In the above diagram
    • This is a representation of a multi-site layout
    • Servers / Networks and Sites are shown in the above diagram
    • You will be logging in to a representative lab environment with this layout

Part 3: Logging Into Workspace ONE UEM

In this Part we validate access to your Workspace ONE UEM resource

Please document all your resource information in the Lab document with the course material

Part 3: Logging Into Workspace ONE UEM
  1. On your Controlcenter server Desktop
    • Navigate to your Site1 Chrome browser
    • Open a new tab
    • In the address bar https://dw-livefire.awmdm.com
      • In the Username area
        • enter the e-mail address that was part of your course registration
        • Select Next
  1. In the Workspace ONE UEM page
    • Under password:
      • enter VMware1!
    • Select Log In
    • In the Terms of Use page
      • next to I agree to the VMware Cloud Services Terms Of Service
        • select the checkbox
      • select ACCEPT
  1. In the Security Settings page
    • In the Password Recovery Question 1 area
      • Next to Password Recovery Answer *
        • enter 1234
      • Next to Confirm Password Recovery Answer*
        • enter 1234
    • In the Security PIN area
      • Next to Security PIN*
        • enter 1234
      • Next to Confirm Security PIN*
        • enter 1234
    • Select SAVE

Part 4: Logging into and gaining access to Workspace ONE Access

In this Part we validate access to your Workspace ONE Access resource

Please document all your resource information in the Lab document with the course material

Part 4: Logging into and gaining access to Workspace ONE Access
  1. In your e-mail
    • Look for a no-reply Workspace ONE Access Tenant Administrator Notification
    • In the email
      • Select and open Workspace ONE Access Tenant Administrator Notification
  1. In the Workspace ONE Access Tenant Administrator Notification email
    • Scroll down to Set Password URL:
    • Select the URL next to Set Password URL
  1. In the Workspace ONE login
    • Under Change your password
      • In the New Password area
        • enter VMware1!
      • In the Confirm Password area
        • enter VMware1!
    • Select Change Password
    • Select Go to Sign in page
  1. On your Site 1 Chrome browser
    • Bookmark your Workspace ONE Access tenant sign in URL
  1. In the Workspace ONE Login
    • Under Username
      • enter administrator
    • Under Password
      • enter VMware1!
    • Select Sign in
  1. In the Workspace ONE Access Terms and Conditions page
    • Select Accept
  1. PLEASE NOTE!
    • Do not navigate or sign up of the EUC early access program on this Tenant

Part 5: Renaming your vCenter server

Section 1: will be dedicated to renaming Site 1 vCenter

Section 2: will be dedicated to renaming Site 2 vCenter

Section 1: Renaming your vCenter server for site 1
  1. On your ControlCenter server
    • On your Desktop
      • Select the DNS shortcut
  1. In the DNS Manager console
    • Expand the Forward Lookup Zones
      • Expand euc-livefire.com
        • Select and right-click euc-livefire.com
          • From the menu
            • Select New Host (A or AAAA)....
  1. In the New Host record
    • Under Name
      • enter vcenterXX-01a
        • where XX is your assigned POD ID
    • Under IP address:
      • enter 192.168.110.25
    • Select Add Host
  1. In the New Host record
    • Under Name
      • enter vcenterXX-02a
        • where XX is your assigned POD ID
    • Under IP address:
      • enter 192.168.210.25
    • Select Add Host
    • To close the New Host window
      • Select Done
  1. In the DNS Manager console
    • Select and right-click euc-livefire.com
      • Select Refresh
    • Validate that your entry is similar to the above screenshot, only that it represents your assigned POD ID
  1. On your ControlCenter server
    • Open your Site 1 Chrome Browser
      • In the Address bar
        • enter https://vcenter-01a.euc-livefire.com:5480
  1. In the VMware vCenter Server Management window
    • In the Username area
      • enter root
    • In the Password area
      • enter VMware1!
    • Select LOGIN
  1. In the VMware vCenter Server Management window
    • In the Inventory
      • select Networking
  1. In the Networking window
    • select EDIT
  1. In the Edit Network Settings window
    1. Select Network Adapter area
      • Select NEXT
  1. In the Edit Network Settings window
    1. Edit Settings area
      • next to Hostname:
        • enter vcenterXX-01a.euc-livefire.com
          • where XX is your POD ID
      • Scroll down
        • Expand NIC 0
          • Note the Toggle above IPv4 is Enabled
            • turn the toggle OFF
            • turn the toggle ON
          • Note that now IPv6 is also Enabled
            • Turn OFF the IPv6 Toggle
          • Note that now the NEXT button has become available
      • In the bottom right corner
        • Select NEXT
  1. In the Edit Network Settings window
    1. SSO credentials area
  1. In the Edit Network Settings window
    1. Ready to complete area
      • next to I acknowledge that I have made a backup of my vCenter Server and unregistered extensions before continuing with my network configuration
        • select the CHECKBOX
      • Select the FINISH
  1. In your vCenter Management console
    • Wait for the Network update in progress to complete
    • Under Your Connection is not Private
      • Select Advanced
    • Select to Proceed to vcenterxx-01a.euc-livefire.com (unsafe)
      • note you are taken back to the vCenter Management Consofe
  1. In your Site 1 Browser
    • In the Address bar
      • Enter your unique vcenter address for site
        • e.g. vcenterxx-01a.euc-livefire.com
          • Where XX is your POD ID
      • Select LAUNCH VSPHERE CLIENT (HTML5)
  1. In the VMware vSphere login window
    • In the Username area
    • In the Password area
      • enter VMware1!
    • Select LOGIN

 

Section 2 will be dedicated to renaming Site 2 vCenter

Section 2: Renaming your vCenter server for site 2
  1. On your ControlCenter server
    • Open your Site 2 Chrome Browser
      • In the Address bar
        • enter https://vcenter-02a.euc-livefire.com:5480
  1. In the VMware vCenter Server Management window
    • In the Username area
      • enter root
    • In the Password area
      • enter VMware1!
    • Select LOGIN
  1. In the VMware vCenter Server Management window
    • In the Inventory
      • select Networking
  1. In the Networking window
    • select EDIT
  1. In the Edit Network Settings window
    1. Select Network Adapter area
      • Select NEXT
  1. In the Edit Network Settings window
    1. Edit Settings area
      • next to Hostname:
        • enter vcenterXX-02a.euc-livefire.com
          • where XX is your POD ID
      • Scroll down
        • Expand NIC 0
          • Note the Toggle above IPv4 is Enabled
            • turn the toggle OFF
            • turn the toggle ON
          • Note that now IPv6 is also Enabled
            • Turn OFF the IPv6 Toggle
          • Note that now the NEXT button has become available
          • In the bottom right corner
            • Select NEXT
  1. In the Edit Network Settings window
    1. SSO credentials area
  1. In the Edit Network Settings window
    1. Ready to complete area
      • next to I acknowledge that I have made a backup of my vCenter Server and unregistered extensions before continuing with my network configuration
        • select the CHECKBOX
      • Select FINISH
  1. In your vCenter Management console
    • Wait for the Network update in progress to complete
    • Under Your Connection is not Private
      • Select Advanced
    • Select to Proceed to vcenterxx-02a.euc-livefire.com (unsafe)
      • note you are taken back to the vCenter Management Console

Give the services about 10 minutes to restart

Save your new vCenter address in your Browsers address bar

  1. In your Site 2 Browser
    • In the Address bar
      • Enter your unique vcenter address for site
        • e.g. vcenterxx-02a.euc-livefire.com
          • Where XX is your POD ID
      • Select LAUNCH VSPHERE CLIENT (HTML5)
  1. In the VMware vSphere login window
    • In the Username area
    • In the Password area
      • enter VMware1!
    • Select LOGIN
  1. In the DNS Manager Console
    • Delete the original vcenter-01a > 192.168.110.25 record
    • Delete the original vcenter-02a > 192.168.210.25 record

Part 7: Configuring vCenter in your Horizon Lab Infrastructure

Due to resources connecting to the Hydra Console having to be unique. Your vCenter instances in your labs have to be renamed. We will now add the new names to the existing Horizon Pods

We will first perform these steps on Site 1 and then on Site 2

Section 1: Configuring vCenter to communicate with your VMware Horizon Pod on Site 1
  1. In your ControlCenter server
    • On your Site 1 Chrome Profile browser
      • In the address bar
        • Enter your Horizon-01a.euc-livefire.com/admin
  1. In your VMware Horizon login
    • In the Username area
      • enter administrator
    • In the Password area
      • enter VMware1!
    • Select Sign in

 

  1. In Horizon Admin Console
    • Expand Settings
      • Select Servers
    • Under the Servers area
      • Select Add
  1. In the Add vCenter Server wizard
    1. vCenter Information
      • Enter the following under:-
        • *Server address :
          • enter vcenterXX-01a.euc-livefire.com
            • where XX is your POD identifier
        • *User name
        • *Password
          • enter VMware1!
      • Select Next
  1. In the Invalid Certificate Detected window
    • Select View Certificate
  1. In the Certificate Information window
    • Select Accept
  1. In the Add vCenter window
    • Select Next
  1. In the Add vCenter Server window
    • Select Submit
Section 2: Configuring vCenter to communicate with your VMware Horizon Pod on Site 2
  1. In Horizon Admin Console of Site 2
    • Expand Settings
      • Select Servers
    • Under the Servers area
      • Select Add
  1. In the Add vCenter Server wizard
    1. vCenter Information
      • Enter the following under:-
        • *Server address :
          • enter vcenterXX-02a.euc-livefire.com
            • where XX is your POD identifier
        • *User name
        • *Password
          • enter VMware1!
      • Select Next
  1. In the Invalid Certificate Detected window
    • Select View Certificate
  1. In the Certificate Information window
    • Select Accept
  1. In the Add vCenter window
    • Select Next
  1. In the Add vCenter Server window
    • Select Submit

Part 8: Setting up the RDS Farms

We will now prepared the RDS server Farm environment for future labs

Setting up the RDS Farm for Site 1
  1. On your ControlCenter server,
    • Switch to your Site 1 Chrome Profile browser
    • On the Favourites bar
      • Select your the Horizon Site 1 Shortcut  
    • Select LAUNCH the Horizon Console (HTML) Console .
      • In the Username are type Administrator
      • In the Password area type VMware1!
      • Select Sign In
  1. In the VMware Horizon Admin Console
    • Expand Inventory
      • Select Farms
      • In the Farms area
        • Select Add
  1. In the Add Farm wizard
    1. Type area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. vCenter Server area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Storage Optimization area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Identification and Settings area
      • Configure the following:-
        • Under *ID
          • enter RDSHXX-01a
            • Where XX is your assigned POD ID
  1. In the Add Farm wizard
    1. Identification and Settings area
      • Configure the following:-
        • Under Pre-launch Session Timeout (Applications Only)
          • select Never
        • Under Empty Session Timeout (Applications Only)
          • select Immediate
        • Under When Timeout Occurs
          • select Log Off
        • Under Logoff Disconnected Sessions
          • select Immediate
        • Under Max Sessions Per RDS Host
          • select No More Than enter 3
      • Select Next
  1. In the Add Farm wizard
    1. Load Balancing Settings area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Provisioning Settings area
      • Configure the following:-
        • Under *Naming Pattern
          • enter RDSXX-01-
            • Where XX is your assigned POD ID
        • Under *Maximum Machines
          • enter 2
        • Select Next
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Golden Image in vCenter
          • Select Browse
        • In the Select Golden Image window
          • next to RDSH-01a
            • select the radio button
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Snapshot
          • Select Browse
        • In the Select Default Image window
          • next to baseline
            • select the radio button
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *VM Folder Location
          • Select Browse
        • In the VM Folder Location window
          • select the Region01A
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Cluster
          • Select Browse
        • In the Select Cluster window
          • select the Bangalore
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Resource Pool
          • Select Browse
        • In the Resource Pool window
          • select the Bangalore
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Datastores
          • Select Browse
        • In the Resource Pool window
          • next to CorpLun01a
            • select the radio button
        • Select Submit
        • In the  Warning window
          • Select OK
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Review your configurations
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Guest Customization area
      • Configure the following:-
        • Under *AD Container
          • Select Browse
        • In the AD Container window
          • expand OU=Corp
            • select OU=Computers, OU=Corp
        • Select Submit
  1. In the Add Farm wizard
    1. Guest Customization area
      • Configure the following:-
        • Under *AD Container
          • Next to Allow Reuse of Existing Computer Accounts
            • Select the CHECKBOX
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Ready to Complete window
      • Review your configuration
      • Select Submit
Setting up the RDS Farm for Site 2
  1. On your ControlCenter server,
    • Switch to your Site 2 Chrome Profile browser
    • On the Favourites bar
      • Select your the Horizon Site 2 Shortcut  
    • Select LAUNCH the Horizon Console (HTML) Console .
      • In the Username are type Administrator
      • In the Password area type VMware1!
      • Select Sign In
  1. In the VMware Horizon Admin Console
    • Expand Inventory
      • Select Farms
      • In the Farms area
        • Select Add
  1. In the Add Farm wizard
    1. Type area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. vCenter Server area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Storage Optimization area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Identification and Settings area
      • Configure the following:-
        • Under *ID
          • enter RDSHXX-02a
            • Where XX is your assigned POD ID
  1. In the Add Farm wizard
    1. Identification and Settings area
      • Configure the following:-
        • Under Pre-launch Session Timeout (Applications Only)
          • select Never
        • Under Empty Session Timeout (Applications Only)
          • select Immediate
        • Under When Timeout Occurs
          • select Log Off
        • Under Logoff Disconnected Sessions
          • select Immediate
        • Under Max Sessions Per RDS Host
          • select No More Than enter 3
      • Select Next
  1. In the Add Farm wizard
    1. Load Balancing Settings area
      • Accept the default
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Provisioning Settings area
      • Configure the following:-
        • Under *Naming Pattern
          • enter RDSXX-02-
            • Where XX is your assigned POD ID
        • Under *Maximum Machines
          • enter 2
        • Select Next
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Golden Image in vCenter
          • Select Browse
        • In the Select Golden Image window
          • next to RDSH-02a
            • select the radio button
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Snapshot
          • Select Browse
        • In the Select Default Image window
          • next to baseline
            • select the radio button
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *VM Folder Location
          • Select Browse
        • In the VM Folder Location window
          • select the Region02A
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Cluster
          • Select Browse
        • In the Select Cluster window
          • select the Seattle
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Resource Pool
          • Select Browse
        • In the Resource Pool window
          • select the Seattle
        • Select Submit
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Configure the following:-
        • Under *Datastores
          • Select Browse
        • In the Resource Pool window
          • next to CorpLun-02a
            • select the radio button
        • Select Submit
        • In the  Warning window
          • Select OK
  1. In the Add Farm wizard
    1. vCenter Settings area
      • Review your configurations
        • scroll through the configurations
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Guest Customization area
      • Configure the following:-
        • Under *AD Container
          • Select Browse
        • In the AD Container window
          • expand OU=Corp
            • select OU=Computers, OU=Corp
        • Select Submit
  1. In the Add Farm wizard
    1. Guest Customization area
      • Configure the following:-
        • Under *AD Container
          • Next to Allow Reuse of Existing Computer Accounts
            • Select the CHECKBOX
      • In the bottom right corner
        • Select Next
  1. In the Add Farm wizard
    1. Ready to Complete window
      • Review your configuration
      • Select Submit

Part 9: Logging into the Horizon Universal Console

  1. On your ControlCenter Server
    • Select your Site 1 profile - Chrome browser
  1. On your Site 1 profile browser
    • In the Favourites bar
      • Select the HZN Cloud shortcut
  1. In the Horizon Cloud Console Login
    • In the Username area (Enter your teams assigned username)
    • In the Password area, type VMware1!
    • Select LOGIN
  1. In the Horizon Cloud Console
    • Note the Getting Started area
      • Note we can configure VMware SDDC or Microsoft Azure
      • In the following Part 2 we will configure 2 Horizon Cloud Connectors
        • One on Site 1 and one on Site 2
          • Each of these PODS could represent a Horizon POD in any GEO locality or cloud platform, whether that be on AWS, Google, Oracle or Azure AVS.

Part 10: Introduction to the Livefire Company

Overview of the Company

Livefire as an Organization was found in 2003, It  started off a revolutionary approach to financial investment. The Organizations headquarters are in New York USA. The company has branches across the USA and now employs just under 6400 users.

This Organization requires a radical infrastructure re-think as employees  appear to be working from home on a permanent basis for the foreseeable future. We will look at  the VMware Workspace ONE Portfolio as way to grant secure Anywhere Access to users.

As a consulting firm you will be testing using the Sales, Marketing, Help Desk and IT Support Teams. In your testing you are welcome to conduct tests using accounts representative of roles in these departments

  • We have the following accounts for the respective departments
    • For Marketing
      • Fernando Dusello                     email is [email protected]
      • Tom Marios                                  email is [email protected]
      • And your custom account
    • For Sales
      • Jill Verneo                                    email is [email protected]
      • Mark Debio                                  email is [email protected]
    • For IT Support we have the following accounts
    • For Help Desk

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.