If you have a question please contact us.

Pcounter Knowledge Base

Upgrading Pcounter to a new version

Upgrading Pcounter for Windows

  • Close all currently running Pcounter programs on the desktop.
  • After downloading, run SETUP.  This will overwrite your existing program files and icons; however, this will not affect printing.  To update the server components, please continue below.
  • Run Pcontrol, Network View.
  • Find your server in the domain/workgroup, right-click, and select Pcounter, Configuration.
  • (Print Server)On the Services/Ports tab:
    • Stop the Pcounter Printer Control Service.
    • Update the Pcounter Port.
      • If the port is being updated from 2.15 or earlier, to version 2.20 or later, first install the Pcounter Port and then update the old ports.
    • Update the Pcounter Printer Control Service.
    • Start the Pcounter Printer Control Service.
  • (Data Server)On the Services/Ports tab:
    • Stop the Pcounter Data Server Service.
    • Update the Pcounter Data Server Service.
    • Start the Pcounter Data Server Service.
  • Generally, newer versions of server software are backward-compatible with older versions of PPopup, so it is not necessary to update PPopup.exe. However, if the upgrade is intended to address any PPopup issues or new PPopup features, then PPopup.exe should be updated on client workstations.

Upgrading Pcounter for NetWare (NDPS)

  • Close all currently running Pcounter programs on the desktop.
  • After downloading, run SETUP.  This will overwrite your existing program files and icons.
  • Run Pcontrol, Network View.
  • Find the NDPS Manager in the NDS tree, right-click, and select Pcounter, Configuration.
  • On the Global Settings page, select Install server files.
  • Either restart NDPSM.NLM, or else shutdown all Pcounter printer agents and start them up again.
  • Generally, newer versions of server software are backward-compatible with older versions of PPopup, so it is not necessary to update PPopup.exe. However, if the upgrade is intended to address any PPopup issues or new PPopup features, then PPopup.exe should be updated on client workstations.

Upgrading Pcounter for NetWare (Queues)

  • Close all currently running Pcounter programs on the desktop.
  • After downloading, run SETUP.  This will overwrite your existing program files and icons.
  • Run Pcontrol, Network View.
  • (NDS Pcounter.NLM)  Find your server in the NDS tree, right-click, and select Pcounter, Configuration.
  • (Bindery Pcount3x.NLM)  Find your server in the NetWare Servers list, right-click, and select Pcounter, Configuration.
  • On the NLM Status page, press Install server files.
  • Restart Pcounter.NLM.
  • Generally, newer versions of server software are backward-compatible with older versions of PPopup, so it is not necessary to update PPopup.exe. However, if the upgrade is intended to address any PPopup issues or new PPopup features, then PPopup.exe should be updated on client workstations.

Manual upgrade instructions for Pcounter for Windows server components

Should an error occur during upgrade, the new versions can be updated manually
  • Open the Services Control Panel.
  • Stop Pcounter Data Server service.
  • Stop Pcounter Printer Control service.
  • Stop Spooler (and dependent) services.  Examples of dependent services are Print Server for Macintosh and TCP/IP Print Server.
  • Copy the following files from the Pcounter program directory (typically C:\Program Files\Pcounter for Windows\NT\Server) to the Windows\System32 or C:\Windows\SysWOW64\ directory:
  • Start Spooler (and dependent) services.
  • Start Pcounter Printer Control service.
  • Start Pcounter Data Server service.

Windows printer configuration in mixed x86 and x64 environments


You have an x86 or x64 server and clients of both types who need to print to queues on the server. However, the server OS will not allow you to install a driver using a different architecture than the server OS uses - ie. x64 print drivers on an x86 server.


You must install the driver, that is using the differing architecture from the server, from a workstation to the server.
  • To do this, login to a workstation that uses the differing architecture, download the printer driver you wish to use on the server. Browse to the printers area on the server from a run dialog box - ie. Start -> Run -> \\servername\printers.
  • Once the window is showing the printers on the server, go to File ->Server Properties -> Drivers -> Add. A window should open up with check boxes for each architecture type supported by the server. Simply check the appropriate architecture type and click next.
  • Now you will be looking at the standard driver selection window. Browse to the driver you downloaded and select the appropriate .INF file.


Please note that both x86 and x64 drivers must have the exact same name. "HP LaserJet 2200 PCL 6" and "HP LaserJet 2200 PCL6" would be regarded as separate printers and the driver would not be correctly distributed. If they have the same name, they will appear automatically in additional drivers for both architectures in your printer's sharing properties, and will be distributed accordingly.

Jobs remain paused in the printer queue instead of printing

  1. Right-click on the Printer object in Pcontrol or the Printers and Faxes folder on the print server. Verify that “Pause Printing” is not checkmarked.
  2. If User account balances and Log File is enabled in the Pcounter printer profile, verify that the user who printed has a sufficient Account Balance to print the job.
  3. In the Printer Profile, check the Rules tab and verify that no rule has been enabled to pause print jobs that matches the names of unreleased documents in the queue. 
  4. In the Printer Profile, check the Settings tab. If Popup is enabled, make sure that the Popup application has been loaded on the workstation that originates the print job. The “Keep jobs paused after Popup” option should only be enabled if you are using the Popup with Pcounter Station, Pcounter Pro, or a Pcounter Embedded product to release print jobs.

Pcounter System Requirements

Pcounter for Windows

Minimum Software:
  • Windows 2000 Professional or Server
  • Windows XP Professiona
  • Windows 2003 Server
  • Windows 2008 Server
  • Windows 2012 Server
  • Windows Vista (Business/Ultimate)
  • Windows 7 (Business/Ultimate)
  • Windows 8
  • 32 and 64 bits OS versions are all supported.
Recommended Software:
  • Windows 2003 Server (Original build or R2)
  • Windows 2008 Server R2
  • Windows 2012 Server (Original build or R2)
Additional Configurations Supported:
  • Cluster Services
  • Server Core
  • Terminal Services
  • x86 and x64 environments
Minimum Hardware:
  • 1 GHz single core CPU
  • 2GB RAM
  • 20 GB for spooling
  • 10 MB disk space required for actual software
Recommended Hardware:
  • 2GHz+ Dual/Quad core CPU
  • 4GB+ RAM
  • 100 GB for spooling
  • 5 GB for data

Changing the print job owner name with an alias in Pcounter

Usually print jobs are assigned to a user according the user´s context (Windows-login data). In cases where this is not feasible or wanted (e.g. in a SAP environment) Pcounter may assign the print jobs to a user according the PJL-Header information. Please follow the below steps to enable the PJL-Alias function:

1. Make sure you are running Pcounter for Windows 2.52 or higher.

2. Create a file called PJLAlias.ini on the Pcounter server.

On 32 bit systems create the file C:\WINDOWS\system32\PCOUNTER\PJLAlias.ini. 

On 64 bit systems create the file c:\WINDOWS\SysWOW64\PCOUNTER\PJLAlias.ini

Alias location

The file should be in the following format :-

Alias File

Important ! - The alias will only be applied by Pcounter if the name in the PJL header does not already match a Windows domain or Pcounter user.

3. Edit the registry on the Pcounter server. Browse to :-


Where <PrinterName> is the name of the print queue where the job owner should be changed.

In the registry key, create a new DWORD value called UsePJLIdentification set this to 1 to enable the alias feature on the selected print queue.

Alias Reg

 Important ! - The option "Count jobs in advance for display" must be enabled on the Pcounter settings for the print queue to make Pcounter check the PJL header.

 4. Restart Pcounter services.

Important ! - The Pcounter services should be restarted if the PJLAlias.ini file or registry key is changed at any time.

5.  Print a test job

The user name on all jobs to the printer will be changed according to the incoming PJL data in the print job as indicated below :-

PJL File


 In this case, "User1" will be changed to "Mike" in the print queue.

Popup not working: Error 1722: RPC Server Unavailable

Solution 1: Close the Popup on the workstation and restart it. Right-click the Popup icon in the System Tray (near the clock), choose Preferences and see whether Status is now reported as OK.

Solution 2: Test Popup by temporarily running PPOPUP.EXE on the Pcounter server and submitting a print job. If Popup appears as it should on the server, check the permissions for the  user account logged into the workstation. Make sure the workstation user account  can execute PPOPUP.EXE. Also verify that the user logged into the workstation can access the Pcounter directory on the server: choose Start->Run on the workstation, enter \\servername\pcounter, and click OK. Once the Pcounter directory appears, doubleclick the PCOUNTER.INI file and confirm that it will open.

Solution 3: If Popup is running on a workstation located on a different subnet from the Pcounter server, check the routing configuration.  Click Start->Run on the workstation, enter \\servername\pcounter (where\\servername\pcounter is the path to your shared Pcounter data directory) and click OK. Verify that the Pcounter data directory opens on the workstation and that the user currently logged in can open and read the PCOUNTER.INI file.

Solution 4: If the workstation is running a real time antivirus scanner, add the directory from which PPOPUP.EXE is launched to the list of A-V scanner exceptions.

General: Check the Windows Services under Computer Management―>Services and Applications―>Services to verify that the Pcounter Printer Control Service and Data Server services are running. If problems persist, you can try deleting and recreating the shared printer object on the workstation. Check the printer object on the workstation. Verify that the Pcounter port is checkmarked in the Port settings

Pcounter and Mac clients

Pcounter for Windows can only account for print queues configured on a Windows print server.

Mac printing can be accounted for by using an LPR print queue on the Mac which essentially forwards the job to the print queue on the Windows server.

This guide details how to create such a printer on a Mac and the necessary changes to make in Pcounter for Windows.

1. Enable the Pcounter LPD Server

The Pcounter LPD Server is the feature of Pcounter which allows it to receive jobs via the LPR protocol. This needs to be enabled in Pcontrol.

To do this

  1. open the Pcounter Server Configuration
  2. Select LPD Server from the left-hand menu
  3. Check Enable LPD Server

All print queues on the server will be displayed in a list. Select the printer which you want Mac users to be able to print from and check the associated checkbox, such as the HP Laserjet above. Once selected, enter a name of your choice into the LPR queue name control.

Important: Use only alphanumerical characters in this name. The name will not be user visible but it will need to be re-entered manually on each Mac so it is recommended to keep it simple, such as HP above.

Important: The Windows LPD server (LPDSVC or Windows TCP/IP Print Service) will interfere with the Pcounter LPD Server and must be disabled if Mac printing is desired.

2. Create an LPR queue on a Mac

Important: This guide was written based on Mac OS 10.5.6. Whereas specifics may be slightly different on other versions of OSX the principles described will be exactly the same.

Important: In order for Pcounter to account for Mac printing and correctly associate print jobs to the correct Active Directory user, either:

- The Macs must themselves be part of the Windows Domain and the user must be logged in with their AD user account.
- You must use PcounterClient on the Macs to allow users to enter their AD or Pcounter User credentials.

Regardless of how the users are authenticated to the Mac, the configuration of the queue is the same.

Create a new printer through Apple > System Preferences > Print and Fax > Plus (+) sign.

The required settings are:

  • Protocol needs to be Line Printer Daemon – LPD
  • Address needs to be the IP Address of the Windows Pcounter Print Server.
  • Queue needs to be what you set to be the LPR queue name back in Step 1.
  • We recommend using the Mac Generic driver. Ensure you choose the same PDL as the driver on the server (e.g. PCL or PS).

Click Add once complete to finish the setup of the print queue.

If users authenticate to AD when logging into the Macs the setup of Mac printing is now complete. Any jobs sent to the Mac based queue will be forwarded to the queue on the server and accounted for via Pcounter.

If users do not authenticate to AD then they will need to use PcounterClient to enter AD credentials on the Mac. The installation and setup guide for PcounterClient for Macs is included with Pcounter Server. Default location is C:\Program Files\Pcounter for NT\NT\Client\Mac Popup Client.pdf and available in the Knowledge Base here

Installing Pcounter in a Windows Cluster

Pcounter works in a Windows cluster almost identical to usage on a standalone server. The main difference is that on a cluster, the Pcounter components are part of a Windows cluster resource, allowing them to be associated with active cluster nodes and groups, and managed in Cluster Administrator.

Pcounter supports Windows clustering from Windows 2000 and later (32 and 64bit), and all Pcounter functionality and flexibility is maintained when running in a cluster environment. Please see the Pcounter for Windows documentation for more detailed notes and exaplantion on all features available with Windows clusters.

This guide steps through a typical configuration of Pcounter in a 2-node Windows active/passive cluster on Windows 2008 R2.

The configuration includes:

  1. Confirming valid Microsoft Windows cluster
  2. Installing Microsoft Print Server Role
  3. Installing the Pcounter services
  4. Adding a print queue to the cluster

This guide assumes that a basic Windows cluster has already been established. For more information about creating Windows clusters, see this and this article.

Verify functioning cluster

First confirm that the Windows cluster passes the Validation Cluster test successfully. This ensures that network and drives are ready for the print server cluster roles. This is an important first step. If the validation tests do not finish successfully, it cannot be expected that the cluster will function.

For more information about validating a cluster, please see this article from Microsoft on Windows 2008 R2.

Prepare Windows cluster with Print Server roles

On each node in the cluster, install Print and Document Services role using the Server Manager.

Once installed, choose Configure a Service or Application and add the Print Server service to the cluster.


Give the cluster print service a recognizable name, in this case Cluster01PS.

Choose the shared cluster storage disk where the Windows print spooler and Pcounter data share will reside.

Once created, bring the new Print Spooler Cluster Resource online.

Installing Pounter for Windows in the cluster

Before proceeding, confirm you're on the active node, and make sure that all services and nodes in teh cluster are online, as Pcounter will attempt to configure both nodes from the active node.

When ready, run the Pcounter setup installer as Administrator.

Continue through the installer, and when complete open the Pcounter tool Pcontrol for managing servers and devices, found in the Pcounter for Windows start menu group.

To make configuration easier, start by adding our new cluster resource to the Quick Server List in Pcontrol. Right-click Quick Server List and choose Add to Quick Server List.

Enter the cluster printer resource name.

Once added, select the new server resource, and click the Pcounter configuration icon. This will open the Pcounter configuration for the selected object.

In this example configuration both the Pcounter data and Pcounter print services are installed in the same cluster. These roles could be separated onto different servers or different clusters, for example 1 active/passive Pcounter data server cluster and 10 non-clustered print servers. There are no restrictions in Pcounter to the mix and match of clusters and non-clustering of services.

To install the Pcounter data services, first create the Pcounter Share folder which contains data and configuration files. Go to Data Server screen and click Create. Choose to create the folder on the shared cluster storage.

Next go to Services/Portsand choose the Pcounter Data service and click Install.

Pcounter will automatically attempt to install the needed services on all nodes in the cluster. For this to succeed, make sure that all nodes and services are online.

In this example, both Pcounter data and Pcounter print services are installed in the cluster, so proceed with installing the Pcounter print services as well.

The services (Pcounter Printer Control and Pcounter Port) will be installed on each node in the cluster.

Tip: The installation on each node may take a few minutes, depending on the cluster configuration. If the installation fails, try closing and reopening Pcontrol and try again.

Once installed, start the Pcounter Print srvices.

If no print queues are installed in the print cluster, an error will appear.

To create print queues on the cluster, open a Windows Explorer windows and navigate to the cluster resource by entering the cluster name, for example \\cluster01ps in this configuration.

Then click View remote printers.

And click Add a printerand choose to create a local printer on the cluster.

Create a Pcounter monitored and managed print queue, by choosing the Pcounter Port from the Type of port. Alternatively create using standard TCP/IP port and migrate to Pcounter using the Printer Port Migrator in Pcontrol.

In this example we will configure a Pcounter Secure Pull Print queue using best practice settings.

Choose relevant driver, share on network and finish adding the printer.

Close and reopening Pcontrol and the newly created print queue is now visible. To start the Pcounter Print services the first time, select the cluster and choose Pcounter configuration.

Under Services/Ports the Print services can now be started.

The installation of Pcounter on the Windows cluster is now complete. Any configuration of print queues, pricing, rules, popup clients and so on, are identical to the standalone Pcounter configuration.

It is strongly recommended to test the failover of the print cluster extensively, in the Cluster Manager, on the print cluster resource, choosing Move this service or application to another node.

Licensing on cluster nodes

Pcounter in a Windows cluster is licensed per server node. To acess the license registration screen in Pcounter on a cluster, go to Services/Ports and double-click a node.

License key is based on Domain name and Server name of each node.

Moving Pcounter for Windows

The Goal

The Goal of this document is to provide step by step instructions for moving Pcounter for Windows from one Standalone** Windows server to another.
Please make sure to follow all Steps below.
** We have not yet tested a method to transfer printers on or off a clustered server.

Step1 - Prepare the new server

In this step the new server will be prepared to receive the old server's data.
The Pcounter software will be installed and ports and services will be installed in preparation of the transfer.
A replacement registration key will be requested from AND Technologies which will be used in later Steps.

  1. Download the newest version of Pcounter from the Pcounter web site download
  2. Unzip file and run setup on the server. 
  3. Open PControl and find the new server on the left side, right click on the server and select Pcounter -> Configuration
  4. Go to the Data Server tab and create the new Pcounter Share 
  5. Go to the Service/Ports tab and install all services and ports. The control service and the data services will also need to be started. 
  6. Email Pcounter Europe or your local Pcounter representative for a replacement key and make sure to include your old Registration key and New Server Name and Domain Name
Step 2 - Using printbrm utility

The next step is to use the printbrm.exe tool to backup your print settings.
This utility should be on both the new server and the old server (eg. in %WINDIR%\System32\Spool\Tools\)

Step3 - Backup Old Server Configuration and Data

Now the old server data must be backed up. Items such as the Pcounter share, all printers, and Pcounter global registry settings must be backed up.
Make sure you are logged in as Administrator to do all of these functions.

  1. Backup all data in the old Pcounter share, including all sub directories (C:\Pcounter by default). 
  2. Open Regedit.exe and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Pcounter
  3. Select file -> export and save the Registry export file
  4. Open the printbrm.exe utility : Open a Command Prompt window, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. Then type: %WINDIR%\System32\Spool\Tools\Printbrm.exe
  5. To save your printer configuration, type: %WINDIR%\System32\Spool\Tools\Printbrm.exe -B -F printer_backupfile where printer_backupfile is a filename of your choice.
  6. Save this file, the previous registry file and the Pcounter Share information to a neutral location and now go to Step 4 to restore this data on the new server 2
Step4 - Restoring Printer Configurations on New Server

In Step 3, the old server had all printers, Pcounter data and registry settings backed up. It is now time to use those files and restore them onto the new server.
Make sure you are logged in as Administrator to do all of these functions.

  1. Restore the Pcounter share data; including all sub directories by copying the contents of the old share to the same locations on the new share created in Step 1 when prompted simply overwrite files. 
  2. Open Regedit.exe and select file -> import, Select the exported registry file created in Step 3 and click ok. 
  3. Open the Printbrm tool as described in Step 3 and run:
    %WINDIR%\System32\Spool\Tools\Printbrm.exe -R -F printer_backupfile, where printer_backupfile is the backup file created in Step 3

All data, printers and settings should now be in the new server. Proceed to Step 5 for some final Clean Up tasks.

For more information on Microsoft Print services migration, please refer to this page.

Step5 - Clean Up

In this step a few settings must be changed on the new server to reflect the changes that have taken place.
Important: These steps should also be done on any computer using the Pcounter Administrator Utilities.

  1. Open Pcounter Administrator and select Utility -> Preferences
  2. Go to the Global settings tab and change the data server to reflect the New Server. 
  3. Verify in Pcounter Administrator that Client Code, Balances and Associations look correct (if applicable). 
  4. Open PControl and find the new server on the left side, right click on the server and select Pcounter -> Configuration
  5. Go to Global Settings tab and select the Registration and Trial Period Link. 
    Your old registration key will be in the registration area Input the new registration key you acquired from Pcounter Europe in Step 1 and click OK. 
  6. Set the Data Server to be the NEW print server (the old server will still be listed) 
  7. Verify the “Get user information from” is set to a PDC or the NEW server (it should not be the old server) 
  8. Go to the Service/Ports tab and Stop, then Start BOTH services. 

Congratulation! Your new server is ready to go, Verify workstation printers point to the new printer shares on the new server.
If your old server is going to be shut down permanently you can do so now, or to uninstall Pcounter on that server please download the Pcounter Un-Install Document from our web site here

How to check the Pcounter registration maintenance date

Pcounter for Windows
  • Run Pcontrol, Network View.
  • Find and select the registered server, right click, choose Pcounter, Configuration.
  • On the Global Settings tab, follow the link to Registration and Trial Period, and the registration information will be displayed.

View only a specific Active Directory OU in Pcounter Administrator

1. Run Pcounter Administrator, and browse to the specific OU which should be locked down.


2. Close Pcounter Administrator.

3. Run RegEdit and browse to the key:HKEY_CURRENT_USER\Software\Pcounter\PAdmin

4. Double-click on the value ADSContainer, and copy the contents to the clipboard.

ADSContainer Key

5. Open the Start menu and go to the Pcounter for Windows program group. Right click on Pcounter Administrator and select Properties

PAdmin Properties

6. Go to the Shortcut Tab. Edit target and add "LockOU=XXX" to the end of the target path, where XXX is the value pasted from the ADSContainer above.  (Example: "C:\Program Files (x86)\Pcounter for NT\NT\PADMIN.EXE" LockOU=LDAP://OU=Staff,DC=labdomain1,DC=com)

7. Run Pcounter Administrator again.

How to make a spool file for troubleshooting

If you'd like to send us a spool file that duplicates a problem, then use following guide:

Ensure that default datatype is set to RAW, and if this is not the case then change to RAW, restart the Pcounter services and see if your problem is gone.

How to change to RAW>

  • Open the Printer Properties.
  • Choose the Advanced tab.
  • Make sure that Enable advanced printing features is disabled.

To create a spool file:

  1. In Pcontrol, pause the printer
  2. Print the job that you know will be causing issues from the workstation application
  3. In Pcontrol, right-click on the job, Save as - please zip the file(s) if they are large
  4. Delete the print job(s) if you don't want them to print
  5. Send the file via email to your Pcounter contact
  6. Please indicate the number of pages in the document
  7. Send both .SHD files as well as .SPL files (Pcounter for Windows)

Important: Include exact information about the driver and driver version used as well as operating system version, for reproducing.

How to lock down Pcounter Administrator to a specific Active Directory OU

  • Run Pcounter Administrator, and browse to the specific OU which should be locked down.
  • Quit Pcounter Administrator.
  • Run RegEdit and browse to the key: HKEY_CURRENT_USER\Software\Pcounter\PAdmin
  • Double-click on the value ADSContainer, and copy the contents to the clipboard.    (Example: LDAP://CN=Users,DC=pcounter,DC=com)
  • Edit the shortcut used to launch Pcounter Administrator  (Example: C:\Documents and Settings\All Users\Start Menu\Programs\Pcounter for NT\Pcounter Administrator.lnk)
  • Edit target and add " LockOU=XXX" to the end of the target path, where XXX is the value pasted from the ADSContainer above.    (Example: C:\Program Files\Pcounter for NT\NT\PADMIN.EXE LockOU=LDAP://CN=Users,DC=pcounter,DC=com)
  • Run Pcounter Administrator again.

Workstation Manager -- Access Denied when server tries to access workstation print job information

After rolling out printers with Workstation Manager to a remote computer, make sure to reboot the data server.

If the problem persists with a Windows Server 2008 data server:

Run gpedit.msc on the data server. Navigate to Local Computer Policy->Computer Configuration
      Windows Settings
        Security Settings
          Local Policies
            Security Options

Set "Network access: Allow anonymous SID/name translation" to Enabled.

Changing the print job owner name in Pcounter

In cases where you want to transfer domain users from one to another or need to change jobs owner from a user to another existing user, you can use the JobOwnerAlias function. 

Please follow the below steps to enable it:

1. Make sure you are running Pcounter for Windows 2.70a or higher.

2. Create a file called JobOwnerAlias.ini on the Pcounter server

On 32 bit systems, create the file C:\WINDOWS\system32\PCOUNTER\JobOwnerAlias.ini

On 64 bit systems, create the file C:\WINDOWS\SysWOW64\PCOUNTER\JobOwnerAlias.ini


The file should be in the following format:


3. Edit the registry on the Pcounter server

Browse to:


Where <PrinterName> is the name of the print queue where the job owner should be changed.

In the registry key, create a new DWORD value called UseJobOwnerAlias set this to 1 to enable the alias feature on the selected print queue.


4.  Print a test job

The user name on all jobs to the printer will be changed according to the ini file.

Pcounter Pro ID Numbers - User manual

For Pcounter for Windows version 2.54 and above

About this Document

This document is intended to give a full explanation of all aspects of Pcounter Pro ID numbers which can be used by Pcounter for authentication to print release and copy accounting applications.

Points to Note

All file locations referenced in this work refer to the drive on which Pcounter is installed on the Pcounter Data Server unless otherwise stated.
It is assumed that all users have read access to the contents of the Pcounter share, default location C:\PCOUNTER.
Pcounter Pro ID numbers can be used for authentication Pcounter Pro application.
Typically this will be MFD "embedded" software or a hardware print release terminal.

Table of Contents


1. Introduction
2. Setting ID numbers in Pcounter Database
     2.1. Manual Creation of ID/PIN Numbers
            2.1.1. Mass Import of ID/PIN Numbers
    2.2. Manual Deletion/Modification of ID/PIN
    2.3. Restrictions on Manual Entry
3. ID Numbers in Active Directory
4. Maintenance and Troubleshooting
    4.1. Backing up CARDPIN.dbf
    4.2. Database Reindex

1. Introduction

Every user in Pcounter (AD user or Pcounter User) has two distinct ID numbers fields which are used for authentication to Pcounter Pro apps.
Each ID number can be assigned an optional PIN for extra security.
If PINs are used a user would need to input both their ID number and their PIN in order to authenticate.

The ID field in Pcounter is most commonly used to store a user’s ID Card Number so that a user can authenticate with a swipe of a card rather than having to type in credentials manually.

ID numbers can contain alphanumerical characters and "none-standard" characters, although it is strongly recommended to only use alphanumerical characters.
PINs can only contain numerical characters 0-9.

All IDs and PINs are stored in the ID database, CARDPIN.DBF.
Default location of this file is C:\PCOUNTER\DATA.
The contents of this file are encrypted and can only be viewed with PAdmin.

2. Setting ID Numbers

Pro ID numbers are managed via Pcounter Administrator (“PAdmin”), default location Start > Programs > Pcounter for Windows.
Select the Pcounter Pro ID/PIN numbers database button at the bottom of PAdmin.


The list of users displayed here will be the users in the OU which was selected in the User Accounting database when PAdmin was first opened.

2.1. Manual creation of ID/PIN Numbers

To set an ID number for a single user, right-click the user and select either Set ID number or Set ID number 2.


You can either:

  • Type in the desired number for the user into the Enter ID number control
  • Select Generate random ID number

Then click OK to assign the number. This will be reflected back in the main window of PAdmin.

Remember: The ID number should only contain alphanumerical characters.


It is also possible to assign numbers to multiple users by selecting all of the relevant users, rightclicking one of the users and selecting either Set ID option again.
The same window will appear.
Selecting User Sequential Numbering will allow you to enter an ID for the first selected user and all remaining users will have their ID set sequentially from this starting point.
Generate random ID numbers will also work for multiple users.


Once users have an ID set, it is then possible to set their PIN by right-clicking the user and selecting Set PIN number or Set PIN number 2.
Remember: The PIN field is numeric only.



2.1.1 Mass import of ID/PIN Numbers

IDs and PINs can both be imported using a csv or txt file. To do this, select Database > Import in PAdmin (when the Pcounter Pro ID/PIN numbers database button is selected).
The format of the file must be in either of the forms listed here:

  • Username,ID
  • Username,ID,PIN

Click OK and browse to your file.
Ensure the correct file format is selected in the Browse dialog (TXT is selected by default).



2.2. Manual deletion/modification of ID/PIN Numbers

To delete an ID or PIN right-click the user in question and select the relevant option, Delete ID number and Clear PIN number respectively.
The option Delete record will delete both ID and PIN.


To modify an existing ID/PIN select Set ID/PIN number again and enter the new value.

2.3. Restrictions on manual entry

It is possible to restrict the format of ID numbers which will be accepted for manual entry. In order to do this:

  • In ~\PcounterShare\PCOUNTER.ini create a new heading [PAdmin] if it does not already exist
  • Under this heading create a new key ProIDRestrictions=X where X is one of the following digits
    • 1: Only numeric entries will be allowed
    • 2: Convert all text to uppercase
    • 3: Convert all text to lowercase
  • Restart the Pcounter Printer Control service

3. ID Numbers in Active Directory

Instead of using its own ID database file (CARDPIN.DBF) Pcounter can be configured to lookup to AD for a user's ID and PIN.
Please note: There is no method within Pcounter import ID/PIN numbers into AD, this must be completed through another method.

This option is set via the Pcounter Pro DLL. This will be accessible through your print release or copy control application gateway, there is no method to open this through Pcounter Server.
If ID/PINs are in AD, simply enter the necessary fields into the ID number attribute and PIN number attribute fields on here.
Important: the names entered here need to be the Attribute LDAP name, not the Attribute display name.
For example: sAMAccountName instead of Username.

For a full list of LDAP Attribute names see Appendix 1.

The Test button will ask for an ID number value it would expect to find in the field you have entered into ID number attribute.
If the test is successful, the username of the account with this value in this attribute will be returned.

If you would like to use both AD and the Pcounter database to store ID numbers, check the box Check database if directory lookup fails.
This is especially useful if you would like to use AD for the ID/PINs of existing users and allow new users to self-associate their ID cards.



4. Maintenance & Troubleshooting

4.1 Backing up Cardpin.DBF

The contents of the ID database, CARDPIN.dbf, can be exported into a .txt file which can then be re-imported in the eventuality that there is a problem with the database, which will repopulate it.
This command uses the Pcounter command line utility ACCOUNT.EXE.
To perform this backup:

  • At a command line browse to ~\PcounterInstallDirectory\NT\ (default is C:\Program files\Pcounter for NT\NT)
  • Type the command:
    • account dumpids > my_dump_ids.txt
  • A file named my_dump_ids.txt will now be created in this location


In the unlikely event that the database needs restoring from such a backup, it is recommended that you first rename the existing CARDPIN.dbf and CARDPIN.cdx files to create a brand new database.
Then, open PAdmin and select Pcounter Pro ID/PIN numbers > Database menu > Import and browse to the file.

Note: For Linux or Novell servers :
You can copy the CARDPIN.CDX and CARDPIN.DBF files from the Linux server /usr/novell/sys/pcounter/dbf/ to a Windows environment and run the account.exe dump command to export the data.


4.2 Database reindex

If the database appears corrupted, it is possible to create a new index file which may
resolve the problem. To do this:

  • Take a copy of the existing CARDPIN.cdx file from C:\PCOUNTER\DATA
  • In Padmin ensure the Pcounter Pro ID/PIN numbers option is selected
  • Select Database menu > Reindex and confirm the prompt



A list of all Active Directory Attribute LDAP Names can be found at :

Permissions required to manage users, balances, and client codes

Modify balances: Full control share permission to \\DataServer\Pcounter.
Read/Write NTFS permission to \\DataServer\Pcounter\Data.
Run reports: Read share permission to \\DataServer\Pcounter.
Read NTFS permission to \\DataServer\Pcounter\Data.  (Write permission required for writing log file when modifying balances.)
Modify client codes: Full control share permission to \\DataServer\Pcounter.
Read/Write NTFS permission to \\DataServer\Pcounter.
Novell NetWare  
Modify balances
(NetWare 4.x):
Read/Write permission to All Properties in the top-level user context(s), or Read/Write permission to Account Balance, Allow Unlimited Credit, and Low Balance Limit properties of each user.
Modify balances
(NetWare 5.x):
Read/Write/Inheritable permission to Account Balance, Allow Unlimited Credit, and Low Balance Limit properties in the top-level user context(s).
Run reports: Read/File Scan permission to the Pcounter.log location.  (Write permission required for writing log file when modifying balances.)
Modify client codes: Read/Write/Erase/Create/Modify/File Scan permission to the PPopup.dbf location.

How to grant permissions to properties in NWAdmin:
(Note: Low balance limit may be shown as Minimum account balance in other applications such as ConsoleOne.)

  • Select a top-level user context, right-click, choose Trustees of this object.
  • Press Add Trustee, and find the object to whom the permissions will be granted.
  • (NetWare 4.x) Under Property rights, select All properties and check Read and Write.
  • (NetWare 5.x) Under Property rights, select Account Balance, Allow Unlimited Credit, and Low Balance Limit, and check Read, Write, and Inheritable.

iPrint queues and Pcounter for Windows

The following article describes a configuration which makes it possible to use Novell iPrint queues with a Pcounter for Windows solution.

We assume you created a Driver store and a Print manager on the OES server using Novell iManager and that Pcounter for iPrint is NOT installed.

We will create iPrint queues on the OES system which will be routed via LPR to the Pcounter LPD server on Windows.

After each configuration change, restart the printer agent.

1. Creating the iprint queue on the Linux server

Go to iManager -> Roles and Tasks -> iPrint -> Create Printer.

Enter a printer name (ex. Pull), select the container, the print manager and enter the IP or DNS name of the printer.

  • Set "LPR" as "Port"
  • Set the IP address of the Windows Pcounter server as "Hostaddress"
  • "Printername" is the name of the Pcounter queue on the Windows server (no space or weird char in the name!)

Create printer

  • Ensure "Enable LPR/LPD client support" is ticked in the configuration of the queue.

Pull queue


2. Creating the LPR queue on Windows server
  1. Install Pcounter for Windows as usual.
  2. Create a LPR queue on the Windows server :
  • From the Start Menu, go to Printers and Devices, then click on Add Printer.
  • Add a Local Printer


  • Create a new port, a Pcounter port (or a Standard TCP/IP then you will migrate it later in PControl)



  • Choose a driver...



3. Enable the LPD server

Enable LPD server in Pcontrol. Make sure Windows LPD server is disabled.


Set the LPR queue name as defined above in the point 1. Creating the iprint queue. It must be the same name as the Printername of the iPrint queue.

4. LDAP or NDS authentication

To get LDAP or NDS authentication working, enable and configure it in the Pcounter config as follow:


Where LDAP server here correspond to the eDirectory.



Install the NetWare Helper service:


Don't forget to click on Grant attribute rights to get balances update working.

5. PPopup or PcounterClient

If you intend to display a popup while printing, the Windows username from the original workstation who send the job via iPrint must match the long NDS username.
So in this configuration, you have to use the PcounterClient and set the following settings in the PcounterClient.ini file:

Example logging on NDS with username "user1.pce" and printing on the "pull" iPrint queue:

0. Configuration fo the pull queue and ppopup:




1. Ensure we're logged on Novell with the correct user "user1":


2. Send a print job from Windows workstation to the iPrint queue:


3. The printjob goes to the LPR queue with the correct username:


4. The popup is displayed:


5. The printjob is printed:


6. The printjob is properly logged:


Important note about Popup:
The current Pcounter version 5.52a doesn't support non-dotted usernames. So you will need this fix (which will be included in the next release) to get Popup working with NDS authentication.

Replace the current Pcounter.exe file located in C:\Program Files (x86)\Pcounter for NT\NT\Server\ by this one then stop/update/restart Pcounter print service.
If the Netware Helper service is running, and a job comes in with a dotted user name, and the first character is not a dot, then we will now add a dot as the first character.

How to exclude Pcounter from antivirus scanning

If you use an antivirus program on your server, either in real time or scheduled scan mode, it may be necessary to exclude certain files and folders from being scanned.

Exclude the following files and folders:

\windows\system32\pcntdata.exe  (for x64:  \windows\syswow64\pcntdata.exe)
\windows\system32\pcounter.exe   (for x64:  \windows\syswow64\pcounter.exe)
\windows\system32\pcountsp.dll  (for x64: \windows\syswow64\pcountsp.dll)
\windows\system32\pcountui.dll  (for x64: \windows\syswow64\pcountsp.dll)
\program files\Pcounter for NT (for x64 \program files (x86)\Pcounter for NT)
\Pcounter   (or whatever you have set as the Pcounter shared data directory)

On the workstation end, simply add PPOPUP.EXE to the exclusions.

Change Windows server spool with Pcontrol

Pcounter Pcontrol tool can be used to easily change Windows spool directory.

Start by opening Pcontrol (remember to open as Administrator) on the server on which to change spool.

Right-click the server and choose Properties.

Then navigate to Advanced tab and enter the new spool folder, and click OK.

Different print queues can have different spool directories (for load balancing or similar), but in this example, we change the spool for all printers.

Right-click in Pcontrol any print queue and choose Spool Directory.

Next choose to Read spool directory from registry, and then choose to either Save this setting for this printer only or Save this for all printers. To set new spool for all printers, choose the Save for all printers.

Note: this will also give access to the directory settings on the new spool directory. Make sure that the spool permission settings are identical to the standard Windows spool folder for uninterrupted operation.