Freigeben über

Renaming your Default Management Pack

  • Artikel

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    January 01, 2003
    @Rob - keep your eyes peeled.  I think you will be happy.

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    @Brian - yes - you can easily rename ANY unsealed MP easily in the console.. as that only modifies the displayname of the MP - it does not change the ID of the MP or any of the workflows.

  • Anonymous
    February 15, 2011
    Thanks. Very Informative...

  • Anonymous
    February 15, 2011
    Great tip!

  • Anonymous
    February 15, 2011
    Good idea! Thank you!

  • Anonymous
    February 16, 2011
    Great tip to the right time! Thank's, Kevin!

  • Anonymous
    February 16, 2011
    Now get rid of the "disable" rule which automatically saves to the default and we'd really be happy (i'm hoping this is picked up in vnext), As VincentK points out it's still being selected as default and if you're not careful you just press the save button, but at least it's hopefully another trigger to select a different mp.

  • Anonymous
    February 16, 2011
    Yes, a very good suggestion indeed.  Thanks for passing this tip along!

  • Anonymous
    February 16, 2011
    Never even thought of that approach Kevin. I've simply created customized MPs for all other imported/created MPs - great WARNING suggestion for the eyes before clicking the mouse.

  • Anonymous
    February 17, 2011
    Good Idea! Thanks Kevin.

  • Anonymous
    April 13, 2011
    So I have to ask this question, can you just rename any of the custom management packs or do you need to delete and do a clean creation with the proper naming convention?  I'm asking this because we just had a reorg and they want the naming convention to fit the newly named groups.