Quantcast
Channel: Print/Fax forum
Viewing all 871 articles
Browse latest View live

Setting up printers on XP in Windows Server 2003 domain

$
0
0

I know XP and server 2003 is not supported anymore but I have a school client that still have quite a few XP machines in their Media center and they have asked me to setup a printer on all the PC's. They are connected to a Windows server 2003 and I have limited experience with servers and the original setup was done by someone else years ago. I can install the printer on the PC's but with the XP ones, after restarting the computers, the printer is no longer there. 

It seems the workstations are setup to return to original state when restarting so users can't save anything on it. There are 2 printers, one connected to the server but the teacher wants the 2nd one to be connected to a workstation on the other side of the classroom which I have connected to a Windows 8 PC I have supplied and setup with lot less restrictions than the XP PC's, so that should work fine.

Please can someone advise me how to install it so that it is still installed after restarting the XP PC's

Thanks


Print Queues

$
0
0

Hi Everyone,

Facing issue on Print server. I have 13 Printers and all printers frequently holding the print queues.

Once deleted all all files from spool/printers folder and restarted services. All print queues cleared.

Thanks in Advance for support.

Thanks & Regards,

Ram Prakash Sharma

  

  

 



Ram Prakash Sharma

Windows 7 SP1 Pro PC cannot connect to printer shared on a Windows 2008 R2 server

$
0
0

I have some Windows 7 PCs that have this printer downloaded from our Server and occasionally can print to it.  Most of the time it locks the print spooler up and you are unable to restart it.  I checked the logs and found the following under print services.  I've tried multiple drivers and nothing seems to correct it.  Windows 10 PCs print fine.  I took the same driver on the server and loaded it locally and it works fine.  Doesn't make sense.  The driver loaded on the server is for 2008 R2 and is the latest one Konica Minolta has.  I've even tried older versions.  

Log Name:      Microsoft-Windows-PrintService/Admin

Source:        Microsoft-Windows-PrintService

Date:          5/3/2018 8:45:44 AM

Event ID:      601

Task Category: Client-side rendering

Level:         Error

Keywords:      Client Side Rendering (CSR),Classic Spooler Event

User:          domain\user

Computer:      DesktopPC.domain.local

Description:

The print spooler failed to download and import the printer driver from\\server into the driver store for driver KONICA MINOLTA C368SeriesPCL. Error code= 800f0242.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />

    <EventID>601</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>41</Task>

    <Opcode>12</Opcode>

    <Keywords>0x8000000000008800</Keywords>

    <TimeCreated SystemTime="2018-05-03T12:45:44.345081100Z" />

    <EventRecordID>809</EventRecordID>

    <Correlation />

    <Execution ProcessID="1548" ThreadID="3392" />

    <Channel>Microsoft-Windows-PrintService/Admin</Channel>

    <Computer>GRNUSH232A2HMV.PPI.local</Computer>

    <Security UserID="S-1-5-21-129632720-523521366-19539831-16733" />

  </System>

  <UserData>

    <CSRImportFailed xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">

      <DriverSource>\\server</DriverSource>

      <Driver>KONICA MINOLTA C368SeriesPCL</Driver>

      <Error>800f0242</Error>

    </CSRImportFailed>

  </UserData>

</Event>

Log Name:      Microsoft-Windows-PrintService/Admin

Source:        Microsoft-Windows-PrintService

Date:          5/3/2018 8:45:44 AM

Event ID:      600

Task Category: Client-side rendering

Level:         Error

Keywords:      Client Side Rendering (CSR),Classic Spooler Event

User:          SYSTEM

Computer:      Desktop.domain.local

Description:

The print spooler failed to import the printer driver that was downloaded from \\server\print$\x64\PCC\koaxtj__.inf_amd64_neutral_8d025ed74f178b9f.cab into the driver store for driver KONICA MINOLTA C368SeriesPCL. Error code= 800f0242. This can occur if there is a problem with the driver or the digital signature of the driver.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />

    <EventID>600</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>41</Task>

    <Opcode>12</Opcode>

    <Keywords>0x8000000000008800</Keywords>

    <TimeCreated SystemTime="2018-05-03T12:45:44.345081100Z" />

    <EventRecordID>808</EventRecordID>

    <Correlation />

    <Execution ProcessID="1548" ThreadID="3392" />

    <Channel>Microsoft-Windows-PrintService/Admin</Channel>

    <Computer>DesktopPC.doamin.local</Computer>

    <Security UserID="S-1-5-18" />

  </System>

  <UserData>

    <CSRImportFailed xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">

      <DriverSource>\\server\print$\x64\PCC\koaxtj__.inf_amd64_neutral_8d025ed74f178b9f.cab</DriverSource>

      <Driver>KONICA MINOLTA C368SeriesPCL</Driver>

      <Error>800f0242</Error>

    </CSRImportFailed>

  </UserData>

</Event>

Unable to print from AutoCad LT2019 to HP Designjet 110plus nr

$
0
0

I am using AutoCAD Lite 2019 and printing to a HP Designjet 110plus nr and unable to do so. when  trouble shoot printer I get error 0x0000007f.

Default Printers Keeps Changing

$
0
0

Good Afternoon,

We are experience some printer issue’s. Every time a user logs in the default printer changes. The user sets the default printer again but when the user logs off and on again the default printer has changed again. The printer where it is changing to isn’t the same printer every time.

Specs environment listed below: Windows Server 2012R2 DC/ConnectionBroker/RDS Server

The printers are installed on the DC an Shared + list in directory. There are no policy’s that manage the printers (in the past there were print policy’s). There is an login script that connects the printers to the user session. The User Profiles are stored in User Profile Disks.

The users using Thin Clients and Desktops (Windows 7 & 10) and connecting to the RDS Servers. In the Client Settings on the connectionbroker are the “Allow client printer redirection” and “Use the Remote Desktop Easy Print print driver first” options enabled.

I’ve already tried to manage the printer through GPO’s and registry such as HKEY_USERS\USERS_SID-HERE\Printers\Connections but all this doesn’t solve the problem. Even with a Print GPO sometimes the user doesn’t seeing any printer at all.

Personally I think when a user is logging on, the session wants to set the last know default printer as default printer, but on that time the printers aren’t yet connected to the session, therefore it sets the first available printer as default printer.

I don’t know if this is possible. But it sounds logical to me.

I’ve created a script that can be used as login script and has an delay of 10 seconds before it sets an printer as default printer. This is working but it doesn’t solve the original problem.

If anyone has an solution for the above problem I would like to hear that.

Sincerely, Niels

Unable to print to Send to Onenote 2016

$
0
0
Hi, I'm not able to print to the OneNote 2016 Send to OneNote 2016 printer.  I've done a quick and an online repair of office, I've deleted the printer and had office re-add it, I've restarted the print spooler, and modified the permissions on a registry key (details forgotten), so everyone had read permission.  I keep getting this error:  Win32 error code returned by the print processor: 2147500037. Unspecified errorin Event Viewer every time I try to print to it.  Print jobs to other devices work just fine.  I've tried from multiple applications, and searched for solutions online, but haven't found anything yet.  Please help!  

Changing drivers - What's the timing/procedure for clients getting the new driver?

$
0
0

We run a few 2012 R2 print servers and a few hundred printer shares. We've got everything finely tuned: GPOs to allow non-admins to install printers, GPOs to install printers, shared/isolated & packaged type 3 drivers when not using a type 4, and so on. Everything hums along as normally as one could expect from a Windows print environment.

The hang-up I have is the timing of clients getting updated printer drivers. (New printer assumes the identity of an old printer, existing printer needs different driver for certain functionality, etc.) I recall reading MS documentation saying that client's installed instances of printers are supposed to pick up on the change on the next print job, but that rarely -- if ever -- happens. Even removing a printer, rebooting, and letting group policy reinstall the printer on next login still uses the previous driver for the printer share. Eventually after just uninstalling & reinstalling & rebooting for some length of time, the client will have the printer installed with the updated driver. This is pretty much the story on Win7, Win8.1, and any version of Win10 from the reports I've gotten from my user support team.

Am I expecting the wrong thing to happen? Should I be deleting/recreating printer shares instead of only changing the driver on an existing one? Is there some client-side command or procedure to make it clear whatever is caching the old driver and force it to grab the one from the server anew?

Any guidance or anecdotes from the field or links to documentation on this would be a great help, because "reinstall it 'til it works" isn't cutting it.

Thanks in advance!

Redirected Printers

$
0
0
I have all my network printers on my domain controller (DC01) and then they are mapped to my 2 Terminal Servers (TS4 & TS5). However, some users are getting "redirected" printers so they have multiples of the same printer. Even as an administrator I am unable to remove the redirected printers. Any help? Thank you.

Group Policy Shared Printers

$
0
0
I have all my network printers setup on my Domain Controller. I want to share them on my 2 Terminal Servers with Group Policy. Do I have to add the printers to the Terminal Servers first or just add them to Group Policy and then Deploy the printers? Thank you.

Windows Server 2008 R2

$
0
0
I have old printers still showing up in control panel devises/ printers in Windows Server 2008 R2. I'd like to delete from Server. When i access remove printer, que comes back saying can't delete, access denied. After  I look at permissions for that printer, I'm listed as administrator and have rights to change since i have all permissions. Am I to look else where to accomplish this printer to be deleted

i cant DELETE a doc in the queue

$
0
0
i cant DELETE a doc in the queue

Win2016 RDS users randomly can not use shared printers

$
0
0

Some months ago we switched to Windows Server 2016 and since then we have a lot of problem with network printers.

We have 2 printer servers (old is w2k3, new is w2016). We want to switch to w2016, but not printer was moved to new one yet. But the problem bellow is not depend on the printer server.

Sometimes and some user(s) can not print to shared printers ever. (while the other users can) There is no error message and the printers still on the installed printers list. We can solve the problem by remove the printer from the user and install it again. When we uninstall printer it ask the administrator account, and remove the printer from the printer server too. We have to reinstall on printserver, share and reinstall it for all users. After this procedure everybody can print for a while.

There are application on the RDS server which does not always see printers (except the "Microsoft print to PDF on PORTPROMPT":)

Could anybody give us some advice to avoid the infinite printer un- and re-installation series?

domain migrations

$
0
0

hi again

I took a backup of SBS2003 and installed in on same Hardware.

then migrated the Active directory to new box with windows server 2012, then clean up and Migrated same Active Directory to new box (windows 2016) with same name as SBS2003 and everything seemed OK.

(this process took about 4 months)(other problem like printers and remote users etc.)

I took the new Server onsite and unplugged the old SBS2003 and connected the new 2016 domain controler

when client rebooted they complained about the trust relationship ?

DO active directory lose there trust after awhile or I need to be looking somewhere else? 

off course I could reestablish trust by rejoining but too many clients.

thanks

For you comments 

Fred   

The print spooler failed to regenerate the printer driver information for driver Microsoft enhanced Point and Print compatibility driver for environment Windows NT x86

$
0
0

I am running Windows Server 2012 R2 as a Print Server and very often I receive the error in SCOM:

The print spooler failed to regenerate the printer driver information for driver Microsoft enhanced Point and Print compatibility driver for environment Windows NT x86. Win32 system error code 2 (0x2). This can occur after an operating system upgrade or because of data loss on the hard drive.

How to fix the issue?


BR Michal Ziemba

PrinterBrm -R got error 0x80070bcb at Win7

$
0
0

At windows 7, I installed a printer named 888d, and install the driver of course.

I backup it with

PrintBrm -B -F D:\888d.printerExport

I didnot restart my computer, then I want to restore it with

PrintBrm -R -F D:\888d.printerExport -O FORCE

But the cmd told me

Operation mode: restore
Target server: local machine
Target file path: D:\888d.printerExport.
Queue publish mode: none
Overwrite mode: keep existing settings
Queue ACL mode: restore ACLs from backup

LISTING PRINT QUEUES
888D
LISTING PRINTER DRIVERS
Deli DL-888D, Windows x64, None


                                        
Restoring Printer Drivers...
************ 0% ************
                                        
Failed to restore printer driver Deli DL-888D, Windows x64, 3. Error 0x80070bcb
************ 50% ************
                                        
Restoring Printer Ports...
************ 50% ************
                                        
Restoring Print Processors...
************ 50% ************
                                        
Restoring Print Queues...
************ 50% ************
                                        
Skipped print queue 888D because a queue with the same name (or same share name) already exists
************ 100% ************
The following objects failed to install:


LISTING PRINTER DRIVERS
Deli DL-888D, Windows x64, None	Error: 0x80070bcb
The specified printer driver was not found on the system and needs to be downloaded.


Check the eventlog for detailed information about the error which occurred.


Successfully finished operation.

Here is eventlog

Log Name:      Application
Source:        Microsoft-Windows-PrintBRM
Date:          8/8/2018 3:58:27 PM
Event ID:      37
Task Category: (3)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PC-17892B
Description:
Printbrm.exe (the Printer Migration Wizard or the command-line tool) could not restore driver Deli DL-888D (Windows x64) from files.  Error reported: 0x80070bcb. The specified printer driver was not found on the system and needs to be downloaded.
. This can occur if the driver requires a file that Printbrm.exe did not back up or if the user does not have permission to install drivers on the destination computer.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" /><EventID Qualifiers="49154">37</EventID><Version>0</Version><Level>2</Level><Task>3</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2018-08-08T07:58:27.000000000Z" /><EventRecordID>2479</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>Application</Channel><Computer>PC-17892B</Computer><Security /></System><EventData><Data Name="param1">Deli DL-888D</Data><Data Name="param2">Windows x64</Data><Data Name="param3">0x80070bcb. The specified printer driver was not found on the system and needs to be downloaded.</Data></EventData></Event>

The 888d.printerExport is 888d.printerExport

The driver of the printer is driver_of_888d

Any more, I can finished restoring with the same methods in windows10.

Could you help me to solve the problem of printbrm?

Here is my systeminfo

Host Name:                 PC-17892B
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          rcd
Registered Organization:   
Product ID:                00426-OEM-8992662-00400
Original Install Date:     1/16/2017, 5:32:02 PM
System Boot Time:          8/8/2018, 3:25:58 PM
System Manufacturer:       RuiJie
System Model:              Standard PC (i440FX + PIIX, 1996)
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 78 Stepping 3 GenuineIntel ~2400 Mhz
BIOS Version:              RuiJie N/A, 4/1/2014
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             zh-cn;Chinese (China)
Input Locale:              zh-cn;Chinese (China)
Time Zone:                 (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Total Physical Memory:     7,299 MB
Available Physical Memory: 5,323 MB
Virtual Memory: Max Size:  14,596 MB
Virtual Memory: Available: 12,650 MB
Virtual Memory: In Use:    1,946 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\PC-17892B
Hotfix(s):                 203 Hotfix(s) Installed.
                           [01]: KB982861
                           [02]: 982861
                           [03]: KB2479943
                           [04]: KB2491683
                           [05]: KB2506014
                           [06]: KB2506212
                           [07]: KB2509553
                           [08]: KB2511455
                           [09]: KB2532531
                           [10]: KB2533623
                           [11]: KB2534111
                           [12]: KB2536275
                           [13]: KB2536276
                           [14]: KB2544893
                           [15]: KB2560656
                           [16]: KB2564958
                           [17]: KB2570947
                           [18]: KB2579686
                           [19]: KB2584146
                           [20]: KB2585542
                           [21]: KB2604115
                           [22]: KB2619339
                           [23]: KB2620704
                           [24]: KB2620712
                           [25]: KB2621440
                           [26]: KB2631813
                           [27]: KB2653956
                           [28]: KB2654428
                           [29]: KB2655992
                           [30]: KB2656356
                           [31]: KB2659262
                           [32]: KB2667402
                           [33]: KB2676562
                           [34]: KB2685811
                           [35]: KB2685939
                           [36]: KB2690533
                           [37]: KB2698365
                           [38]: KB2705219
                           [39]: KB2706045
                           [40]: KB2712808
                           [41]: KB2727528
                           [42]: KB2729452
                           [43]: KB2736422
                           [44]: KB2742599
                           [45]: KB2743555
                           [46]: KB2757638
                           [47]: KB2758857
                           [48]: KB2770660
                           [49]: KB2789645
                           [50]: KB2803821
                           [51]: KB2807986
                           [52]: KB2813430
                           [53]: KB2840149
                           [54]: KB2840631
                           [55]: KB2847927
                           [56]: KB2855844
                           [57]: KB2861698
                           [58]: KB2861855
                           [59]: KB2862152
                           [60]: KB2862335
                           [61]: KB2862966
                           [62]: KB2862973
                           [63]: KB2864058
                           [64]: KB2864202
                           [65]: KB2868038
                           [66]: KB2868626
                           [67]: KB2868725
                           [68]: KB2871997
                           [69]: KB2872339
                           [70]: KB2876331
                           [71]: KB2887069
                           [72]: KB2892074
                           [73]: KB2893294
                           [74]: KB2894844
                           [75]: KB2900986
                           [76]: KB2911501
                           [77]: KB2931356
                           [78]: KB2937610
                           [79]: KB2943357
                           [80]: KB2957189
                           [81]: KB2965788
                           [82]: KB2968294
                           [83]: KB2972100
                           [84]: KB2972211
                           [85]: KB2973112
                           [86]: KB2973201
                           [87]: KB2973351
                           [88]: KB2977292
                           [89]: KB2978120
                           [90]: KB2978668
                           [91]: KB2978742
                           [92]: KB2980245
                           [93]: KB2984972
                           [94]: KB2991963
                           [95]: KB2992611
                           [96]: KB2993651
                           [97]: KB3000483
                           [98]: KB3003743
                           [99]: KB3004361
                           [100]: KB3004375
                           [101]: KB3005607
                           [102]: KB3010788
                           [103]: KB3012176
                           [104]: KB3019978
                           [105]: KB3021674
                           [106]: KB3022777
                           [107]: KB3023215
                           [108]: KB3023607
                           [109]: KB3030377
                           [110]: KB3031432
                           [111]: KB3033889
                           [112]: KB3035126
                           [113]: KB3035131
                           [114]: KB3035132
                           [115]: KB3037574
                           [116]: KB3042553
                           [117]: KB3045171
                           [118]: KB3045685
                           [119]: KB3045999
                           [120]: KB3046017
                           [121]: KB3046269
                           [122]: KB3055642
                           [123]: KB3057154
                           [124]: KB3059317
                           [125]: KB3060716
                           [126]: KB3061518
                           [127]: KB3063858
                           [128]: KB3067903
                           [129]: KB3067904
                           [130]: KB3071756
                           [131]: KB3072305
                           [132]: KB3072630
                           [133]: KB3072633
                           [134]: KB3074543
                           [135]: KB3075220
                           [136]: KB3076895
                           [137]: KB3076949
                           [138]: KB3078071
                           [139]: KB3078601
                           [140]: KB3080446
                           [141]: KB3081320
                           [142]: KB3083992
                           [143]: KB3084135
                           [144]: KB3087039
                           [145]: KB3092601
                           [146]: KB3093513
                           [147]: KB3097966
                           [148]: KB3097989
                           [149]: KB3101722
                           [150]: KB3101746
                           [151]: KB3108371
                           [152]: KB3108381
                           [153]: KB3108664
                           [154]: KB3108670
                           [155]: KB3109103
                           [156]: KB3109560
                           [157]: KB3110329
                           [158]: KB3115858
                           [159]: KB3121461
                           [160]: KB3121918
                           [161]: KB3122648
                           [162]: KB3124280
                           [163]: KB3126587
                           [164]: KB3126593
                           [165]: KB3127220
                           [166]: KB3135983
                           [167]: KB3135988
                           [168]: KB3138612
                           [169]: KB3138910
                           [170]: KB3138962
                           [171]: KB3139398
                           [172]: KB3139914
                           [173]: KB3139940
                           [174]: KB3142024
                           [175]: KB3146963
                           [176]: KB3149090
                           [177]: KB3150220
                           [178]: KB3155178
                           [179]: KB3156016
                           [180]: KB3156017
                           [181]: KB3156019
                           [182]: KB3159398
                           [183]: KB3161561
                           [184]: KB3161949
                           [185]: KB3161958
                           [186]: KB3163245
                           [187]: KB3164033
                           [188]: KB3164035
                           [189]: KB3170455
                           [190]: KB3177186
                           [191]: KB3178034
                           [192]: KB3184122
                           [193]: KB3185911
                           [194]: KB3188730
                           [195]: KB3192391
                           [196]: KB3197867
                           [197]: KB3205394
                           [198]: KB3210131
                           [199]: KB3212642
                           [200]: KB4012212
                           [201]: KB4014565
                           [202]: KB4015546
                           [203]: KB976902
Network Card(s):           1 NIC(s) Installed.
                           [01]: RuiJie VirtIO Ethernet Adapter
                                 Connection Name: 本地连接
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.59.194
                                 IP address(es)
                                 [01]: 172.21.6.90
                                 [02]: fe80::5d52:3a0c:db87:1e57



Print Server - Driver Update Needed after adding new driver

$
0
0

Hello,

We have strange problem with printer driver for Canon printers. We've added a new printer driver to our print server, and assigned it to new Canon printer.

The problem is, that other (older) Canon printer now shows "Driver update needed" on user PC's, and when user hit "Update button" (we have GPO, that allows users to install/update printer drivers without admin permission), it "installs" the new driver, and it shows "Driver update needed" window again.

I've checked Event Viewer, and it shows, that some VALIDATINGDRVINFO operation failed with error code: 0xBCB.

As a "workaround" we can delete "faulty" printer from user PC, then intall it again from print server, but it's not a fix to our problem, because we want to be automatically.


Error when install printer with local admin account

$
0
0

Hi,

I want to install a network shared printer in a local admin account. I logged into a domain joined computer with local admin account. I open the printer server in Windows Explore by \\printerserver, I double clicked the shared printer icon and I prompted for user credential, then I entered my domain account credential, but I got access deny error. 

My question is how I can install a network shared printer for local computer account?

Please help!

Thanks in advance!


Grace

Printing from Server on a local printer

$
0
0
I have a windows server 2016, hosted in the cloud. How can I do work from my laptop using the "remote desktop connection" to the server, but I still want to print on the printer that is physically near my laptop not where the server is. How can I set this up?

Windows 2008 R2 Print Management - Add Print Server instead of mapping printers individually?

$
0
0

Hey folks, I have 600 printers that I must network map which are located across 6 print spoolers within our organization. These printers need to be mapped to this single server allow an application to push print jobs. Unfortunately I don't think Windows 2008 R2 was ever designed to have this many printers mapped via network simultaneously. Once it reaches about 350 - 500 printers I start to experience problems after I restart the spooler. Examples include, the spooler crashing or the logs showing that printers are being deleted with no explanation, driver errors... etc. Originally the design never had the print management service, however I'm looking for other options and now that I have it installed, i noticed that I can add other print servers.

We went ahead and tested to see if simply adding the server to the print management screen would work for us. I deleted all printers that I had mapped via network, restarted the machine, added the print servers and attempted a test. The results I got back shows that the printer was added via network, job was pushed and then the printer was automatically deleted. It worked!

My question is, is this the intended design? Is it sustainable? When we upgrade to 2k12 servers, is this something I can consider.

Alternatively we are looking at the ability to just go head and install the printers locally as non-shared printers by migrating the 600 printers from the other print servers... basically creating one massive private print server that is exclusive to the applications use.

Also note that when i'm referring to logs above, i'm referring to Event Viewer PrintService Operational logs.

Maximum Number of Printers on Windows Server 2012 R2 Standard

$
0
0

We are consolidating several application servers and consolidating into a single windows server 2012 R2 standard. We have 10 source servers each having 200+ printers installed on them.

We have been tasked to migrate all the printers from these 10 older servers (Windows server 2008 R2 and Windows Server 2012 R2) and install onto a single instance of Windows server 2012 R2.

We know how to migrate the printers, there is no problem and we have been doing that already. However, going forward we would like to understand MS recommendations as to how many printers can a server hold/manage. I can see, the server responding too slow when accessing Devices & Printers.

Any MS recommendations, limitations or documentation link may be helpful in understanding how we can optimize the server load and performance.

Thanks in advance.

Durga Pathak

Viewing all 871 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>