We are currently using the Canaveral New Moon system, and are running
into an issue with the printers. The application that is primarily
being used requires the exact name of the printer be entered into it.
The clients are connecting through the web interface of New Moon.
The problem we are running into is that the client's printer name, has
an underscore added to the end of it with a number (assuming connection
or client id number).
Every morning, when the client computers connect to the New Moon
System, the user has to log into the application, and change this
printer name. (i.e first login printer name is "agg_45", next login,
printer name is "agg_128").
How can I set some sort of static name for the client's local printer?

Mike
mlawrence(at)fisher-wavy.com

The only way I know of is if the server and client are on the same logical
network, so you can install the client printer on the server as a local
printer. Auto-created Session printers must contain the session ID
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com


"mike" wrote:

> We are currently using the Canaveral New Moon system, and are running
> into an issue with the printers. The application that is primarily
> being used requires the exact name of the printer be entered into it.
> The clients are connecting through the web interface of New Moon.
> The problem we are running into is that the client's printer name, has
> an underscore added to the end of it with a number (assuming connection
> or client id number).
> Every morning, when the client computers connect to the New Moon
> System, the user has to log into the application, and change this
> printer name. (i.e first login printer name is "agg_45", next login,
> printer name is "agg_128").
> How can I set some sort of static name for the client's local printer?
>
> Mike
> mlawrence(at)fisher-wavy.com
>
>

Great. This should make things fun.
Well... Now I am unable to print from the client or the server to
within a specific app. Check the event logs and found the following;
"Document 158, COMMANDoutput owned by mlawrence was printed on agg_95
via port IFS_PORT_95_2. Size in bytes: 0; pages printed: 1"

The very interesting part is that I can print from notepad or any other
app, and find that the event logs show the same output for the print
job, except the end of the message, it states it is printing via port
"IFS_PORT_95_0".

Any ideas?
Mike
mlawrenc(at)gmail.com

It'sm not uncommon for non-terminal server friendly applications to have
printing problems, i.e. some programs will not accept a printer name longer
than 25 characters, or will not default to the Windows Default Printer, but
rather require the default printer to be set in the application.

These kinds of problems must be addressed with the application developer, as
it is there programming choices that induce this kind of problem. If you can
print from standard Windows application, but not from a specific application,
I'd lean on that application vendor for a solution.

I will point out this particular article about applications not using the
Windows API for getting the printer list:

http://www.printingsupport.com/mambo...id=40&Itemid=1


--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com


"mike" wrote:

> Great. This should make things fun.
> Well... Now I am unable to print from the client or the server to
> within a specific app. Check the event logs and found the following;
> "Document 158, COMMANDoutput owned by mlawrence was printed on agg_95
> via port IFS_PORT_95_2. Size in bytes: 0; pages printed: 1"
>
> The very interesting part is that I can print from notepad or any other
> app, and find that the event logs show the same output for the print
> job, except the end of the message, it states it is printing via port
> "IFS_PORT_95_0".
>
> Any ideas?
> Mike
> mlawrenc(at)gmail.com
>
>