Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Moving NT Print Server
- Thread starter snicks2
- Start date
CitrixEngineer
Technical User
You don't say anything about the rest of your setup!
All you need to do for your networked printers (ie ones with a NI device) is to create IP/LPR ports for them on the stand-alone printer server (and install the drivers).
Your clients will then have to map to these printers as usual.
When you say workstation printers, do you mean local printers to workstations that are shared?
If so, then you won't have to do anything to these or to clients that use them.
If I have misunderstood your situation, please provide more information.
I hope this helps
All you need to do for your networked printers (ie ones with a NI device) is to create IP/LPR ports for them on the stand-alone printer server (and install the drivers).
Your clients will then have to map to these printers as usual.
When you say workstation printers, do you mean local printers to workstations that are shared?
If so, then you won't have to do anything to these or to clients that use them.
If I have misunderstood your situation, please provide more information.
I hope this helps
- Thread starter
- #3
Thanks - What I meant by workstation printers was network printers (defined on the PDC) mapped at the client. Users would have to map to the new print server and believe it or not this would generate numerous help desk calls. I wanted to make it easy for them (and us) and have their default printers automatically mapped. Any ideas on that?
CitrixEngineer
Technical User
I know of a utility called Printmig, but I've never used it. This link explains it fairly well:
There is also a utility with the same name, which does much the same thing (a shareware version with nag screen is available):
I hope this helps
There is also a utility with the same name, which does much the same thing (a shareware version with nag screen is available):
I hope this helps
MasterRacker
Active member
snicks,
On any given workstation, whether you've created a LPT port and redirected it or directly connected to a shared printer, somewhere inside that link is a reference to "\\servername\sharedprinter". By moving the shared you've changed "servername". This means that every printer connection on every workstation must be remapped on the workstation. Since the drivers are installed, you shouldn't need to re-install, just re-map) The utilities CitrixEngineer mentioned may help with this, but it simply must be done one way or another.
(BTW: If you were in a pure NT environment the you, at least don't need to install drivers on a workstation. Users can right-click on the printer in Network Neighborhood and choose Connect. The workstation uses the driver on the server. Update the server driver and all users use the update. Yet another reason to get rid of all 9x as quickly as possible.)
Jeff
masterracker@hotmail.com
If everything seems to be going well: you don't have enough information.......
On any given workstation, whether you've created a LPT port and redirected it or directly connected to a shared printer, somewhere inside that link is a reference to "\\servername\sharedprinter". By moving the shared you've changed "servername". This means that every printer connection on every workstation must be remapped on the workstation. Since the drivers are installed, you shouldn't need to re-install, just re-map) The utilities CitrixEngineer mentioned may help with this, but it simply must be done one way or another.
(BTW: If you were in a pure NT environment the you, at least don't need to install drivers on a workstation. Users can right-click on the printer in Network Neighborhood and choose Connect. The workstation uses the driver on the server. Update the server driver and all users use the update. Yet another reason to get rid of all 9x as quickly as possible.)
Jeff
masterracker@hotmail.com
If everything seems to be going well: you don't have enough information.......
AnonGod
IS-IT--Management
- Jun 5, 2000
- 223
This may apply or not, you be the judge.
We recently had a couple of users move to another floor in our building, and they brought their network printer with them, as they were the only ones to use the printer. Our naming scheme for the printers is by floor, so I needed to change the share name of the printer.
After you connect to a shared printer, the client gets the IP of the printer and lists it under the Ports tab of printer configuration. Seeing this, I did not see any drawbacks to changing the printer sharename.
The change went off without a hitch, but Jeff brings up a good point that I am curious if I will run into in the future. I'm sure the 2 clients that moved still have the old printer sharename. And although they can print just fine now, will future updates (new print drivers on the server, for example) not download to these clients, as they have a sharename that no longer exists?
And as far as the "Connect" button - will this mess up communication between the server and the clients, or will NT magically connect them?
Just some things I have come to start to think about as our company grows, and the exact configuration of these 2 clients become harder and harder to remember.....
Not really a question, just my experience.
>
:O>
anongod@hotmail.com
"Drawing on my fine command of language, I said nothing."
We recently had a couple of users move to another floor in our building, and they brought their network printer with them, as they were the only ones to use the printer. Our naming scheme for the printers is by floor, so I needed to change the share name of the printer.
After you connect to a shared printer, the client gets the IP of the printer and lists it under the Ports tab of printer configuration. Seeing this, I did not see any drawbacks to changing the printer sharename.
The change went off without a hitch, but Jeff brings up a good point that I am curious if I will run into in the future. I'm sure the 2 clients that moved still have the old printer sharename. And although they can print just fine now, will future updates (new print drivers on the server, for example) not download to these clients, as they have a sharename that no longer exists?
And as far as the "Connect" button - will this mess up communication between the server and the clients, or will NT magically connect them?
Just some things I have come to start to think about as our company grows, and the exact configuration of these 2 clients become harder and harder to remember.....
Not really a question, just my experience.
>
:O>anongod@hotmail.com
"Drawing on my fine command of language, I said nothing."
MasterRacker
Active member
Anon, sounds like you're describing some fluke of persistent connections. I'vs never seen that one, but I'll
believe anything.
I've never come up with a naming scheme I liked. I'vetried naming printers by type and by location and now I'm naming them by department. That experiment seems to be the best one yet.
Jeff
masterracker@hotmail.com
If everything seems to be going well: you don't have enough information.......
believe anything.
I've never come up with a naming scheme I liked. I'vetried naming printers by type and by location and now I'm naming them by department. That experiment seems to be the best one yet.
Jeff
masterracker@hotmail.com
If everything seems to be going well: you don't have enough information.......
- Status
Similar threads
- Locked
- Question
- Locked
- Question