Windows Terminal Server Bullzip PDF installation

Installation and setup related issues.

Moderator: jr

bdopudja
Posts: 1
Joined: Sat Jan 19, 2008 4:04 am
Location: Croatia

Windows Terminal Server Bullzip PDF installation

Post by bdopudja »

Short guide how to install Bullzip PDF Printer on to a Windows Terminal Server 2003, no AD installed, somewhat risky environment:

[b]1.[/b] Download and normally install Bullzip PDF, including Ghost Script.
[b]2.[/b] Print a file on terminal server with Bullzip PDF Printer
[b]3.[/b] go to: C:\Documents and Settings\"your account name"\Application Data\Bullzip\PDF Printer

Put this into the [b]settings.ini[/b] (Excluding stars):

*************
[PDF Printer]
afterprintprogram=
afterprintprogramdir=
disableoptiondialog=
author=<username>
creationdate=
creator=
keylength=128
keywords=
mergefile=
mergeposition=bottom
moddate=
output=<title>.pdf
ownerpassword=
permissions=
settingsprogram=
showpdf=no
subject=
superimpose=
target=printer
title=<title>
userpassword=
watermarkrotation=c2c
watermarktext=
suppresserrors=no
watermarkcolor=#D9D9D9
watermarkfontname=ARIAL.TTF
watermarkfontsize=45
watermarkoutlinewidth=2
watermarklayer=top
watermarkverticalposition=center
watermarkhorizontalposition=center
watermarkverticaladjustment=
watermarkhorizontaladjustment=
rememberlastfilename=no
rememberlastfoldername=yes
zoom=fitall
showprogress=
showprogressfinished=
runonsuccess=
runonsuccessdir=
runonerror=
runonerrordir=
confirmoverwrite=yes
usedefaultauthor=no
usedefaulttitle=no
openfolder=no
showsaveas=always
showsettings=never
appendposition=
*************

And this in your [b]user.ini[/b]:

*************
[User]
lastfoldername=\\tsclient\C\
*************

[b]4.[/b] Now, go to printers, Bullzip PDF Printer, Security and allow Remote Desktop Users to print. No other setting are necessary.
[b]5.[/b] Copy "Bullzip" directory from your application data to the application datas of your users.

[b]6.[/b] Voila! :)


There are many more ways this can be done, modify setting to your liking. Normally, I was getting some strange file access errors, and found that this practice works for me. You must tell your clients to connect their drives (an option in RDP client) to the RDP session, and also - you must enable users to connect their drives in Terminal Services Configuration.


I hope this is will help someone!