"Does not work", his term, which means the files show up on the gui as
being in the default management class.

The new management class does not show up in "Q inclexcl".

The new management class shows up on the active policy set.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Thursday, November 29, 2007 2:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] INCLUDE for new management class

On Nov 29, 2007, at 3:23 PM, Fred Johanson wrote:

> Our desktop support unit has a user that wants a new retention
> policy on
> their file share.  The admin added this to the dsm.opt:
>
> INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
> Office\*"
> LONGADMIN
> INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
> Office\*.*" LONGADMIN
>
> I can't see anything syntactically wrong, but it does not work.  He's
> also tried 'f:...' with no effect.  He says that he's restarted the
> service after each change.
>
> Can anyone see his error?
>

Fred -

What are the details of "does not work"?
Are any problems/conflicts reported by 'dsmc q inclexcl'?
Has the Policy Set been activated with that Managment Class?

    Richard Sims