This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
This explains how to remove K2 on one of two application servers, which are currently load balanced by a virtual IP address entry
in DNS which can be modified to point to the one server.
Before You Begin
On a production environment, please arrange downtime and also ensure no users are connected to the environment before making any changes.
Please complete the following steps:
1. Update NLB to have only the servers where K2 will remain, in the resource group.
2. Execute uninstall of K2 on servers where K2 is to be removed.
3. Restart K2 services on servers where K2 is to remain.
4. Inspect the “server.server” and “HostServer.Server” tables in the K2 Database to ensure that entries to the old servers have been removed.