Doors32 Badging License

Doors32 Badging License

1.0 Introduction

The license code is a unique number based on a computer’s hardware ID number. It is not transferable to other computers.  Each computer that will be printing badges will need to have its own Badging license code. Badging is a fee-based option and  while badging can be run in Demo mode without a license code,  all printed badges will have the word “SAMPLE” watermarked across the face of the badge.

Note: BEFORE PRINTING BADGES, THE DRIVER FOR THE BADGE PRINTER MUST BE INSTALLED ON ALL WORKSTATIONS FROM WHICH BADGES WILL BE PRINTED. Next, a badging template must be created. The template defines the content and layout of the information to be printed on the badge. If you are printing only from the host workstation, only one license code is required. 


2.0 Printing Badges

The standalone program used to create templates is called GuardDraw. The badge printer can be either directly connected to the workstation via a Parallel printer port or it can be configured as either a network printer or a shared printer on another remote workstation. The badge printer driver and the GuardDraw  program must be installed on each remote workstation from  which badge print commands are performed.


3.0 General Notes

Badge printing can only be done from one workstation at a time. However there is an advantage to this... any changes or modifications made by that user can be sent immediately to the database without concern of  interference by another user.

4.0 Card Templates

Ensure the badge templates are saved to the badge folder of the installation and that the GuardDraw program itself is pointing to the Doors.mdb in Options>> View.


5.0 Troubleshooting

  1. Check Read Only Is not flagged on the DB files.
  2. Ensure you are logged into the host PC with full administrative rights.




    • Related Articles

    • Doors32™ Photo ID Badging Data Sheet

      Attached.

    • Doors32™ - System Migration

      Transfer the Doors32 System to a New PC The following steps detail the quickest and easiest method for transferring a Doors32 system to a different PC. Note: Doors32 is not compatible with and version of Windows after Windows 7. Also note; if ...

    • Doors32™ System Upgrade

      With the advent of Windows 10 and the non-support of Windows XP by Microsoft, we strongly advocate upgrading your system to from Doors32 to Doors.NET. Keri Systems has breathed new life into legacy PXL-500 and Entraguard Telephone Entry systems; ...

    • Doors32 - Daylight Savings Time

      1.0 Introduction Due to a change in US Federal law governing the beginning and ending dates for Daylight Saving Time, the firmware on PXL-250s (v6.3.61), PXL-500s/PXL-510s (v8.4.47), and EntraGuards (Gold/Silver/Titanium v7.3.17 and Platinum v9.0.3) ...

    • Doors32™ - Creating a Full Backup

      Quite simply, all the Doors32 database information is held in a single folder which, for a typical installation (of the latest version), can be found at the following location: C:\Kerisys\Doors_v5.42\DB This is the only file you will need to restore ...