How long does it take to replace ZNS VMS with CORTROL? Can I run both clients on the same computer? Here are some frequently asked questions and answers about the ZNS-to-CORTROL migration process.
In the era of digital progress and globalization, the product and service lifespan has become shorter. The technologies develop rapidly, demanding everyone and everything to conform — or be consigned to oblivion. Here, at Ganz, we agree with the famous character who said, "Change is the essential process of all existence". We choose to keep up with the progress and make headway in the development of the surveillance software.
Ganz ZNS has reached its end-of-life and we are somewhat proud of it. We have worked hard to replace it with the new generation software: CORTROL product family, based on more than 15 years' experience. While CORTROL retains many things from ZNS — architecture, recorder core, device integrations, — we have significantly revised and optimized it, and have also added a whole bunch of new features, the latter being nearly impossible with ZNS. CORTROL also gained a brand new, fresh looking interface and a new HTTP API aimed at a faster and simpler way of integration.
And now that you have come to the point of replacing the software.. here comes the dreadful migration. But is it really so appalling?
In this article, we dispel a few myths about Ganz ZNS-to-CORTROL migration.
Truth: the latest ZNS versions allow you to export the configuration, and you can import it into any CORTROL server from the generated XML.
The configuration export from ZNS is partial, yet it covers the most time-consuming part: cameras. This is possible because CORTROL, in its core, has support for all the devices that were there in ZNS. As for the rest of the settings, simply look them up and set up the same pattern in CORTROL: CORTROL Console allows to do that in no time at all.
Use exported ZNS configuration in CORTROL Console
Use exported ZNS configuration in CORTROL Console
Here are several other settings that are not exported automatically but may matter. Examine these before getting rid of ZNS completely:
Permissions in CORTROL are much more advanced in CORTROL. Hence, there is no way to convert ~15 ZNS permissions into the complicated scheme of user privileges in CORTROL. But the good news is that user management in CORTROL is well thought and you do not have to go through the countless wizards anymore. Tip: use groups for even faster management!
As for the event and action (E&A) rules, most of ZNS's events and actions exist in CORTROL as well; however, an automatic transfer is not feasible because we have re-engineered the E&A engine for CORTROL. Again, thanks to its optimized user interface, CORTROL event & action management allows you to set up the same rules much faster. On top of that, CORTROL servers now have additional features in the E&A Configurator for even more complex scenarios.
Truth: with everything mentioned above, it takes less than one hour to migrate to CORTROL Premier. You will spend approximately 10 minutes installing CORTROL and transferring the configuration. The rest of the time, as per our experience, you will have to dedicate to handling Windows updates — in case the server has never received any ever since ZNS was installed.
So, if you have been keeping Windows up to date during the server operation, the actual total downtime for the software migration will be under half an hour for each server. With CORTROL Global, you can pre-configure all the recording servers - even if they are offline. This means the recording server downtime will be equal to the amount of time required to uninstall the old software and install CORTROL. Even for an operating system running on an HDD instead of an SSD this will take less than 15 minutes, and is more likely to take about 5 minutes event with the most slowpoke way of clicking "next-next-next".
CORTROL Global has one more advantage that helps minimize the downtime during the migration. Once you have set up at least one CORTROL Recording server, you can temporarily assign cameras from other servers to it. Then, after setting up the rest of the servers, simply move these cameras to the servers they should belong to! In such a way, you will retain the video archive from those cameras while their original servers are offline. And yes, you can go ahead and use this lifehack when taking servers down for maintenance :)
Truth: : while the two software suites are indeed not compatible, we have prepared a special version of ZNS Client, which can be launched on any machine running CORTROL Monitor.
We understand that during the migration period of the whole project there are both old and new servers present in the system, and it is often necessary to connect to both from one and the same client machine in the control room or similar place. Any component of the new generation software — Ganz CORTROL — cannot be installed together with ZNS Server or ZNS Client. It is so by design: the two video management systems share several libraries so it is safer to keep them apart to avoid interference. Yet, having collected some feedback, we have developed a workaround and here is the CORTROL-friendly version of ZNS Client.
The special ZNS Client edition is called Portable ZNS Client and you can download it from our website by going to Downloads > Software > Ganz ZNS > Other downloads. To get it running on your CORTROL machine, follow three simple steps:
The application is installed in the C:\Users\<Windows_user>\AppData\Local\Ganz\Ganz ZNS Client portable\ folder by default, and we recommend that you keep the default path.
This client application has the same — exactly the same! — functionality and requirements as your good old ZNS Client. It is 32-bit but it can co-exist with any CORTROL bit version: both 32- and 64-bit CORTROL, be it server or client, can be installed on the same machine.
Truth: in fact, all older third-party integrations are compatible with CORTROL.
Over the years, ZNS has become a favorite of many. Chances are, you are also one of those having integrated ZNS with third-party software using ZNS SDK — Client Kit. For some integrations, you may need to re-compile the application that is using the SDK, but you certainly do not have to apply any modifications whatsoever.
Furthermore, CORTROL has a new, simplified HTTP API. This means that now, instead of "serious" programming, you can build the communication between an external module and CORTROL merely using HTTP requests, which is way less difficult and much more elegant. Our own additional modules, license plate and face recognition, also use HTTP API for "talking" to CORTROL servers.
Have you faced any other challenges while migrating? Contact us.