Scott’s Blog

Monthly Activity Report
January 2007 

1. Support AIMWorX users, database, and servers
2. Support MCS users, database, and servers
3. Point of contact with NEC for AIMWorX issues
4. Backup SMDR and archive to CD (raw call files)
5. Backup CDR and archive to CD  (SQL DB backup)
6. Backup traffic data from MAT5 (admin) & MAT61 (student) traffic computers to CD
7. Backup AIMWorX billing data for 2005 & 2006 to CD
8. Weekly update of Cost Center & Student information in AIMWorX
9. Support Eclipse traffic servers, make sure traffic is collecting properly
1. Talked with Operations group about turning this server off
2.  Worked through Perl script issues to pull traffic from AIMWorX
10. Call detail lookup for Police & Security and Help Desk fax problems
11. Updated month-end Perl scripts to correct ‘sql view’ problem
12. Updated month-end Perl scripts to pull call records when no V-Net is used
13. Discovered student calls with no V-Net and reported to Switch techs, they determined there was incorrect programming on some routes, corrected in mid January
14. Applied Windows OS patches to all AIMWorX servers including DST patch
15. Ordered IBM server for ND&E to replace current AMP server
16. Reloaded ESX servers 2, 4, & 7 to meet current standards
17. Installed Altiris on OSIS servers
18. Setup ssh tunneling through dogberry host to windows servers
19. Formatted old AIMWorX1 server and redistributed to Security team
20. Created new AIMWorX template to install Outbound caller ID
21. Modified several AIMWorX templates to update/remove outbound caller ID
22. Loaded AmCom software on 3 computers in PBX operator area to expedite testing of software
23. Installed Tight VNC software on PBX operator position 29 for AmCom access
24. Attended Microsoft kick-off event for Windows Vista at Opryland Hotel
25. Start-up & shutdown procedures for AIMWorX-web2 & VMSPE servers
26. Research Business Objects Enterprise & Crystal Reports DST patches
27. Installed Microsoft Office 2007 on desktop and laptop
28. Informed No V-Net project manager about AIMWorX implications

Monthly Activity Report
December 2006

1. Support AIMWorX users, database, and servers
2. Support MCS users, database, and servers
3. Point of contact with NEC for AIMWorX issues
   a.       Tracked AIMWorX problem tickets
   b.      send information about problems when requested
   c.       send information on new problems
4. Maintained AIMWorX-web2 server and around 252 Crystal Report reports.
5. Backup SMDR and archive to CD (raw call files)
6. Backup CDR and archive to CD  (SQL DB backup)
7. Weekly update of Cost Center & Student information in AIMWorX
8. Support Eclipse traffic servers, make sure traffic is collecting properly
9. Call detail lookup for Police & Security and Help Desk fax problems
10. Rack OSIS-IVRI01 & 02 servers for AmCom project (OSIS)
11. Move OSIS-TAPI01 & OSIS-VAT01 to Hill Center room 107
12. Move all OSIS servers to their production VLAN 
13. Worked with Kenon to reconfigure virtual servers 1, 3, & 8