vSpace Management Center

Best Practice: How to join N-Series devices to vSpace Management Center

This brief guide applies to vSpace Management Center 3.6 and later versions.  vSpace Management Center 3.3.1 for Window is no longer supported and it is highly recommend that you migrate to the most current version vSpace Management Center Appliance.

In previous versions of vSpace Management Center devices within the same subnet could autodiscovery the VMC, join and add their configuration to the database.  The functionality has been deprecated in current versions of VMC as it lead to inconsistent and sometimes catastrophic configuration database corruptions. 

N Series devices can still be automatically added to vSpace Management Center, by using DHCP scope options.
If you are unaware of how to create a custom DHCP scope option, here are some resouces:
  • For DHCP on Server 2008R2/Server 2012: https://technet.microsoft.com/en-us/library/dd183679(WS.10).aspx
  • For other DHCP solutions you will need to research how to create custom DHCP scope options
Requirements for the Custom Scope Option: 
  • Name: vSpace Management Center or VMC
  • Data Type: String
  • Code: #171
  • Description: vSpace Management Center for N Series Management
  • String value: (IP address or Fully Qualified Domain Name of VMC):1284 notice the port number is attached.
Requirement on N Series device:
Be sure the Autodiscovery box is unchecked and the N-Series device receives a DHCP assigned IP address.

Article: 1014

    • Related Articles

    • VMC Search results are Truncated (RESOLVED)

      Issue: Using  VMC 3.7.17.476 witn N-Series 2.4.2.1. When performing a device search for devices such as Retail the search results may not display all devices that meet the search criteria Solution: This problem has been addressed in VMC 3.7.20 Please ...

    • Configuring N-Series devices with custom DHCP scope options

      NComputing recommends using the most current version of vSpace Management Center for N-Series device management, however, there may be a need to configure some settings on an N-Series device via DHCP scope options. Specifically the Tag (171) for ...

    • How do I get support for my N-Series device?

      The N-Series product family includes the 400, 500, 500W, and 600. The N-Series 400 has reached its “End of Support” date and is therefore limited to self-help via our KB articles in this portal. The 500, 500W, and 600 will reach end of support ...

    • L-series Legacy: Device cannot get IP address from DHCP

      If you are using terminals that are not compatible with vSpace Pro 11 or Enterprise edition, likely, these are outdated and need to be upgraded.   You can see our new line of products and consult your sales representative or authorized partner about ...

    • Firmware update availability for N-series devices

      N-series devices (N400, N500, N500w, N600) will reach End-of-Life on the following schedule: N400: December 30, 2019.  N500: December 31, 2020 N500w: December 31, 2020 N600: December 31, 2020 Firmware for these devices are no longer in development. ...