Point Client Computers to a New Print Server

Logon script that changes the printer connections on workstations.

 
 
 
 
 
4.8 Star
(14)
Add to favorites
Printing
8/10/2009
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Not working for me either
    1 Posts | Last post January 21, 2016
    • It does nothing. I added some "echoes" but nothing. Is there an easy way I can debug it so I can find out where is it going?
  • Multiple Print Servers
    1 Posts | Last post October 21, 2015
    • I wanted to find out how this script can be modified to allow changes of multiple print servers. We have multiple print Servers.
      
                       Old Server 	New Server
      		 "KBFILE01"  = "\\vkbprt01\" 
      		 "HHPRINT01" = "\\vhhprt01\" 
      		 "HHPRINT02" = "\\vhhprt02\" 
      		 "LBPRINT01" = "\\vlbprt01\" 
      		 "LBPRINT02" = "\\vlbprt02\" 
      		 "BTPRINT01" = "\\vbtprt01\"
      		 "BTPRINT02" = "\\vbtprt02\"
  • Does this still work?
    1 Posts | Last post January 22, 2015
    • I tried this on windows 7 and windows 8 and it doesn't do anything. My printers are named the same. I have put in server A and server B. The share name is the same but no luck....How are you to migrate print servers these days without being able to redirect your clients? Any ideas.....
  • No result returned, no changes
    5 Posts | Last post October 20, 2014
    • I have copied this script out to a .vbs file, changing the names of \\old and \\new to the correct server name holding the new printers.  I can manually get to either oldprintserver and newprintserver and install any printer, and all installed printers are matched on both oldprintserver and on newprintserver.
      My question then is why do I receive absolutely no results when I run this script in a saved .vbs file?  No error, no changes, no printers removed or added, and while watching taskmgr when opening the file i see no cscript.exe or wscript.exe even kick off as a running process.
      Can anyone explain what I am missing here?
      TIA,
      jasma12
    • Hi,
      I dont know if you were able to fix. I had to try this script in my environment and i was able to just run the script fine.
      
      Firstly,  I tested the VBS script itself after updating the \\old and \\new variables with correct server names and running the script using cscript in command prompt(Open Command prompt, browse to the folder where u have saved the script, enter the command "cscript scriptname.vbs", thats it) then i could see the updated printers.
      
      John
    • Hi,
      I dont know if you were able to fix. I had to try this script in my environment and i was able to just run the script fine.
      
      Firstly,  I tested the VBS script itself after updating the \\old and \\new variables with correct server names and running the script using cscript in command prompt(Open Command prompt, browse to the folder where u have saved the script, enter the command "cscript scriptname.vbs", thats it) then i could see the updated printers.
      
      John
    • Hello,
      
      i have just used the script to test results on client printer connections, the scrip[t does work and moves the printer to a second printer server but it does not make any changes to the printers that are installed as Local Ports directed to the print server, just wondering if anyone know of a way round this as i would like printers installed as Local Ports to also be redirected to the new print server name.
      
      thanks in advance.
    • I also had trouble with this script. When I first ran it, it did nothing, then I noticed looking at some background tasks that there was a hidden prompt asking to install the printer driver. Once the drive is installed, the script works fine. 
      
      Is there anyway to tell the script to not prompt for driver install?