- A+ Certification
- A+ 220-1001: Day 1: Intro, Resources & the Test
- A+ 220-1001: Day 2: CPUs
- A+ 220-1001: Day 2: RAM
- A+ 220-1001: Day 3: Firmware, Motherboards & Power Supplies
- A+ 220-1001: Day 4: Disks & Mass Storage
- A+ 220-1001: Day 5: Peripherals & PC Builds
- A+ 220-1001: Day 6: Windows Operations, User Management & Windows Maintenance
- A+ 220-1001: Day 7: The Command Line & Troubleshooting
- A+ 220-1001: Day 8: Displays & Networking
- A+ 220-1002: Day 9: Ethernet & WiFi
- A+ 220-1002: Day 10: The Internet & Virtualization
- A+ 220-1002: Day 11: Portable & Mobile Computing
- A+ 220-1002: Day 12: Mobile Administration & Printing
- A+ 220-1002: Day 13: Security & Operations
- A+ 220-1002: Day 14:
- A+ 220-1002: Day 15:
Current A+ objectives include at least some degree of familiarity with the Windows, Linux and Mac command lines. Fortunately, Linux and Mac use the same commands, for the most part.
Our text covers specific commands in some detail. You need to know:
- How to open a Windows CLI
- How to open a Linux terminal
- How to open a Mac terminal
- How to change directories, move files, rename files
It will be a real strong point on your resume if you can say you have some experience – any experience – writing command-line shell scripts. The process is very different between the Unixes and Windows.
So do a simple search. It’s good to get used to starting almost every process with a search:
WikiHow, for instance, has a good starter tutorial, though its use of loops might put off beginners:
HowToGeek has a little more advanced demo, including a video:
And SpeedGuide has a good, technical tutorial that will give you a great backup script:
Now, let me intoduce you to the excellent SpiceWorks community, and a Windows shell script to back up an entire Windows profile:
Another excellent source is StackOverflow. Notice how this script only backs up new or changed files:
It may be handy to turn this into a fun hacking exercise:
Don’t you hate those clickbait “10 Great Pictures of …” or “10 Mistakes Men Make,” etc. etc.?
I say, as always, consider the source. For instance, TechRepublic is a pretty darn reliable, high-quality site for the hard-core geek (and you are one if you’re here reading this).
Whether trying to diagnose a single device or dealing with the urgency of a company-wide outage, there are solid best practices on what NOT to do. With that in mind, here are 10 things to avoid doing, so you can limit the pain and keep things running as smoothly as possible….
Yes! Exactly! Please show me your painful mistakes so I can wince and try to avoid them forever (at least try). Check out the list and see what you think:
Chapters 15 and 16