Verifying the Microsoft Azure Setup
PART 1
This is an overview of deploying the Unified Access Gateway script for VMware Horizon
- On your ControlCenter server,
- Go to the Downloads folder
- Select and open the uagdeploy folder
- observe the contents
-
In the uagdeploy folder
-
select the uag2-advanced.ini,
- Copy and Paste so that you have a backup of the original file .
-
select the uag2-advanced.ini,
- In the uagdeploy folder
- select uag2-advanced
-
right-click
- In the Menu
- select Edit with Notepad++
- In the Menu
-
right-click
- select uag2-advanced
- In the NotePad++ application
- next to name
- change to UAG-HZN-01a
- Next to source change
- next to name
source=\\horizon-01a\Software\UAG\euc-unified-access-gateway-23.12.0.0-23175218_OVF10.ova
- Next to target change it to:
target=vi://[email protected]:[email protected]/Region01A/host/Bangalore/esxi-01a.techseals.co
-
Scroll down in your NotePad++ window
- Next to ds=Local Disk 1 change to ds=CorpLun01a
- Next to #diskMode=thin change to diskMode=thin
- Change the following network settings to:
- netInternet=CorpDMZ01
- netManagementNetwork=CorpDMZ01
- netBackendNetwork=CorpDMZ01
- defaultGateway=172.16.20.1
- deploymentOption=onenic
- ip0=172.16.20.10
- netmask0=255.255.255.0
- routes0=172.16.20.0/24 172.16.20.1
-
Scroll Down
- Change dns=192.168.0.10 to
dns=192.168.110.10
-
Scroll Down
-
Under sessionTimeout=39600000
- Add
-
Under sessionTimeout=39600000
allowedHostHeaderValues=uag-hzn-avi01.techseals.co
- Under [SSLCert]
- change pfxCerts=sslcerts.pfx to
pfxCerts=C:\certificates\WildCard_2024.pfx
- In the [SSLCertAdmin] section ,
- change pfxCerts=sslcerts.pfx to
pfxCerts=C:\certificates\WildCard_2024.pfx
- Under the [Horizon] section change proxyDestinationUrl=https://192.168.0.209 to
proxyDestinationUrl=https://horizon-01a.techseals.co
gatewayLocation=external
disableHtmlAccess=false
healthCheckUrl=/favicon.ico
proxyDestinationIPSupport=IPV4
smartCardHintPrompt=false
queryBrokerInterval=300
proxyPattern=(/|/view-client(.*)|/portal(.*)|/appblast(.*))
matchWindowsUserName=false
windowsSSOEnabled=false
proxyDestinationUrlThumbprints=ae 59 3f 46 28 2b bb 49 42 56 41 08 d3 16 4e a9 9b af 50 3a e1 04 c9 b6 15 7a d9 33 41 b6 b5 08
proxyDestinationPreLoginMessageEnabled=true
- Scroll down and Change
- tunnelExternalUrl=https://uag2.horizon.myco.com:443
- blastExternalUrl=https://uag2.horizon.myco.com:443
To
tunnelExternalUrl=https://uag-hzn-01a.techseals.co:443
blastExternalUrl=https://uag-hzn-01a.techseals.co:8443
-
Scroll down and Change
- In the pcoipExternalUrl section change pcoipExternalUrl=10.20.30.90:4172 to:
pcoipExternalUrl=172.16.20.10:4172
- SAVE THE .ini File
Part 2 - Section 1
In this section, we will deploy the first of two Unified Access Gateway using a Powershell Script
-
On your ControlCenter server ,
- Launch the powershell shortcut from the Start Menu
-
We will set the script execution is set to unrestricted.
- Execute the following command.
Set-ExecutionPolicy -scope currentuser unrestricted
When Prompted select Y
- Within the powershell interface
- type the following command
cd downloads\uagdeploy
- Execute the following command
.\uagdeploy.ps1 -iniFile uag2-advanced.ini
- When you get a security warning type: R
- When you get a second security warning type: R
- When prompted to enter a root password for UAG-HZN-01a,
- type:- Pa$$w0rd
- when prompted to confirm type Pa$$w0rd
- When prompted to
- Enter an optional admin password for the RESP API management access for UAG: type Pa$$w0rd
- When prompted to Re-Enter an optional admin password : type Pa$$w0rd
- When prompted whether or not to join the customer experience program type Yes
- In the PowerShell script
- when prompted:
- "Fingerprint will be added to the known host file"
- "Write 'yes' or 'no' "
- enter yes
- when prompted:
- When prompted to
- Enter password for the .pfx type: 1234
- When prompted to confirm type 1234 again.
- When prompted the password for [email protected]
- Type Pa$$w0rd
- Your virtual Appliance deployment will now start , it will take between 5 - 10min to deploy. Proceed to step 8
- Review the deployment once the setup has completed
- On your ControlCenter server
- On your Site 1 - Bangalore Browser
- open a new Tab
- from the Bookmarks Bar
- select the UAG-HZN-01a bookmark
- from the Bookmarks Bar
-
login to your UAG server by entering the following
- Admin Username : admin
-
Admin Password: Pa$$w0rd
- select Login
- open a new Tab
- On your Site 1 - Bangalore Browser
- On your UAG Admin Console
- under Configure Manually
- click the Select button
- under Configure Manually
- On your UAG Admin Console
- Under General Settings
- next to Edge Service Settings,
- move the toggle to the right
- next to Edge Service Settings,
- Under General Settings
- On your UAG Admin Console
- To the right of Horizon Settings,
- select the Gearbox
- To the right of Horizon Settings,
- In your UAG Admin Console
- Under Horizon Settings
- Browse and familiarize yourself with config, we will be changing some of the settings in a future exercise
- Logout from the UAG Admin Console
- Browse and familiarize yourself with config, we will be changing some of the settings in a future exercise
- Under Horizon Settings
Part 2 - Section 2
In this section, we will deploy the second of two Unified Access Gateway using a Powershell Script
- On the ControlCenter server
- Go to your Downloads > uagdeploy folder
- In the uagdeploy folder
-
copy the uag2-advanced.ini
- paste this to the uagdeploy folder
- select the uag2-advanced - Copy (2).ini
- rename to uag2b-advanced.ini
-
copy the uag2-advanced.ini
- In the uagdeploy folder
- select the uag2b-advanced.ini
-
right-click
-
from the menu
- select Edit with Notepad++
-
from the menu
-
right-click
- select the uag2b-advanced.ini
- In the uag2b-advanced.ini file
- edit name=UAG-HZN-1a
- to
- name=UAG-HZN-01b
-
scroll down to the Network configuration
- just below diskmode=thin
- edit name=UAG-HZN-1a
- In the uag2b-advanced.ini file
- edit ip0=172.16.20.10
- to
- ip0=172.16.20.11
- ip0=172.16.20.11
- to
- scroll down to the PCOIPExternalURL configuration
- edit ip0=172.16.20.10
- In the uag2b-advanced.ini file
- edit the following
- tunnelExternalUrl=https://uag-hzn-01a.techseals.co:443
- blastExternalUrl=https://uag-hzn-01a.techseals.co:8443
- TO
- tunnelExternalUrl=https://uag-hzn-01b.techseals.co:443
- blastExternalUrl=https://uag-hzn-01b.techseals.co:8443
- AND
- pcoipExternalUrl=172.16.20.10:4172
- TO
- pcoipExternalUrl=172.16.20.11:4172
- edit the following
- In the NotePad++ application
- select SAVE
-
On your ControlCenter server ,
-
from the Start Menu
- launch the PowerShell shortcut
-
from the Start Menu
-
We will set the script execution is set to unrestricted.
- Execute the following command.
Set-ExecutionPolicy -scope currentuser unrestricted
When Prompted select Y
- Within the powershell interface
- type the following command
cd downloads\uagdeploy
- Execute the following command
.\uagdeploy.ps1 -iniFile uag2b-advanced.ini
- When you get a security warning type: R
- When you get a second security warning type: R
- When prompted to enter a root password for UAG-HZN-01b,
- type:- Pa$$w0rd
- when prompted to confirm type Pa$$w0rd
- When prompted to
-
Enter an optional admin password for the RESP API management access for UAG:
- type Pa$$w0rd
- When prompted to Re-Enter an optional admin password :
- type Pa$$w0rd
- When prompted whether or not to join the customer experience program
- type Yes
-
Enter an optional admin password for the RESP API management access for UAG:
- When prompted to
-
Enter the password for the specified [SSLcert] PFX certificate file wildcard_2024.pfx:
- type 1234
-
Enter the password for the specified [SSLcertAdmin] PFX certificate file wildcard_2024.pfx:
- type 1234
-
Enter the password for the specified [SSLcert] PFX certificate file wildcard_2024.pfx:
- When prompted to
- for the [email protected] password
- type Pa$$w0rd
- Your virtual Appliance deployment will now start , it will take between 5 - 10min to deploy. Proceed to step 8
- for the [email protected] password
- Review the deployment once the setup has completed
This concludes the Deployment of your UAG Servers on Site 1
0 Comments
Add your comment