Tuesday, October 30, 2007

MS Exchange - 10/30/2007

With 2/3 of the class present, we forged ahead and covered what we should have covered last week: Lab 4. Lab 4 is important because in it we study the difference between regular server clustering and Microsoft's Network Load Balancing. Remember that NLB is able to see which servers are working harder than the others and can then route traffic to the less busy ones. Clustering is a little dumber (duhrrrrrr) and only splits the loads up in a round-robin pattern.

We also discussed the concepts of Front End and Back End servers, and their relation to an Exchange organization. An easy way to keep these straight is to think of them in terms of fast food employees. You have employees that work the front, and employees that work the back. The ones in the front are the ones that actually talk to customers (or clients) and the ones in the back are the ones with their fingers in the hamburger (gross).

Homework:
  • Lab 4, pg 53: Lab questions 1-4

A+ Hardware/Software - 10/30/2007

Today was an interesting day: we first took our first checkpoint exam and then moved onto the software portion of our class.

First of all, great job on the checkpoint exams. Seriously. In most classes I teach this, there is a *massive* curve, and many many failures. No one failed this one. How cool? I've had people in the past fail despite a 40 point curve. Yeah, that means that they scored less than a freaking 20% on the test. You could guess and do worse than that!

Anyway, we studied up one how MS-DOS worked and then how Windows 95 improved on that. And, just to make things fun, we installed Windows 95 and played with it. Next week, we'll install Windows 98 and look at some of the improvements that it made over Windows 95.

Homework:
  • Nada. I'm what they call a nice guy.
  • Oh, and sorry for taking so long to get this posted. I'm what they call a lazy guy. :)

Monday, October 29, 2007

Server+ - 10/29/2007

Yikes! Sorry I'm so far behind on the updates guys, it just got away from me!

Tonight we had a nice little checkpoint exam, and most of you did quite well. Great job!

Clay was nice enough afterwards to show us some of his server equipment that he's aquired and, I don't know about you, but it was nice to see some real-life examples of what you guys will be working on one day.

Homework:
  • No homework!

MS Exchange - 10/29/2007

Today was unit 4, which dealt with network load balancing and clustering. Remember that hte main difference between to the two is that NLB is service-aware and can throw any server requests to the "most available" server, while clustering rotates through each server blindly.

Homework:
  • Lab Questions pg 53 1-4.

Strategies for Success - 10/29/2007

Today we did Units 11-13, one of which included the topic of Comfort Zones. Bobbi Steelman made a great performance by coming in and blasting you guys out of your comfort zones. Remember, we all have comfort zones, and we need to recognize them so we can rise above them.

Starting next week, we're going step up the pace and hopefully get done with class a week early. I'll keep you posted as we get through.

Homework:
  • No negative thoughts for 24 hours!!!

Wednesday, October 24, 2007

IMAP comes to Gmail

I'm having a nerd-moment.

As many of you know, I use Gmail as my primary e-mail address. It was somewhat reluctantly -- I've used every version of Outlook since it debuted in 1997 -- and Gmail's web interface just paled in comparison to what I was used to doing in Outlook. But I needed two things that my old insightbb.com account just wasn't offering me: 1) portability and 2) effective spam blocking. Gmail offered both, so I sold out my need for Outlook's features. That was in 2004.

Fast forward to October 24, 2007. Google announced today that they would start rolling out IMAP capabilities to their Gmail accounts. Why is this a big deal? I mean, Gmail has offered POP3 access for a while.

If you rememeber back from your CompTIA Network+ class (you do remember that, right?), IMAP stands for Internet Message Access Protocol and works as an e-mail messaging protocol. Simply put, it's one of the ways we can acccess our e-mail accounts. The other ways are via the web (http) and POP3. POP3 has been the most popular, but it has its drawbacks. The main one for me is that to use POP3, you have to actually download your e-mail off of the mail server down to your client machine. For most people, that's fine, but I find myself on as many as four different clients during any given week. Which means that once I read an e-mail at say, work, I won't be able to look at that e-mail anywhere else other than work! That's been the main reason I've had to abandon Outlook as a mail client and use G-mail's web interface instead. But now, now, grasshoppers, Gmail offers IMAP too...

So, so what? The big deal is that Outlook is an IMAP client as well! And when setup to use IMAP, Outlook won't be downloading my messages off of Gmail onto whatever client machine I'm using. Outlook instead will be channeling Gmail on the web and showing me my messages while staying connected to the Gmail server. I can use four different installations of Outlook to access the same web information.

Hopefully the calendar will sync up as well.

It's Peanut Extra Credit Time!

I extended this offer to my A+ students, and now I extend it to you, o student of Ben. Throw me up a one page paper detailing the new 802.11n wireless standard. I want to know speeds, ranges, hardware requirements (is it backwards compatible with b/g? hmm? hmm?), etc. 10 points are up for grabs, and I need this by the start of whatever class you want me to apply the points to.

Tuesday, October 23, 2007

MS Exchange - 10/23/2007

Ok, so yeah, did the night group talk to the day group (or more likely, read the blog?). 2/3 of you were out tonight (for very good reasons, by the way), so in the night class too, we will be postponing the important chapter four for next week. I'm really wanting you guys to go through this lab because it has us actually setting up clustering & load balancing -- very important stuff if you want to call yourself an engineer. And you do.

Homework:
  • Get to class next week!!!!! :)

A+ Hardware/Software - 10/23/2007

Great class today, guys.

We covered Chapters 7 and 8 today. First up was Chapter 7, dealing with printers -- different types and how we get them hooked up to our computers. Remember the differences between the different types (of printers and connectors). Chapter 8 was over the portable computer which, somewhat disappointingly, is pretty much like a standard desktop computer, except that it's more compact. Heat's an even bigger issue though. Make sure you can tell me the difference between Type I, II and III PCMCIA cards and that you know the basics on how the LCD screen on the notebook computer works.

Next week, we have the first Checkpoint exam, which will cover everything we've talked about thus far in the book -- pretty much all of the hardware portion of this class. I know that I've virtually covered you up with information, and believe me, I understand how overwhelming that can be. Please try not to let the overwhelming feelings bog you down -- judging from where I stand, having seen dozens of other students at the same point you are, you're doing very well. If you really hit the books hard this week, I have no doubt you all will pass the test with flying colors.

Homework:
  • No homework, other than to bust yourself silly studying for this crazy test.

Monday, October 22, 2007

Server+ - 10/22/2007

Tonight we covered Unit 5, which dealt with server upgrades. Remember, Checkpoint Exam next week!

Homework:
  • Other than study for that checkpoint exam, nuffin.

MS Exchange - 10/22/2007

Well, today was a bust. Only half the class showed, and since Chapter 4 is a pretty important chapter, I've postponed today's class for next week. Make sure you're here -- we're going forward next week, no questions asked.

Homework:
  • Get to class next week!

Strategies for Succcess - 10/22/2007

See yourself covering Unit 10 today. Imagine yourself imagining yourself being successful in all you do. And good things will come, grasshopper.

And they did, with Liz Heller. Liz came in after our unit and discussed with us the importance of our portfolios and resumes and cover letters (oh my!). We then took the rest of our class time and worked on the portfolios, resumes and cover letters of our own, which will be a major part of your grade in this class.

Homework:
  • Continue work on portfolios!

Wednesday, October 17, 2007

Securing Your Wireless Router

I just realized it had been a while since I had blogged about something else other than specific classroom activities. I wish I could say that that was because I had been extremely busy, but that's only half of the case. The other half is that I'm lazy.

Anyway, one of the topics in my Tuesday A+ class was configuring a router. We actually connected to the classroom router and had a look around. There were several instances where I said sentences that began with the words, "If this were a wireless router...", so we had to use our imaginations a bit. So I decided that this blog provided a great opportunity to show you this configuration, step by step, if you were at all interested.

The first thing we need to do is actually find our router. Remember, the router is our gateway out of the network, so we need to find the address of our gateway. We can use a great little command-line tool called ipconfig to help us figure out what that address is. To get to the command prompt, we click Start > Run, and type cmd.

In the command prompt window, type ipconfig. This returns the following output, which is our networking configuration info:



The line we're looking for is the router, or gateway, and we see this listed under Default Gateway. Its address, as you can see, is 192.168.15.1 Now, we simply take that address and type it into any web browser. After typing in our credentials (check your router's documentation for more information), we are presented with this opening configuration screen:



Here, there are many things we can configure for our network, such as the router (Default Gateway)'s IP address, the range of IP addresses the router will assign, the name of the router, etc. But what we're concerned about is making sure that our own computers are the only ones that will be able to access this router (no deadbeat neighbors, please!). So we will click on Wireless and be presented with this screen:



On this particular router, we can choose to broadcast in 802.11b or 802.11g or both (more on that later in class), and choose the SSID, or name, of the network. Mine is set now to Spolai105. But here, we want to go one step further in to the menu and click on Wireless Security:



Here we're presented with a few options. First, the security mode can be basically one of two things: WEP or WPA. WEP is easily cracked, so I'd recommend choosing WPA, if at all possible. The thing is, my stupid wireless card won't support WPA, so I'm stuck using the old school WEP. That's ok though, because I really doubt that my elderly neighbors will be trying to hijack my Internet connection to send out porn spam. But, I've been wrong before.

Anyway, I've chosen WEP, and given some more blanks to fill in. The first is "passphrase". I'll type in a password here (by the way, this is not the real information on my router), halleberry and then click Generate. You'll see that I'll get four possible keys to choose from. I've chosen to make the router require the third key. If I were to click Save now, the router would reboot, and I'd have to type in the key in the configuration settings of any wireless device I want to connect to the router. That would be nice, but I'm not done yet.

I want to add yet another layer of protection to my router, just in case my key is cracked. I want to only allow certain MAC addresses on the router, which can be set to my personal computers. Anyone else who tried would be denied. Blam. I say that like it's totally impossible to spoof a MAC address. It's not. Regardless, I'll click on Wireless MAC Filter and get this screen:



Here, I can choose to deny specific MAC addresses, or deny everyone except certain MAC addresses. I'm a paranoid delusional, so I'm going with the second choice. Then, I'm going to actually put those MAC addresses in the list:



Now, I can start typing in the names of MAC addresses I want to allow. How do we find out our MAC addresses, you ask? Great question.

We need to open back up the command prompt like we did before, and reissue the ipconfig command. This time, we need to add the /all switch to it, like this:



The physical address is another way of saying MAC address, and so we need to type in the physical address of our wireless card. If your computer has a wired network card and a wireless card, like mine, make sure you get the physical address of the wireless card. In this case, mine is 00-0E-35-E0-FD-54. Either typing it over, or marking and pasting it over, I can get this into the MAC Filter list (see above) and allow this particular MAC address have access to the router (and ulitimately, the Internet and any other computers allowed on the network.

Hopefully this has made the process of securing a wireless router a little less daunting. This is a necessary task, since the majority of consumer routers we see today are shipped with no security enabled. Too many people simply plug in their routers and go -- leaving themselves exposed to evil elderly people with porn spam to send. Lock 'em down, grasshoppers.

Tuesday, October 16, 2007

MS Exchange - 10/16/2007

Tonight we heard from Scott Duvall, the systems administrator for Holland CPAs in Bowling Green. Scott shared some of his stories of implementing Exchange 2007 in his organization and various other aspects of his job.

Next week, we'll pick up on Chapter Four, make sure you're ready!!

Homework:
  • No Homework!

A+ Hardware/Software - 10/16/2007

Today, Chapter 6 was covered, which was an introduction to networking. I like to call it "Net+ in a Day". We covered a whole host of topics, including network topology, network cabling, network protocols, and then some popular command line tools in TCP/IP (like ping, arp, netstat, ipconfig, etc.)

Scott Duvall from Holland CPAs also dropped by to talk for a bit about various aspects of his career as a systems administrator. Scott spoke briefly about some of the projects he's been involved in and shed some light on his philosophies regarding different aspects of his day to day activities. Interesting stuff.

Homework:
  • Chapter 6 Exam Questions 1-10.

Monday, October 15, 2007

Server+ - 10/15/2007

Tonight we conquered Unit 4, dealing with Uninteruptible Power Supplies, racks (nice rack! huh huh huh), and network cabling.

Homework:
  • Questions 1-22 starting on pg 4-45.

MS Exchange - 10/15/2007

Today we took a little break from the daily grind and instead fixed a computer for a friend of Ryan Wigginton in financial aid. He asked me to thank you guys for working on it.

Homework:
  • No homework!
  • Be ready to launch into Chapter 4 next week!

Strategies for Success - 10/15/2007

Today we did Units 7, 8, and 9, which dealt with our attitudes and how our beliefs make up our current reality. Remember, words turn into pictures, which turn into emotions. Emotions drive our decisions and therefore dictate our lives. Speak positive words to yourself! Our minds talk to us 6 times faster than other humans, so use that speed to your advantage!

Next week, Liz Heller from Career Services will be speaking to our class and helping us with resumes, portfolios and cover letters. After she's finished, we'll actually get started on them and get a running start for the end of the quarter due date.

Homework:
  • No homework!

Tuesday, October 09, 2007

MS Exchange - 10/9/2007

Chapter 3, pimps.

Homework:
  • Chapter 3: 1-11, odd.

A+ Hardware/Software - 10/9/2007

Today we covered Chapters 4 and 5, which dealt with the I/O (input/output) system of our computers and mass storage in our computers.

Three things I'd like you to remember are IRQs, I/O Addresses, and DMA settings.
  • IRQ - How devices talk to the processor. Remember, the interrupt is simply a request and the processor can say no if it needs to (maskable interrupt). However, the device can say NOW! with a non-maskable interrupt. (NMI) Oh, KNOW YOUR IRQ TABLES!! :)
  • I/O Address - How the processor talks to devices. Processors, despite being the kings of the computers, are pretty polite and can wait on a device if necessary -- the processor just can't do anything else until the device responds.
  • Direct Memory Address - These are paths that allow devices to bypass the processor altogether and directly access the RAM. Most of these are obsolete, but make sure that you know that the floppy drive uses DMA 2.
In Chapter 5, we talked about ways to store mass amounts of data, and typically this will mean the hard drive (although we did cover lots of other alternatives). Make sure you know your hard drive "geometry" and be able to identify what tracks, sectors, platters, and cylinders (we didn't go over cylinders today -- make sure you look over your notes from previous classes!)

I also introduced the idea of hard disk arrays, which are collections of hard disks designed to keep our data in one of several methods -- each with their own benefits and drawbacks. Make sure you know the differences between RAID0, RAID1, and RAID5.

Homework:
  • Chapter Four - Exam Questions 1-10
  • Chapter Five - Exam Questions 1-10

Monday, October 08, 2007

Server+ - 10/8/2007

Tonight was Unit 3, Server Room design. It was a nice easy class, and I think fun was had by all.

Homework:
  • No homework!

MS Exchange - 10/8/2007

Today, unit three was covered where we actually went through and explored the Exchange System Manager. We'll be spending a lot of time in it, so get comfortable with it!

Homework:
  • Chapter 3: 1-11 odd.

Strategies for Success - 10/8/2007

Today we received DiSC training from Jeremy Atwell, the Draughons King of well, uhm, DiSC stuff. We all learned something about ourselves, I hope.

One thing for sure, each main behavioral tendency (D, I, S and C) is well represented in our small class, which should make for some interesting dynamics as the class goes on.

Uncle Lou talked us through Units 5 and 6.

Homework:
  • No Homework!

Wednesday, October 03, 2007

MS Exchange - 10/2/2007

Yikes.

Well, after a crazy night, we finally got Exchange installed, but geez-louise, what a journey. If you weren't in class and are somehow interested in what happened, read on.

It all started with the same type of thing that happened in the Monday class -- students could start forestpreppping just fine, teacher could not. I have no idea why that was, it just was. I finally was able to do my forest and domain prepping, but after that, our domain controllers wouldn't replicate. Remember why?

Remember that server clocks have to match up exactly in order for replication to work properly. Knowing that, I was checking our time down in the system tray to make sure that the times were the same on computer one and two. Yep, both said 6:43 (or whatever).

After some headscratching and idea tossing with Brent, we checked the time zone of each computer and -- lo and behold -- each computer had differing time zones, which meant the times were really off by an entire hour. D'oh. Once that little error was fixed, replication occured and we were on our way. Ugh.

Finally, we got installed, and next week, we'll actually start using this blasted program.

Homework:
  • I wouldn't feel right giving you guys homework just yet. So, I won't.
  • Uh, YOU'RE WELCOME!

A+ Hardware/Software - 10/2/2007

Hey guys, sorry for the late post. This is literally the first chance I've had to post since we got out of class. Wow.

Anyway, we covered the ins and out of the main system board (AKA the motherboard), and some of the common things we like to plug into them. Some examples of stuff we do like to plug into motherboards are hard drives, expansion slots (and then all the stuff that goes into those), processors, RAM, etc.

Later, we did lab 3, which had us exploring the BIOS settings of our computers. Keep in mind that the book examples were 10 years old, and that each motherboard has its own BIOS which differs a little bit from other BIOSes. As long as you know the basiscs of the BIOS, which is what I was going for with that lab, you'll do fine.

We covered a lot of information today, and hopefully I didn't totally drown you with it. See ya next week!

Homework:
  • Chapter 3: Exam Questions 1-10 (the multiple choice questions)

Monday, October 01, 2007

Server+ - 10/1/2007

Tonight we covered Unit 2, which dealt with storage. We started at the hard drive, well, inside the hard drive, really, and covered all the parts inside and how they all work together to store our data. Then, we moved to the connectors of these hard drives (IDE and SCSI) and then on to technologies that help us keep our data safe and/or fast.

Homework:
  • No Homework
  • Study Unit 2 for the test next week!

Microsoft Exchange - 10/1/2007

Well, today was kind of weird in that everything kind of went haywire. I have a sneaking suspicion it has something to do with our domain controllers replicating, but it's still annoying that nothing seems to be working. Hopefully by next week we can get things going.

Homework:
  • No homework!

Strategies for Success - 10/1/2007

Today's class was marked by Units 2 - 4 and the taking of our DiSC assessments. DiSC is an extremely cool tool that allows us to get to know ourselves enable us to understand and communicate with other people effectively. Seriously, cool stuff.

Homework:
  • No homework!