COMPUTER+NETWORK

This is the new module. The class has been cut back to only 3 hours per week now - Monday nights - but not starting til Monday 26 October (so you still get to hand in your assignment this Wednesday night). Unfortunately, I have been unsuccessful in finding a textbook (Cooma, Shoalhaven, Dapto, Wollongong & Strathfield sections were all unable to help me) but we do have the Admin Toolbox.

There is a folder on J:\Admin Studies\LINDA\ESTABLISH & MAINTAIN A WORKGROUP COMPUTER NETWORK called NETWORKS which looks at what a computer network is and the different network topologies ie bus, star etc. and why you would want to network.

You will need to keep in mind budget constraints and what the requirements are for software and hardware. As well as basic and specific application software, you will also require system software. System software performs the following tasks: There are some definitions in a folder called SYSTEM SOFTWARE. Then you need to decide how to install the software. There are a number of different installation methods that can speed up the process: This technique is used to install a common set of applications and settings to a group of computers. The required pieces of software are installed, configured and optimised on a single computer. A copy or image of this computer's hard disk drive is transferred to the hard disk drives of other computers, eliminating the repetitious process of setting up software on each individual computer. Some software can be installed over a network connection, which eliminates the need to be at the actual computer requiring the software. This technique can be useful for installing software to computers in remote or hard-to-reach locations. Automatic installation of software can occur either over a network (an intranet or the Internet) or on a scheduled basis using files already stored on the computer; for example, a suite of anti-virus tools may be configured to automatically retrieve the latest virus definition files from the software manufacturer's website every time someone logs on to the computer.
 * provides the operating system
 * network management
 * file management
 * user management
 * security
 * backup
 * anti-virus
 * Imaging: This technique is used to install a common set of applications and settings to a group of computers. The required pieces of software are installed, configured and optimised on a single computer. A copy or image of this computer's hard disk drive is transferred to the hard disk drives of other computers, eliminating the repetitious process of setting up software on each individual computer.
 * Installing over a network: Some software can be installed over a network connection, which eliminates the need to be at the actual computer requiring the software. This technique can be useful for installing software to computers in remote or hard-to-reach locations.
 * Automatic installations: Automatic installation of software can occur either over a network (an intranet or the Internet) or on a scheduled basis using files already stored on the computer; for example, a suite of anti-virus tools may be configured to automatically retrieve the latest virus definition files from the software manufacturer's website every time someone logs on to the computer.

There should also be a system in place to keep track of software licences, ensuring they are up-to-date and you have the correct number. Belarc is a free PC Audit program []. The **[|Belarc Advisor]** builds a detailed profile of your installed software and hardware, missing Microsoft hotfixes, anti-virus status, [|CIS] (Center for Internet Security) benchmarks, and displays the results in your Web browser. All of your PC profile information is kept private on your PC and is not sent to any web server.

Another aspect to consider is where to store the physical media - disks etc - that comes with the computer system.

Careful consideration needs to be given to **who** will be granted access to the network and exactly **what** they will have access to. Check to see if your organisation has a policy which describes various levels of access and gives a method for determining who should be given each of these access levels. When I was working at The Times in London we had 7 different levels of access and trainers were able to allocate different areas of access depending on your job ie sales staff had only very basic access whereas Heads of the departments had a higher level. The levels were not "set in concrete" - you could restrict or grant access to certain areas for individuals and not just positions. Such a policy usually defines types of users, for example: You may be familiar with these terms from setting up your home computer so the kids can't download programs (and their friends are "guests").
 * Manage the maintenance of a workgroup network**
 * **administrator** – who has no restrictions on access to any resource or system component
 * **normal user** – who can only access the data and programs associated directly with their own work and who cannot install or remove programs or modify system settings
 * **guest** – who can only access resources that are available to the public or visitors to the organisation.

If problems do occur, there should be a policy/contingency plan to deal with them. You probably have already prepared one for the previous assignment. There are examples etc in the folder on j:\ drive (J:\Admin Studies\LINDA\MANAGE BUSINESS DOCUMENT DESIGN & DEVELOPMENT\CONTIGENCY PLANS). Have a look at the examples in the Admin Toolbox on pg 2 under the Manage the Maintenance of a Workgroup Network section.

Of course, most of you are probably able to fix a variety of problems with a computer (I always love the EAG problems - Excessive Air Gaps - where something isn't plugged in).

Scheduled maintenance is always best when it will affect the least number of users - preferably at night or on the weekend.


 * Assist and Train Network Users**

The primary goal of establishing and using a network is to increase the productivity and efficiency of the organisation. There are four basic rules which can help this to happen: Obviously, a primary goal should be to make the network available for the maximum time, with as few failures as possible. This is achieved through regular maintenance and prompt response to problems. Users should be able to access all the resources they need to do their job easily, without the need to log in several times (perhaps we could mention this to TAFE), switch networks, change hardware or navigate around a complex network structure. Mechanisms should be put in place to listen and respond to user feedback, not only on problems and failures, but also on speed, reliability and ‘transparency of access’. Encourage "good" feedback too - try to promote positive experiences. Both experienced and new users will need ongoing training and support to make the most of the network and to adapt to using new technologies as they are introduced Remember to keep users informed as that should help make the transition a smoother experience. Do all staff need training and how do you determine this? Training Needs Analysis. There is information in J:\Admin Studies\LINDA\PLAN OR REVIEW ADMINISTRATION SYSTEMS\TRAINING Depending on the size of the organisation, you may want to make individual visits or send emails to staff (this could be to discuss training needs; give basic and/or detailed information about what the changes are; where to find help; solutions to common problems etc). You may have personal knowledge of each staff's capabilities and whether training will be necessary.
 * Maximise up time, minimise down time**
 * Provide transparent, seamless access to resources**
 * Seek and respond to user feedback**
 * Provide training to new and existing users**