OCS R2 Cumulative Update 6 issue…

Microsoft Released OCS R2 CU 6 (kb 983472) in end of July , 2010 on the same day I applied the updates running a test ending up with an issue. A well operated OCS R2 server was stopped with failed Front end services just after the CU6 application.

The CU6 applied 13 major updates bundled in a single installer listing below

image

The update KB983472 causing this problem and front end services started up once uninstalled this update selectively.

Microsoft immediately released a workaround as to install OCS2009-DBUpgrade.msi (http://support.microsoft.com/kb/2032834) and reinstall KB983472 to rectify the problem.

Immediately next day Microsoft removed kb 983472 and re-released http://support.microsoft.com/kb/968802/en-us article which includes the solution in the order of installation.

This release is tested and works fine…ready to go…Smile

OCS R2 Standard to Enterprise upgrade

If anyone suppose to upgrade an OCS R2 Standard server to OCS R2 Enterprise on Windows Server 2008 R2 platform using same hardware by following uninstall and reinstall option, these points might useful in before hand.

OCS R2 does not provide in place upgrade to Enterprise from Standard resulting some additional steps as below,

  1. Create new OCS R2 enterprise pool and add a new OCR R2 enterprise server to Pool (preferably in VM environment if additional physical server is not present)
  2. Move all SIP users accounts to new Enterprise Pool
  3. The new Enterprise server is used for uninterrupted services while the transition
  4. Uninstall OCS R2 standard server on physical server
  5. Install OCS R2 Ent on the same server so that we’ll get 2 enterprise servers running in same Pool
  6. Uninstall temp (VM) Enterprise server from the pool and the Swap operation is done.

Issue

  • If you try to install OCS R2 Enterprise on the same server which was prepared by decommissioning previous OCS R2 Standard server (unformatted), there will be an unexpected problem of starting up below 04 services in first place.

image

  • the reason behind that is these services are not getting removed by uninstallation operation.

Workaround

  • These services must be wiped off from services by deleting the 04 registry values given below

image

image

  • Restart the server and install OCS R2 Enterprise would go as a charm…