I would surely follow mark's link and take a well note on that segregation on "Ïnstall" and "configure". Those are tow different steps.
The install step in the installation is what commonly is indicated/known as the installation.
The configuration is different as it can be more seen as System integration - Wikipedia, the free encyclopedia or Configuration design - Wikipedia, the free encyclopedia
Before doing those steps you can need several desktop clients up and running. And those clients can be needed to be adjusted after all servers are up and running. (sasenv.ini)
Your question is hitting an area SAS institute is missing the alignment what is happening in the world.
As example Linux Directory Hierarchy: Oriented to the Software Parts is giving the background on folder namings with the ratio why to do that in Linux and the usage of rpm. (SDW is not aligned to that)
You want to install the SAs clients on a Citrix client. That is also a signal something is going on the desktop side. The SAS java clients are as zero impact to be copied. The challenge with those are the ini- files (xmx limits java runtimes etc). With Eguide, Base and AMO there is thight MS dependicy by the windows register, the first two are being installable by a MSI approach in 9.4 .
---->-- ja karman --<-----