NetXMS Forum

Ok. So it was an oversight by me. The error is caused if you do not enable zoning in the configuration. I would assume, after reading other issues involving "Incompatible Operation," that when you see Incompatible Operation, it means that that particular option is not turned on. I just happened to stumble across the "Enable Zoning" option, while looking for another option in the configuration.

Most of the servers we have deployed are Debian/Ubuntu, primarily because that is where most of our collective knowledge here resides. That being said we use NetXMS on Ubuntu 16.04. The stability difference between Windows and *nix systems is tremendous. Most of our workstations are on Windows though.

To answer your follow up question, we use all headless (non x-win) systems, except for our 1 Windows Server. I believe, and this will probably spark a fiery debate, that to learn the most from a system, you have to have intimate knowledge of the console. GUI's are great for a lot of things, but the meat-and-potatoes comes from the console/ssh sessions.

Sorry to bump an old post. 

Hey all,

I am fairly new to NetXMS, so this post may be trivial and most likely an oversight by me, somewhere. I was using an older version of NetXMS and had no problems before. I both upgraded my older version and installed a new instance on our stack, in hopes of remedying the issue.

I am using Server and Management Console (Windows) versions 2.2.11 and I am trying to add a Zone to my network. When adding I get an "Incompatible Operation" error. I have searched for causes of this issue, but have not come up with anything. I am hoping that remedying this issue, also remedies my other issues.