[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2569
  • Last Modified:

The Printer Name is invalid (error 80070709)

I just Implemented a new Terminal Server into my environment on Friday and now 5 out of 30 users are getting this scripting error message. If I have the users log back onto the old terminal server this error message is not present. I have removed the printer reference on the last line listed below of the printer script.vbs but I still continue to get this error message. I have also discovered that this printer is installed to my terminal server although it does not exist anymore and I didnt install the drive for it. I checked the 5 USERS in question to see if this was a profile issue but there profiles conform to out SOP. Can someone shed some light on how to proceed?

Error Message:

Script:         \\ist\SysVol\IST\scripts\Printers.vbs
Line:      6
Char:      1
Error:      The printer name is incalid.
Code      80070709
Source:      (null)

Printer Script:

'
' Printers.vbs - Windows Logon Script.
Set objNetwork = CreateObject("WScript.Network")
objNetwork.AddWindowsPrinterConnection "\\appsrv\BizHub 500 PS"
objNetwork.AddWindowsPrinterConnection "\\appsrv\BizHub 350 PS"
objNetwork.AddWindowsPrinterConnection "\\appsrv\BizHub 350 PCL"
objNetwork.AddWindowsPrinterConnection "\\appsrv\7085 PS"

objNetwork.AddWindowsPrinterConnection "\\appsrv\KM 161"      (this printer does not exist anymore - KONICA MINOLTA 161f PCL6)
0
jjrules68
Asked:
jjrules68
1 Solution
 
nightmare2Commented:
In Terminal Services Configuration, RDP-Tcp Properties,
there is a tab names 'Client Settings' in which ou can check 'Connect client printers at logon'

This will connect any printer existing in the user profile.
Uncheck this checkbox or delete the obsolete printer from your 5 users' profiles.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Tackle projects and never again get stuck behind a technical roadblock.
Join Now