Re: Adding printers to NTPRINT.INF
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 26 Nov 2005 03:52:50 -0800
Yes, but this isn't possible with some driver packages.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SnVuaW9y?= <Junior@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
26 nov 2005 in microsoft.public.windows.terminal_services:
> I believe that an easier way to install the drivers on the TS is
> to find the driver install package, right click on the .inf file
> and this installs the drivers for you. Much less work than
> actually installing the printer and uninstalling it.
>
> "Vera Noest [MVP]" wrote:
>
>> If the drivers are really Windows Hardware Quality Labs (WHQL)
>> signed drivers, you can install the driver on the server.
>> Just install a local printer on the Terminal Server (you don't
>> actually need to have the printer connected), but do *not*
>> print a test page during the creation. Then delete the printer
>> again. The server will keep the driver and use it to
>> autocreated the client printer.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Myles Duffy" <Myles.Duffy@xxxxxxxxxxxxx> wrote on 29 sep 2005
>> in microsoft.public.windows.terminal_services:
>>
>> > We use win 2003 terminal services for remote clients that
>> > only print to their own local printers (never to a server
>> > attached printer).
>> >
>> > I understand the auto creation of client printers and that
>> > has all been working great. What I am confued about is
>> > whether or not there is a way to get a new printer which
>> > supplies a supposed mircosoft certifed driver that is not
>> > contained in the ntprinit.inf installed so remote users can
>> > have their a client attached printer of the new printer to
>> > work wiithin their session.
>> >
>> > I have seen the new "hit it over the head with a hammer"
>> > feature of win 2003 sp1 which allows the specification of a
>> > single new fallback printer driver to be installed for all
>> > unknown printers but that does not work ini our case.
>> >
>> > I have also seen article Q275495 at:
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;q27549
>> > 5 that talks about using the PrinterMappingINFName and
>> > PrinterMappingINFSection to specify a new inf file that can
>> > be used to map an unknown printer to a printer known to
>> > ntprint.inf.
>> >
>> > Both of these assume that there is a backward compatible
>> > driver available for a new printer.
>> >
>> > I've seen articles that talk about modifying the ntprint.inf
>> > to add a printer but the above article says this file has a
>> > digital signature and if you edit the fiile it really screws
>> > things up. I've also read things that tell me I should modify
>> > the ntprint.inf.
>> >
>> > Since Win 2003 has been out for 2 years many of the printers
>> > in ntprint.inf aren't even made any longer. How do you go
>> > about adding a new printer driver for a new and currently
>> > available printer that is not contained in the ntprint.inf or
>> > driver.cab for win 2003?
>> >
>> > We need to support new printers with supposedly Microsoft
>> > certified drivers in client sessions that do not have
>> > backward compatible versions of drivers in the ntprinit.inf
>> > that allow us to use the new printers client attached and
>> > through that specific client session only.
.
- References:
- Re: Adding printers to NTPRINT.INF
- From: Junior
- Re: Adding printers to NTPRINT.INF
- Prev by Date: RE: TS crashed and Blue Screen of Death
- Next by Date: RE: TS crashed and Blue Screen of Death
- Previous by thread: Re: Adding printers to NTPRINT.INF
- Index(es):
Relevant Pages
|
