I'm doing some research into retention strategies on SP2010.
As it stands there seems to be enough functionality here to do what we would like to on our intranet of approx. 1700 users across 40 sites on one SC. We're pretty keen on keeping server space to a minimum (part of a silly contract we're part of), so I've planned on creating retention strategies for all document libraries/pages that kicks in after 4 months prompting the user to 'touch' their file/page to refresh it's modified date... otherwise it gets deleted.
Now, here's my irking issue: Should I just create a site-wide (from the very top) strategy on all desired content types, or should I use retention specifically on each library of interest?
The former seems much easier... just set the thing up once and basically walk away, however the latter puts my mind at ease (despite the initial config time) and I'm afraid of having an otherwise broad policy across the whole site maybe deleting things inadvertently.
Any thoughts or comments are very welcome!
Many thanks! :)
-- EDIT ---
When trying to add retention to the Document content type, I run into odd hindrances.
Top Site -> Site Actions -> Site Settings -> Galleries (Site Content Types) -> Document Content Types (click: Document) -> Information management policy settings -> checkbox: Enable Retention -> Add retention stage.
I get this message (error?): An expiration schedule set on the Document or Item content type cannot be based off of a system generated property such as Date Created or Date Modified. To use a system generated property, create a new content type that is derived from the Document or Item content types
Any idea what may be causing this? I don't really want to create a sub-content type just to do retention (and go through the nightmare, if it's even possible, to respec all those Document content types).