Solved

Windows 8.1 old printers showing following sysprep

Posted on 2014-02-24
3
1,376 Views
Last Modified: 2014-03-03
We currently have a number of Windows Server 2012 R2 RDSH servers and also Windows 8.1 desktops that have been deployed using sysprep images.  The original server/ pc image is fine but any that have been deployed using an image have an issue with printers.

When a user logs on and looks in printers it seems to show every printer that was mapped for other users when that PC/ server was originally syspreped.  If you go to a select a printer within an application none show.  

This is confusing for our users as 6 instances of a network printer show in some cases.  Its almost like the sysprep process has converted any network mapped printer to a local and this shows in anyones account who logs on.  See the attached screenshot of the printers in system, if I delete these they just re-appear after about 30 seconds.

Please could someone advise if these is a way of removing these rogue printer mappings.  I have tried deleting in system and also removing the print drivers with no success.
sys.jpg
sys-2.jpg
0
Comment
Question by:ernie10
  • 2
3 Comments
 
LVL 39

Assisted Solution

by:Adam Brown
Adam Brown earned 250 total points
ID: 39886371
Part of the sysprep process is the removal of GUID mappings that may be unique to the system. Printers are mapped using GUIDs to define which entry points to which printer, and this information is stripped out by Sysprep. Printers shouldn't be installed prior to sysprep, but should instead be deployed through group policy or installed manually from a server share.
0
 

Accepted Solution

by:
ernie10 earned 0 total points
ID: 39888954
The printers were never intentionally installed, these had simply been picked up by users logging onto the PC who already had network mapped printers.  

The MS solution below to delete the old print mappings from the registry resolved the issue.

http://support.microsoft.com/kb/2023766

On the affected Windows 7 and Windows Vista client machines, go to the following registry locations

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers\<print_server>\Monitors\Client Side Port

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers\<servername>\Printers

Delete the stale Printer {GUID} from both location and restart the Print Spooler service.
0
 

Author Closing Comment

by:ernie10
ID: 39900020
Expert comment helped but my comment is the actual process to resolve the issue and delete the old printer GUIDs
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
DFSR ConflitandDeleted folder 14 32
Performance monitors 6 26
Sony EVI-D70 and Skype 2 41
Windows updates manual or  automatic 2 13
The article will show you how you can maintain a simple logfile of all Startup and Shutdown events on Windows servers and desktops with PowerShell. The script can be easily adapted into doing more like gracefully silencing/updating your monitoring s…
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question