Hello,
I will try to sum up\simplify as best I can. Does Windows 2008 terminal services allow Printer Property settings set at the printer\OS level to be propagated to all applications and users? If so, how do I force the printer property settings (like page size) I make on the printer in the Printers folder at the OS level to that same printer's properties for any application?
Scenario: I have a document that when printed to the desired forms printer prints on two pages instead of one no matter what I do. I am assuming this is because the printer properties of the application I am printing from assumes "letter" sized paper and not the custom form size I specified in the printer's properties at the OS level.
Testing: I create the custom form size on the 2008 terminal server. I install the printer (prints test pages fine). In the printer's properties at the OS level I define the custom form size (under General tab, under Advance tab, and under Device Settings tab). If I open the document in Notepad, Adobe Reader, or another app and check the printer properties there, the printer's property page size is set back to "letter". It then prints on two pages. If in the app I set the printer's propery page size to my custom form it prints correctly. Why is the application's printer properties (specifically the paper size) varying from the OS's printer properties?
Does Windows 2008 terminal services handle these printer settings differently because I never noticed this issue in Windows 2003, or 2000...or NT for that matter (XP, 7, Vista seem to play by different rules). Is there a registry setting or policy where I can hardcode the printer's paper size for all users and all applications?
Specifics: Windows 2008 Standard 32bit and 64bit, Star TSP800 printer, tested form as a RPT, PDF, and TXT file in SaberLogic RPT Viewer, Adobe Reader, and Notepad.
Thank you very much for your input and professionalism.
You need to set the default settings in "Printing Defaults" not "Printing Preferences". Right-click the queue, select Printer properties, navigate to the Advanced tab, and press "Printing Defaults...". The Printing Defaults will automatically propagate to the user as the default preferences.
If these are network printers hosted on a print server, then set the printing defaults on the print server. All mapped queues will follow the same rules mentioned above.
James Szivos
Unfortunately I have already set the paper size there and it does not propogate. I tested this on two different Windows 2008 terminal servers on two different domains. The printer properties seem to be application specific and for whatever reasons is not picking up the Printing Defaults (I set the page size under the General tab - Printing Preferences button - Advanced button, the Advanced tab - Printing Defaults button - Advanced button, and the Device Settings tab - Friction field). This is why I was wondering if this behavior is different in Windows 2008 terminal services than previous Windows TSs. For what it is worth I verified my login is an admin on the server and has printer manager rights. I also added the Printer Role.
Have you\can you verified this behavior on a Windows 2008 terminal server in your environment? To do so, you can install a dummy printer on the 2008 server, set the printer's page size to something unique like "Envelope C5" (the page size under the General tab - Printing Preferences button - Advanced button, the Advanced tab - Printing Defaults button - Advanced button, and the Device Settings tab - Friction field), and then open up notepad. In Notepad if you click File - Print, then choose the printer you just created and click the Preferences button - Advanced button, is the default page size the unique setting you made at the OS level? (for reference, I am installing the printer as a local printer to existing LPT1 port using HP LaserJet III printer driver. I don't set it as my default printer and then I pause it for good measure).
Thank you again for your time
CLARIFICATION - The PAGE SIZE seems to be application specific. Other settings such as Paper Source will propogate (from the General tab I believe).
Paper size is an application-defined setting. If I specify legal paper in MS Word then it's going to use the tray with legal paper. Sure, you can specify something different for the paper size, but the application paper size ALWAYS overrides the queue's configuration. This is the behavior you want otherwise you would be printing legal sized documents to "Envelope C5" paper size.
From what I've experienced in printing the conflict resolution follows this order:
I am sure if you tested Black/White color configuration the same way you would get the results I suggested in my first response.
Thank you for your input. The challenge is that the application paper size is defaulting to "Letter" when I need it to default to "104mm x receipt". I need a way to force application paper size to default to the desired paper size because users will not have access to the application's printer properties settings to change it (nor would I want them to).
This was never an issue with Windows 2003 for whatever reasons. I have tried to find policies to force paper size without success. I even tried to remove all other paper sizes but the one I wanted for this particular printer without success. I just tried to print to a CutePDF printer that was properly configured and it still printed out incorrectly sized. So this may be an issue with Crystal Reports, or the form size, but I was hoping for a way to fix it at the app level.
Open to suggestions. But regardless, thanks again.
I haven't used much Crystal Reports, but I'm fairly certain that the paper size is defined as the report is compiled. This MSDN article references some of the relevant settings: http://social.msdn.microsoft.com/forums/en-US/vscrystalreports/thread/a256a9ce-40ba-41d8-8699-cd0427b7642b
It is, but on Windows 2003 we didn't have to specify the paper size in Crystal and the printer properties were inherited at the OS level. I am going to read through the article you sent and look closer at Crystal for issues...
Thank you for the information.
Update: Just confirmed this is an issue related to the version of Crystal Reports' controls embedded in our application. We have been able to work around it by "over-specifying" the necessary settings in the report. There is a supposed fix from Crystal that we will be looking into.
Thanks jszivos for your input and help.