Hello:
In GP 2013 R2, we're testing the use of GP's Distributed Process Server (DPS).
Specifically, we tested the printing of a payables check to the Microsoft Document Image Writer, which "prints" to a .xps file.
On this RDS server that I was on, during this test, I saved this .xps file to its Desktop. The rest of the check processing went fine.
Later, I logged on to the RDS server that houses the DPS. Upon doing so, the server essentially prompted me to save the .xps file. Again, I had already done this on the other RDS box, upon printing the check.
Why was the DPS prompting me to do something that I had already done? True, the Microsoft Document Image Writer is the default printer on the RDS server where the DPS lives. But, I had already printed the check and posted it successfully, on another box.
Before this test, we had already had a user in the A/P department successfully test the printing of a check to a printer. Regardless, I want to ensure that there will be no issues with using the DPS. I don't want for the end users to generate reports to files on the network, with the DPS box prompting for the location of a file, whenever we log on to its box.
Oh, I just noticed that the GP User ID that we were testing with still had "Local" set in User Preferences for Remote Processing. So, as usual, the DPS did handle printing to "file". My guess is that if "Local" is set, the user at the same time is granted the opportunity to print to "file". Perhaps, since the user does not "control" what happens on the DPS, that's why the DPS box was "at the ready" in terms of printing to "file".
Thank you!
John
