Design a safe disk-space inventory instead of an administrator cleanup script

Instruction: Design the smallest useful automation, including scope, permissions, output, failure handling, pilot, and success criteria. No code is required.

Context:

A fictional service desk spends time asking users how much disk space remains on 200 managed Windows laptops. A new hire proposes running a script as administrator on every device to delete Downloads and temporary folders. You are the senior technician reviewing the proposal. The actual request is a read-only inventory of system-volume capacity and free space. Policy permits an approved management tool to collect asset ID, collection time, volume capacity, and free space after a user notice; it forbids collecting filenames, personal data, or credentials. The existing delegated reporting role is expected to support the inventory but has not been tested on every device type. A five-device pilot is authorized. Remediation needs a separate reviewed change and relevant user approval; remote screen control requires consent.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would narrow the proposal to the requested read-only inventory and keep cleanup out of this release. We need reliable free-space information from two hundred managed laptops, not permission to delete people’s files. I would work with the new hire on a five-device pilot using the delegated reporting role and the approved management tool. The output would contain the asset identifier, collection timestamp, system-volume capacity, free space, and an explicit status such as collected, offline, or access denied...

Upgrade to view official answer

Related Questions