Tuesday, October 11, 2011

The Print Path - Part 1

For some reason, correctly identifying printing issues seems to be a major blind spot for otherwise excellent technicians.  They struggle with correcting minor printing issues, and this is because they can't actually identify the issue.  In this post, I am just going to introduce the concept of the print path, and explain how a print job travels down that path in order to produce a printout.

When you are sitting at your home computer and you print something out, you are creating a print job which your computer sends directly to your printer.  When you add a network to the mix, that same print job can take several extra steps, and it is often these extra steps that lead to a misunderstanding of printing problems.



In the above diagram, you can see that there are several steps that a print job can make between a computer and the printer.  The first and most basic addition to the print path is the print server.  A print server is added to the path to take the load of managing print jobs off the individual clients, and to keep the connections to the printer simple.  The print server will manage a print queue that manages the jobs until the printer is ready to print them.  For example, lets say that you have 20 people using one printer and they all decide to print at once.  Without a print server that queues those jobs up in order and sends them to the printer one at a time, the printer would be deluged with jobs possibly resulting in an error.  A print server is the main component that allows multiple people to share a printer.

The next main addition is some kind of external application.  This could be a web app of some kind or in a business environment it could also be some kind of mainframe style application.  This adds the possibility that the print job, either in whole or in part, is generated outside of the client workstation, and the user only initiates the job.  This can add a layer of complexity as well.  For example, let's say you made a purchase on your favorite website, and you want to print an invoice.  That invoice will be generated by an external application which then uses your local computer as a conduit to your printer.  This is very similar to many business applications, however it may be that the application is connected to a print server instead of using your computer to make the connection.  Additionally, it may be connected directly to the printer itself, functioning as a print server itself.  The configuration may vary from app to app.

So, basically there are two (or three paths depending on how you count it) that a print job can take from a computer to a printer.  The blue path represents the most common path, and you can remove the external application portion if you are dealing with applications that are only locally installed.  Note:  Web apps are external apps.  The green path deals with an external app that has it's own path to a printer and does not use your normal connection.

Friday, October 7, 2011

I Feel Bad

OK, I created this blog almost two years ago, and I just didn't get around to writing any articles yet.  That wouldn't be such a bad thing if not for the fact that many people have been clicking on this site expecting something and getting, well, shinola.  For this egregious lack of content, I'm sincerely sorry.

So here's what I'm going to do.  I'm going to start writing a few posts about printing very soon.  I've got some clear divisions in my head about troubleshooting printing, but even though I'm going to break this into a few articles, I will publish them together without much of a delay between them, and even cross-reference them so it makes sense.

After tackling printing, it will probably be a while before I write another new article, but when I do, I'll address scripting, networking and I'll even throw the site open for some questions.  From there, we'll have to see.