This document is intended to provide a detailed overview of the three stages of an L-series, M-series, and vSpace Client deployment:
• Host Deployment
• NComputing Product Installation.
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 all these product series are very similar to each other in terms of the software they use and the way in which they interact with a vSpace Pro 10. For this reason, the vast majority of configuration, troubleshooting, and server tuning resources should be pretty similar for whichever product you use.
1. PRE DEPLOYMENT PLANNING
1.1 Review the Product Manuals.
The documentation section of our website 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 Be aware of your networking infrastructure.
If you are using our network compatible products, the best environment is 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 expertise in order to ensure that TCP/UDP protocols pass trough safely and without delay.
• If you have questions about cross-segment or WAN deployment, you may find this article informative:
• Regarding the ports and executables needed to be open for best performance, please consult this article:
1.3 For deployments on ESX or Hyper-V.
vSpace Pro 10, 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:
• We recommend that you use GEN 1 VMs.
• Hyper-V deployment recommendations.
1.4 For Linux Deployments. (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:
In short: Desktop type operating system (Windows 7, 8.1, 10) is best suited for VDI 1:1 deployments, meaning, one thin client accessing one operating system. Server type (2008 R2, 2012, 2016 and Multipoint Server) 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
1.6 Review Host Scaling Guide 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 Understand the vSpace Pro 10 Platform.
• vSpace Pro 10. Tips and Best Practices on installation and registration:
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.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. For 2008 R2, instructions for changing these settings can be found in the Windows Tuning Guide linked in section 2.6.
2.4 Configure network security, firewall and antivirus.
Links to articles of interest are shown 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.
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.
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.
Last Edited: May 18, 2020