NCM 7.1.1 fresh install must be on primary NPM server

I just wanted to share with everyone some news I received yesterday while working through a new install of NCM 7.1.1. According to support, a fresh install of NCM 7.1.1 must be installed on the primary NPM server and can not be separated. If you would like to have your primary NCM server on a separate server, you must first install an older revision (in the 7.0 range) and upgrade from that and it should theoretically work. Unfortunately, if you attempt to perform a fresh install of NCM 7.1.1 on a separate server, it may appear to install properly, but will create issues in the database and potentially affect other modules (in my case IPAM would not work because of this).

ncm.standalone.png

Justin T. Lewiss

Find more posts tagged with

ncm_7.1.1

standalone

fresh_install

Accepted answers

All comments

shuth

I ran into the same problem and after some research I found the following article/blog post:

In this article they mention that integrated separate servers are no longer supported in 7.1+ and recommend moving to a single server integrated or standalone as it will be desupported.

NCM 7.0 can be hosted on a separate server from NPM 10.2, and be integrated.
NCM 7.1 can be hosted on a separate server from NPM 10.3, and be integrated, but only in an upgrade scenario. A fresh installation of NCM 7.1 does not allow for this deployment mode. This deployment will be entirely desupported in a future version of NCM (i.e. upgrade won't be possible either). We recommend moving away from this config by moving your NCM on the same platform as NPM, if you want to keep them integrated.