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

forcing new home directory name?

Hi,

We've recently been using IDM to manage our users based on a DB that contains a user's legal name and in turn, will properly rename that user based on those criteria.

The problem is, and seems to always happen; that if you forget to rename their home directory as well, it goes unnoticed and ends up causing me a couple headaches when validating users and their home directories.

I had a user recently who had their login as 'Chantal' but her legal name was 'Shauntelle', therefore the home directory did not gain the new name.

Does NSM have the capability to automatically rename those directory once a change is made into eDir?

I tried the 'enforce path' management action, but nothing happens and the 'consistency check' comes back as valid (i.e. the DS path exists just as the actual directory/file path)

Also, looking under management actions, and under the 'Name Mismatch' tab, I don't see that user but I do see several users that actually don't have this issue any longer. How can I clear this and get a new list of name mismatches to work with?

Thanks for any help with this.
  • 0
    On 8/28/2014 3:46 PM, beaujona wrote:
    >
    > Hi,
    >
    > We've recently been using IDM to manage our users based on a DB that
    > contains a user's legal name and in turn, will properly rename that user
    > based on those criteria.
    >
    > The problem is, and seems to always happen; that if you forget to rename
    > their home directory as well, it goes unnoticed and ends up causing me a
    > couple headaches when validating users and their home directories.
    >
    > I had a user recently who had their login as 'Chantal' but her legal
    > name was 'Shauntelle', therefore the home directory did not gain the new
    > name.
    >
    > Does NSM have the capability to automatically rename those directory
    > once a change is made into eDir?
    >
    > I tried the 'enforce path' management action, but nothing happens and
    > the 'consistency check' comes back as valid (i.e. the DS path exists
    > just as the actual directory/file path)
    >
    > Also, looking under management actions, and under the 'Name Mismatch'
    > tab, I don't see that user but I do see several users that actually
    > don't have this issue any longer. How can I clear this and get a new
    > list of name mismatches to work with?
    >
    > Thanks for any help with this.
    >
    >

    beaujona,

    NSM does have the ability to rename user home folders. However, the only
    attribute it uses for naming home folders is the CN. First name and last
    name attributes are irrelevant for home folder naming purposes. For
    example, if Bob Smith (cn=bsmith.ou=users.o=org) were renamed to Robert
    Smith, but their eDirectory object's name was unchanged (still
    cn=bsmith.ou=users.o=org), the home folder (\\server\vol\bsmith)
    wouldn't be renamed. If their eDirectory object FDN were renamed to
    rsmith.users.org, however, the home folder would be renamed.

    The "Name Mismatch" report is based of GSR Collector data. Re-run the
    GSR Collector, and verify that your name mismatches show up correctly there.

    -- NFMS Support Team
  • 0 in reply to 
    I ended up creating a "dummy" policy that moves the folder to another directory, and then remove that user's association; but I don't know if there is an easy way to manage the 100 or so users that have had this issue.

    We base our home directories on the CN, obviously, but I was hoping that a CN change would make an appropriate change in NSM

    Thanks for the confirmation
  • 0 in reply to 
    beaujona wrote:

    > We base our home directories on the CN, obviously, but I was hoping
    > that a CN change would make an appropriate change in NSM


    As noted in the post by NFMS Support Team, a change to the CN *should*
    trigger a rename of the home directory. If that's not hapenning then
    you've got an issue going on.

    --
    Your world is on the move. http://www.novell.com/mobility/
    BrainShare 2014 is coming. http://www.novell.com/brainshare/