Text only | Skip links
Skip to Navigation

OUCS Current Operational Standards


5. OUCS Core Network Services Contribution

Services supported currently are the following:

5.1. Description

Members of the ICT contribute skills and expertise to supporting part of the OUCS Core network Services. The primary areas of contribution are the Windows expertise required to run the WINS and VPN Services, and to help define policies and procedures for Active Directory integration with DNS.

NB This service is provided to the University as a whole and as such some components of the service may extend beyond the scope of the ECE.

5.2. Active Directory Service

5.2.1. Objectives

To work together with the Infrastructure Group in defining policies for Active Directory DNS integration with the central DNS servers, and in supporting University IT Support Staff in configuring Active Directory installations.

5.2.2. Description

Active Directory is heavily dependent on the correct functioning of DNS, both for replication between domain controllers, and for clients to locate services. It is therefore essential to ensure that the relationship between DNS and Active Directory is well understood, that implications for systems administrators and central DNS administrators are reviewed regularly, and that policies, configuration information and documentation are modified accordingly.

5.2.3. Service Maintenance

  1. Respond to queries from IT Support Staff regarding Active Directory installation and configuration, particularly with respect to DNS configuration.

5.2.4. Service Development

  1. Assess new releases of Active Directory, where possible before release, and determine impact on current policies and procedures and plan action accordingly.
  2. Manage changes in policies and procedures, collaborating with other staff (particularly networks) as necessary in order to implement changes. Ensure, where appropriate, that any changes are planned carefully, interested parties consulted, and that necessary testing is carried out before implementation.
  3. Regularly review documentation provided, and update as required.
  4. Provide information to ITSS via web, email, seminars or other routes as appropriate.
  5. Assess whether proposed service developments will increase the service maintenance load. If they will, the development may need to be changed, or more resources found to support it.

5.2.5. Service Levels

To assess implications of changes to Active Directory and implement appropriate changes within 3 months of release.

To resolve problems according to the response times defined in the Response Levels document.

5.3. WINS Service

5.3.1. Objectives

To maintain the central WINS service provided to the University. Eventually to decommission said service once all systems that currently rely on NetBIOS name resolution have moved to using DNS.

5.3.2. Description

The WINS service provides a central NetBIOS name to IP address resolution service to the whole University, together with naming standards recommendations. Historically Windows systems have been dependent on NetBIOS to advertise and locate services, while Samba servers and Netware servers can also advertise services using NetBIOS. While technically modern Windows installations can use DNS rather than NetBIOS for name resolution, it is likely that the WINS service will be required until at least 2010. As the NetBIOS name space is flat, naming standards are also crucial.

5.3.3. Service Maintenance

  1. Manage the University WINS servers (i.e. system administration, including checks of security, hardware and software health, loading etc.)
  2. Investigate and resolve any hardware or software problems relating to the WINS servers.
  3. Plan and execute any WINS-related downtime. Assess impact and risks and communicate in advance with affected parties regarding same.
  4. Respond to IT support staff queries regarding the WINS servers and related topics (e.g. NetBIOS name resolution) via RT.
  5. Maintain the static database entries on the WINS servers.
  6. Ensure where possible that the WINS service is maintained through any power outages.

5.3.4. Service Development

  1. Regularly review WINS hardware and software; plan, purchase, install, configure and manage the transition to new hardware and software as required.
  2. Regularly review and maintain the WINS and NetBIOS naming convention web pages. Ensure information is available particularly to ITSS via web, seminars, mailing lists etc. as appropriate.
  3. Eventually, create and manage plan to decommission WINS servers (probably not for a few years yet).

5.3.5. Service Levels

To ensure 99% availability of the service during standard working hours.

To resolve problems according to the response times defined in the Response Levels document.

5.4. VPN Client Service

5.4.1. Objectives

To work together with the Infrastructure Group in providing the VPN component of the Remote Access Service.

5.4.2. Description

Primary contribution is Windows and OS X expertise in testing new client releases and managing the distribution of the client software.

5.4.3. Service Maintenance

  1. Manage mechanisms for distributing client software (currently http/ftp and via the Shop on CD.)
  2. Resolve problems relating to obtaining client software via the advertised channels.

5.4.4. Service Development

  1. Package and distribute new versions of the VPN client software, as they are released by Cisco, as untested new releases via selected distribution channels.
  2. Reguarly (at least once every 18 months) package and distribute new versions of the VPN client software as full releases via all distribution channels. Ensure adequate testing on appropriate operating systems prior to full release.
  3. Assess effects of major client changes to service levels and flag potential problems.
  4. Review documentation on client changes and manage updates as required.

5.5. Time Commitment

0.4

Up: Contents Previous: 4. Anti-Virus Service Next: 6. Desktop Systems Development Services


Style: Simple text | Single file | Normal | PDF

Maintained by: OUCS Webmaster (webmaster@rt.oucs.ox.ac.uk) 28 October 2005 . Bridget Lewis .
University of Oxford. Back to top
Skip to search