31 lines
1.7 KiB
Markdown
31 lines
1.7 KiB
Markdown
## How to use
|
|
|
|
Simply download the [.bat file](https://git.tobiastime.xyz/Tobias/automated_rammap.bat/src/branch/main/automated_rammap.bat) and right click "run as admin"
|
|
|
|
This automatically handles downloading RAMMap, running it after its download, and creating a scheduled task to run it in the background every half an hour indefinitely
|
|
|
|
To verify the scheduled task has been deployed, in an admin cmd run:
|
|
|
|
```
|
|
schtasks /query /tn "RAMMap Automated Cleanup" /fo LIST /v
|
|
```
|
|
|
|
## Overview
|
|
|
|
Winblows 11 is awful, bloated and absolutely terrible, (like the Windows before it but worse). It is something I have to be paid to use and is filled with countless memory leak errors.
|
|
|
|
Consequently, Helpdesk technicians get "slow PC" tickets daily, wherein one of their resolution steps is manually logging onto the device with 8GB RAM and running RAMMap
|
|
|
|
Inevitably the device will slow down once more, after which another "slow PC" ticket will be raised by the user, and another technician will log on and spend their time performing the same manual remediation steps
|
|
|
|
This script is aimed to reduce that manual work and be deployment friendly, simply right click to run as admin and the entire download and installation will be automated
|
|
|
|
Having the script run as SYSTEM avoids the need to create another user with local admin permissions, harnessing a global built-in identity
|
|
|
|
This methodology is used since RAMMap requires elevated permissions, which end-users are typically not granted
|
|
|
|
Additionally it avoids assuming an admin's username, as these will vary heavily between customers in an MSP environment
|
|
|
|
## To-do
|
|
|
|
- Add optional logging which will create a second task that logs each time RAMMap runs, clearing said log file on reboot |