I expect that, when a fault is logged though to me to investigate, that some troubleshooting has been done.

“Printer jams.  Vendor technician has thoroughly tested printer.  I think it’s a driver problem.”

And that was it.  No other details.

What did they mean by ““Printer jams?””.

Is it physically jamming?

I’m never seen a printer driver cause that.  Perhaps it’s stopping mid-print.  ie. stopping at page 10 of a 20 page document.

I bounced the call back, as there was not enough details.

I’ve heard nothing further since.

Physical printer jams are caused by one of four things:

• Incorrectly loaded paper trays.
  (Lexmark Optra’s were infamous for this.)
• Non-laser printer paper being used in a laser printer.
• Paper stuck in the printer’s paper path.
  (this is caused by failing to remove all the paper from a previous jam)
• Paper not stored in the same environment as the printer, being used.
  Changes in temperature and humidity can cause paper to jam.

From Microsoft, February 2007:

Distribution Point
You must plan for the appropriate number and placement of distribution points. This kind of planning is basically the same as you would do for any other deployment of SMS packages. However, there are some considerations specific to Operating System Deployment.

Consider the number of computers that can be deployed at one time from a given distribution point. The processing speed and disk I/O of the distribution point must be considered along with the available bandwidth on the network, and the effect that the size of the image package will be on those resources.

For example, on a 100Mb Ethernet network, if no other server resource factors are considered, the maximum number of computers that can process a 2GB image package in one hour would be 23.

1 Megabit transfers 8 Megabytes of data
100 Megabits/sec = 12.5 Megabytes/sec = 750 Megabytes/min = 45 Gigabytes/hour= 23 images @ 2GB per image.

In reality, the number might be far less. So it you need to be able to deploy a specific number of computers within a specific time frame, you will need to distribute the image package to an appropriate number of distribution points, and use SMS features such as protected distribution points and branch distribution points to ensure that the appropriate destination computers receive the image.

- Planning ConfigMgr Site Systems for Operating System Deployment

Yes, I know the weblink states ConfigMgr.  Microsoft has a habit of revising content when they release new products.
This Microsoft advice applies to SMS 2003, and SCCM when doing Unicast transfers.

Real world?
50 PCs per night per site.

If you used mulitcast, with either Ghost Solution Suite, or Microsoft SCCM/WDS; you could do as many as you can support the next day.
Heck, I know of a 250 PC deployments a night project.  They could have done more, but the customer said no.

If you look under my Useful Links tab, you find some further information about SMS & WDS