Getting started in your realm of use involves some very important
effort which can make the difference between success and failure. This
is not technically oriented effort and so might be overlooked in the
flurry of hardware acquisition/installation, software downloading and
familiarization and the rest of all that fun!
At this point you have the starter VCL system running, and your
internal systems staff has done a thorough job of using it in test mode.
Now is the time to go outside to the rest of the campus. Train some
early faculty adopters and teaching support staff. Have them try out
the VCL with their students - work with them and smooth out any rough
edges in the training and/or the campus culture. Getting them used to
the VCL and getting used to helping users use the VCL productively are
not technical systems chores, but are very important.
You may find some surprises. For example, people who haven't run a
remote system before (whether through RDP or X) may be taken aback by
the need to possibly install and then use the client software on their
own desktop or laptop. Even though most computers come with either RDP
or X, very few, if any, come with both. Many users have used neither.
It doesn't take a lot of effort to bring them up to speed, but
neglecting them can cause them to have unhappy experiences and be lost
as users and supporters. Look through the past posts on this list for
some "gotchas" in this area.
Now you can move to real production - and that's just scaling up what
you already have running. Scaling up the hardware is straight forward,
although the networking does increase in complexity with the need for
additional outside-the-chassis switches to allow inter-chassis
There are more issues which arise with scaling up into production
mode - to be discussed next.