Renamed Tree; Printing Problems

[bluffer]

I've just renamed my 4.11 tree (about to upgrade to NW6 and the old name would have clashed with a tree that already exists in our network).

Unfortunately I didn't spend enough time looking at printing and this has now gone up the wall. Windows workstations have NDS print queues looking at \\old_tree_name\queue. There's about 250 users, and I don't fancy manually reinstalling all those printers so I'd be grateful for any suggestions.

Thanks!!

 

[TheLad]

If you have setup Point and Print on all of these printers, your best option is to write brief instructions on how the users can remove and reinstall their printer. Otherwise you will personally have to visit every workstation. In my experience, registry hacks don't seem to be effective in this case. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Provogeek]

Use the ZENLite distribution (should still be avilable someware). In the policy package you can distribute windows network queue mappings. Not sure if you can distribute drivers, been awhile since I've used it. The software is free and if your familure with Windows policies you should have no problem with ZENLite.

If you have WIn2K workstations, you may have problems with policies. The ZENLite is ZENv2, came out before 2K so support isn't there with out patches.

You can also make a mad dash to get NDPS up and running. This would prove to be a pain in the $%! though, NDPS can be tricky but it allows you to distribute printer mappings to users with out touching the desktop. This includes the driver. Also, NDPS 2 has a bug that makes the driver install on every login until disabled by admin. Some patches came out that fixed it in some cases, didn't help in others. I've never tested NDPS 3 on NW4.x Brent Schmidt CNE, Network +
Senior Network Engineer
provogeek@hotmail.com
East Bay, California; USA

 

[bluffer]

Thanks for all your help - I did end up going to each machine and re-adding the printers so it was a bit of nightmare week (my own fault though!! - more testing next time!!).