Product Release Notes:

NComputing vSpace Management Center 3.3.1

Product: NComputing vSpace Management Center for vSpace 7
Version: 3.3.1 (build 3.4.17)
Supported Operating Systems:
Microsoft Windows Server 2008 R2 SP1
Supported NComputing Access Devices:
N-series with firmware version 1.5.0
L-300 with firmware version 1.7 or newer
M-300 with firmware version 2.1 or newer
Supported vSpace Server Version:
vSpace Server 7.1
This release replaces the previous vSpace Management Center 3.3.0 release and
expands management support to include newly released features and
functionality for N-series access devices, introduced as of firmware version 1.5.0.
The sections that follow include important information on additional changes,
notes for installation and known errata. Please read each section carefully.

Key new features:

The following features have been added to vSpace Management Center with this
version:

N-series Firmware v1.5.0 Feature Management

New menus and configuration options have been added for use with the
network, security, and display settings recently added to N-series access
devices via firmware v1.5.0. These include:
o
o
o
o

Enterprise Wi-Fi Features and Security for N500w

Discrete Secondary Monitor Settings
Additional Connection and Security Options
Performance optimizations and more

NOTE: Update all vSpace Management Center servers to 3.3.1 before

attempting to update N-series devices to firmware 1.5.0. For more
information on these new N-series features, consult the N-series firmware
v1.5.0 release notes.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 1

Improvements to Server Stability and Failover

vSpace Management Server Failover has been improved within certain
environments. Specifically: several intermittent issues that impacted
database replication between servers that share a common switch have
been resolved resulting in a much more robust solution.
For additional information on VMC database backup and propagation
functionality, consult the following KB article:
http://www.ncomputing.com/kb/FAQ-How-frequently-does-vSpaceManagement-Center-backup-its-database_415.html

Post-install Server Role Changing

Previously, the Slave Only or Master/Slave roles had to be defined at the
moment of installation and were permanent. Administrators can now
change a servers role after VMC has been installed. This new feature can
be found under the Administration -> Management Server Administration
menu. Note that the conversion process takes 3-5 minutes while the
database propagates from server to server, and that servers currently
performing the Master role for a Management Zone cannot be converted to
Slave Only.
IMPORTANT: In this initial implementation, the only supported post-install
role change is from Master/Slave to Slave Only. Administrators wishing
to convert a Slave Only server to a Master/Slave server will need to
reinstall VMC. [VMC-3086]
NOTE: While vSpace 7 servers will display the option to switch between
Master/Slave and Slave Only within VMC, this functionality is not yet
implemented for vSpace 7 and should only be used to change the roles of
VMC servers.

Fixed in this Version:

The following known issues have been resolved in this version:

Device Name Character Limit

A known issue allowed device names to exceed the intended maximum of
15 characters. This has been resolved, and attempts to enter a device
name larger than 15 characters will result in an error message.

Printer Removal
Attempting to remove individual printers from a device through vSpace
Management Center previously resulted in all printers associated with the
device being removed. This has been corrected, and printers can now be
removed individually as intended.

Additional Notes and Errata Items:

The following section covers addition notes not included in the sections above,
and describes any known issues that may exist with this release.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 2

Multiple Master Servers in Single Management Zone [VMC-2080]

It is currently possible for a second VMC server, when joining an existing
Management Zone as Master/Slave, to connect as a second Master
server. Intended design would stipulate that the second server would
automatically assume the Slave role due to a Master server already
being in place. There is currently no known workaround for this issue.

802.1x Certificate Configuration

Due to a current limitation, the 802.1x network feature may not be fully
configurable when creating a new profile. For now, administrators can
fully configure 802.1x by editing existing profiles once they have been
created, or on a per-device basis from the device list.

Master / Slave Election Behavior

A known issue can result in the Master VMC server within a zone going
offline when a vSpace Server in the same zone goes offline. By design,
the vSpace server going offline should have no effect on the VMC server,
but in this case it can cause the VMC server to go offline as well. If there
is a third VMC or vSpace Server within such a zone, it will pick up the
Master role (by design) due to the current Master being offline. There is
currently no known workaround for this issue.

Rejecting Management Zone Join Requests [VMC-2773]

When a server attempts to join a Management Zone, the Master server
for that zone is given the option to accept or reject the request. Currently,
selecting the requesting server and clicking reject a) fails to reject the
request, and b) disables the accept / reject / remove buttons on the
Management Server Administration menu. This is also true if any other
already joined server is selected. There is currently no known workaround
for this issue.
Furthermore, if in the above scenario the Accept button is pressed it does
not function, though it does not disable other buttons as with the Reject
button.

Client Certificate Display

In some situations, client certificates added to a device from the View /
Edit configuration menu will not show up when returning to view the
devices configuration after theyve been applied. In these cases, the
certificates show up correctly while editing the device. The display issue
occurs when leaving device configuration and returning to view it again.
This should be resolved in a future build.

Zone Requests Automatically Accepted

Under the Management Server Administration menu, there is a checkbox
that, when checked, will automatically accept zone join requests from
other servers. When disabled, the intended functionality is that no server
will be added to the zone without manual authorization. Currently, a
known issue is allowing servers to show up automatically as part of the
zone in spite of this checkbox being unchecked. This will be resolved in a
future build.
vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 3

VNC Password Update [VMC-2809]

Currently, if an administrator edits ONLY the VNC password setting on a
device, disabling the password requirement while making no other
changes to the device, the VNC password state is not pushed to the
device as intended and the password remains active. This will be
resolved in a future build.

Date/Time Settings
If the edit settings checkbox is disabled in the Date/Time tab, the previous
settings are lost. Intended functionality would preserve the previous
Date/Time settings so that they can be easily re-enabled by checking the
edit settings checkbox. This will be resolved in a future build.

Wifi Settings Certificate Display

Security certificates displayed within the Wifi settings tab (N500w
configuration only) can extend beyond the viewable area of the text box.
The lack of a horizontal scroll in this box can prevent the admin from
viewing the entire certificate. This will be resolved in a future build.

Resolution Settings in L-series Profiles [VMC-2789]

An issue is currently preventing changes to resolution settings in L-series
device profiles. There is currently no known workaround for this issue.

N-series Device Reset [VMC-2659]

An issue is currently preventing vSpace Management Center from being
able to remotely reset N-series devices from the Manage Devices menu.
Note that this does not affect the profile update process. There is
currently no known workaround for this issue.

Stand-alone Mode [VMC-2792]

The newly added Stand-alone mode is not currently functioning as
intended. This will be resolved in a future build. In the meantime, this
feature should not be used.

HTTP-500 Error When Editing N-series Wifi Network Settings [VMC2750]

An issue is currently causing the vSpace Management Center browser

window to crash if the administrator attempts to add or edit a wifi network
to an N500w device. For now, wifi network additions and changes should
be made on the device end. This will be resolved in a future build.

Small Wallpaper Files [VMC-2782]

Attempting to upload a small wallpaper (testing results indicated this
consistently happened with files around 10KB) file to VMC resulted in the
VMC browser window crashing. Wallpapers of this size should be added
directly to devices for the time being. This will be resolved in a future
build.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 4

N-series Wallpaper [VMC-2658]

An issue is currently preventing vSpace Management Center from
pushing wallpaper updates to N-series deices. This will be resolved in a
future build.

SSID List May Appear Blank After Applying Profile Update

[VMC-2935]

A known issue may cause the SSID of an N-series device, when viewed
through the view/edit configuration menu in VMC, to appear blank after Nseries settings are changed via a profile update.

Redirection Policy Tab Appears Blank [VMC-2930]

A known issue may cause the Redirection Policy tab, under the
Peripherals section of an N-series profile, to appear empty, lacking its
standard features. This can be resolved by exiting and re-entering the
device / profile management menu.

N-series Device Passwords On Profile Creation [VMC-2927]

The device password settings are not functional from within the profile
creation menu of VMC, when creating a new profile.

SSID Key Length Under 8 Characters [VMC-2924], [VMC-2923]

Currently, it is possible to enter an SSID Key of less than 8 characters.
This can lead to a number of network-related issues for the device
including disconnects, and should be avoided. This will be resolved in a
future update.

N-series Device Enters Offline State after SSID Entry Removal

[VMC-2915]

In some cases, removing an SSID entry from VMC may result in the Nseries device in question going offline. If a device becomes unresponsive
as a result of this, close the VMC window, turn off the N-series device, log
back into VMC, then start the device back up. It is recommended that
SSID edits be made from the device end to avoid this issue.

Installation Hang During Manual Zone Request [VMC-3024]

When installing vSpace Management Center, the installation process may
hang if the user attempts to manually join a Management zone by
specifying the IP or Hostname of a server within that Zone. This does not
appear to affect installations that are configured to automatically join a
Zone, only manual join attempts. There is currently no known workaround
for this issue, and installation attempts that are disrupted in this way may
require a host reboot.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 5

N500w Wireless Network Disconnect on Remote Settings Update

[VMC-3049]

In some situations, an N500w may lose its network connection when the
SSID settings are updated along with other settings (which can include
display settings, for example). This may require that the network settings
be adjusted from the device end to resolve the loss of connection.

Cannot Edit N-series USB/Serial Devices Containing / [VMC-3042]

USB and Serial devices added to an N-series device form the device end
that contain a slash / in the name cannot be edited or removed via
vSpace Management Center. Alterations to these devices must be made
from the device end.

N500w Network Settings (New Profiles) [VMC-3043]

Network settings made during the creation of a new N500w profile may
not save properly. To be certain that network settings are applied to the
profile as desired, verify the network settings by re-opening the profile
after it has been created.

N500w May Not Switch Automatically to Wireless Connection [VMC3044]

If an N500w is connected via a physical Ethernet cable and its profile is

then updated via VMC to include a wireless SSID, the device may not
automatically switch to the wireless connection if its Ethernet cable is
disconnected. In these cases, it may be necessary to switch connection
types from the device end.

Cannot Resend Join Request After Rejection [VMC-3058]

Currently, it may not be possible to resend a Zone join request during
installation if the first request is rejected. If this occurs, attempt to rejoin
the Zone in question from the Management Server Administration menu.

VMC becomes unresponsive when switching from Slave Only to

Master/Slave [VMC-3086]
Currently, when using the new post-install role changing feature to switch
a Slave Only host to the Master/Slave role, the VMC service will
become unresponsive and the server will be inaccessible. Currently, this
failure requires that VMC be uninstalled and reinstalled on the host in
question. That being the case, Administrators should use the post-install
role changing feature ONLY to change Master/Slave hosts to a SlaveOnly role.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 6

First-time Installation:
The vSpace Management Center installer will sequentially install Java JRE, Apache Tomcat and then vSpace
Management Center. Follow the steps below to proceed through the installation:
1. Launch the installer: vSpace_Mgmt_Center_3.3.1_Installer.msi
(click Run on the initial pop-up window)

2.
3.
4.
5.
6.
7.
8.

Select Default Installation

Accept the NComputing End User License Agreement
Follow the steps for the Java JRE Automatic Installation
Accept the Java/Oracle License
Follow the steps for the Apache Tomcat Automatic Installation
Accept the Apache License
Choose Tomcat Components
a) Tomcat (Required)
I.
Core (Required)
II.
Service Startup (Not required, but recommended)
III.
Native (Not required, but recommended)
b) Start Menu Items (Not required)
c) Documentation (Not required)
d) Manager (Not required, but recommended)
e) Host Manager (Not required, but recommended)
f) Examples (Not required)
9. Choose Apache Tomcat Specific Settings
a) Server Shutdown Port (Default recommended)
b) HTTP/1.1 Connector Port. Remember this setting (8080 by
Default)
c) AJP/1.3 Connector Port (Default recommended)
d) Windows Service Name (Default recommended - Tomcat7)
e) Create Shortcuts for All Users (Optional)
f) Tomcat Administrator Login
Username/Password(Recommended - take note)
g) Roles (Default recommended)

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

10. Select Location of Java's JRE installation

directory
11. Select Location of Apache installation
directory
12. Finish the installation (Recommend - Run
Apache Tomcat)
13. Reboot the system.

Page 7

Verify Installation:
Once you have installed vSpace Management Center check the following items to confirm a successful
installation and to familiarize yourself with the services that will be running on your server:
1. Validate that all required services are "Started" (Start Button->Run->"Services.msc")
a. Apache Tomcat 7.0 Tomcat7
i. It is recommended that the Startup Type for this service be "Automatic".
If this service is set to "Manual" or "Disabled", you will need to start
the "Apache Tomcat 7.0 Tomcat7" service manually at every boot.
b. NCMSWinService
i. It is recommended that the Startup Type for this service be "Automatic".
If this service is set to "Manual" or "Disabled", you will need to start
the "NCMSWINService" service manually at every boot.
2. Verify Apache Tomcat Installation
a. Open your browser and navigate to the Apache instance (Port specified during Tomcat Install)
i. http://localhost:8080 || http://127.0.0.1:8080 || http://Server.ip.address:8080
b. Make sure the default confirmation Apache Tomcat page loads
c. If the default page times out, make sure the Apache Tomcat Service is
"Running". In addition, check your firewall settings to be sure that
Tomcat and port 8080 are unblocked.
3. Verify VMC WAR Application is running properly
a. Open your browser and navigate to the VMC Instance (Use same port as Apache)
i. http://localhost:8080/vmc
b. If the VMC login Screen appears, login with the default username/password
i. Username: vmcadmin
ii. Password: vmcadmin
c. If the VMC login screen does not appear and you receive the message "Management
Server is unavailable," check to make sure the "NCMSWinService" is still running.
d. If the VMC login screen does not show up and you receive an HTTP 404 error, check to
make sure that the vmc.war file exists in the Webapps directory under the Apache
Tomcat installation directory. If the vmc.war file does not exist, re-install
the vSpace Management Center package.
4. Note the IP address of your server, as you will need to enter this into your managed devices and to
connect to it from your browser.

Configure Devices for Connection to Management Zone:

By default the device will auto-discover vSpace Management Center servers on the same subnet. For
configuration of devices connecting across subnets, you can use DHCP tags to auto-populate the location of the
vSpace Management Server or you can enter it manually during device setup. Refer to the N-series device
manual and the vSpace Management Center manual for more details on connecting your device to the
management server.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 8

Contacting Technical Support and Additional Resources

Visit the NComputing Knowledge Base at www.ncomputing.com/kb for

more information.
To request Technical Support, please visit the NComputing Support
page at www.ncomputing.com

Disclaimer
Information contained in this document may have been obtained from internal testing or from a
third party. This information is for informational purposes only. Information may be changed or updated
without notice. NComputing reserves the right to make improvements and/or changes in the products,
programs and/or specifications described herein anytime without notice.
All NComputing software is subject to NComputing intellectual property rights and may be used only in
conjunction with Genuine NComputing hardware and in accordance to the NComputing End User Licensing
Agreement and Terms of Use.

www.ncomputing.com
Copyright 2003-2013 NComputing, Inc. All rights reserved. NComputing is the property of NComputing.
Microsoft, Windows and XP are registered trademarks of the Microsoft Corporation. Other trademarks
and trade names are the property of their respective owners. Specifications are subject to
change without notice. Performance may vary, depending on the configuration of the shared computer.

vSpace Management Center 3.3.1 (build 3.4.17)

Dec 5, 2013

Page 9