A municipal Windows host grants the tester only a standard user session; software installs that need admin rights are blocked. What staging concept fits?

With only a standard user session on a municipal Windows host and admin-required installs blocked, stage assessment utilities in permitted user-writable locations using native capabilities that do not require admin installs. Forcing local privilege escalation before any file can be placed is not always required or authorized yet. Reimaging the workstation mid-engagement to gain admin quietly is destructive and out of bounds. Copying tools into System32 without write permission and ignoring errors is futile and noisy. Exam caveat: user-land staging still must follow malware and tool-approval constraints in RoE. Operational check: locate writable user paths, stage only approved utilities, avoid persistence unless authorized, and record file paths for later removal from the municipal host. Document the rationale in the municipal engagement notes so later civic responders know which boundary was honored and which failure modes the rejected options would create for public services. Document the rationale in the municipal engagement notes so later civic responders know which boundary was honored and which failure modes the rejected options would create for public services. Document the rationale in the municipal engagement notes so later civic responders know which boundary was honored and which failure modes the rejected options would create for public services.