This topic applies to Profile Management 3.1 and later.
The two procedures, mirroring folders and deleting stale cookies, are related. If you manage the Internet Explorer Cookies folder, use both procedures. This ensures transactional integrity while also reducing profile bloat involving Index.dat and browser cookies.
Mirroring can also be applied more widely because it can help solve similar issues involving any transactional folder (also known as a referential folder), that is a folder containing interdependent files, where one file references others. Mirroring folders allows Profile Management to process a transactional folder and its contents as a single entity, thereby avoiding profile bloat.
For example, consider how Index.dat references cookies while a user browses the Internet. If a user has two Internet Explorer sessions, each on a different server, and they visit different sites in each session, cookies from each site are added to the appropriate server. When the user logs off from the first session (or in the middle of a session, if the active write back feature is configured), the cookies from the second session should replace those from the first session. However, instead they are merged, and the references to the cookies in Index.dat become out of date. Further browsing in new sessions results in repeated merging and a bloated cookie folder.
Mirroring the cookie folder solves the issue by overwriting the cookies with those from the last session each time the user logs off so Index.dat stays up to date.
The cookie folder can become bloated not only when multiple sessions are involved but also when Web sites are revisited and stale cookies build up. The second procedure in this topic solves the latter issue by removing the stale cookies from all profiles.