printui.dll problem

OK, here are the Details:  I have an office setup with Win2K servers and XP Pro work stations.  On one of the servers I have created multiple print queues (some for different trays on the same printer).  I am using a script like the following to map network printers on the workstations:

REM Delete the printer if it is there
rundll32 printui.dll,PrintUIEntry /dn /q /n "\\server\US Tray2 Toshiba"
REM Map the printer
rundll32 printui.dll,PrintUIEntry /in /q /n "\\server\US Tray2 Toshiba"
REM Apply the saved settings file
rundll32 printui.dll,PrintUIEntry /Sr /q /n "\\server\US Tray2  Toshiba" /a "\\server\share\Tray2Toshiba.dat"

I created the saved settings file (Tray2Toshiba.dat) with the following:
rundll32 printui.dll,PrintUIEntry /Ss /n "\\server\US Tray2  Toshiba" /a "\\server\share\Tray2Toshiba.dat"
I did this while logged on as a user with the standard permissions that all user have (Domain Users, Local Administrator of the workstation). PS - all users have full control over the print queues.

The Problem:
When I run this script it does indeed map the printers and applies the saved settings file.  But, the settings in the saved settings file do not always take effect (i.e. - printing preferences tray select is set to auto select not Tray2 like it is supposed to be.)
The kicker is that sometimes it works and sometimes it does not.  When it does not I have to go to the PC and change the tray settings manually.  On top of that though, when I try to manually change these settings on some of the users PC who used this script, it will not save the changes.  It always goes back to auto select for the tray.

Any ideas?  I am assuming that some how it has to be a permission issue or something?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tfountainAuthor Commented:
Problem solved.
After doing further research I found the driver to be the problem.  I was using HP's generic 8100 series PCL driver.  I downloaded the PCL6 driver for my specific printer, recreated my saved settings file and re-execute the scripts on the PC's.  It works perfectly.
Question answered by asker or dialog valuable.
Closed, 500 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.