WD-40 Company Ltd saves 1,000+ IT man-hours each year through streamlined patching and mobile management

The WD-40 Company is a globally recognized manufacturer best known for its iconic blue-and-yellow can and its flagship product, WD-40 Multi-Use Product. Founded in 1953 in the United States, the company began with a simple mission: solve complex problems through smart chemistry—most famously creating a formula that displaced water on the 40th attempt. Today, WD-40 Company has grown into a trusted household and industrial brand, offering a range of maintenance, cleaning, and lubrication solutions used by consumers, professionals, and industries worldwide. Built on a strong culture of innovation, reliability, and problem-solving, WD-40 Company continues to protect, maintain, and extend the life of tools, equipment, and machinery across the globe.

Problem statement

• Manual, time-heavy software deployment and patching
• Poor visibility into software inventory and update status
• Disjointed tools for remote and mobile device management

Before adopting Endpoint Central, the IT team struggled to keep applications and operating systems up to date across all endpoints. Updating software and deploying patches at scale was cumbersome, and existing tools did not provide a clear, centralized view of which devices were compliant or at risk. PDQ connect worked inside the LAN but made managing devices outside the corporate network difficult, while Intune complicated package updates and patch rollouts. These gaps created productivity loss, higher operational overhead for admins, and increased risk from unpatched systems.

Solution with Endpoint central

Endpoint Central was introduced as the organization’s unified platform for patch management, remote administration, and mobile device management. With all devices already domain-joined, deployment was straightforward the IT team initially pushed the agent over the LAN using a service account and later transitioned to Microsoft Intune as the primary method for delivering the agent as an application.. This flexibility allowed them to choose the best deployment mechanism for each scenario, including Group Policy options where required.

Once onboarded, endpoints could be patched, monitored, and accessed from a single console. Automated patch management replaced manual processes, while built-in inventory and reporting tools gave administrators a real-time view of software versions and vulnerability exposure. The interface’s intuitive design and shallow learning curve enabled first-line technicians to use the console confidently, accelerating issue resolution and spreading operational ownership beyond a small core team.

Modules used

Patch automation

Remote control

Mobile device management

Results

• At least 1,000 IT man-hours saved annually through automated patching and remote remediation
• Faster, more consistent patch rollouts with immediate insight into missing or failed updates.
• Anticipated significant time savings in patching and security management.
• Improved audit readiness with centralized SOX and security posture reporting

Why Endpoint Central was chosen over competitors

The organization had previous experience with PDQ Deploy and Microsoft Intune but found them limiting for their needs. PDQ was effective only for on-premises endpoints and struggled with devices outside the LAN, particularly as remote work increased. Intune, while powerful, was more complex when it came to updating application packages and orchestrating patch rollouts. Endpoint Central offered a simpler, more unified experience—combining patch management, remote control, inventory, and MDM in one console with a user-friendly interface that frontline technicians could adopt quickly.