Updating KanBo to No Instances version (Azure installation)


Before the update starts, update KanBo App and SQL databases.

See the backup manual here.


1. Download the newest KanBo 2.7 package and extract it.

2. Open the old web.config of your KanBo and the web.config from the newest package.

3. Start editing the most recent web.config. To avoid issues please remove entire section for on-premises configuration.

 <!-- <on premise> -->
      <provider id="sp" type="Sharepoint" spHostUrl="{SPHOSTURL}" clientId="{CLIENTID}" issuerId="{ISSUERID}">
        <!-- signer is described below, this one must contain a private key -->
        <signer type="X509SignerFromStore" storeName="My" storeLocation="LocalMachine" key="Thumbprint" value="{Thumbprint}" />
      <!-- </on premise> -->

4. Delete the following line in <plugins> section.

<package name="search-db" />

and replace it with your old Solr configuration

<plugin alias="plugin-config-executor.multiplex-config" user="{USER}" pass="{PASSWORD}" allow-all-certificates="true" solrurl="{https://SOLRADDRESS:PORT/solr}">
        <plugin alias="search-docs.solr"></plugin>
        <plugin alias="search-cards.solr"></plugin>
        <plugin alias="search-boards.solr"></plugin>

Make sure you have your Solr Core updated to the version for KanBo 2.7. If not, proceed with this instruction.

5. Fill parts of {CLIENTID}, {CLIENTSECRET}  accordingly with values from “old” web.config. In {SPHOSTURL} add address of the Site Collection where KanBo is installed.

 <!-- <o365> -->
      <provider id="sp" type="Sharepoint" spHostUrl="{SPHOSTURL}" clientId="{CLIENTID}" clientSecret="{CLIENTSECRET}" />
<!-- </o365> -->

5. Leave the License Key empty. You will fill it later during the update. 

6. Compare the following settings.

    <!-- <o365> -->
    <add key="IsOffice365" value="true"></add>
    <!-- </o365> -->
    <add key="KanBoAllowOpenbook" value="false"></add>
    <add key="KanBoAllowPublicBoards" value="true"></add>
    <!-- A path in your KanBo IIS Site used to identify KanBo instances, you can set any value, for example setting intranet here will make it look like this: https://kanboapp.kanbo.com/intranet/1 -->
    <add key="KanBoInstancePath" value="intranet"></add>
    <add key="KanBoLicenseKey" value=""></add>
    <!-- Determines whether myboards are disabled or enabled -->
    <add key="KanBoMyBoard" value="true"></add>
    <!-- override server's timezone if necessary
      <add key="Timezone" value="US Mountain Standard Time" ></add>
    <!-- Determines whether License warnings are shown -->
    <add key="KanBoLicenseWarnings" value="true"></add>
    <add key="KanBoEmailNotifications" value="true"></add>
    <add key="KanBoUserCanSyncProfile" value="false"></add>
    <add key="KanBoUserCanEditAvatar" value="true"></add>
    <add key="KanBoUserCanLinkProfile" value="false"></add>
    <add key="KanBoUserCanEditProfile" value="true"></add>
    <add key="KanBoDebuggingTokenIssuerPassword" value=""></add>
    <add key="KanBoIncomingMail" value="false"></add>
    <add key="KanBoIncomingMailDomain" value=""></add>
    <add key="ErrorReportingUrl" value="https://sendto.kanbobugs.net/kanbo_error_reporting"></add>

7. Adjust the connection strings. In KanBo 2.7, Instances and Profiles databases won't be needed further. You must only add a connection string to KanBo Content DB. You can simply copy the connection string value from the old web.config and adjust name of your Content database.

    <add name="KanBoContentConnectionString" connectionstring="Server=tcp:{AZURE SERVER ADDRESS,1433};Initial Catalog={KANBO CONTENT DATABASE};Persist Security Info=False;User ID={USER};Password={PASSWORD};MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;" providername="System.Data.SqlClient"></add>

8. Make a .zip archive from the freshly adjusted package.

9.Navigate to your Azure website folder via FTP or KUDU service (add .scm just before azurewebsites.net e.g https://kanbo-online-kanbo.scm.azurewebsites.net, then select Debug console -> PowerShell).

10. Delete everything under Sites -> wwwroot (ensure you have backup of those files).

11. Now drag and drop you .zip archive into left upper part of KUDU service.

Updating KanBo (Azure backend part) KanBo Update

12.  After almost every KanBo update, you need to upgrade its databases. Before proceeding make sure that you prepared a full database backup.

Please visit UpgradeDatabases.aspx page to fire upgrade scripts on KanBo databases. You can do it by entering the following URL address:

/Pages/UpgradeDatabases.aspx just after first part of your KanBo IIS URL. Please make sure to turn on your KanBo Web App on Azure on II Site before entering this page.

An example:

If your URL is https://oc-kanbo.azurewebsites.net/intranet/1# (remove bolded part of URL) your address to upgrade page will be https://oc-kanbo.azurewebsites.net/Pages/UpgradeDatabases.aspx

https://YOUR KANBO NAME.azurewebsites.net/Pages/UpgradeDatabases.aspx

When upgrade of databases is complete, you will see the following communicate:

You can see the entire log of the Migration in the kanbo.log.

13. Now enter your KanBo site. Please adjust the address and remove the last section of the address (intranet/1).
If you address was https://mykanbo.azurewebsites.net/intranet/1, now it will be https://mykanbo.azurewebsites.net/.

14. You will be redirected to Setup. Click on Automatic Setup.

In couple of seconds, you will be presented with your KanBo ID. Send this ID to us, so we can generate a license for you.

15. When you receive a license for your new KanBo ID, add it to your web.config (in Azure Kudu Service) in the following section.

 <add key="KanBoLicenseKey" value="{LICENSE KEY}" />

16. Go to KanBo Setup once again, select Advanced and hit KanBo ID. 
Once it appears, click on License Status. You should see information regarding the license on the right.

Click on Exit to go back to your KanBo.

17. As the last step, repair Document Sources -see the manual here.

Updating KanBo Search Component

1. KanBo Search Component's core must be updated in order to work fine with the recent KanBo update.

See the manual for updating the Search's core here.

2. Open the web.config and update entry for the Search.

  • Find the <plugins> section
  • Add or adjust the following entry (you can copy it from the old web.config and make adjustments - only the url changes as the core's name is added to it).  

<plugin alias="plugin-config-executor.multiplex-config" user="{SOLRUserName}" pass="{SOLRUserPassword}" 
allow-all-certificates="true" url="https://{SOLRUrl}:{SOLRport}/solr/{YourSOLRCoreName}">
   <plugin alias="search-docs.solr" />
   <plugin alias="search-cards.solr" />
   <plugin alias="search-boards.solr" />
<plugin alias="search-users.solr">

Is this article helpful for you?