How to install OCS2009-DBUpgrade

[tweetmeme source=”stalehansen” only_single=false]On several OCS 2007 Enterprise installations this patch was not that easy to install when you are using SQL 2008 backend database. Here’s what I had to do to install this patch

To apply the hotifx, you must have the following software installed.

  • OCS administration tools
  • MS SQL Native Client
  • If you decide to install SQL 2008 Client Tools, SQL 2005 Service Pack 2 (SP2) Backward Compatibility must also be installed.
  • To install the  SQL 2005 Service Pack 2 (SP2) Backward Compatibility you need to download and install
    • Microsoft SQL Server 2005 Management Objects Collection
    • Microsoft SQL Server 2005 Backward Compatibility Components
  • Finally run the patch with the following command when on a OCS Enterprise deployment
    • OCS2009-DBUpgrade.msi POOLNAME=poolname

If the installation failes check Scott Oseychik’s post about SQL won’t allow update here: http://blogs.msdn.com/scottos/archive/2009/08/21/installation-of-ocs-2007-r2-hotfix-package-969834-may-fail-if-sql-settings-have-been-changed.aspx

View the full technical article here: http://support.microsoft.com/kb/969834

8 thoughts on “How to install OCS2009-DBUpgrade

  1. Thanks so much for this. I don’t know why it is above Microsoft to make this stuff easier. Those were the backward compatible things I needed.

  2. Should the db update be done before or after the server updates? Also did you run the db update on FE OR BE?
    Thanks a million
    P

    • I recommend doing the DB update after the server updates, but before you reboot the FE server. Usually I run this update on the FE, as long as firewall ports and the SQL prerequisites are available I think that is the simplest way to go about it.

      • Thank you so much for this information. We’re patching our two front end servers before upgrading to Lync. I did have one question. We have two front ends but no load balancer (we switch the DNS record if we need to “cut” over). My plan is to patch the passive server and the DB, then cut the clients over with the DNS change, and patch what will now be the passive FE.

        If I patch the passive server and the DB, will the clients disconnect that are using the active FE server?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.