I am currently performing tests at home, where I do have a SRSS 4.0
with uttsc
2.0.23 on an Intel Xeon server. I use a Windows XP machine as my
Windows
Terminal Server, but I found something of interest using the
"Follow-Me-Printing" addon.
I as well forgot to mention that, since HP did not provide his
"hppi" (also
known as "JetDirect" or "HP JetAdmin") package for x86 platform, I
put a CUPS
server (the one from the Companion CD of Solaris 10 8/07) and added
my printer
with it, both on my client's setup and at home.
So, with the "Follow-Me-Printing 0.3" addon, we are supposed to put
"SR-Default" as the print queue name in the "-r printer:SR-Default"
option to
the "uttsc" command. I did some testing here and found that when I
ran the
"uttsc" command within an xterm, I tried to print from Windows to my
"SR-Default" print queue, but nothing went out on the printer. It was
dissapearing like gone in a black hole. But, closing my Windows
session and
back to JDS, in my xterm, I had an error like:
lp: unable to print file: client-error-not-found
Googlin' it shortly, I found something related to a bad print queue
name. So
I did a try with the exact print queue name, instead of the "SR-
Default" and
it worked!!
So on my Kiosk script, I put a variable like this:
QUEUE_IMP="`cat ~/.printers | head -1 | awk '{print $2}'`"
and then, I added this option to "uttsc":
-r printer:${QUEUE_IMP}
and it worked perfectly!! My test print went out perfectly from
Windows.
Now, I have to test it on my client's setup, but I feel pretty
encourraged.
Is somebody has any clue on why the "SR-Default" name doesn't do the
trick
here? It was so well explained in the documentation... I'll keep
you all in
touch on this, for what will be the results of our tests at my
client's site.
Ben Audet
On Tue, 11 Mar 2008 08:39:46 -0500, Benoit Audet wrote
Hi fellow Sun Ray Gods! (I thought it would be a good start calling
you all 'Sun Ray Gods' ;-))
One of my clients have in place a Sun Fire x4200 with Solaris 10
8/07, with SRSS 4.0 and uttsc 2.0.23. Following patches has been
installed on the servers: 127554-01 and 127554-01. AFAIK,
everything seem to be working flawlessly.
We installed some HP printers on the server, using CUPS, and when
printing
from Solaris (let's say from a JDS session), it prints perfectly.
We as well put in place the "Follow Me Printing" 0.3 and it works
just perfectly.
What we want to do is to be able to "push" de print queue to through
RDP with "uttsc" to be able to use the same printer from Windows
Terminal Server (which is a Windows 2003 Server), but this is where
we have problem.
We did some tests using the uttsc command options: '-r printer:SR-
Default'
(without the quotes...). Windows seems to see it, but use a generic
driver, instead of the good one. So we put '-r printer:SR-
Default="HP LaserJet 8150"'
(using only the double-quotes for the driver name - and this is the
exact
driver used if we try to install this printer in Windows 2003 (it
works well this way on Windows 2003)): the printer seems to be seen
perfectly, with the good driver, but again, we're unable to print
yet.
Finally, we decided to test "manually", without the Follow-Me-
Printing option. In a terminal window, we put this command in a
shell:
$ uttsc -r printer:exact-print-queue-name="HP LaserJet 8150" -m
ip-of-the-win-server
but we get the same result. Is there anything I should do to be
able to "push" the printer through RDP with uttsc that I am missing?
Related to the documentation, it should do the trick... ...and I
push a good driver to Windows, a driver that works for *this*
printer when installed localy (and of course the driver is on the
Windows 2003 Server).
Thanks in advance!!
Ben Audet
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
Benoît Audet
GRAB Informatique Inc.
[EMAIL PROTECTED]
Tel.: (418) 871-6946 #25
Cel.: (418) 802-5882
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
