https://github.com/deekayen/ansible-role-cleanmgr
Install Desktop Experience and then run Disk Cleanup on Microsoft Windows using Ansible.
https://github.com/deekayen/ansible-role-cleanmgr
ansible ansible-role desktop-experience disk-cleanup
Last synced: 16 days ago
JSON representation
Install Desktop Experience and then run Disk Cleanup on Microsoft Windows using Ansible.
- Host: GitHub
- URL: https://github.com/deekayen/ansible-role-cleanmgr
- Owner: deekayen
- License: bsd-3-clause
- Created: 2017-06-02T19:11:29.000Z (almost 8 years ago)
- Default Branch: main
- Last Pushed: 2020-10-06T20:51:30.000Z (over 4 years ago)
- Last Synced: 2025-03-27T06:01:40.371Z (about 1 month ago)
- Topics: ansible, ansible-role, desktop-experience, disk-cleanup
- Homepage: https://galaxy.ansible.com/deekayen/cleanmgr/
- Size: 24.4 KB
- Stars: 5
- Watchers: 4
- Forks: 4
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
- awesome-starred - deekayen/ansible-role-cleanmgr - Install Desktop Experience and then run Disk Cleanup on Microsoft Windows using Ansible. (Others)
- awesome-starred - deekayen/ansible-role-cleanmgr - Install Desktop Experience and then run Disk Cleanup on Microsoft Windows using Ansible. (Others)
README
[](https://travis-ci.org/deekayen/ansible-role-cleanmgr) [](https://www.repostatus.org/#inactive)
Disk Cleanup
============Install the Desktop Experience feature and run Disk Cleanup on Microsoft Windows.
Role Variables
--------------Setting the `cleanmgr_install_reboot` value to `true` allows Ansible to reboot
the target Windows computer after installing the Desktop Experience feature.
Ansible doesn't get a result from `cleanmgr.exe` to know if it should reboot or not, so toggling `cleanmgr_cleanmgr_reboot` will always or never reboot after running `cleanmgr.exe`.cleanmgr_install_reboot: true
cleanmgr_cleanmgr_reboot: false
cleanmgr_sagerun: "0001"cleanmgr_active_setup_temp_folders: false
cleanmgr_branchcache: false
cleanmgr_downloaded_program_files: true
cleanmgr_install_path: C:/Windows/System32/cleanmgr.exe
cleanmgr_internet_cache_files: true
cleanmgr_memory_dump_files: false
cleanmgr_old_chkdsk_files: false
cleanmgr_previous_installations: false
cleanmgr_recycle_bin: false
cleanmgr_service_pack_cleanup: false
cleanmgr_setup_log_files: false
cleanmgr_system_error_memory_dump_files: false
cleanmgr_system_error_minidump_files: false
cleanmgr_temporary_files: false
cleanmgr_temporary_setup_files: false
cleanmgr_thumbnail_cache: false
cleanmgr_upgrade_discarded_files: false
cleanmgr_user_file_versions: false
cleanmgr_windows_defender: false
cleanmgr_windows_error_reporting_archive_files: false
cleanmgr_windows_error_reporting_queue_files: false
cleanmgr_windows_error_reporting_system_archive_files: false
cleanmgr_windows_error_reporting_system_queue_files: false
cleanmgr_windows_esd_installation_files: false
cleanmgr_update_cleanup: true
cleanmgr_windows_upgrade_log_files: falseExample Playbook
----------------- hosts: servers
roles:
- { role: deekayen.cleanmgr, cleanmgr_install_reboot: false }Requirements
------------Windows 2012R2+. Executing cleanmgr.exe by Powershell over winrm on Windows 2008 doesn't seem to work well.
Dependencies
------------None.
License
-------BSD