Office Communications Server 2007 R2 Operations Guide Now Available


The Office Communications Server 2007 R2 Operations Guide provides guidance on procedures that should be considered to fully incorporate Microsoft Office Communications Server 2007 R2 into an existing IT operational framework as well as how existing procedures should be expanded to make Communications Server 2007 R2 fully operational. The Operations Guide describes the operational processes, tasks, and tools that are required for you to maintain a Communications Server 2007 R2 environment, and it explains how to manage Communications Server 2007 R2 according to the Microsoft Operations Framework (MOF) model. This article gives you a basic overview of the checklists and tasks that you will find explained in depth in the Operations Guide. Download the complete Office Communications Server 2007 R2 Operations Guide from the Microsoft Download Center.

Author: Gareth Ireland

Publication date: December 2010

Product version: Office Communications Server 2007 R2

Operations Management

Operations management involves administering an organization’s infrastructure components, and includes the day-to-day administrative tasks, both planned and on-demand, that are required to keep an IT system operating smoothly.

In a Communications Server 2007 R2 environment, typical system administration tasks include enabling users, moving users (if required), backing up data, managing settings, monitoring system status and performance, and managing connectivity.

Standard Procedures

Several resources can help you define what standard procedures are required in the organization, and how to perform them. Because each organization is unique, you may have to further customize and adapt these resources to suit everyday requirements.

Standard operational procedures change, and documentation occasionally needs to be revised. As changes are made, the change management process, as defined in the Service Management Functions of the Microsoft Operational Framework, should identify how each change is likely to affect how and when administrative tasks are performed. Use the change management function to update and control the documentation.

We recommend that operational tasks be separated into manageable workloads, where tasks are performed on a daily, weekly, and monthly basis. Daily tasks focus efforts on aspects that are critical to the functioning of a system and monthly tasks focus more on ensuring the long-term health of a system. The tasks that must be performed can be separated into the following categories:

  • Daily tasks
  • Weekly tasks
  • Monthly tasks
  • As-needed tasks

When preparing documentation for operations management, use checklists to help ensure that the required tasks are performed at the appropriate time.

We recommend that you recommend document the required operational tasks that you will regularly perform. Documenting how you perform tasks ensures that your information is preserved when there is a change in your operational environment, such as when new technologies are deployed or staff changes occur.

Daily Tasks

The following topics from the Operations Guide represent tasks that we recommend be performed daily. For details, see the Operations Guide.

  • Performing Physical Environmental Checks
  • Performing and Monitoring Backups
  • Checking Disk Usage
  • Checking Event Viewer
  • Monitoring Office Communications Server 2007 R2 Performance
  • Monitoring Operating System
  • Monitoring Network Performance
  • Scanning for Viruses and Checking Virus Definitions
  • Viewing and Analyzing Monitoring Server Reports
  • Ensuring All Required Office Communications Server 2007 R2 Services are Running
  • Validating Number Normalization and Routing
  • Validating Connectivity and Call Quality using Deployment Validation Tool
  • Validating Address Book
  • Viewing Status of Global Settings for Forest
  • Viewing Edge Server Settings
  • Viewing Status of Pool
  • Monitoring Back End Office Communications Server 2007 R2 Storage Performance
  • Monitoring Group Chat

Weekly Tasks

The following topics from the Operations Guide represent tasks that we recommend be performed weekly. For details, see the Operations Guide.

  • Archive Event Logs
  • Check for Security Updates
  • Run Office Communications Server 2007 R2 Management Console Validation Tool
  • Install and run the Office Communications Server 2007 R2 Best Practice Analyzer
  • Review SLA Performance Figures
  • Environmental Tests
  • Review SCOM Management Pack and Quality of Experience Reports
  • Generating and Viewing Database Reports for Enterprise Pools

Monthly Tasks

The following topics from the Operations Guide represent tasks that we recommend be performed monthly. For more, see the Operations Guide.

  • Viewing Status of Global Settings for a Forest
  • Viewing Edge Server Settings
  • Check Office Communications Server 2007 R2 Server Certificates
  • Security Checks
  • Service Account Password Expiration
  • Capacity Planning
  • Disaster Recovery Test

As-Needed Tasks

The following topics from the Operations Guide represent tasks that we recommend be performed on an as-needed basis. For details, see the Operations Guide.

  • Full Security Auditing
  • Replace Certificates about to Expire
  • Updating Performance Baselines
  • Managing Enterprise Pool
  • Managing Usage
  • Changing Service Account Credentials
  • Managing Edge Server Connectivity
  • Administering the Address Book
  • Managing User Accounts
  • Analyzing Office Communications Server 2007 R2 Log Files  

Lync Server Resources

We Want to Hear from You

Comments (3)
  1. Really glad to see this white paper in the download center. Much needed. Thanks to everyone involved!

  2. Edward Walton says:

    I would assume that most of the tasks are the same for Lync 2010

  3. Gareth Ireland says:

    Thanks Dr Rez! Ed we are busy updating this document to suite Lync. The generic "environmental" checks would apply but new methods and tools like PowerShell and synthetic transactions need to be considered. Also key is some valuable experience from the field which will come in time but we hope to get it out the early first half of next year. Until then i suggest that you use this guidance.

Comments are closed.

Skip to main content