Thursday, September 16, 2021

COMPUTER SYSTEMS SERVICING NCII

  Core Compentecies :

 / INSTALLING AND CONFIGURING COMPUTER SYSTEMS (ICCS) 

 / SETTING-UP COMPUTER NETWORKS (SUCN)

 / SETTING UP COMPUTER SERVERS (SUCS)

 / MAINTAINING AND REPAIRING COMPUTER SYSTEMS AND NETWORKS (MRCN)


Responsibilities

  • Set up hardware and install and configure software and drivers
  • Maintain and repair technological equipment (e.g. routers) or peripheral devices
  • Install well-functioning LAN/WAN and other networks and manage components (servers, IPs etc.)
  • Manage security options and software in computers and networks to maintain privacy and protection from attacks
  • Perform regular upgrades to ensure systems remain updated
  • Troubleshoot system failures or bugs and provide solutions to restore functionality
  • Arrange maintenance sessions to discover and mend inefficiencies
  • Keep records of repairs and fixes for future reference
  • Offer timely technical support and teach users how to utilize computers correctly

Requirements

  • Proven experience as computer technician or similar role
  • Experience with LAN/WAN networks
  • Thorough knowledge of computer systems and IT components
  • Good knowledge of internet security and data privacy principles
  • Excellent troubleshooting skills
  • Very good communication abilities
  • Exceptional organizing and time-management skills
  • BSc/BA in Computer Science, engineering or relevant field
  • Relevant certifications (e.g. CSS NCII holder or higher) will be an advantage.

Friday, December 3, 2010

THE TEN COMMANDMENTS OF COMPTER ETHICS

1. Thou shalt not use a computer to harm other people.
2. Thou shalt not interfere with other people's computer work.
3. Thou shalt not snoop around in other people's file.
4. Thou shalt not use a computer to steal.
5. Thou shalt not use a computer to bear false witness.
6. Thou shalt not use or copy software fotr which you have not paid.
7. Thou shalt not use other people's computer resources without autjorization.
8. Thou shalt not appropriate other people's intellectual output.
9. Thou shalt think about the social consenquences of the program you write.
10. Thou shalt use a computer in ways that show consideration and respect.

Sunday, November 28, 2010

THE HARDWARE APPROACH

1. Dont Panic
2. Observe the Condition
3. Use your senses
4. retry
5. Document
6. Assume one Problem
7. Use correct service data
8. Use the proper test equipment
9. Diagnose to the section
10. Consult your index or symtoms
11. Localize to a stage
12. Isolate to the section
13. Test and verify proper operation

Thursday, November 25, 2010

Dont Panic
-Beside your users and reference manuals, you now have a book that help you.

Observe the Condition
-What are the symtoms?
-What conditions existed?
-What fuctions Still work?

Use your senses
-Look and Smell

Retry
-If the display monitor is dark check the power plug and the power cable.

Document
-Documents everything you see, sense and do.
-What is the PC doing?
-Waht is it not doing?
-what is being displayed on the monitor?
-is there an error message?
-What is still operating while everything's connected?while everything but the monior is disconnected?
-Is power still indicated on each part of the system?

Assume one problem
-in digital circuitry the likelihood of multiple simultaneous failure is low?

Use Correct service data
-Even a do it yourself needs good information.

Use proper Equipments
-If you intend to go after the dog use the right test equipments.

Diagnose to the section
-if the System works when the peripheral were disconected (step 4) turn
the power off and reconnect one of peripheral, power on and test.

Consult the symptoms Index
-if the trouble symtoms match a problem described in the pertinent troubleshooting
index turn to the reference page and follow the instruction given.

Localize to a stage
-turn off the power to the computer and disconnect the power supply.

Isolate to the part.
-Close following the detailed circuit troubleshooting and analysis procedure given in the following
chapter should guide you to the failed part.

Test and verify proper Operation
-After booting up and testing the system using the copy of your DOS program disk run
the same program that was in the machine at the time of failure to verify that the system is fixed and operating properly.

OTHER RELATED TROUBLESHOOTING LINKS.

-http://www.mypcgallery.blogspot.com/
-http://www.mycggallery.blogspot.com/

-http://www.nod32-jem.blogspot.com/
-http://www.pcaddict-rob.blogspot.com/