K2 Package and Deployment is part of K2 blackpearl. The K2 Package and Deployment tool uses a Microsoft Management Console plugin, and optionally a PowerShell snapin for deployment scripting.
We recommend that packaging and deployment only be performed on the K2 Server. While packaging and deployment may be performed on client machines, performing these operations on the K2 server reduces network traffic.
The following applications are required for installation of K2 Package and Deployment:
To install Package and Deployment, refer to the installation and upgrade path below:
Clean K2 blackpearl installation |
Upgrading to the latest K2 blackpearl |
|
---|---|---|
If Package and Deployment was not previously installed | Package and Deployment will be installed automatically. |
|
If Package and Deployment was previously installed | N/A | Package and Deployment will be automatically upgraded to the current version. |
If Package and Deployment was not previously installed, it will not be installed by default when upgrading to the latest version of K2 blackpearl. This is the default behavior in order to ensure that the K2 administrator can choose the optimum installation location, particularly in the case of distributed environments.
When the installation is complete, Package and Deployment can be launched from the Windows Start menu link as below:
Video | Links | Learn | Support |
No videos found for this article K2 on YouTube
No Additional links found for this article
No self-learning content for this article Try some scenarios...
No relevant support links available for this article
|