Lately we have been offering our applications as remote published applications using Windows Server 2012 R2.
Generally our apps run as fast or faster than they do on desktops.
One exception we notice is with composite datawindows when the remote user has printer redirection from the server to a client attached printer.
We notice that some reports run 10-20x faster when we replace the default printer with a generic server based printer definition - rather than the users local printer (which is attached by default).
Is there a way to modify reports so that the powerbuilder runtime doesn't try to do constant communications with the printer?