Document conversion

%3CLINGO-SUB%20id%3D%22lingo-sub-1924237%22%20slang%3D%22en-US%22%3EDocument%20conversion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1924237%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3EWe%20have%20been%20testing%20the%20Universal%20Print%20feature%20in%20combination%20with%20pull-print%20scenario.%20It%20worked%2C%20basically%2C%20all%20things%20considered.%20But%20we%20also%20wanted%20to%20test%20the%20document%20conversion%20and%20this%20particular%20feature%20failed.%3C%2FP%3E%3CP%3EWe%20enabled%20the%20feature%20under%20the%20corresponding%20section%20in%20the%20Universal%20Print%20management%20view.%20We%20have%20also%20configured%20the%20virtual%20printer%20(used%20for%20pull-print)%20to%20accept%20only%20PDF%20as%20content%20type.%3C%2FP%3E%3CP%3EStill%2C%20when%20we%20spooled%20a%20print%20job%20using%20a%20Windows%20client%2C%20the%20job%20data%20remained%20in%20OpenXPS%20format.%3C%2FP%3E%3CP%3EIs%20something%20wrong%20with%20our%20approach%20%2F%20configuration%3F%20Or%20is%20the%20document%20conversion%20not%20supported%20yet%3F%3C%2FP%3E%3CP%3EDoes%20anybody%20tested%20this%20and%20can%20confirm%20that%20it%20works%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello!

We have been testing the Universal Print feature in combination with pull-print scenario. It worked, basically, all things considered. But we also wanted to test the document conversion and this particular feature failed.

We enabled the feature under the corresponding section in the Universal Print management view. We have also configured the virtual printer (used for pull-print) to accept only PDF as content type.

Still, when we spooled a print job using a Windows client, the job data remained in OpenXPS format.

Is something wrong with our approach / configuration? Or is the document conversion not supported yet?

Does anybody tested this and can confirm that it works?

0 Replies