This document is intended to provide a detailed overview of the three main stages of a deployment with vSpace:
We will cover in this document the following:
2. Host Deployment and Tuning
Below you'll find a consolidated list of resources related to each of these three deployment stages. We encourage anyone who is planning a deployment with our products to go through this checklist to gain an overview of what to expect from this process.
Note that while we have a wide variety of vSpace-based products, they all commonly use the vSpace software and the communications protocol UXP 2.0.
For this reason, the vast majority of configuration, troubleshooting, and server tuning resources should be pretty similar for whichever vSpace-based thin client you use.
1. PRE DEPLOYMENT PLANNING
1.1 Review the Product Manuals.
The documentation section of our website (https://www.ncomputing.com/en/support/documentation) stores all our product manuals and Quick Install Guides. These will serve as a source of information and reference for the operation of the devices and the vSpace platform.
1.2 Networking infrastructure, online connection and security.
If you are using our network compatible products, the best setup will be a Gigabit network, form point-to-point, with CAT5e cable or better. Our product will by default work on a LAN (same subnet) and DHCP, however further configurations will need your networking expertise in order to ensure that TCP/UDP protocols pass trough safely and without delay.
Cross-segment or WAN deployment, is better achieved with modern think clients like the RX or EX series thin clients. L300s I'm not optimized for WAN deployment.
For more information on set up please see the following article:
Also, vSpace requires a fluid connection to the Internet, 24/7. Interruptions could lead to a lack of synchronization from your local deployment to our Management Portal in the cloud. This could affect your licensing and may impact your deployment. Please ensure that you have a constant online access.
For your security filters, firewall, antivirus and security layer related items, there will be ports and executables needed to be open for best performance.
1.3 For deployments on Virtual Machines.
vSpace Pro, should work on a virtual machine environment. However, some configurations will need your expertise. You can always consult our support team
if you have a question.
A few articles that can be helpful:
• General tips
• We recommend that you use GEN 1 VMs.
• Hyper-V deployment recommendations.
1.4 For Linux Deployments.
General Information (Applicable to L250/L300/L350 thin clients, M300 thin client and MX100S standard connect thin clients.)
1.5 Review Microsoft's OS Licensing Guidelines.
If you are using a Microsoft Windows operating system, you will need to be aware of Licensing requirements.
• About Microsoft Licensing and NComputing products:
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. In the other hand, Server OS type (2008 R2, 2012, 2016, 2019, 2022) will be prefect for MultiUser deployments, which is, sharing one operating system and delivering sessions to multiple thin clients.
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, 2019 and 2022
• Extra licensing requirements from Microsoft for multiuser deployments starting on the 2019 and forward
1.6 Review Specifications of your prospect Session Host Server.
• This Host Scaling Guide will be very helpful to determine the type of hardware you need in relation to how many concurrent sessions are going to use:
1.7 Confirm that the operating system you have chosen is compatible and supported.
1.8. Make sure that you are aware of any needed licensing in order to connect your devices to vSpace.
As mentioned earlier, we have a wide array of vSpace-based devices and some may have different licensing requirements than others. Please consult our tech support if you are in doubt.
2. HOST DEPLOYMENT / TUNING
2.1 Perform a clean install of the OS and review the best practices of installation.
• First time installation tips:
2.2 Perform vSpace Pro Platform and installation.
• vSpace Pro Tips and Best Practices on installation and registration:
2.3 Configure Power Management.
It is recommended that all hibernation and power saving features be disabled on vSpace hosts to prevent complications with user sessions and terminal connections.
2.4 Configure network security, firewall and antivirus.
Links to articles of interest are shown above on section 1.2.
2.5 Configure your Server operating system to deliver the sessions with a "look and feel" of a 'Desktop" operating system.
A Server OS has the capability to change the User Experience of sessions presented to the access terminals. (e.g., 2008 R2 to deliver a Windows 7 desktop)
Here are some helpful links that can get you started:
• For Server 2008 R2:
• For Server 2012 and 2016:
2.6 Create a New Local User and Configure RDS User Group.
A good example on how to do this, is show on these articles:
• For Windows 10:
• For Server 2012:
• For Server 2016:
2.7 Setup your licensing Server. (for MultiUser deployments)
In section 1.5 we give you helpful links related to this topic. However, keep in mind that the configuration of the Licensing Server needs to be done "per user" and not "per device".
You can either have the Licensing Server on a separate machine or you can add this role to your vSpace Server. This is an acceptable role that can be shared with your NComputing server.
As mentioned on the said section 1.5, Be aware of the latest requirements for multiuser sessions, per Microsoft starting on 2019 and 2022.
2.8 Do not mix Server Roles with your vSpace server.
It is a good practice to do a separation duties on sever roles, i.e., have a server dedicated to vSpace, have a separate server to manage Active Directory and have another for Domain Controller, etc.
An example article of this practice:
2.9 Clone Drive / Create Backup Image.
It is at this stage that we recommend that administrators create a Master Image of their host configuration using an imaging/backup utility of choice.
One more thing...
Our NComputing Technical Support is available If you have any questions regarding this or other NComputing technical issues or concerns in your environment, please feel free to contact us or review additional self help technical content at the following link.