Submit a Ticket
Cannot connect to a Windows session after vSpace Pro installation. (Secure Boot)
This article is for customers who have installed vSpace Pro and are not able to connect any hardware or software clients to their vSpace host server.
UPDATE DECEMBER 2017: Issue has been resolved with vSpace 10.5
This is not an NComputing vSpace configuration however, you will need to
the existing vSpace installation and then
Secure Boot in the BIOS before installing again.
Page 9 in our release notes for the latest vSpace Pro highlight a configuration setting that needs to be disabled before installation. See below note and attached file for reference.
• Secure Boot: The Secure Boot feature of current PC models needs to be disabled temporarily
install of vSpace Pro 10.3. After finishing the installation it can be turned back on.
Since there are several motherboard manufacturers, the interface and steps could be slightly different for this process, make sure and identify your specific system model.
Below is an image of one of the many examples of the system BIOS where you would toggle this setting.
Here are a couple links showing how to navigate in different BIOS.
See below link for a related article with Hypervisors/virtual machines and Secure boot.
2017.06.06 vSpace Pro 10.3.4.2 Release Notes.pdf
vspace pro client
Updated: 21 Dec 2017 05:19 AM
Help us to make this article better
Cannot Connect to vSpace Pro
Primary vSpace Services in Windows
“You need administrative rights to install this software. Installation Failed.”
vSpace Pro Installation - Tips, References and Process Detail
vSpace Pro Client 1.9 Release Notes
© 2016 NComputing. All Rights Reserved.