Using UNICENTER TNG at the OU

1
Using UNICENTER TNG at the OU

• Jeff Lewis
• MSD
• The Open University

2
What we have onsite

• UNICENTER TNG 2.1
• WV 2D Map
• Enterprise Management
• Agent Works
• AHD 4.0 - Advanced Help Desk
• AMO - Asset Management Option
• SDO - Software Delivery Option
• RespMan - Response Manager

3
Key lessons

• Dont do it alone
• It takes a long time
• It requires a dedicated team
• It requires a clear management view
• It may impact your organisational structure

4
Who we support

• The user community
• Walton Hall - Milton Keynes
• 13 regional offices Brussels Dublin
• Warehouse Correspondent Services
• The network topology
• 30 domains
• Local ITFs

5
The MSD structure
6
What we had before UNICENTER

• UNIX
• Central event logging
• Automatic checking routines
• Menus for checking control
• NT
• Desktop S/W delivery
• Desktop asset management
• Static asset management system

7
What we wanted

• UNIX
• Increased monitoring automated responses
• Improved incident management
• NT
• Centralised logging of NT servers
• NT service monitoring
• eg. Exchange Replicators, WEB servers
• S/W delivery to dept. NT servers

8
Why we chose UNICENTER

• A common way of managing things
• Existing CA Ingres user
• CHEST
• Ingres Agent
• CA reference site

9
TNG Implementation

• Difficult

10
AHD Implementation

• Also difficult

11
The current situation

• TNG
• Limited monitoring for UNIX NT
• AHD
• Abandoned
• AMO
• Waiting
• SDO
• Waiting

12
What do we want for our enterprise?

• Maximum service availability.
• Achieved by-
• Monitoring components
• or
• Application confidence tests