Please speciy different port name for different edocprinter instances.
For example:
Create a eDocPrinter instance for documents requiring long time printing:
C:\Program Files\ITEKSOFT\eDocPrinter PDF Pro>addprn azm "edoc4longdoc" "edoc99"

correspondingly, where the [Profile Name] is the printer instance name.

For example, the printer “eDocPrinter PDF Pro” has its per-user settings in
HKEY_CURRENT_USER\Software\ITEKSOFT\eDocPrinter\PDF\5.0\Profiles\eDocPrinter PDF Pro

Administrators can deploy MUST settings on per name-value basis or apply FlagProhibitHKCU policy in a specific property page subkey in HKLM to enforce specific profile settings for all users. In addition, administrator can also apply FlagProhibitHKCU policy in a specific property page subkey in HKLM to hide the property page showing from all users. Since build 6067, administrators can deploy MUST settings on per name-value basis in HKLM for all eDocPrinter instances for all users.

Instead of utilizing GPO (Group Policy) to deploy settings to all Windows systems or users, centralized settings could be achieved by remote registry settings from a specific server. A special registry setting [RemoteRegSever] can be set as a server name or IP address for reading settings from a remote server's HKLM. When enabling this feature (it requires ADV pack license), the eDocPrinter instance will load the global default settings, per-profile MUST settings, and all-profile MUST settings from the remote server's HKLM instead of the local machine. RemoteRegServer can be enabled on a per printer instance or all printer instances depending on the configuration.

Ist es möglich, Variablen im Speicherpfad zu verwenden?

Yes. These Adv. variables can be used both in Filename fields and embedded commands. (which requires Adv. license)
Just ending tag # is supported in Ver 7 or later. %#DATE#

Ver 6 supports ending tag % only For example, %#DATE%_bambi.pdf

Please be careful about using %#DATE% or %#DATE#, which is resolved to date in format defined in Formats in Windows Regional settings.
It may contain slashes (/) which is reserved as Windows directory path separator.

Better using %#DATEX#_xxxx.pdf or %#YYYY#-%#MM#-%#DD#_xxxx.pdf or like.

(* Adv variables in V7)
It adds new Adv. variables FININAME and FINITITLE for resolving the initial filename with/without file type extension which is from lpszDocName in StartDoc when printing. This variable can be used in Filepath command to build a destination path from the initial job info name, e.g., %%Filepath: %#FINITITLE#-%#DATE#.pdf%%.
It also adds Adv. varaibles FINIDIR and FINIFILE for resolving the initial DestDir and DestFile values.
In addition, it supports resolving Adv. variables using # as end tag. For example, %%Filepath: Job%#DATEX#%% will also be resolved to the proper value when used. This avoid '%' may be conflicted with the default command tag(%%).

PDF Verarbeitung asynchron vs. sequentiell

For silently batch printing or appending, please choose [Process PDF sequentially] mode in Destination property page.
[Process PDF sequentially] mode is for queuing multiple jobs to ensure those are processed sequentially.
For example, print by batch to append to the same destination, print by batch to ensure processing in a logic order, or print by batch with sending emails by singleton application like Outlook.
In [Process PDF sequentially] mode, it will process PDF and email sequentially to avoid racing condition.
On the other hand, the default is [Process PDF asynchronously] for highest throughput if there is no race condition.

The default is "Process PDF Asynchronously" mode
It will start an epdfact.exe for processing each job PDF.
It will end when PDF is finished.
When printing multiple jobs, it will have multiple epdfact.exe

For batch printing or appending,
Please select "Process PDF synchronously" mode
It will queue all jobs by only an epdfact.exe

Mehrere Dateien ans PDF anängen

For multiple PDF files, they have to merge one by one on each print job.

Or suggest using drag2pdf.exe UI or command line to merge:

What you need is to use Drag2PDF.exe, which is an optional Adv. toolbox
feature.

You can either
1.
Run Drag2PDF.exe UI. And select the existing PDF files. And set
the watermark property page of Drag2PDF. Click to convert to save.
Or
2.
For Drag2PDF command line, (you still need to use UI to set the
corresponding watermark page of the printer profile used (e.g. Drag2PDF
profile)

In addition,
Drag2PDF.exe relies on eDocprinter instances used for controlling detailed behavior.

For example, the default instance used by drag2pdf.exe is "Drag2pdf" printer instance.
You can modify or create a new edocprinter instance and turn OFF [Launching PDF reader postaction] in its Destination property page.
(e.g., create a "MyPDF1" printer by "Add new printer in "eDocprinter PDF Pro shortcuts from Windows Start-> All programs)
(You can also control the edocprinter instance by registry setting or embedded commands Please refer epdfsdk.pdf for details)

It shall be due to postaction is asynchronous by default.
Please add the command or registry setting (DestWaitPostAction in Destination subkey)
%%DestWaitPostAction: True%%
It will wait the post-action commandline finished.

1.
If what they need append to the destination PDF created by eDocPrinter,
Please use
drag2pdf.exe -s -svx -sm1 "%s" "c:\Vorlagen\agb.pdf"

where it will use the first as the result PDF when calling drag2pdf.exe
And please set the When File exists mode to [Merge by Append to] in Destination page of Drag2PDF printer profile.

OR

2.
In ver 7,
they may use FNAME, FDIR variables in the command line which represents the destination dir and file name
For example,
drag2pdf.exe -s -svx -sm1 -sf"%#FDIR%\%#FNAME%" "%#FDIR%\%#FNAME%" "c:\Vorlagen\agb.pdf" "c:\Vorlagen\agb2.pdf"

And please set the When File exists mode to [Replace directly] in Destination page of Drag2PDF printer profile.

BTW, if they just want to append 1 PDF file to the destination path, they may use the Overlay with function for that.

2. If using embedded commands, users can add a command %%EmailOLClickSend: True%%.
When it is true, it will emulate clicking Send button when in silent mode instead of EMAPI SubmitMessage.
It requires build 6205 or later.

Gruppieren von eDocPrinter Profilen verhindern.

For adding edocprinters without group, please use the commandline “addprn.exe azm”

For example:
C:\Program Files\eDocPrinter PDF Pro\addprn azm "my edocprintername" “uniqueport1"
Where the port name must be an unique one.
Windows groups printers of the same driver and port name together.

The silent key exe has to be executed under real administrator permission.
(e.g., right-click on the CMD.exe to run as administrator, it will prompt
for UAC grant of real administrator permission)
(because silent key exe is designed for executing silently)

The main registration key information shall be in
HKEY_LOCAL_MACHINE\SOFTWARE\ITEKSOFT\eDocPrinter\PDF\5.0\Register

eDocPrinter kann den E-Mail Client nicht starten (Win7, 64 Bit)

There is an improvement on build 5901 (or later) for the default email
client mode for 64bit Windows with some legacy 32bit email client.

Problem beim Drucken aus App-V virtualisierten Anwendung

That shall be ok on APP-V when using eDocPrinter 6.68 or later with the OSD
configured with
<LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>
Since it is verified by several customers' deployment.
Please
1. Check the .OSD file directly in their app-v project to see whether the
value is TRUE.
For example:
<VIRTUALENV TERMINATECHILDREN="FALSE">
<POLICIES>

“Attach to eDocPDF port” it attaches eDocPDF port instead of LPT port.
Windows requires every printer attaches a port, though it is has no real function on virtual printer like “eDocPrinter PDF Pro” or similar

Like most activations method, the activated reg info depending on the
hardware info.

They shall stream the server without eDocPrinter HKLM reg info first. (on
HKEY_LOCAL_MACHINE\Software\ITEKSOFT\eDocPrinter\PDF\5.0\Register)
And activate the server on the About page after server running.

They may backup the reg key info for servers activated, which is also in
HKEY_LOCAL_MACHINE\Software\ITEKSOFT\eDocPrinter\PDF\5.0\Register
Each server have its own activation info.

Add the following registry settings in the corresponding "Doc Info" registry, for example:
HKEY_CURRENT_USER\Software\ITEKSOFT\eDocPrinter\PDF\5.0\Profiles\eDocPrinter
PDF Pro\Doc Info
Set True to DocInfoEnableCustom
And add
CustomDocInfoCreator
CustomDocInfoProducer

When set to 1, it will convert 0xAD to 0x2D (normal dash) And 0xA0 to 0x20 (normal space) Some application may use 0xAD or 0xA0 which has similar glyph as normal traditional 0x2D or 0x20. However, these 0xAD or 0xA0 are illegal characters in email address
protocol.

Wie die Druckweiterleitung gemeinsam mit einer Vorlage nutzen?

For overlaying in Redirect, (in using "by printing the spool job" mode)
in addition to the template PDF (your header& footer template page), you
need to a template spool job file (.PDJ) first
(this is for used in Redirect "by printing the spool job" )
For example, open your original template doc (header&footer),
and print to eDocPrinter PDF Pro
(in Redirect property page,
enable "Redirecting current print job..." and the option "Save print job as *.pdj!)
It will then create PDF and, in the same directory, there will be an .PDJ of
the same filename
( BTW, If you have only PDF, you may create PDJ by printing it from Acrobat reader,
though the pdj may be large due to reader printing method.
Hence we recommend printing directly from the original application to
eDocPrinter PDF Pro to create the template PDF and pdj)
Afterwards,
when doing redirect with overlay with,
it will automatically find the template.pdj for redirect to print.

Wie kann man default Einstellungen für die Benutzer festlegen?

For default settings,
1. Default settings are stored in HKLM for the corresponding printer
profile.
For example,
The per-user settings of printer profile "eDocPrinter PDF Pro" is in
HKEY_CURRENT_USER\SOFTWARE\ITEKSOFT\eDocPrinter\PDF\5.0\Profiles\eDocPrinter
PDF Pro

Its default settings is in
HKEY_LOCAL_MACHINE\SOFTWARE\ITEKSOFT\eDocPrinter\PDF\5.0\Profiles\eDocPrinter PDF Pro
Administrators may use PropAdm to set the default settings.

However, default settings will be overridden by the per-user settings in
HKCU
(that is if a key-value is existing in HKCU which will override the default
value in HKLM).

2. MUST settings
Since default settings in HKLM may be overriden by settings in each user's
HKCU,
instead of default settings, administrator may add MUST settings in HKLM
e.g.
HKEY_LOCAL_MACHINE\SOFTWARE\ITEKSOFT\eDocPrinter\PDF\5.0\MUST\Profiles\eDocprinter PDF Pro
MUST settings have to created manually or by commandline.

Please refer epdfsdk.pdf installed

3. For deploying settings in HKCU or HKLM,
administrator may use either
(i). regedit.exe command line to import settings
or
(ii). using GPO to set startup script or logon script to set registry
setting
or
(iii). using GPO with registry .adm template to set these settings.
Please refer Microsoft Technet for more info.
or
(iv). call eDocPrinter addprn.exe commandline to write registry values "addprn.exe ag" is for writing registry settings with arguments specified.
(refer http://www1.iteksoft.com/download/doc/edocpdfSilent.pdf )
Administrator may call this command line in startup or logon script.
Or they may write a .bat file with calling this commandline.
.MSI installer may config a property to call a .bat when installing
for deploying HKLM settings.

Kann PDF Sealer multisign smart cards verwenden?

PDFSealer supports signing by USB token or Smartcard reader by Windows CSPs
(it requires the USB token and smart card inserted before signing).
However, PDFSealer does NOT read directly from USB security token or
Smartcard reader.
It requires the vendor of smartcard reader or usb token for supporting
Windows CSPs, some legacy cards may not support this.
PDFSealer supports entering PIN code UI by Windows CSP and will be granted permission to sign when its process not
terminated
by Windows CSPs
(Windows CSPs requests PIN code for the permission).
eDocPrinter supports embedded command (registry setting) DestSignCertPasswd
for automating PDFSealer
to sign silently when batchly creating and processing PDFs.

Currently PDFSealer supports only signing PDF internally, not as external .p7s or .p7m file.

Wie kann ich Seitenzahlen hinzufügen?

There are variables supported in Text watermark%#p1% for representing current page number
and %#p0% for representing total number of pages

It requires EPDFADV license, otherwise some extra text are stamped
(since it is an ADV feature Advanced variables)
For details of other variables, please epdfsdk.pdf installed or http://edocprinter.info/download/doc/edocprinter-commands.pdf
Command2Action- Variables section.

eDocPrinter is a NATIVE Windows printer driver rather than a real printer instance. It supports Office-addins and UIs. For installing and using in Windows workstation (e.g. XP/Vista) locally, users need to install locally and it requires WKSLIC.

For centralized usage, we suggest Terminal server licenses. (TSESVR or TSECLI) For Terminal Servers support, it can be installed in terminal servers ONLY, and users can remote logon to print in the terminal sessions or remote
desktops. Users can remote logon to the terminal server and access the applications to print to ceate PDFs and saves on the server drives or redirect mapped local drives.

If users really need sharing eDocPrinter, users have to add new eDocPrinter printer instance (by PropAdm or Add new printer shortcut). And enable the "printer server mode" option in the adding new printer instance query dialog. AND please refer below for special printer server mode, (INTRASVR)

============================================================================
Since Ver. 6.30, eDocPrinter supports a “printer server” mode for accepting printing jobs from other computers, which may not have eDocPrinter installed. It requires intranet or internet server license (per-server)(INTRASVR, INTERSVR).

eDocPrinter PDF Pro is a native Windows printer driver with Office-addin support for creating PDF files on local or network file systems. For fully functioning with support of prompting UI and Office addin interactions, it is required to install eDocPrinter PDF Pro driver on necessary machines locally.

The new printer server mode is designed for special purpose usage, which will do the printing and post-processing in the server. However, under this server mode,

It does NOT support prompting SaveAs dialog or similar UI dialogs. It does NOT support Office-addins for internal links, cross references, or headings -> bookmarks conversions.
It does NOT support launching PDF readers or Email clients in clients.
It does NOT support Drag2PDF.

As a result, it may NOT be suitable for ordinary customers.

Administrator have to add or set extra printer instances by “PropAdm” or
“Add New Printer” shortcut to enable printer server mode in addition to
sharing the printer instance by printer control panel. These actions will
enable “print server” mode for the eDocPrinter instances (profiles).

Printer server mode does not support prompting UI (e.g. SaveAs dialog)
because the printing jobs are processed all in the server side. By default,
it automatically generates the filename and saves the PDF into the user’s My
Documents folder. And it does not launch PDF reader. Usually the user’s
context is determined by the logon session or printer connection session in
the active directory. Normally, it is the logon user context if printer and
clients are both in the same active directory domain.

Basically, printer server mode provides a function similar to the network
sharing or active directory printers without installing eDocPrinter drivers
on client workstations. Users may change the profile settings, e.g., to
enable detecting embedded commands, stamping watermarks, or etc. in the user’s profile in the server. Multiple printer servers are supported in the same
way as multiple printer instances of eDocPrinter PDF Pro.
============================================================================