ASc Computer Systems Technology Library Guide

This guide supports students in the Associate of Science (ASc) in Computer Systems Technology at Vector Technology Institute (VTI). Use it for practical labs, troubleshooting exercises, systems administration and networking assignments, technical-support practice, technical reports, and academic research.

Move from a clear problem to a tested and documented result: learn the concept, consult the right technical authority, work safely in a lab or approved environment, keep evidence, and explain what you found. Learning resources build skill; official documentation and scholarly sources support current configuration and academic claims.

---

How to Use This Guide in Technical Courses

1. Identify the task or problem. Define the symptoms, requirements, constraints, and expected output.
2. Consult official or vendor documentation. Confirm supported settings, commands, versions, and prerequisites.
3. Verify relevant standards or frameworks. Check the applicable networking, security, service-management, or systems guidance.
4. Test in a lab or safe environment. Use an approved simulator, virtual machine, container, spare device, or isolated network.
5. Document findings and cite sources. Record the method and evidence, then cite the documentation, standard, or scholarly source supporting the explanation.

1. Start Here: Core Learning & Reference Tools

Open textbooks and learning resources build foundations in computing, operating systems, networks, and problem-solving. For current implementation details, supported options, version changes, and configuration steps, prefer official documentation from the relevant project or vendor.

• OpenStax – Open textbooks for computing and mathematics foundations.
• Open Textbook Library – Open textbooks for programming, systems, databases, and related subjects; check title-level review information.
• Free Computer Books – Books, lecture notes, and tutorials for background learning and revision.
• Open Library – Digital access to computing and technology books.

2. Operating Systems & System Administration

Use system-administration resources to connect a concept to a repeatable operational task. Work from a known baseline, make one controlled change at a time, and record how to verify or reverse it.

• Configuration: identify the intended state, dependencies, configuration files, environment variables, and restart requirements before changing a service.
• Users and permissions: apply least privilege, distinguish account ownership from group membership, and check permissions when access fails.
• Services and processes: check whether a service is installed, enabled, running, listening on the expected interface, and consuming expected resources.
• Patching and updates: confirm the version, review release or security notes, plan a rollback or recovery path, and test after updating.
• Logs: use timestamps and related service logs to separate the first failure from later symptoms; protect sensitive information when sharing evidence.
• Backups: know what is backed up, where it is stored, how retention works, and whether a restore has actually been tested.
• Virtualization and containers: understand the difference between a host, guest, image, container, volume, and network before troubleshooting an environment.

• Linux Foundation – Free Training – Linux and open-source foundations for guided study and lab preparation.
• Kali Linux Documentation – Official documentation for an authorized security-learning environment; use it defensively and only with permission.
• VMware Documentation – Virtual-machine concepts, administration, and platform-specific configuration guidance.
• Docker Documentation – Official reference for images, containers, storage, networking, and deployment behaviour.

3. Networking Fundamentals & Infrastructure

Separate the purpose of each source. Learning resources explain concepts and practice; standards describe agreed requirements and protocols; diagnostic tools provide evidence about what is happening on a network.

• Learning and certification preparation: use Cisco Networking Academy and Professor Messer – Network+ for guided explanations, terminology, and practice.
• Physical infrastructure: use the Fiber Optic Association Reference Guide when studying fiber types, testing, connectors, and installation concepts.
• Standards and protocols: consult ITU Standards and IETF Standards when an assignment requires a formal protocol or standards-based explanation.
• Diagnostics and evidence: use Wireshark Documentation to learn capture, filtering, and interpretation. Capture only on networks you are authorized to examine and protect sensitive traffic.

4. Troubleshooting Workflow

Observe -> Reproduce -> Isolate -> Check logs/configuration -> Test safely -> Verify fix -> Document result

• Change one variable at a time. Otherwise you may not know which change affected the result.
• Keep evidence. Record the original symptom, exact steps, timestamps, versions, relevant outputs, and expected versus actual behaviour.
• Avoid undocumented configuration changes. Record the change, reason, owner, and rollback path instead of leaving a hidden workaround.
• Verify beyond the immediate symptom. Confirm the intended service works, related functions still work, and the fix survives the relevant restart or repeat test.

5. Cybersecurity & Systems Protection

Use cybersecurity resources for defensive learning, risk reduction, standards, and authorized practice. Focus on protecting accounts, systems, data, services, and users; do not test or access systems without permission.

• NIST Computer Security Resource Center – Guidance and publications for secure systems and software.
• NIST Cybersecurity Framework (CSF 2.0) – A risk-management framework for organizing cybersecurity outcomes and communication.
• OWASP Top 10 – Defensive awareness of common web-application risks and mitigations.
• HackerOne – Hacker101 – Introductory security learning for authorized, educational practice.

6. Computer Hardware & Technical Support

Technical support combines observation, compatibility checks, safe maintenance, and clear communication. Before replacing a component, confirm the symptom, model, firmware or driver version, power and connection state, and the evidence pointing to the suspected cause.

• Diagnostics: reproduce the fault, check basic connections and environmental conditions, separate hardware from software symptoms, and use the least invasive test first.
• Compatibility: check interfaces, power requirements, capacity, operating-system support, drivers, firmware, and physical fit before installing or recommending a component.
• Maintenance: follow approved safety procedures, protect data, record asset details, and keep maintenance and replacement dates.
• Component documentation: use manuals, specifications, pinouts, datasheets, and manufacturer guidance rather than relying on an unverified diagram or video.
• Support records: write the reported symptom, checks performed, evidence collected, action taken, result, and recommended next step so another technician can continue the work.

• Professor Messer – CompTIA A+ – Guided hardware, operating-system, and support fundamentals.
• All About Circuits – Electronics concepts and reference material for understanding components and signals.
• eFunda Engineering Formulas – Formula reference for relevant technical calculations; verify assumptions and units.

7. Video, Labs & Practical Learning

Videos and hands-on labs can make an unfamiliar system easier to see and practice. Treat them as supplementary learning: check the date and version, reproduce the steps in an authorized environment, and confirm important configuration details in current official documentation. A video or lab exercise should not replace scholarly sources when an assignment makes an academic claim.

• YouTube (Educational Channels) – Demonstrations and explanations; evaluate the creator, date, version, and supporting documentation.
• Vimeo – Creative Commons – Supplementary demonstrations and openly licensed media; check reuse terms.
• SkillsCommons – Workforce and practical-learning materials that can support lab preparation.

8. Virtualization, Containers & Cloud Foundations

Use virtualization and containers to create repeatable practice environments, but first identify what is isolated and where data is stored. A virtual machine includes a guest operating system; a container packages an application and its dependencies while sharing the host kernel. Check resource limits, networks, volumes, images, and cleanup steps before a lab begins.

• VMware Documentation – Virtual-machine configuration, administration, and platform behaviour.
• Docker Documentation – Images, containers, networking, storage, and deployment details.
• Lab habit: snapshot or back up work when appropriate, label environments, avoid storing credentials in images or notes, and record versions so the result can be reproduced.

9. Research & Academic Support

Match the source to the claim. Technical documentation supports current configuration and product behaviour; scholarly literature supports academic explanations, comparisons, and research claims.

Peer-reviewed research

• IEEE Access – Open peer-reviewed research in computing, engineering, and technology.
• Directory of Open Access Journals (DOAJ) – A directory for discovering open-access journals; verify the individual journal and article record.
• Peer-Reviewed Scholarly Articles Guide – VTI guidance for finding and evaluating peer-reviewed journal articles.

Discovery tools

• Google Scholar – Broad discovery across articles, books, theses, and conference papers; results are not automatically peer reviewed.
• BASE – Discovery of research papers and repository records; verify the original publication and source type.

Theses and dissertations

Open Access Theses and Dissertations (OATD) can provide advanced examples, methods, and literature leads. A thesis or dissertation is not automatically peer-reviewed journal literature, so check the source type before using it for a journal-evidence claim.

Best Starting Point by Task

• Learning a system concept: start with OpenStax, Open Textbook Library, Linux Foundation training, or a focused course, then confirm current details in official documentation.
• Troubleshooting a device or system: define the symptom, check support or vendor documentation, collect logs and versions, isolate safely, and record the verified fix.
• Networking assignment: use Cisco Networking Academy or Professor Messer for concepts, ITU or IETF for standards, and Wireshark documentation for diagnostic evidence.
• Cybersecurity assignment: use NIST and the CSF for risk and standards context, OWASP for defensive web-security awareness, and authorized labs for practice.
• Technical report or research paper: use official documentation for implementation facts, IEEE Access or DOAJ for peer-reviewed research, and Google Scholar or BASE for discovery.
• Preparing for hands-on lab work: review the concept, identify prerequisites, set up an approved VM, container, simulator, or spare device, and prepare a checklist for evidence and cleanup.

Technical Report Workflow

Problem/Objective -> Environment -> Method -> Evidence -> Findings -> Resolution/Recommendation -> References

State what was investigated, describe the environment and constraints, explain the method, present evidence rather than guesses, distinguish findings from recommendations, and cite the sources behind technical or academic claims.

Recommended Companion Guides

• Research Skills Library Guide
• How to Write the Research Paper
• APA Style & Citation Guide
• Find Resources
• Peer-Reviewed Scholarly Articles Library Guide – Find and verify peer-reviewed journal articles for academic work.

---

Prefer official documentation for current technical configuration and peer-reviewed sources for academic claims. Ask the VTI Library for help when you need to locate, evaluate, or cite a source.