Friday, August 7, 2009

K2 blackpearl supports Windows Server and SQL Server 2008

Windows Server 2008 and SQL Server 2008 Supported

K2 blackpearl 4.8210.3.0 has now been released. The importance of this release is that Windows Server 2008 and SQL Server 2008 is now officially supported!!!

Here is a link to see other new features and functionality of this release -

Specifically some notice changes for 4.8210.3.0 are:

  • Out of Office has been cleaned up.
  • No more InfoPath Temporary files. What used to happen is when you click on a worklist item that is for an InfoPath client event, it would generate an InfoPath form in the form library. If the user closed the InfoPath without taking action, the form would remain in the form library. Otherwise, the temporary InfoPath form would be deleted by in the succeeding rules of the activity where the InfoPath client resides. Apparently they did this to support the Out of Office functionality.
  • Improvements for team development with TFS.
  • Debugging issues have been resolved.
  • String Tables and Environments been updated for 2003 migrations.
  • Some performance improvements for Worklist web part.
  • Plus a tons of other things discussed in the release notes…

Visual Studio 2008 is not supported just yet. I know it had been targeted for this release however it should be out soon.

There are two installers for this release. Basically there is:

  • 4.8210.3.0 – Which will support the installation of K2 blackpearl on Windows Server 2008.
  • 4.8210.2.450 – Is a release to upgrade existing 2.8210.2.X installations.

Both 4.8210.3.0 and 4.8210.2.450 are really the same from a bit perspective. You can only install 4.8210.3.0 on a machine if no K2 is installed or if the machine has K2 blackpearl version prior to 4.8210.2.X.

Both 4.8210.3.0 and 4.8210.2.450 support running on SQL Server 2008.

This past week I upgraded a client to 4.8210.2.450 and it went pretty smooth. They also had MOSS on Server 2008 in the farm but their SharePoint and SQL machines were on Server 2003. We were able to install of their Server 2003 machines to 4.8210.2.450 and then installed 4.8210.3.0 on the MOSS machine which had Sever 2008. We did not get time to fully test it but a configuration like that should work.

Release Issues

IMPORTANT - build 483 was released

No comments: