Having a roaming profile save time for users who hot-desk. However, a roaming profile can cause confusion and slow logon when misused. The killer reason to delete roaming profiles is where you have a 'Kiosk' machine with mainly one-off users. What can happen is that the disk fills up with roaming profiles that will never be used again.
Other scenarios where deleting roaming profiles helps are, if you get calls to the helpdesk about broken shortcuts, or error messages saying: 'Roaming profile cannot be found.'
♦
The key question with tweaking the registry setting to delete roaming profiles is: 'Where does the cache get deleted? On the server or the Windows 7 computer?' The answer is on the machine where you set the value, DeleteRoamingCache=1.
Here is a classic case of checking that your logic matches the registry's; in this instance, a value of 1 means: no roaming caches gets saved. To be doubly clear, 1 means that all roaming profiles get deleted on that computer
On the other hand, changing to DeleteRoamingCache=0, would be a double negative, (don't delete), therefore you would end up with roaming profiles!
This registry dword, DeleteRoamingCache, controls whether or not, the local computer saves a copy of a user's roaming profile when users logoff.
Roaming profiles are stored on a server. However, by default, when a user with a roaming profile logsoff, the system saves an additional copy of their profile on the local hard drive. This scheme was designed to give roaming users faster logon, especially when network traffic was busy.
The incentive to change the default behaviour occurs when lots of roaming users logon to one 'kiosk' machine. As a result, the disk fills up with profiles, and if it's unlikely they will ever logon again, you may as well make a registry tweak which deletes these unwanted roaming profiles.
SolarWinds' Orion performance monitor will help you discover what's happening on your network. This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.
Perhaps the NPM's best feature is the way it suggests solutions to network problems. Its second best feature is the ability to monitor the health of individual VMware virtual machines. If you are interested in troubleshooting, and creating network maps, then I recommend that you try NPM now.
Download a fully functional free trial of the Network Performance Monitor.
This DeleteRoamingCache registry tweak works in Windows NT 4.0 and Windows 2000. However, it does not seem delete the roaming profile cache in XP, Vista or Windows 7.
My advice is to abandon the registry and check your Group Policies, look for:
Delete cached copies of roaming profiles
Here is an alternative location for DeleteRoamingCache
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System
While it worked in Windows 2000, again creating a delete roaming profile value in the registry seems to have no effect in XP, Vista or Windows 7.
** HKLM is an abbreviation of HKEY_LOCAL_MACHINE, and HKCU is shorthand for HKEY_CURRENT_USER. These acronyms are so well-known that you can even use them in .reg files; Vista will understand and obey the registry instruction.
Creating a .Reg File
This page explains how to create, and then edit .reg files for your computer. As it's easy to import the contents of a .reg file into the registry, do take extra care with procedures. Example DeleteRoamingCache .reg file.
This registry tweak had its hey day in Windows 2000. While you can still add DeleteRoamingCache to the registry in Windows 7 it does not seem to have the desired effect of deleting roaming profiles.