Before installing any software update, please refer to TEC90813 and DWN59018 in the Other Useful Articles section below. These articles detail RM's recommendations regarding software update installation and support.

Any references to Community Connect 3 in this document apply equally to RM Smart-Tools 3.

Important: You may install this Security Update on networks running Service Release 3, Service Release 4 or Service Release 5.

We recommend that you apply this Security Update as soon as possible.

IMPORTANT: During the installation of HFXCC3080, the Update Package List procedure and the allocation of a new Microsoft security update package must be done MANUALLY. Please ensure that you fully complete ALL steps in the How to install the Security Update section of this article.

This Security Update should be installed on to all Community Connect 3 servers detailed in the Who should install this Security Update? section below.

HFXCC3080 contains the following Microsoft^� security update:

1. MS04-028: Buffer Overrun in JPEG Processing (GDI) Could Allow Code Execution (833987) - for Community Connect 3 servers running Windows Server 2003 and Community Connect 3 workstations.  This applies to all Community Connect 3 Domain Controllers so that the package can be allocated to all Community Connect 3 workstations. This also applies to any member servers that are running Windows Server 2003.

More information on the issues resolved by this update is available from Microsoft's website (http://www.microsoft.com).

You should install this Security Update as soon as possible if you are running a Community Connect 3 network.

HFXCC3080 should be installed onto the following Community Connect 3 servers:

• All Community Connect 3 domain controller servers running Windows 2000 Server
• All Community Connect 3 domain controller servers running Windows Server 2003
• All Community Connect 3 member servers running Windows Server 2003

NOTE: You must have already installed at least Service Release 3 before installing HFXCC3080.

IMPORTANT: Community Connect 3 servers running Windows Server 2003 will need to be restarted in order to install this Security Update completely. You should therefore plan to install the Security Update out-of-hours to minimise disruption to your network if you are using any servers with this operating system.

If you are unsure which (if any) of your Community Connect 3 servers are running the Windows Server 2003 operating system, please refer to TEC209390 in the Other Useful Articles section below.

1.      Select the HFXCC3080.exe file to download.

2.      Choose to "Save" the file, browse to the location you wish to save it to and click Save.

3.      When it has downloaded follow the installation instructions below to install the Security Update.

(NOTE: If you previously started to install the Security Update but cancelled the operation, follow the installation instructions in the Installing after cancelling a previous install section below)

1.      Download HFXCC3080.

2.      Log on to your first Community Connect 3 domain controller as Administrator (not SystemAdmin) and copy the Security Update to a temporary location (e.g. D:\temp).

3.      Run the Security Update by double-clicking the self-extracting executable file (HFXCC3080.exe).  The Security Update will extract files automatically and run the RM Installation Assistant to begin the installation.

4.      When prompted, click Continue.

5.      The installation will proceed automatically.  When prompted that the RM Installation Assistant has finished, click Finish.

NOTE: If this server is running Windows Server 2003 then reboot the server for the Security Update to be applied fully.

6.      Repeat Steps 2-5 at all your other Community Connect 3 domain controllers.

7.      Also repeat steps 2-5 at any member servers (e.g. DAMMS or MIS servers) which are running Windows Server 2003.

NOTE: Ensure that any server running Windows Server 2003 is rebooted for the Security Update to be applied fully.

8.      When all relevant Community Connect 3 servers have had the Security Update applied open the RM Management Console at a domain controller or a workstation

9.      In the RM Management Console, expand Workstations, right-click on Main Site and choose to Update Package List. Click Yes to confirm this action.

NOTE: If you have a multi-site network, run this Security Update on every server in all sites and then update the package list once only for each site.

10.  HFXCC3080 provides a new workstation package but does not automatically allocate it. You should allocate this new package to all your workstations at your earliest convenience. NOTE: If you choose to allocate the package at a later time, you MUST still complete all of steps 1-9 above now, including running the Update Package List. 

The simplest way to do this is to allocate the package at Main Site level. If you prefer to allocate it at a lower location, ensure that you do so for all workstations. The new security package is JPEG Processing (GDI) security update KB833987 (client) and is available by ticking the 'Show RM system packages' box and then selecting 'Available packages'        

11.  Once you have allocated the package to workstations, restart the workstations for the Microsoft security update to be installed.

1.      Browse to D:\RMNetwork\RMManage\RM Hotfixes\HFXCC3080_extracted and double-click the file RM Installation Assistant.exe. (If this folder or its contents does not exist, re-run the HFXCC3080.exe file downloaded from the RM Support website).

2.      Follow the procedures in 'How to install the Security Update' from step 4 above.

The components of HFXCC3080 will be included in a future Community Connect 3 Service Release or Microsoft Service Packs validated by RM.

The Security Update can be installed on to networks running Community Connect 3 with Service Release 3, Service Release 4 or Service Release 5.

HFXCC3080 is NOT included in RM Service Release 4 or Service Release 5. If you install HFXCC3080 on CC3 SR3 and then upgrade to CC3 SR4, you will not need to re-install this hotfix.