Cookies Size on Disk

[Mikey]

Hi,

 

We've got a roaming profile setup, that works OK up to a point. This point is generally where cookies take over and destroy it!

When the profile begins to take an age to logon it's 9 times out of 10 because the cookies "size on disk" is about 30 meg, even though the actual size is only 1MB!

 

How do you deal with this kind of issue, or is anyone aware of why it might be happening?? Any ideas for best practices will be greatly received!

 

Many thanks, and this is a phenomenal site!

 

Mike

[ChrisH]

Id be tempted to delete them on log off if there isnt a GP that can control it.

[Mikey]

Yeah, a little logoff script is my current thinking - ooh it'll be fun upsetting people with that one! They hate surprises!

[RobC]

Well, I can tell you why the "Size On Disk" is about 30 times larger than the actual file sizes - Cluster Size. Each cookie is a 1kb file, while the smallest cluster size is a lot larger than 1kb, so for each cookie stored it is wasting quite a bit of space & thus increasing the "Size On Disk" value.

 

And now I bet you wish that you'd never asked...

[Mikey]

Aha, now that bit I knew.... the question is BUT WHY!!?

lol!

 

I've decided to throw this VB script found from the Hey, Scripting Guy! site on M$ as a logoff script...

 

Const COOKIES = &H21&

 

Set objShell = CreateObject("Shell.Application")

Set objFolder = objShell.Namespace(COOKIES)

Set objFolderItem = objFolder.Self

strPath = objFolderItem.Path & "\*.*"

 

Set objFSO = CreateObject("Scripting.FileSystemObject")

objFSO.DeleteFile(strPath)

 

 

So what if they can't save their turned off Google Images SafeSearch - they shouldn't be doing that anyways!!

 

This'll really sort out our major profile problems.

 

Thanks for your input...

I'd be interested to know if anybody does anything different or do you just stick with the 'let live' scenario - or even the mandatory route. We tried it, but it just upset those used to the roaming.

[Dos_Box]

Roaming sucks (my opinion). The debates we've had here in the past about roaming vs mandatory vs local profiles have almost led to all out civil war. If you are having problems with roaming profiles then it may be time to tell your users straight.

[E1uSiV3]

the NTFS default cluster size is 4K, an average cookie is probably only hundreds of bytes in size (anything greater than 0 but less than 1024 bytes appears as 1k in explorer, to see the real size you can right click -> properties it), therefore the massive difference in size.

[Mikey]

I'm not a huge fan of the Roaming (Mandatory all the way if you ask me!), but I think if setup properly, and controlled, it can be a real success.

We've only ever had roaming for staff, with a mandatory for the kiddies. But now we've managed to successfully knock out any major cracks, we're tempted to give the kids roaming. Dangerous stuff at this place!

[john]

I LOVE Manadatory Profiles, they are ACE!