You can use CCleaner Network to remotely diagnose and fix issues.
Even if you cannot immediately resolve the problem within CCleaner Network, running its diagnostics is a good way to eliminate possiblities and narrow down causes.
You may receive emails from users or management saying that their PCs are slow to run, crash often, or are slow to boot. Or, they may be receiving a low disk space message:
Or, you may receive formal support incidents from employees.
Lastly, you may hear about problems by word-of-mouth.
First, determine whether the problem appears to be an individual Endpoint, isolated to a Group, or widespread across a Network. You can run an audit to check Endpoint, Group, and Network health.
Alternatively, you can run a report to produce data that you can further manipulate in Excel or other programs.
As always, unless you know for sure that the problem is isolated, start at the Network level, then work down to Groups and finally individual Endpoints.
You should weigh any audit results or reports against typical patterns in your organization. It may be quite common for development or media Endpoints, for example, to be extremely defragmented - but it may be much less so for a lightly-used reception Endpoint.
Another factor to consider is whether the problem may be more perception than anything else. Someone who has two crashes in a row after months of trouble-free computing may suddenly feel that their PC is in trouble, but it may also be an unfortunate coincidence.
Lastly, use CCleaner Network's audits as part of your administration toolkit. Reported issues may also be a result of underpowered PCs, Network problems, or other concerns outside the scope of CCleaner Network.