Since the application does screen prints, you might want to double check when and if the default printer is being set. I ran into a historic issue with historic TS profiles and migrating from PS3 to PS4 in regards to an application handling default printers. It turned out to be a combination of two issues. 1) how PS4 policies handled setting the default printer at first (this has been hotfixed) 2) how old default printer data in the TS profile was being read by the app, but there was not a matching printer name that was being presented. I ended up writing a script to clean the user's registry settings for the default printer in the profile. This had to do with PS4 handling the default printer differently. It seemed to work fine for autocreation, but not for our network printers presented through policies. On 12/27/06, Christine Allen <Christine.Allen@xxxxxxxxx> wrote:
SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com ************************************************ For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link:I have just built a new ps4 farm. Because of an application we host, Facets, I need to use the Universal print driver to map to printers because this application only supports screen prints. With our XPa fr3 farm, it works fine, however it will not work with the PS4 farm. The application cannot recognize the default printer. Any idea's why? I thought printing was supposed to be improved?
//www.freelists.org/list/thin ************************************************