hi my name is Peter Bjork this video will
provide you with a quick guide on how to deploy the legacy versions
of workspace one access connector but why would you deploy an older
version of the connector well with version 2001 of access we
re-architected the connector the connector is now stateless
microservices which is much easier to deploy
and scale up and down but in version 2001
we do not have the feature parity with old connectors
until feature parity you have to pick your connector version depending on the
use case if you are planning on integrating
thinner packaged applications into your catalog you must use the
connector version that was released with version 3.3 which is version 2018 of the
connector and for horizon or citrix use cases you
should use connector version 1903 please note it's not supported to mix
connector versions and the connector version must be the
same or lower than the service an older service
version doesn't support newer connector versions see the release
notes for each access version to know which connector versions are supported
let's cover at a high level what you need to do to deploy
a legacy connector the first step is performed within the access admin
console you must create a new connector instance
for legacy connectors that generates an activation code
you deploy the connector and pair it to the access using the activation code
once the connector is up and running and paired to the access service
you configure the directory sync and authentication methods
you configure your access policies and then you can configure integration with
your thinapp repository citrix and horizon environments by
creating virtual apps collections for thinapp integration you must use
the connector released with the version 3.3
of identity manager which is the old name of workspace one access
but the connector is available as both a linux and windows version
and it's only the linux version supporting thinapp integration
the linux version of the connector is a virtual appliance you deploy
using vmware vsphere during the ovf deployment wizard
you must specify network settings and the fqdn
and you must also have both an a and ptr dns record pointing to your
connector for horizon or citrix integration you
can use the connector version 1903 this connector version is only available
as a windows installer you download the installer and run it on
a windows server during installation you can choose to
specify a domain user to run the service this is recommended if you want to
connect to your active directory for usersync using integrated windows
authentication or IWA
now let's have a look at deploying both versions of the connector and i'll start
with a version 2018 connector first i need to choose if my workspace
one access should use legacy or the new connector architecture
and in my case of course i pick the legacy connector
since i will use virtual apps i create a new connector and generate
the activation code and i copy the code since i will have to
enter it into the connector during setup make
sure that you copy the whole activation code
not leaving any characters at the end
next i deploy the linux virtual appliance
i point to my downloaded virtual appliance and specify what name
i want the virtual machine to have within vsphere
i need to fill in the ova properties
and specify the fqdn and gateway
and i typically leave domain name and domain search path empty
and i'm finishing it all by entering dns ip address and the netmask
once the virtual appliance is deployed and powered on
i need to run the web-based setup i need to specify passwords for the
linux user root and ssh user as well as for the local connector admin
the local admin is used to access the web admin console
of the connector
paste the activation code and the connector should now be paired with the
access service but before i can connect to my thinapp
repository i must connect to an active directory
i want to use integrated windows authentication which means
i need to join my connector machine to the domain
and i specify which groups and potential individual user objects i want to sync
into access
once i have a connection to my active directory
i can now create a virtual apps collection
and in this case i pick thinapp as the source type
i need to give it a name and then i specify the path to my thinapp
repository
optionally you can specify an active directory user to access the share
once that is set up i run a sync and when finished i can see my thinapp
packages within the admin console
if you need to change the configuration of the connector
you can access its web console by browsing to it
on port 843 using https for access you enter the local admin
password specified during the initial setup
via the web console you can change the certificate used by the connector
and you can upload root certificates if you need to add new root certificates to
the trust store you can configure an external syslog
server and change the local admin password as well as the passwords for
the linux local users root and ssh user
and it's also here you can download the logs from the connector to help with
troubleshooting
so now let's move over to a 1903 connector
i've already created a new connector within the access admin console just
like i did with the version 3.3 connector and i have also
copied the activation code i run the connector installer on my
windows server
i specify the fqdn and what port i wanted to use
and since i want to use windows integrated authentication when
connecting to my active directory i specify a domain user to run the
service
once the installation is completed i run the web setup wizard
since version 1903 of the connector runs as a windows service
i'm only asked for the password of the local connector admin
and next i paste the activation code to pair it to the access service
setting up the directory is identical to what i showed before so
let's skip directly to set up the horizon virtual apps collection
i give it a name and then i add a pool
i need to type in the fqdn to one of my connection service
and provide a user who has access to my horizon environment
i save the settings and then i need to specify what connection url or
fqdn my clients should use when connecting to horizon
i perform a sync of my virtual apps collection and
in this example i only have one entitlement
but this is now visible within the access catalog
for connector specific settings you can access the connector's web console using
port 843 and https here you can change the
certificate of the connector and configure an external syslog server
you can change the local admin password and if needed specify an outbound proxy
you can download the log bundle to help with troubleshooting
and change the server used for time synchronization
and that was it make sure to visit techzone.vmware.com
for more technical content