Network Printer

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Guys...

Is it possible to map a network printer from a batch file without the use of login scripts?

Did a google on this but not getting anywhere

 

I agree with the sum of Sparky's post. Why do this other than as a logon script? There are sample VBScripts that do this quite easily and place an icon on the desktop, but why make it so the scripts are run manually? I guess I don't understand your purpose in wanting to do it manually.

 

Basically its because the user is at different locations, some where there is a file and print server and some where there isnt, so creating a logon script on the server would mean it would take forever to pull down in the location where there is no server... does that make sense? So to avoid it, I wanted to create a map network printer command for when they are in the file and print server location

 

Laptop

 

What do you mean? The printers are installed on the server, if a logon script is used that is what pulls the list of printers down depending on which printers are specified in the .ini file.

 

Dont know if your thinking of a different setup but that wouldnt work, basically we have a server which the printers are installed on, so in user manager the ini file is specified IF a profile is setup for the user on the server then within that ini file is the specified printers. If the ini file is not specifed no printers will be pulled down.

Anyway dont worry, ive resolved it by creating a batch file which allows the user to connect up to the specified printer when in the location where the server is!

 

Makaveli, all you have to do is, on the Windows client, add a network printer. The client will, as Sparky says, install the drivers that it finds on the print server locally. All a user has to do is then select the printer just like it was a local printer. If they try to print to it and the client is not connected to the correct network, you'll just get a "printer failed to respond" type error.

 

Yes thats what I explained to the helpdesk, but the user insisted on another way to do it as it was too complicated for her to do each time....although we do have a big list of servers to scroll through and locate, its not very hard to remember! But anyway im sure u know what users can be like......

 

How do you mean "each time"? You only have to do it once per printer.