Upgrading > Upgrade Overview

The OfficeStatus software solution is comprised of components that are installed either on the server or client side.

Each OfficeStatus software component has a four-part version number associated with it (e.g. 1.5.0.0). The four parts of the version number correspond to the major, minor, revision, and build numbers (respectively).

When upgrading your OfficeStatus deployment, a key consideration is the version compatibility of the server and client side components. OfficeStatus takes a simple and effective approach to this issue, outlined below.

•	When the major / minor component version numbers are different:

o	OfficeStatus Client cannot communicate with an older version of OfficeStatus Server.

o	OfficeStatus Client can communicate with an newer version of OfficeStatus Server.

•	When the major / minor component version numbers are the same:

o	Client and server components can communicate freely.

The reasoning behind this approach is straight-forward: certain features within OfficeStatus Client require communications level support within OfficeStatus Server. Changes that could potentially impact communications compatibility between client and server components are only ever made in new major / minor version releases.

As noted above, these compatibility rules only apply when the client and server side components have different major / minor version numbers. When the major / minor version numbers are the same (OfficeStatus Client v1.5.1.9 with OfficeStatus Server v1.5.0.1, for example), all components will interoperate freely.

Upgrade Version Rule

This information can be distilled into the following simple rule:

When upgrading to a newer major / minor version (e.g. 1.0.x.x to 1.5.x.x), upgrade OfficeStatus Server first, then upgrade OfficeStatus Client installations.

Doing so will always ensure proper communications compatibility between client and server components.