mapping network printer

neo468neo468 Member Posts: 123
Is there a way to map a network printer remotely without using the printer wizard. Like through a remote command line
1's and 0's

Comments

  • sprkymrksprkymrk Member Posts: 4,884 ■■■□□□□□□□
    Hmmm... Sorta maybe...
    You could try telnet or psexec to the remote machine and try :
    net use lpt1 \\servername\printername
    but I think that sets it up as a local printer on the remote machine. Which works, it might just not be what you want.
    All things are possible, only believe.
  • TrailerisfTrailerisf Member Posts: 455
    create login scripts and map it... set the profile in AD to use a login.bat

    http://www.kixtart.org/

    Is a good site to get scripts...
    On the road to Cisco. Will I hunt it, or will it hunt me?
  • gojericho0gojericho0 Member Posts: 1,059 ■■■□□□□□□□
    you can use the PrintUI from the the command prompt.

    Open the command line and type

    rundll32 printui.dll,PrintUIEntry /?

    This will give you all the different switches supported...type what you want to do in a text file then save as a batch or vb script and you should be good to go
  • TeKniquesTeKniques Member Posts: 1,262 ■■■■□□□□□□
    Trailerisf wrote:
    create login scripts and map it... set the profile in AD to use a login.bat

    http://www.kixtart.org/

    Is a good site to get scripts...

    Agreed ... this is the best way to do it. I use them all the time for the users here and it is really nice to just create a login and know that the user's network drives and printers will all be mapped without hassle.
  • sprkymrksprkymrk Member Posts: 4,884 ■■■□□□□□□□
    TeKniques wrote:
    Trailerisf wrote:
    create login scripts and map it... set the profile in AD to use a login.bat

    http://www.kixtart.org/

    Is a good site to get scripts...

    Agreed ... this is the best way to do it. I use them all the time for the users here and it is really nice to just create a login and know that the user's network drives and printers will all be mapped without hassle.
    Yeah, I forgot about login scripts because it simply is not a good way to do it where I work. I have users in about 35 different buildiings, and each building can have 3-4 printers in different areas. No way I am going to sort through what user sits near what printer and create a group or seperate login script for each. They tend to move occasionally and sometimes have more than 1 desk/work area. In my case, I just have the Help Desk tech set them up on nearby printers when we first deploy the computer to a user (or set up a new user on an existing computer). If they need one added at a later date it's simple enough to walk them through the process on the phone, or send out a tech again.
    All things are possible, only believe.
Sign In or Register to comment.