(This will hopefully be the first of many Group Policy Setting of the Week (or GPSW) articles where I will showcase one policy setting and what it does.)
I just read about this cool new policy setting on the “Ask the Performance Team” blog that will help address the issues of computers hard drives filling up over time with multiple user profiles. Previously you either had the option to purge the local users profile on log off or keep a cached copy of the profile forever. Either users would have to download their profile every time they logon to the computer which could greatly slow down the logon process or their cached profiles was never deleted which resulted in the system drive running out of space. This new setting “Delete user profiles older than a specified number of days on system restart” allows you to set a timer on the local cached profiles so that they will be purged X number of days after being used. This means users who commonly logon to a particular computer will still have their profile cached but users that logon seldomly will have their files cleaned up thus saving precious disk space.
This might sound like a great setting to implement on a Terminal Server however note the clean up wont happen until the server is rebooted. This restriction should not be so bad as Terminal Servers are probably rebooted at least once a month any way for patching (you do patch your terminal servers don’t you?).
This setting can be found under Computer Configuration \ Policies \ Administrative Templates \ System \ User Profiles
5 thoughts on “Group Policy Setting of the Week 1 – How to remove old user profiles after X days”
According to the accompanied text; If you enable this policy setting, the User Profile Service will automatically delete on the next system restart all user profiles on the computer that have not been used within the specified number of day.
I’m worried that this does apply to all profiles including local?
Also keep in mind that (untested) theoretically this policy will ‘conflict’ in a way with https://www.grouppolicy.biz/2010/03/setting-of-the-week-19-set-roaming-profile-path-for-all-users-logging-onto-this-computer/
This because a local profile will become ‘roaming’ and therefore subject to deletion. Again, this is not tested by myself but I noticed that a local profile became roaming.
Very great post. I simply stumbled upon your weblog and wished to mention that I’ve truly enjoyed browsing your weblog posts.
After all I will be subscribing to your rss feed and I am hoping you write again soon!
Look into my webpage :: webpage (Letha)
Is there any way to exclude a profile from being deleted?
Our Shoretel phone system application has to be reinstalled everytime the local administrator (the account used to install) profile is deleted.