PDF printing slow? - Here's the FIX!!

When the print is given to the network printer in the office it is printing very slow. It lasts a long time before the print job has been sent to the printer, after sending the print job to the printer it lasts a very long time before the printer prints. It prints page 1 and than I have to wait 2 minutes before the second page prints

And to fix the issue carry out the steps mentioned below 

If Adobe Acrobat Reader prints slowly try the following:

1.             Open a PDF file

2.             From the menu, select File > Print

3.             From the dialog displayed, click on the Advanced button at the bottom

4.             On the Advanced Print Setup dialog, make sure that “Let printer determine colors” is CHECKED.

5.             Click OK and OK to print the document.

This worked for me and believe will help you

Or try the below option

On the PC version, when you select print there will be an advanced button

After selecting the advanced button there will be a “print as image” selection box that must be checked to allow for quicker printing.

On a Mac, the procedure is similar, go to print, and on the bottom left will be an advanced button.

Click the button then you will be presented with the next window that contains the print as image option.

Hopefully this helped in alleviating annoying print problems with PDF’s. Please leave a comment if this helped solve a problem for you, or if you have anything else to add

Fix - No Remote Desktop Licence Server available on RD Session Host server

A fully functional and activated Windows 2008/2008 R2/2012 Remote Desktop Session Host server displayed the following message



This was a simple setup on one server with the: connection broker, Session Host and Licensing server with RDS/TS CAL’s installed.

Even though the licensing seems to be configured correctly, in server manager:


Licensing diagnostics:


everywhere you look, everything seems to be OK. But the license manager shows something odd where No licenses are being used? 
This server was used since late 2012 Some interesting things could also be found in the event logs, the following events appear


EventID: 1130
Source: TerminalServices-RemoteConnectionManager

The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.


EventID: 1128
Source: TerminalServices-RemoteConnectionManager

The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.


Solution 

Delete the REG_BINARY in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod"

Only leaving the default.


After a reboot the server should be working fine and get the licenses issued now and being getting used


Although everything seemed to be ok and configured correctly with valid licenses, it seems that the setup was still in a 120 day grace period, even though it was correctly configured.

Note: you must take ownership and give admin users full control to be able to delete this key.

Image Source - Internet

Reset Terminal license on Windows Server OS

While Windows installed with Terminal Server role it does work without License for 120 Days on trail license, where within 120 days if the License server is not Connected the server will stop accepting connection with below error and event ID



EventID: 1128
Source: TerminalServices-RemoteConnectionManager

The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.



The official solution is to Activate the RDS/TS CAL License server and point the Server to License server with User/Device License and will be resolve the problem

But if you want to reset the timer and again avail 120 days grace time  here is the solution

The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.


Note: you must take ownership and give admin users full control to be able to delete this key.

After a reboot the server should be working again for another 120 Days


Source - Internet