The following article is a detailed process and tips for installing our vSpace Pro platform (vSpace Pro LTS, vSpace Pro Enterprise Edition).
As an additional supplement,
this article will deal with all other aspects of Pre-Deployment and vSpace Host deployment.
1. IMPORTANT CONSIDERATIONS BEFORE STARTING
• Use the right Operating System. Use our
Compatibility Matrix as reference to find if your Windows or Linux OS is compatible with our platform. Also, if you will use Microsoft Windows to share multiuser sessions, check the reference page for
Microsoft Windows Multiuser Licensing. This article will focus on the Windows installation.
• Use a clean, fresh, formatted server. If the purpose of this server is to share sessions, (multiuser) then, a recent install of a fresh compatible Server OS is best. After, motherboard drivers install should follow. These should be fully installed and updated directly from the manufacturer's website, eliminating the need for OS generic drivers. On the OS, install Windows Updates as well.
• Delay antivirus installation. You can include the antivirus program
after our platform has anchored fully in the host computer and registration has taken place.
When you
contact support for any installation issues or troubleshooting purposes, the host should also be antivirus free.
• Open up your firewall. It is recommended to turn off your firewall during installation. After opening the firewall and for all security software and hardware we provide a comprehensive list of ports and executables you will need to keep open for the correct operation of vSpace in your network and also for the vSpace Manager to communicate with our cloud services. These are mentioned
here.
•
Online connection 24/7 is needed. It is assumed that if you are using vSpace Pro, you were always have an uninterrupted internet connection. This is important for the proper synchronization of your local environment with our cloud services. If this is not in place, your environment may not work as intended or may eventually stop working. If you are in an environment where there is no Internet connection, and never will be, there is an option for vSpace to work, under certain conditions. This is mentioned at the end of this article.
WARNING About Aged Devices:
(manufactured prior to January 1, 2015)
Your account will need to be properly licensed with vSpace AMP in order to connect to vSpace Pro according to our
compliance policy.
Also, an environment that includes aged devices, will
require a permanent online connection. (Aged devices will not work in an off-line setting, even if vSpace
AMP
has been associated to the account.)
2. KNOW HOW VSPACE PRO WORKS
Our platform consists of 4 main parts interacting together:
vSpace Pro Basic Scheme
1.
Clients. vSpace Pro delivers sessions to a wide array of hardware and software products.
2.
vSpace Server. Our platform installs on the PC, deploys our UXP 2.0 connection protocol to the clients for session access and provides at the server a modern admin console with an intuitive user interface and user experience.
3.
vSpace Manager. Think of it as a broker. Through it, you can centrally manage your local software licenses and premium features allocation to connected vSpace Servers. For more info, check out
this article. vSpace manager can be installed on the same vSpace host or can reside in a separate computer, depending on your needs, we'll discuss this below and different scenarios are discussed
here.
4.
Management Portal. This is your cloud based dashboard and services, all accessible through
www.ncomputing.com. It provides remote access to your NComputing software licensing, premium features and more, via any web browser.
Please note: The vSpace Manager and the Manager Portal synchronize daily. A fluent internet connection is needed.
The system will also warn you of the need to reboot at the end of the process.
Reboot when the installer is done.
LINKING EVERYTHING TOGETHER
Once you reboot the computer, you will need to start piecing everything together. vSpace will do the heavy lifting, but, you will need to make sure that everything is lined up.
First, we need to register. open the vSpace Manager application. Please
be sure to register, as it is a required process
.
Launch the vSpace Manager (You can launch the vSpace Manager from the Start Menu Search Bar or Programs list)
and you will see the Registration Wizard.
Follow the prompts and register with your already created account used to login to the ncomputing.com website. Your server will immediately be associated with your account.
NComputing.com / Management Portal Accounts are unique and when you register a server to a particular account, it becomes permanently associated to it, unless you format your server or ask technical support to help you, your vSpace Server cannot be linked or migrate to another account.
Once you have registered, then, open the vSpace Console. Select Manage Servers and make sure that your server is there and is green-lit.
The last step will be to connect the terminals. For as long as these are in the local LAN and under the same subnet, (the first three octets of their IP address match the devices will find their vSpace server in your network.
For multiple servers deployment, if you only installed the vSpace Manager, make sure you register it so it can be linked to your account and be ready to receive connections of the other vSpace Servers. If you only installed the vSpace Software, when you launch it for the first time, (after the installation and reboot) it will display a connection window. You will be able to enter the IP address of your vSpace Manager. Once you do, your vSpace Server will connect to the vSpace Manager and will be ready for devices to connect.
Next, let's connect your NComputing devices.
If you are using a hardware device, it should discover your vSpace Server, nevertheless, every time you install a new version, or update your software, you need to always update the firmware of your devices.
Generally, as soon as the vSpace Console discovers the devices, you will be able to push the firmware to them. Try to do that with one of the terminals, upon success, then you can start working on the rest.
The process for the L Series devices is described
here.
It is essential to have the exact matching firmware build with every version of vSpace. When the firmware is mismatched, certain functions may not work or the access devices may refuse to connect.
If you have a device with an NComputing Client software like
vSpace Pro Client or
LEAFOS, be sure that you have the latest version of your client software installed.
ADDITIONAL NOTES ABOUT REGISTRATION
• Remember that "a
lways on", internet connection is
assumed. As mentioned before,
vSpace Pro is a platform that requires online connection. Therefore the registration should be done online, always.
• If you have no online connection at the site of deployment.
In rare cases where there is no online connection, like a secure facility or in a remote village, "Off-line Registration" is available in vSpace 11.x LTS.
Off-line registration is only offered on vSpace Pro 11.x LTS Edition.
This will freeze the platform to a current state when the registration took place. Any changes done in the platform will require another Off-line Registration. This choice needs to be carefully calculated. If later on, an internet connection is detected in the server, it will detect a discrepancy as Internet is not supposed to be allowed in your server. Your environment will be locked up until you contact tech-support for assistance.
Remember the warning About Aged Devices: (manufactured prior to January 1, 2015)
Even properly licensed with vSpace
AMP for vSpace Pro according to our
compliance policy,
an online connection is required. These devices cannot be used in a server with no internet connection and they will not benefit from an off-line registration setting.
5. OPERATING SYSTEM CHORES
AFTER INSTALLING
1. Create users like you would on any regular computer. For Server OS, here is a quick tutorial:
Note: Make sure you got unique credentials and passwords for all your Windows Users. Your users will not be able to login if they don't have a password in their sessions.).
Also, using the same user credentials for multiple terminals is not supported and not encouraged).
MICROSOFT LICENSING
If you are using a Microsoft Windows operating system, you will need to be aware of Licensing requirements.
• About Microsoft Licensing and NComputing products:
In short:
Desktop type operating system (Windows 7, 8.1, 10, 11) is best suited for
VDI 1:1 deployments, meaning, one thin client accessing one operating system.
Server type (2008 R2, 2012, 2016, 2019, 2022 and Multipoint Server) will be prefect for
MultiUser deployments, which is, sharing one operating system and delivering sessions to multiple thin clients.
Windows Server 2019, Windows Server 2022 and Windows 11 are supported only on vSpace Pro Enterprise Edition
A
MultiUser
scenario, will require CAL licenses and the proper familiarity to setup a
Licensing Server. Our documentation here will help you:
• For Server 2008 R2
• For Server 2012
• For Server 2016
• For Server 2019
• For Server 2022