Microsoft RDS Environment
|1. Login VSI in Short|
|5. Target Environment|
|6. Active Directory|
A typical Login VSI 4.x environment consists of the following (optional) components:
Login VSI Dataserver / VSIshare
The Login VSI Dataserver / VSIshare is the server where Login VSI is installed on. This server contains all data used by Login VSI. The following list contains the most important components and functions:
- Management Console
- Session Monitor
- Data Library
- Logfile store location
More information concerning the VSIshare can be found later on in the documentation.
Login VSI Launcher(s)
The Login VSI Launcher(s)are machines that launch sessions. The Launcher(s) simply connects to the environment using a commandline and starts a session.
More information concerning the Launcher(s) can ben found later on in the documentation.
The Active Directory houses all of the Login VSI test users and GPO settings. These users and GPO can be created manually or by using the Login VSI AD-Setup script found in the Management Console.
- Login VSI Group Policies
- Login VSI Users
- Login VSI Group
More information concerning the Active Directory and Login VSI can be found later on in the documentation.
RDSH Farm, RDGateway and RDCB
These parts together is what we call the Target Environment. This is where are the virtual machines (or physical) are located. The RDS machines can either be Virtual or physical machines, it does not matter to Login VSI as long as a connection to that server can be made Login VSI will work.
As for the RDgateway / RDCB, since these are optional the connection to them is faded out. But if these components are used in the environment Login VSI can connect through these components, creating a real-world connection scenario.
More information concerning the Target Environment and Login VSI can be found later on in the documentation.