Re: Migrate Printers with Printmig 3.1
From: Paul Baker [MVP, Windows - SDK] (paulb_at_online.rochester.rr.com)
Date: 10/14/04
- Next message: Cari \(MS-MVP\): "Re: Network Printer Question"
- Previous message: arnt witteveen: "Re: Set the postscript dirver option TTDownloadFormat ("TrueType Font Download Option")"
- In reply to: Steven Worling: "Re: Migrate Printers with Printmig 3.1"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 14 Oct 2004 09:39:09 -0400
Yes, the clients sound fine! I am by no means an expert, and all I can
suggest at this point is that you go through the "additional things to
consider..." section with a fine-tooth comb.
Paul
Additional things to consider before you use this solution
. The solution in the MoreInformation section works only if clients
use DNS or another name resolution method that incorporates DNS when they
connect to the print server. Clients cannot take advantage of this solution
if they: . Are connected directly by Internet Protocol (IP) to the print
servers.
. Use only network basic input/output system (NetBIOS).
. Use Windows Internet Name Service (WINS) but do not use WINS
reverse lookup.
.
. If some clients use WINS, permit those clients to correctly resolve
the print server names. To do this, remove from the WINS database the names
of the print servers that were removed during consolidation.
. The particular node type that you use for name resolution can also
affect the outcome of this solution. You must use a node type that uses DNS
for name resolution. We recommend the hybrid node type (h-node). For
additional information about node types, click the following article number
to view the article in the Microsoft Knowledge Base:
167640 Automatically changing the node type of a Windows NT
workstation
160177 Default node type for Microsoft clients
Paul
"Steven Worling" <sworling@nascar.com> wrote in message
news:%231WPG$WsEHA.3872@TK2MSFTNGP15.phx.gbl...
> Paul,
>
> the clients are all windows XP. printers currently on 2000 servers with
sp4
> going to win2k03 servers
>
> Steve
>
> "Paul Baker [MVP, Windows - SDK]" <paulb@online.rochester.rr.com> wrote in
> message news:eS0q75WsEHA.3788@TK2MSFTNGP15.phx.gbl...
> > Do you meet the requirements listed under "Additional things to consider
> > before you use this solution".
> >
> > What versions of Windows are the clients?
> >
> > <pray>please don't say Windows 95...</pray>
> >
> > Paul
> >
> > "Steven Worling" <sworling@nascar.com> wrote in message
> > news:OVr1jsWsEHA.3136@TK2MSFTNGP11.phx.gbl...
> >> We can move printers to a new server using the Print Migrator 3.1 tool.
> >> everything looks good. But when clients connect based on a KB article
> >> (http://support.microsoft.com/default.aspx?scid=kb;en-us;870911) we get
a
> >> error access denied from the client. We are trying to avoid touching
all
> >> client computers to remap their printers.
> >>
> >> Please Help
> >> Steve
> >>
> >>
> >
> >
>
>
- Next message: Cari \(MS-MVP\): "Re: Network Printer Question"
- Previous message: arnt witteveen: "Re: Set the postscript dirver option TTDownloadFormat ("TrueType Font Download Option")"
- In reply to: Steven Worling: "Re: Migrate Printers with Printmig 3.1"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
