Microsoft Print To Pdf Windows Server 2016
Reyes Grindberg
I developed a C#, web forms application that generates a PDF document server-side and sends it to the client. I generate the PDF using Microsoft Print To PDF (MPTP), PrintDocument, and PrintPageEventArgs.Graphics.DrawString. This works great on my local machine.
Enter server: When I uploaded my application and tried running it on my server, I get an error saying there's no printer installed. I check in Printers and devices and behold, MPTP isn't listed on the server (one fix for my problem is setting MPTP to default printer).
I tried generating a PDF using CutePDF Writer and Spire.PDF (I did generate the PDF, but local characters aren't working [č,š,ž] and I have to use PdfDocument, PdfSection, PdfTextWidget). I don't like generating with Spire.PDF because I must implement the correct header and signature for multipaged documents (which is a pain in the ass and I would prefer using the already written and tested code that uses PrintDocument and MPTP).
The problem is I was googling "Windows 10 print to pdf". When I tried searching Server 2012 I found out that Print to PDF doesn't exist on Server 2012, which is why I couldn't find it.
We have a Windows Server 2019 instance that we use as a Remote Desktop server. Until today, people could print to PDF. Suddenly today the Print button Preferences button, and options are greyed out and cannot be clicked. Someone online suggested removing and reinstalling the Microsoft Print to PDF printer. I was able to remove it using Device Manager, but when I try to reinstall it (manually adding a printer, selecting PORTPROMPT: (Local Port) as the port, and the Microsoft Print to PDF driver), I get an error: "Unable to install printer. The handle is invalid." I uninstalled some recently installed updates (a newer version of KB4598230 and then KB4598230), but that didn't help. We also have OneNote installed on the computer and printing to that doesn't work either (same greyed out Print button). Regular physical printers do work. I can't find anything helpful online. SFC /ScanNow didn't find any issues.
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sorry that didn't help.
Here's a workaround suggested by one user From this thread:
"I found a place to delete the driver manually through help I was getting with a printer issue (I ran "printui.exe /s" then found the driver in the drivers list and removed it). When I got back to adding the "printer" manually, clicking the "Windows Update" button under the list brought it up this time. "
Thanks for the thought, but I just tried and it didn't help. First I told windows to delete the driver but safe the files (for the XPS printer), then I told windows to delete everything. When I run Windows Update on this Server the XPS and PDF drivers don't show up. I still see the XPS driver in the installed drivers, and when I select it, I get the same error messages. When I try to re-install the PDF printer, I don't see the drivers installed locally (Makes sense becuase I told windows to fully delete them), and Windows Update doesn't find them. Now I don't have drivers I can even try to re-install.
NOTE: our configuration is a little different. We are running windows server 2012 R2 (Now with all the latest updates) and Windows 10 1909 or windows 10 20h2 with all the latest updates.
We had removed the updates from the server in November to regain functionality. About 2 weeks ago an update installed to our windows 10 workstations that broke this again. After testing, I found that Remote pdf printing now works if both the servers and workstations are updated.
In June 2021, security researcher Zhiniang Peng tweeted a POC (proof of concept) exploit. It contained an unpatched zero-day vulnerability in all supported and Extended Security Update versions of Windows OS.
Microsoft fixed the exploit, as a result, they were constantly changing the defaults for Windows Point and Print. The complication with Point and Print was, as a connection to a printer shared from a server with Type 3 drivers, the Print Driver (software) gets downloaded from the server onto the client machine.
The smartest thing to do is read the Microsoft Advisory in full. Assess the risk PrintNightmare poses to your systems. Then understand the impact and scope of all the mitigation options before you take action.
Print Deploy can install a client, without admin access. The Mobility Print printer can be delivered to the client machines. With a few extra steps, Print Deploy can also deliver the vendor driver onto the client machine, for those end-users who need higher functionality options. You can also deliver that printer to specific groups, or your whole organization.
Print Management provides up-to-the-minute details about the status of printers and print servers on the network. You can use Print Management to install printer connections to a group of client computers simultaneously. Print Management can help you find printers that have an error condition by using filters. It can also send e-mail notifications or run scripts when a printer or print server needs attention. On printer models that provide a printer Web page, Print Management has access to more data, such as toner and paper levels, which you can manage from remote locations, if needed.
Investigate the output on a hung service: How to use the Userdump.exe tool to create a dump file. Because the Citrix Print Manager service depends on the Microsoft Print Spooler service, Citrix may ask for both services to be analyzed.
In some cases, the native driver might be listed with the vendor ID, but in this case the OEM URL in the registry key should point to the Microsoft support Web page rather than to the vendor support Web page.
Missing provider information generally points to an incorrect driver installation (possibly an updated driver). Some vendors may intentionally leave this field blank. If Citrix print driver replication is used, the blank field is ported to all servers.
In general, all of the Microsoft-supplied printer drivers are tested with Terminal Services and guaranteed to work with Citrix. However, before using a third-party printer driver, ensure it has been certified for Terminal Services. There is a Windows Hardware Quality Labs (WHQL) program for getting third-party printer drivers certified on Terminal Services. Citrix does not certify printer drivers. Consult your printer driver vendor to ensure the driver you plan to use has been certified for a Terminal Services environment.
I have been trying to configure the load balancing with LTM for windows 2012 print servers. The file explorer opens but still not all the printers are listed, and the listed printers are not connecting either. Please help if any procedure to follow for load balancing the print servers.
After installing KB5005623 on our Windows print server it seems to have broke printing from macOS to our SMB queues. Windows machines seemed unaffected as were macOS clients printing via LPR. We have heard that uninstalling it will restore printing from Macs. But we do have print servers at 50 sites and each would require an uninstall and reboot. If the Windows machines are still printing I'm wondering if there is something that can be done on the Mac side that will allow them to print as well.
In 12.3 if you destroy your kerberos ticket, and send your credentials across using domain\username, it will work. We're still struggling in our environment as well. Prior to that folks could enter just their username and the translation would happen.
We still have it set in our environment. We're also deploying a krb5.conf file as well, I recall this was to address a Kerberos issue we had with JC at the time. Not sure if it's still needed, we've not stopped the deployment since setting it up in 2022, and it's not hurting anything. It was needed then. To answer your question no, we still have it set to "0".
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
Because PrinterLogic is able to eliminate print servers completely, it also eliminates all of the common Windows Server 2012 R2 printing problems while shrinking your infrastructure to a single-server solution that is able to deliver more functionality, higher availability and greater ease of use than Server 2012 R2 or any of its predecessors. PrinterLogic takes print management to a new level, so you and your support staff can stop worrying about how to configure a printer in Windows Server 2012 R2 and focus on other important tasks.
Organizations need to audit their print server to identify what data is being printed, the volume of data being printed, and who is printing sensitive data. Such audits also help organizations understand their printing costs. It can help you optimize your printer usage as you get to know what printers are being used the most. A printer audit report can help you prevent data exfiltration, and insider attacks. For example, you can immediately get to know if your most sensitive data is being printed by an authorized or unauthorized user.
d3342ee215