We are experiencing the same thing as user titafthestar. In our RDS farm, we only have two Windows Server 2012r2 (french canadian) with FoxitReader 7. The One Kiera Cass Pdf Epub Books. 2.0.722 (english version) installed. RDS users can print in every other applications like MS Office, Google Chrome and other software but not in FoxitReader. When they try to print a PDF file, the only printer available is the local printer 'PDF Creator'.

Ap Biology Seventh Edition Campbell Reece Notes From The Underground here. The only workaround I found to get the user's printer's back it was to delete the user profile VHD. Somethings makes FoxitReader loosing users printer's. Do you have an ETA regarding a fix for incident ID#65341?

Pc Ace Pro32 Installation Password For Gmod. I've seen this problem posted other places with no real resolution presented. - Here it is - Ever since installing office 2010 I have several end users / customers that are unable to successfully keep print settings changed in Office 2010. The settings in office 2010 themselves work fine, but if you try to change the printer properties they get reset as soon as you change them. An example is network MFPs that are set to B/W by default.

Why is TPrinter (XE7) suddenly having problems today? My own test was done using a PDF printer driver. I've got this week's updates installed on Windows 7 64.

The customer changes to color on the printer properties, but word and excel seem to ignore those settings. Acutally worse than ignore they reset them to the default properties for the printer. If you click on the properites, change them, click ok - then before printing I click on the properties again and they have already been reset. This is a big issue for several customers - they need to access the properties to set to color, change other settings, or use shortcut items for specific types of document printing. Also, the problem didn't exist until they installed office 2010. They can print successfully from any other application with the ability to change any settings needed.

I appreciate the suggestions so far. First it is always good to check the driver, but this is the latest driver and furthermore it is a network printer. I have the problem with several machines on the network, but there are a few that don't seem to have the issue. I have XP and Windows 7 machines - I haven't noticed the issue on Windows 7, and I even have at least 1 XP machine that works fine. But the problem exists on several XP machines. I have also seen the problem at another site - completely different machines and printer.

At the main site the printer as I said is an HP CM8050 Large Network MFP. The driver is on the server. The driver was installed from the server on each machine and then was changed to a local port to point to the server queue. The reason for this is allocation / account codes that are used with the printer. Some of the machines were upgraded to office 2010 from 2003, some from 2007 to 2010. Like I said the problem didn't appear until office 2010 was installed. It obviously doesn't happen in every scenario but enough times for it to be an issue of concern.