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

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


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   

Printui.dll and Windows Server 2016

$
0
0

I have a script that uses printui.dll to install printers as machine printers, using /ga. The script is a visual listing of the printer servers printers and the user chooses which one they want and hits install. For the last 5 years or so this has worked perfectly and the Windows Servers that have housed the print server roles have been Windows Server 2008 R2 and Windows Server 2012. They have always worked perfectly.

We are starting to migrate to Server 2016 for our enterprise and the prinui.dll is not working anymore.

This page is my reference for the command: https://docs.microsoft.com/en-us/windows-server/administration/windowscommands/rundll32-printui

Here is an example of what I am trying to do:

 RUNDLL32 PRINTUI.DLL,PrintUIEntry /ga /n"\\Print_Server.domain.domnet\PrinterQueue"

The command appears to result in a queue deployed, but it isn't visible to windows, only in:

rundll32 printui.dll,PrintUIEntry /ge

Any idea what I am doing wrong?


Portland Public Schools / Systems Administrator II





Cannot print PDF files, word / excel works.

$
0
0

Hi, 

Hardware /Software

- Konica Minolta c454e Network printer

- AdobeReader (latest Ver.)

- Adobe Acrobat (latest Ver.)

Windows 2012 R2 Terminal- and Print server

The Issue:

Some users cannot print .pdf files from AdobeReader or Internet Browser (Chrome, Firefox, Internet Explorer).

They have to reconnect (remove broken printer and then add it again) the network printer to make this work again. Unfortunately the problem reoccurs after some weeks.

Troubleshooting:

- Installed the general printer drivers instead of the specific one.

- Setup a new Printserver 

Everytime a user cannot print a PDF the printer config window looks like this:

Evertime a user can print a PDF the printer config window looks like this:

As you can see, when it's working the Option " Print on both sides" is available. I don't know if this helps troubleshooting this.

 

Cannot print PDF files, word / excel works.

$
0
0

Hi, 

Hardware /Software

- Konica Minolta c454e Network printer

- AdobeReader (latest Ver.)

- Adobe Acrobat (latest Ver.)

Windows 2012 R2 Terminal- and Print server

The Issue:

Some users cannot print .pdf files from AdobeReader or Internet Browser (Chrome, Firefox, Internet Explorer).

They have to reconnect (remove broken printer and then add it again) the network printer to make this work again. Unfortunately the problem reoccurs after some weeks.

Troubleshooting:

- Installed the general printer drivers instead of the specific one.

- Setup a new Printserver 

Everytime a user cannot print a PDF the printer config window looks like this:

Evertime a user can print a PDF the printer config window looks like this:

As you can see, when it's working the Option " Print on both sides" is available. I don't know if this helps troubleshooting this.

 




Print Server cleanup Tool

$
0
0

We have a Windows 2012 R2 test server which we use to test print drivers on server before deploying them to production print servers.

During one of the testing, an intern accidentally installed the HP UPD using the installer (instead of the inf add driver method we normally use.) What it does is instead of opening the properties of printers using UPD it opens a HP popup asking for IP Address. When you enter the IP it doesn't take it. There is no option to close it also. I have to close the print management to close it.

I removed and resinstalled the driver (using the inf method), still the pop-up comes.

I removed the driver, then removed it from driver store (unable to remove it from here) and reinstalled the driver. Still pop up comes.

I deleted the registry entries of all the drivers.

I found deleted the files and then tried to remove the driver (successful) and then remove from driver store (unsuccessful) and reinstalled it. Still the pop up comes.

I tried looking for uninstall for HP in Uninstall Programmes. Nothing there.

This is not happening with same driver on other Windows 2012 R2 server. It directly opens printer properties without any issues.

There used to be a print server cleanup tool offered by Microsoft but since it has been discontinued (not available for download anymore)

Is there anything else that I can try to remove the HP UPD?

Could we see all printers on console?

$
0
0

1. It is seemed that we can use

rundll32 printui.dll,PrintUIEntry /ge /c\\MyPcName

to display all printers of my computer on the console. But I don't know how to do. Could you help me?

2. I don't know what is the "/ge" mean. Whatever printers I have installed, such as local, and shared, and a printer from other computer's sharing, I can't see any priner in the window.



Printbrm -R get error 0x80070005

$
0
0

At machine A, there is only one printer named "Deli 888-D".I store the printers by

Printbrm -B -F D:\888d.printerExport -NOBIN -NOACL

At machine B, I install the driver of the printer name "Deli 888-D".

As the administrator, I want to restore the printer with

Printbrm -R -F XYZ\888d.printerExport

But it told me some error

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...
Restored printer driver Deli DL-888D, Windows x64, 3
Restoring Printer Ports...
Restoring Print Processors...
************ 50% ************
The following objects failed to install:


LISTING PRINT QUEUES
888D    Error: 0x80004005
Unspecified error


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


The following error occurred: 0x80070005.
Access is denied.

Check if you are an administrator or member of the administrators group.
Check if you executed the tool with elevated permission.
Check the eventlog for detailed information about the error which occurred.
Here is something from eventvwr
- <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">71</EventID> <Version>0</Version> <Level>2</Level> <Task>4</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-08-16T11:50:57.000000000Z" /> <EventRecordID>549</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>lida</Computer> <Security /> </System>
- <EventData><Data Name="param1">C:\Users\Test\AppData\Local\Temp\0DA25D74-7319-4F06-B8D8-5FFC645F3427\PRTPROCS\Windows x64\winprint.dll</Data> <Data Name="param2">C:\Windows\system32\spool\PRTPROCS\x64\winprint.dll</Data> <Data Name="param3">0x5. Access is denied.</Data> </EventData></Event>

Indeed, there is no dir named

C:\Users\ADMINI~1\AppData\Local\Temp\0DA25D74...

perhaps it is the reason, I guested.

I can restore it at machine A. The machine A and B are the same os

6.1.7601

perhaps machine B is lack of some windows patch, I guested.

Could you teach me how to restore printer at machine B? Thank you very much!



Create a report queue usage

$
0
0

Dear all,

I need your kindly help in order to create a report that contains the amount of print jobs per months per queue on a server that host 600 queues, for the moment I manage to setup printing logs on the event logs in order to get all jobs.

at this point this is what I have construct:

$Results = Get-WinEvent -FilterHashTable @{LogName="Microsoft-Windows-PrintService/Operational"; ID=307;} -ComputerName $Computer


ForEach($Result in $Results){
  $ProperyData = [xml]$Result.ToXml()
  $PrinterName = $ProperyData.Event.UserData.DocumentPrinted.Param5
    
     $hItemDetails = New-Object -TypeName psobject -Property @{
      MachineName = $ProperyData.Event.UserData.DocumentPrinted.Param4
      PrinterName = $PrinterName
      TimeCreated = $Result.TimeCreated
    }

    $aPrinterList += $hItemDetails
  }

  $file="C:\temp\PrintAudit.csv"

#Output results to CSV file
$aPrinterList | Export-Csv  $file

$filc=gc $file
$filc.count

FOr the moment I anly got to know how many jobs for the hold server, now I need to get the amount per queue.

Thanks in advance for your help

Win2012R2 Print Server Won't Print Jobs After Network Migration

$
0
0

Greetings all,

We're doing a network migration at my small office and now have a problem with our file & print server. Whenever I send a job (such as test page) to our Win2012R2 print server, the job never actually prints at the print device. The print queue on the print server shows the job is "Printing", and then "Restarting", and continues to loop indefinitely.  I am pretty sure the problem is with the print server, because I print directly to the device (in this case a Xerox C60) at the new IP address. Drivers are current for our Windows 10 workstations. We are using the "Type 4 User Mode" drivers on the print server. Troubleshooting steps taken so far are:

0. Verified the print server can ping / reach the print device.

1. Created a new port at the new IP address. Mapped the printer to the new port. Same problem.

2. Deleted the share, device, and port. Recreated the printer and port. Same problem, and identified an additional one: when I attempt to share the printer, I get an error msg which says, "Sharing is not supported for this type of printer".  Printer does not appear in the list of shared folders or devices when I run a net view\\servername.

Everything worked perfectly before I changed the IP address of the printer.

Any suggestions?

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.

Network Printers

$
0
0
So we have 7 networked printers in our office. Currently, I have them all setup on the Domain Controller as shared printers. Then my users login to 2 different Terminal Servers where the printers are shared from my Domain Controller. Is this an okay practice to have the printers on the DC? Thank you for any opinions or advice.

SPOOLER Service doesn't restart on W2K8_R2_64

Allowing certain trusted users to manage print queues

$
0
0

One of our customers, an elementary school, would like to allow certain (trusted) instructors to manage the print queues of Windows Server-managed laser printers.  I have two questions about two different aspects of this:

1)  Rights:  Is making them members of the Print Operators group a sane choice, or is there a more "tailored" way to do this that's more appropriate?

2)  Managing the queues:  what tool(s) do I give them to actually allow them to manage the queues, without letting them on the server?  Should I install the Print Management snap-in on each instructor's PC?  Or just install the printers that are going to be managed on each instructor's PC, and have them use the same queue management utility that ships with Windows that they'd use to manage a locally-hosted printer?


cannot see forms from print server

$
0
0

I have just changed photocopiers from one manufacturer to another and deployed by gpo from print server but when i look at forms from client pc it is looking at local forms and not forms from the print server. How do i make client machines view forms from print server. We have a lot of custom forms on the print server and can view them from print management on the server but cannot find a way to point clients to view from server instead of locally.

server 2012r2 
clients windows 10
full domain

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

enable printer Service operational

$
0
0

can I enable Microsoft-Windows-PrintService/Operational  logging enabled by GPO for domain controller?


Jimmy Wang

Print spooler won't stay running after in-place upgrade from 2008R2 to 2012 R2.

$
0
0
Last weekend, I attempted to do an in-place upgrade of a 2008 R2 Print server to 2012 R2. I ended up having to revert to the snapshot (VMWare) because the print spooler would not stay running. I have done other print servers before, and never had this issue, but this is one of the older print servers in the company. I will eventually need to upgrade this server, so are there any tools available to scan the 2008 server and report any incompatible with 2012 R2 drivers? This print server has about 150 printers in the list, and the ESX host at the location does not have enough resources for me to build a new server.

Printer Properties on HP 5660 Envy locked and will not activate

$
0
0

I had my Printer driver checked by HP yesterday and Printer checks out. When I try to activate Printer Properties it will not open up so that I can change ink from normal to best or change type of paper in the printer options. I cannot open printer properties across programs. I think this occurred with one of the Windows 10 updates as I know this feature was working several months back. What do I do to correct this?

Thank you

Viewing all 1936 articles
Browse latest View live


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