Course Title Updating Systems Administrator Skills from Microsoft Windows 2000 to Windows Server 2003
Course Code G11 Cost $1195 Duration 3 Days
Leader Joseph Agius
Time / Day

Sept 27-29, 9am to 4.30pm

Location Monash University Engineering Computer Lab G11
Course Outline

Overview

This course provides attendees with the knowledge and skills to manage and maintain a MS Windows Server 2003 networked environment.

Students will learn how to identify the systems administration tasks in Windows Server 2003 that are new or different from the tasks performed in Windows 2000, manage user, computer, and group accounts in a Windows Server 2003 Active Directory-based environment, use the Group Policy Management Console (GPMC) to manage Group Policy, manage resources and security, configure and manage DNS and manage servers in remote locations.

Participant will also learn how to manage Terminal Services, manage IIS 6.0 Web Services, maintain computers that run Windows operating systems by implementing and managing Software Update Services and prepare for and implement disaster recovery solutions.

Audience

This workshop is intended for expert Windows 2000 systems administrators who manage and maintain Windows 2000-based Active Directory directory service-based networks. The workshop assumes extensive, day-to-day, practical, hands-on experience using Windows 2000 and a preference for learning by doing and discovering in non-prescriptive lab environment.

Course Outline

  1. Introduction to Systems Administration in Windows Server 2003
  2. Managing Users, Computers, and Groups
  3. Using the GPMC to Manage Group Policy
  4. Managing Resources and Security
  5. Managing DNS
  6. Managing Servers
  7. Managing Terminal Services
  8. Managing IIS 6.0 Web Services
  9. Maintaining Software by Using Software Update Services
  10. Managing Disaster Recovery


Course Title Help Desk Management for Schools
Course Code G19 Cost $295 Duration 1 Day
Leader Mark Chapple
Time / Day

Sept 29, 9am to 4.30pm

Location Monash University Engineering Computer Lab G19
Course Outline

This the first offering of this course that has been specifically developed by Microsoft to provide schools with the knowledge and expertise to run an efficient Help Desk to assist in the management of technology across schools.



Course Title School Intranet Development Lifecycle
Course Code G20 Cost $495 Duration 2 Days
Leader Dave Kelly
Time / Day

Sept 28-29, 9am to 4.30pm

Location Monash University Engineering Computer Lab G20
Course Outline

Course Duration:
2 days – The course is an abbreviated version of a longer more in depth 5 day course. Concentration of the course will be on parts 2 Planning, 5 Stakeholder Needs, 6 Mapping, 7 Planning the Database Back End, 9 Design and 11 Development and Coding.

Prerequisites:
A basic knowledge of creating web pages although not totally necessary. A knowledge or an involvement in what is required in the day to day running of the school. A knowledge of basic databases and simple SQL. Prerequisites are generally recommended but not necessarily required

Who should do this course:
Technical Staff, Teachers and Administrators who want to create or have a need to contribute to the school’s intranet using database managed processes to create electronic formats for the running of the school.

Result:
Participants will be able to create processes that allow for retrieval, addition, editing and secure viewing of database managed WebPages on an intranet/internet. The course will follow the process of the System Development Life Cycle (SDLC) adapted to the unique process required for the school – School Intranet Development Life Cycle (SIDLC). The result of the week will be the ability to link into the databases around the school and create web pages from that data while also developing useful process tools on the web such as class lists, attendance rosters, discipline and achievement records, parental information, medical information, sports days, subject selection etc. The approach to the course will combine the use and promotion of the school’s intranet using available resources at the school, sourcing outside contractors and using off the shelf products.

Content

1. Introduction to the brief.

The intranet should have an outline of the needs wants and desires of all the key stakeholders. We will go through a classic brief out what a school requires and who requires discussing the implications of each as we go. We will alter this brief to suite the purposes of the training course.

2. Planning

In this section we plan out each section of the project to give ourselves a timeline of completion for each phase. Usually done in a software package such as MS Project. This will include organising meetings with all the key stakeholders to methods of obtaining feedback on the intranet.

3. Server Requirements for the intranet to function.

Making sure that the server/intranet will display our pages as we create them.

4. Setting Up our intranet on our local server

Setting up our development machine with all the relevant local servers to enable us to test our intranet as we develop it. We will start to develop our testing procedures here also.

5. Stakeholder Needs

Setting Up meetings to enable us to list all the stakeholder requirements. This will also set us on the path to creating the necessary levels of security in our system.

6. Mapping

A full map of page flow and process flow of the intranet is developed. This is best created in MS Visio.

7. Planning the database back end

Creation of the necessary tables to generate the pages in our intranet. This would also include any links with databases within the school.

8. Phasing the plan

Creating escape points in the intranet plan where we can go live with sections of the intranet to allow staff to use and learn the functions of the intranet as it is developed.

9. Design

Creating any template pages that we can use in the intranet. This is essentially headings, page formats and styles throughout.

10. Menus

From the phase plan we work out the necessary menus required at each implementation phase so as to not create redundant menus.

11. Development and Coding

Creation of the pages. It is in this section we learn the CFML, HTML, SQL, Java and ASP to create our pages. From here we code the pages. The first section would be the log in pages.

12. Integration and Testing

Each section is tested locally. Upon each test we add to the testing document so that a full test can be carried out at the implementation of each phase.

13. Implementation

Publishing to the intranet and internet. Live testing.

14. Operation and Maintenance

Tips on what to expect from the staff when the system goes live. How to create impressive help files and training tips.

15. Continuous Improvement

Creating feedback areas and also planning for upgrades and improvements.

16. A look at off the shelf products

We will look at some of the off the shelf products which are relevant to all schools which will circumvent much of the code that is required by all schools.

17. Discussion

A discussion forum between the group time permitting





 Copyright © Education Communities 2000-2004
Education Communities Pty Ltd | ACN 079 541 736 | PO Box 122 Mt. Eliza Victoria 3198 Australia
email: bruce@educationcommunities.com

www.purelogic-s.com www.swashwebdesign.com www.otoriyose-sakai.com www.shangke100.com www.alphadeaf.org www.gzyzi.com www.parsz.com www.hodistro.com www.bohemialab.com www.bagbag.org www.tillacum.com www.catherineLie.com www.marylandrvexpo.com www.midatlanticrvshow.com www.realityininvestment.com www.realityininvesting.com Michael Kors Outlet Michael Kors Factory Outlet Cheap Michael Kors Handbags Michael Kors Outlet Michael Kors Handbags christian louboutin outlet cheap christian louboutin christian louboutin outlet christian louboutin outlet christian louboutin outlet Cheap Michael Kors Michael Kors Outlet Cheap Michael Kors Purses christian louboutin outlet christian louboutin shoes red bottom shoes