Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 769
  • Last Modified:

sbs 2003 client's printer driver problem

I have 6 Brother HL5240 printers attached to clients on my SBS 2003 R2 network. All the printers are shared and listed in the directory.
5 clients are running XP Pro, and using the Brother recommended XP driver v3.16

I recently installed a new PC, running Vista Business, and connected another HL5240 printer locally to it. I had to use a newer Vista specific driver v3.24. This printer was then shared also.
The problem I have is that one of my existing XP Pro clients has decided to start using the Vista Driver. The user started having problems printing from multiple applications on this particular client, and the driver is indeed the vista one v3.24, which must have been installed via the server.

Realising this, I cleared all the printer drivers from the XP client, installed the older v3.16 XP specific driver, and then added in the printers again. This resolved the matter for 2 days. Then, on the third day, the XP client changed again to the newer Vista driver v3.24. Can anyone advise how I can get this resolved once and for all? My concern is that other clients will start moving to the newer driver too, causing further problems.



0
jbr0lly
Asked:
jbr0lly
  • 9
  • 9
1 Solution
 
souseranCommented:
With such a small number of PCs, I'd remove all the drivers again and set up the printers on TCP/IP ports with the drivers you want for each, including the Vista unit.

Or you could downgrade the Vista unit to XP. :-)
0
 
jbr0llyAuthor Commented:
The pc came with Vista business preinstalled, so I have no XP licence for a downgrade & seems a waste of the Vista licence which we have already purchased.
There are in excess of 20 PC's in my network, I just listed those that are connected to this particular printer type. The other pc's use different printers.
I would not be familiar with setting up printer TCP/IP ports , etc. Sounds like a lot of work if all the drivers will need cleared on each client. Also, the server hands out dynamic IP addresses, so would this work in this instance?


0
 
souseranCommented:
Ah. With that many units, no, that wouldn't be your best solution. Yes, it would be a bit of work to clear all the printers for each unit and start again. Since the other systems were already printing to this printer, was there a reason you made it a shared device on the Vista PC? If that's the only unit with Vista on it,  I would think you'd want to isolate it so as to avoid the kinds of problems you're experiencing. Can you remove the share, then clear the drivers on one of the affected units and see if that makes a difference?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
jbr0llyAuthor Commented:
Thanks, just to clarify:
This new PC is located in a location separate from the other PC's. The unit it replaced was a printer server as well, so we replaced like with like. However, I am starting to tend to your original suggestion that maybe we should just replace this os with XP Pro!
I have already spent time correcting an XP unit, for it then to move to the newer Vista drivers after a few days again. This suggests to me that the SBS2003 has taken on the newer vista drivers as well.
If I replace the Vista OS with XP, will this automatically change the drivers on the SBS2003 back to the older version too, as at present it appears to showing the newer Vista drivers as well?
0
 
souseranCommented:
Q. If I replace the Vista OS with XP, will this automatically change the drivers on the SBS2003 back to the older version too, as at present it appears to showing the newer Vista drivers as well?

A. I believe you will have to manually resolve those drivers and any others that have changed. However, you should only have to do this once.

Re the Vista downgrade, if you purchased the unit from an OEM like Dell or HP, they may offer what they call a "Genuine Windows Vista┬«  Business with Downgrade Rights Service to Windows┬«  XP Professional." If you contact them and find that they do, you might also want to ask them about providing XP drivers for your unit. Otherwise, if you post the make and model here we should be able to help you locate those. Let me know if you decide to go that way, and I'll share with you my recommended downgrade procedure.
0
 
jbr0llyAuthor Commented:
Hi, I am hoping to carry out the downgrade on Saturday. This particular Dell was not purchased with Downgrade Rights, but I have reviewed Dell's website & it seems straight forward enough.
It is an optiplex 760 MT, and when I typed the service tag into Dell's website, I was able to see XP drivers, which I will download prior to the change.
Any other help much appreciated.
0
 
souseranCommented:
We have OptiPlex 760s and yes, the drivers from the Dell site should work. Assuming that you're doing the install manually, and not using an imaging or deployment solution, this is the process I generally recommend for *ANY* Vista to XP downgrade is this:

Save any important data on the unit to external media such as a USB flash drive, external hard drive, etc.

Download DBAN from:

http://dban.sourceforge.net

Create the necessary media. For the 760, you'll need Download Darik's Boot and Nuke 2.0.0. Direct download link here:

http://superb-west.dl.sourceforge.net/sourceforge/dban/dban-beta.2007042900_i386.zip

Find and download *all* the most current versions of the necessary XP drivers, BIOS, etc.
Print out a copy of the Dell "Driver install order for desktops and laptops" article available here:

http://support.dell.com/support/topics/global.aspx/support/downloads/en/driver_install_order?c=us&l=en&s=gen&~lt=print

If you haven't already, upgrade the system's BIOS to the most current version BEFORE YOU BEGIN.

Disconnect the system from the network.

Boot to the media onto which you have burned DBAN. At the prompt, type AUTONUKE. Press Enter. Take a break until you see the black screen that indicates the disk wipe has completed.

If you *are* using an imaging solution, this is the step at which you'd perform that procedure. Otherwise:

Boot to your OS media.

Once the OS has been installed, follow the steps in the Driver install order for desktops and laptops article.

After that's done, reconnect your network cable and once you have network connectivity, go to

http://update.microsoft.com

Do a Custom install of the necessary OS updates. This will allow you to see what you'll be getting and opt out of any updates you don't want.

Reinstall all other software applications.

Finally, copy back your saved data.

Look forward to hearing how it goes.
0
 
souseranCommented:
One other thing, if you *do* have an imaging solution and it depends on WinPE, there are a number of problems with that particular solution and the NIC drivers on the 760. We're still trying to find the solution to that in our shop. If you can put your image on a flash drive or CD-ROM, it should boot and run fine.
0
 
jbr0llyAuthor Commented:
I am currently running DBAN, and have downloaded my drivers, etc.

I have also got an XP CD, which I have added SP3 too, but I have been reading on the internet about problems with XP & SATA Drivers. This Dell has an WDC SATA drive: this will probably cause my OS CD to fail on loading?, and I can not see where I can get these drivers from. for this PC, Dell makes mention of Intel Matrix Storgae Manager pre install drivers, but I think this is something different?

0
 
jbr0llyAuthor Commented:
Sorry, that last post now appears incorrect.

I found info on the intel website that confirmed the Matrix Storage driver supplied by Dell relates to my WD Sata hard drive, and I have managed to slipstream it into a windows pro installation CD. The installation now appears to be proceeding.
Will update you when I have completed it.
0
 
souseranCommented:
Sounds like it's going well. Did you slipstream using nlite or another method?
0
 
jbr0llyAuthor Commented:
I used nlite  v1.4.9.1 to slipstream.
Will not get the installation finished now until Monday, so will update you after that.
When you said to take a break after running autonuke, I did not appreciate the process would take 5hr's as I have a 300Gb hard drive!

0
 
souseranCommented:
Yeah, autonuke takes a while. :-) But it'll wipe out any Vista remnants, including recovery consoles, and return the drive to as close to a "like new" state as anything I've used. Much better foundation for doing a clean reinstallation.
0
 
jbr0llyAuthor Commented:
Hi, i have completed the installation of XP Pro on the unit. I then installed the Brother HL5240 printer on it, with the 3.16 XP driver, and then connected the unit to the SBS network, using connectcomputer, etc.
However, connecting the unit to the SBS network has updated my driver to the Vista driver (3.24), my original problem on a different unit! This driver must have been supplied by the SBS. Is there now something I need to be doing on the SBS as well to remove this 3.24 vista driver?
0
 
souseranCommented:
The driver absolutely has to be removed from the server. Earlier in the thread we had this exchange:

Q. If I replace the Vista OS with XP, will this automatically change the drivers on the SBS2003 back to the older version too, as at present it appears to showing the newer Vista drivers as well?

A. I believe you will have to manually resolve those drivers and any others that have changed. However, you should only have to do this once.

"Manually resolve" meant you'd need to remove the driver from the SBS by hand. :-)

To do that, first delete the printer from Printers and Faxes. If there are any drivers installed, uninstall them, and reboot the SBS (yes, I know this part may have to wait until after hours). Once you've done that, go to Printers and FAxes | File | Server Properties | Drivers (tab) and select the drivers from the "Installed printer drivers." Highlight them. Click the Remove button. Click OK. Reboot again.

The "and any others that have changed" part of my answer means you may also need to perform this procedure on any of the other PCs that received the Vista driver.
0
 
jbr0llyAuthor Commented:
Excellent, I think I have this now resolved. I followed your instructions above to remove the driver from my SBS, and also from the various desktops that had inherited it.
Everything now appears to running with the XP drivers,and the various printing problems I had have all disappeared. Hoepfully the driver will  not reappear again and I have cleansed the network right.
Your guidance has been excellent & detailed.
Rebooting my unit with XP has also resolved other issues I was having with my scanner randomly freezing, etc, so all good.

0
 
jbr0llyAuthor Commented:
thanks for your patience,  many thanks.
0
 
souseranCommented:
jbr0lly:

Glad to help. :-)

souseran
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 9
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now