This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Association Removals

All,

We have NSM 3.1 and I'm curious about if there are ways to affect the behavior of when an association is removed from a policy. In this particular case, an OU was accidentally added into a policy and home directories were built. However, these users don't need home directories, but when I remove the association it doesn't vault or delete the home directory, it just leaves at is and becomes unmanaged by NSM.

Any thoughts around this or is this simply working as designed?

Thanks for any help!
  • 0
    On 8/13/2015 3:26 PM, e110019 wrote:
    >
    > All,
    >
    > We have NSM 3.1 and I'm curious about if there are ways to affect the
    > behavior of when an association is removed from a policy. In this
    > particular case, an OU was accidentally added into a policy and home
    > directories were built. However, these users don't need home
    > directories, but when I remove the association it doesn't vault or
    > delete the home directory, it just leaves at is and becomes unmanaged by
    > NSM.
    >
    > Any thoughts around this or is this simply working as designed?
    >
    > Thanks for any help!
    >
    >


    This is working as designed. In fact, these users aren't actually
    "unmanaged" by NSM. NSM doesn't have a policy for that OU anymore, but
    those users who were originally managed by NSM still have managed paths
    in the NSM database. NSM may still take action on these managed users if
    they are moved, though other events may be ignored.

    This can be remediated easily enough, however, with the "Remove from
    Database" management action. If you want to clear their home folder
    attribute, the "Clear Managed Path Attribute" management action
    (introduced in NSM 4) would be your best bet.

    -- NFMS Support Team