EUC

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

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

Before starting this section make sure you have access to the following:-

Your assigned Resource accounts in Microsoft Teams
You have downloaded the Microsoft Word LAB document
- This will be used to record your resource access, this will include URL's, passwords you are using.
- If you fail to use this document and you need support from us and you fail to forward this document to us. We will reserve the right not to support you in troubleshooting your labs
Have and understand what your assigned POD ID is
Know your individual external IP address for your vAPP.

Timings

Lab access will be available for the entire 4 day session and will be cut the following day.
Due to us using production resources no extensions will be offered.
It is therefore in your interest to make the most of the time you have been allocated.
We are not in a position to make exceptions

LAB Networking Architecture for this week

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

Part 1. Account information

We will revise your Account information with you

Section 1. Overview of Accounts

On your Laptop or Desktop

Step number 1
- Recently we have decided to use Microsoft TEAMS as a collaborative Platform
  - First, make sure you have Microsoft Teams installed on your Desktop or Laptop
    - Check your email, and select Open Microsoft Teams, to join the Horizon Livefire session
      - This will have all your notes and collaborative info this week.
Step number 2
- Have a dummy email account with a fictitious name
  - This will be helpful when you do your Azure lab on Day 4. The Azure Developer account will be created later on, in the Introduction in this section.
    - 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

Section 2. Validating you understand your Microsoft TEAMS Account information

In Microsoft Teams
- Select the Teams Channel
- Look out for an icon and heading with the following:
  - An ICON with HCAI in it, with Livefire EUC - Horizon Cloud Advanced Integrations
    - A General container
      - Below, the date of your session and GEO location
  - Select the date of your session and GEO location

Note, Use the screenshot as an example to follow, your date and Geo will be different

In the Microsoft Teams Console
- Select the Attendee Accounts tab

We will now proceed to give you an overview of this information
It is critical that you document this information in your Lab guide document, together with all the resources you will get access to in this section

In the Microsoft Teams Console
- Ensure you scroll to the left and your Name
  - Document your Pod ID in the Lab document

Your POD ID will be used as an Identifier in certain parts of the Lab to ensure there are no conflicts in this environment with other attendees on this session, it critical at all times to follow the prescribed naming conventions in the labs and use your POD ID when directed

In the Microsoft Teams Console
- Ensure you scroll to the right and keep in line with your Name
- Note: The Horizon Console Accounts column and the Horizon Console Password column

This will be your assigned account and password to access the Horizon Universal Console

In your Lab Guide Document
- Document this information under Horizon Cloud Services requirement information

In the Microsoft Teams Console
- Ensure you scroll to the right and keep in line with your Name
- Note: Your assigned Domain
  - Document your assigned Domain under the Microsoft 365 section of the Lab Document

In the Microsoft Teams Console
- Ensure you scroll to the right and keep in line with your Name
  - Note : Your assigned Landing Desktop Username
  - Note : Your assigned Landing Desktop Password
  - Note : Your assigned Landing Desktop IP
- Document your assigned
  - Landing Desktop Username
  - Landing Desktop Password
  - Landing Desktop IP
    - In your Lab Document under External Landing Desktop required information

Note: This information will be required in Part 3 of this Guide to access what will be representative of on-premises resources

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 1: Overview of our On-premise and SaaS resource

LAB Architecture for this week

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

You are going to 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

Part 3: Accessing your Horizon Landing desktop

In this section we take you step by step from your where you are on your Laptop to your assigned Lab environment

Part 3: Accessing your Horizon Landing desktop

On your laptop ensure you have the Horizon Client deployed, if necessary go to https://tinyurl.com/2e85y2k9
- Download and Install the appropriate operating system Horizon Client

Once the Horizon client is installed on your laptop
- Select the + Plus sign in the top left hand corner
- In the VMware Horizon Client window under Enter the name of the Connection Server
  - type https://desktop.livefire.dev
  - Select Connect

On the VMware Horizon Client next to
- Username: enter your assigned [email protected]
- Password:enter your assigned Lab password
- Select Login

XX - Fetch from the excel sheet.

On your Horizon Desktop
- Select and right-click the DW-RDP Shortcut
- Select Edit`

In the Remote Desktop Connection next to
- Computer: enter your assigned ADDRESS to your POD
  - (Remember to note this IP Address down)
- In the Enter your Credentials window
  - Username : [email protected]
  - Password : VMware1!
- Select OK
- Select Yes

You are now on your ControlCenter server
- This is the center point of the lab environment.
- Notice you have a Remote Desktops folder.
  - (You will RDP to the majority of your resources)

On your ControlCenter server desktop
- Open your Chrome Browser shortcut
  - Notice you have a Site 1 and Site 2 Profile
- Open your Site 1 Profile
  - Familiarize your yourself with shortcuts in the Favourites bar
- Open your Site 1 Profile
  - Familiarize your yourself with shortcuts in the Favourites bar

Make it a point to save and edit forthcoming urls like your assigned

Workspace ONE UEM tenant
Workspace ONE Access tenant
Edited vCenter URL
Edited Horizon URL

Part 4: 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 4: Logging Into Workspace ONE UEM

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

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

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

Note. In your Site 1 browser. Bookmark your Workspace ONE UEM URL

Note your user name , password and Group ID in your Lab document

Part 5: 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 5: Logging into and gaining access to Workspace ONE Access

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

In the Workspace ONE Access Tenant Administrator Notification email
- Note the following:
  - Your assigned
    - Tenant URL
    - Admin Username
    - Admin Password
- Make a note of this in your Lab Document in Microsoft Teams

On your ControlCenter Server
- On your Site 1 Chrome browser
- Bookmark your Workspace ONE Access tenant sign in URL

In the Workspace ONE Login
- Under Username
  - enter administrator
- Under Password
  - enter VMware1!
- Select Sign in

In the Workspace ONE Access Terms and Conditions page
- Select Accept

PLEASE NOTE!
- Do not navigate or sign up of the EUC early access program on this Tenant

Part 6: 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

On your ControlCenter server
- On your Desktop
  - Select the DNS shortcut

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)....

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
  - Select OK

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
  - Select OK
- To close the New Host window
  - Select Done

In the DNS Manager console
- Select and right-click euc-livefire.com
  - Select Refresh
- Validate the following:
  1. That the entry are created is similar to the above screenshot,
  2. That it represents your assigned POD ID
  3. Is created in the root of the euc-livefire.com forward lookup zone

If you do not complete the above criteria, the following steps will fail and lead to a loss of lab time on your part

On your ControlCenter server
- From your Taskbar
  - Open your Chrome Browser
    - Open a new Tab
      - In the Address bar
        
        enter https://vcenter-01a.euc-livefire.com:5480

In the VMware vCenter Server Management window
- In the Username area
  - enter root
- In the Password area
  - enter VMware1!
- Select LOGIN

In the VMware vCenter Server Management window
- In the Inventory
  - select Networking

In the Networking window
- select EDIT

In the Edit Network Settings window
1. Select Network Adapter area
  - Select NEXT

In the Edit Network Settings window
1. Edit Settings area
  - next to Hostname and DNS:
    - enter vcenterXX-01a.euc-livefire.com
      - where XX is your POD ID
    - Select NEXT

In the Edit Network Settings window
1. SSO credentials area
  - next to Username:
    - explicitly type over the example
      - enter [email protected]
  - next to Password:
    - enter VMware1!
  - Select NEXT

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

On your Chrome browser
- You will have the Network update in progress window
  - which will after about 3 or 4 minutes go to Redirecting to Login Page
- On the Redirected Page
  - select Proceed to vcenterXX-01a.euc-livefire.com (unsafe)

Note! this part takes about 15 minutes to complete and to get your vCenter services to restart.

Move on to site 2 configuration in Section 2 and complete these steps later

In your Site 1 Chrome Browser
- In the Address bar
  - Select and right click the vCenter shortcut
    - Select Edit...
  - Next to the URL area
    - enter your unique vcenter address for site
      - e.g. vcenterxx-01a.euc-livefire.com
        
        Where XX is your POD ID
    - Select Save
  - In the Bookmarks bar
    - Select your vCenter bookmark
      - Select LAUNCH VSPHERE CLIENT (HTML5)

If you get any of the following messages please wait

The vSphere client Web serve is initializing
no " healthy upstream "

Give your vCenter services time to restart. Move on to Section 2 and start the naming of vCenter on Site 2

In the VMware vSphere login window
- In the Username area
  - enter [email protected]
- 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

On your ControlCenter server
- Open the Site 2 Profile - Chrome
  - In the Address bar
    - enter https://vcenter-02a.euc-livefire.com:5480

In the VMware vCenter Server Management window
- In the Username area
  - enter root
- In the Password area
  - enter VMware1!
- Select LOGIN

In the VMware vCenter Server Management window
- In the Inventory
  - select Networking

In the Networking window
- select EDIT

In the Edit Network Settings window
1. Select Network Adapter area
  - Select NEXT

In the Edit Network Settings window
1. Edit Settings area
  - next to Hostname and DNS:
    - enter vcenterXX-02a.euc-livefire.com
      - where XX is your POD ID
        
        Select NEXT

In the Edit Network Settings window
1. SSO credentials area
  - next to Username:
    - explicitly type over the example
      - enter [email protected]
    - next to Password:
      - enter VMware1!
  - Select NEXT

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

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

In your Site 2 Browser
- In the Address bar
  - Select and right click the vCenter shortcut
    - Select Edit...
      - Next to the URL area
        
        enter your unique vcenter address for site
        
        e.g. vcenterxx-02a.euc-livefire.com
        
        Where XX is your POD ID
      - Select Save
    - In the Bookmarks bar
      - Select your vCenter bookmark
      - Select LAUNCH VSPHERE CLIENT (HTML5)

If you get a no " healthy upstream " message, the vCenter services are still restarting.

Refresh your browser to validate if the services have completed their restart

You might also get a vSphere client service has stopped working message

Refresh your browser until the vSphere services have completed their restart

In the VMware vSphere login window
- In the Username area
  - enter [email protected]
- In the Password area
  - enter VMware1!
- Select LOGIN

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

In your ControlCenter server
- On your Site 1 Chrome Profile browser
  - In the address bar
    - Enter your Horizon-01a.euc-livefire.com/admin

In your VMware Horizon login
- In the Username area
  - enter administrator
- In the Password area
  - enter VMware1!
- Select Sign in

In Horizon Admin Console
- Expand Settings
  - Select Servers
- Under the Servers area
  - Select Add

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
      - enter [email protected]
    - *Password
      - enter VMware1!
  - Select Next

In the Invalid Certificate Detected window
- Select View Certificate

In the Certificate Information window
- Select Accept

In the Add vCenter window
- Select Next

In the Add vCenter Server window
- Select Submit

Section 2: Configuring vCenter to communicate with your VMware Horizon Pod on Site 2

In your ControlCenter server
- On your Site 2 Chrome Profile browser
  - In the address bar
    - Enter your Horizon-02a.euc-livefire.com/admin

In your VMware Horizon login
- In the Username area
  - enter administrator
- In the Password area
  - enter VMware1!
- Select Sign in

In Horizon Admin Console of Site 2
- Expand Settings
  - Select Servers
- Under the Servers area
  - Select Add

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
      - enter [email protected]
    - *Password
      - enter VMware1!
  - Select Next

In the Invalid Certificate Detected window
- Select View Certificate

In the Certificate Information window
- Select Accept

In the Add vCenter window
- Select Next

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

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

In the VMware Horizon Admin Console
- Expand Inventory
  - Select Farms
  - In the Farms area
    - Select Add

In the Add Farm wizard
1. Type area
  - Accept the default
  - In the bottom right corner
    - Select Next

In the Add Farm wizard
1. vCenter Server area
  - Accept the default
  - In the bottom right corner
    - Select Next

In the Add Farm wizard
1. Storage Optimization area
  - Accept the default
  - In the bottom right corner
    - Select Next

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

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

In the Add Farm wizard
1. Load Balancing Settings area
  - Accept the default
  - In the bottom right corner
    - Select Next

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

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

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

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

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

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

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

In the Add Farm wizard
1. vCenter Settings area
  - Leave the VM Compute Profile Settings as default
  - Review your configurations
  - In the bottom right corner
    - Select Next

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

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

In the Add Farm wizard
1. Ready to Complete window
  - Review your configuration
  - Select Submit

Setting up the RDS Farm for Site 2

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

In the VMware Horizon Admin Console
- Expand Inventory
  - Select Farms
  - In the Farms area
    - Select Add

In the Add Farm wizard
1. Type area
  - Accept the default
  - In the bottom right corner
    - Select Next

In the Add Farm wizard
1. vCenter Server area
  - Accept the default
  - In the bottom right corner
    - Select Next

In the Add Farm wizard
1. Storage Optimization area
  - Accept the default
  - In the bottom right corner
    - Select Next

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

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

In the Add Farm wizard
1. Load Balancing Settings area
  - Accept the default
  - In the bottom right corner
    - Select Next

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

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

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

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

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

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

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

In the Add Farm wizard
1. vCenter Settings area
  - Leave VM Compute Profile Settings as default
  - Review your configurations
    - scroll through the configurations
  - In the bottom right corner
    - Select Next

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

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

In the Add Farm wizard
1. Ready to Complete window
  - Review your configuration
  - Select Submit

Part 9: Logging into the Horizon Universal Console

We will validate your Horizon Cloud Services Console Access

Logging-into-the-horizon-universal-console

On your ControlCenter Server
- Select your Site 1 profile - Chrome browser

On your Site 1 profile browser
- In the Favourites bar
  - Select the HZN Cloud shortcut

In the Horizon Cloud Console Login
- In the Username area (Enter your teams assigned username)
- In the Password area, type VMware1!
- Select LOGIN

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
  - Kim Markez email is [email protected]
  - Rowan Tunjay email is [email protected]
- For Help Desk
  - Kevin Ikin email is [email protected]
  - Sandra Palmores email is [email protected]

About Project

Project Description :
- Create a Anywhere workspace infrastructure for a financial investment named Livefire. Anywhere workspace should run on high-availability mode
The following tools must be used:
- Horizon VDI and Application
- AVI Load Balancer
- Unified Access Gateway
- Universal Broker
- Image Management and Horizon Workspace ONE Assist
- Unified Endpoint Management.
- Workspace ONE Access.
- Office 365 for Dynamic Environment Management and One Drive integration
The following things are to be kept in check:
- You need to create a Virtual Desktop and Remote Apps
- Two Sites for High Availability and redundancy.
- Users should use cloud based Universal Broker as a single FQDN for both the sites
- For better golden master management for both the Sites, use Image Management.
- To provide L1 support to end users on their Virtual Desktop, the IT Admin helpdesk should use Workspace One Assist for Horizon
- For a Seamless user experience from any device, use Workspace ONE UEM and Workspace ONE Access
- User data shouldn't be stored on a internal drive but instead use Dynamic Environment Management with One Drive to store user data and settings.

EUC

Introduction to the Horizon Cloud Services Advanced Integration Labs

Colour Code Convention

Part 1. Account information

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

Part 3: Accessing your Horizon Landing desktop

Part 4: Logging Into Workspace ONE UEM

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

Part 6: Renaming your vCenter server

Part 7: Configuring vCenter in your Horizon Lab Infrastructure

Part 8: Setting up the RDS Farms

Part 9: Logging into the Horizon Universal Console

Part 10: Introduction to the Livefire Company

0 Comments

Add your comment

Last Updated