RFID Sync Service: Automating ZKTeco RFID & Attendance Synchronization | VB.NET Windows Service

In this video, I provide a complete overview of RFID.SyncService, a VB.NET Windows Service designed to automate synchronization between ZKTeco RFID/biometric machines and a central database. The project is designed for environments where multiple ZKTeco devices are deployed across different locations and employee/RFID information and attendance transactions need to be synchronized automatically. 🔹 What does RFID.SyncService do? The service handles two major synchronization workflows: 1. RFID / Employee Synchronization Employee and RFID information can be synchronized between a designated Master ZKTeco machine, central database, and multiple target machines. The system supports multiple devices and locations and can process machines sequentially or concurrently, depending on configuration. 2. IN/OUT Attendance Synchronization Attendance transactions recorded on ZKTeco machines are collected by the service and synchronized back to the central database. The attendance workflow uses temporary and backup tables to provide a controlled processing pipeline before records are stored in the permanent attendance table. 🔹 Architecture Covered In this video, I explain: Overall RFID.SyncService architecture Windows Service lifecycle ServiceHost and background workers RFID synchronization workflow IN/OUT attendance synchronization Master device concept Multiple machines and multiple locations Sequential vs. parallel device processing Database repository architecture Oracle and Microsoft Access support ZKTeco device communication IDeviceClient abstraction Database connection factories Configuration through appsettings.json Logging and troubleshooting Daily machine maintenance Temporary and backup attendance tables Adding support for a new device Adding support for a new database provider Deployment and external dependencies How to modify and extend the application 🔹 Database The project separates database access from synchronization logic through repositories and connection factories. The database layer includes tables for: Employee/RFID information Temporary RFID synchronization data Device information Synchronization scheduling Deleted users Temporary attendance transactions Attendance backups Permanent IN/OUT attendance The project can be adapted for different database providers by implementing the appropriate database infrastructure rather than rewriting the synchronization workflow. 🔹 ZKTeco Integration The service communicates with ZKTeco devices through the device abstraction layer and the ZKTeco SDK. This design keeps vendor-specific communication separate from the core synchronization logic and makes the application easier to maintain and extend. 🔹 Deployment The video also explains what is required to deploy the service on a production server, including: .NET Framework requirements ZKTeco SDK and required vendor components Oracle ODP.NET Managed Driver Microsoft Access database components when Access is used Network and firewall configuration appsettings.json Windows Service installation Logging and initial verification 🔹 Extending the Project The architecture is designed so that new technologies can be added without unnecessarily changing the core synchronization logic. For example, adding a new device type generally involves implementing the device interface and registering the new implementation. Similarly, adding a new database provider involves implementing the database connection and repository layer for that provider. 🔗 Source Code The complete project source code is available on GitHub: https://github.com/anjumsohail/RFID.S... 🎯 Who is this video for? This video is useful for developers working with: ZKTeco biometric/RFID devices Attendance management systems VB.NET / .NET Framework Windows Services Oracle databases Microsoft Access Device synchronization Multi-location attendance systems Repository and factory-based application architecture The goal is to explain how the different components work together and how the system can be deployed, maintained, and extended for future requirements. Chapters 00:00 — Introduction 01:10 — The Problem 03:00 — Overall Architecture 03:40 — ServiceHost 04:10 — Workers and Scheduling 06:15 — RFID Synchronization 07:15 — Multi-Device Processing 09:15 — IN/OUT Attendance Synchronization 10:30 — Daily Device Maintenance 11:30 — Database Architecture 12:30 — ZKTeco Abstraction 13:15 — Configuration 13:45 — Logging & Troubleshooting 14:15 — Deployment 14:30 — How to Modify 15:00 Conclusion Related Videos • ZKTeco Time Attendance Software Setup & API    • Zkteco Time Attendance Software Setup and ...   • ZKTeco 4500 Biometric Integration using C# .NET SDK    • ZKTeco Fingerprint SDK   #ZKTeco #RFID #AttendanceSystem #VBNet #WindowsService #Oracle #MicrosoftAccess #Biometric #SoftwareDevelopment #Database #Synchronization