• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 68 subscribers
  • Views 88 views
  • Users 0 members are here
Options
Related

Is the username generation button broken in 8.5?

charleneforbes

Hi,

Since we updated to 8.5 the mmc console doesn't show the username generation button, has anyone else seen this?  The web console still has it, and it works, but the mmc console doesn't.  I've recreated the rule and that hasn't helped, and when I create it there's a message in the General tab of the policy saying "Provisioning policy failure. The 'User Logon Name Generation' policy encountered an error."

Has anyone else found this?

  • 0

    Hi Charlene,

    That message on the policy's General tab — "Provisioning policy failure. The 'User Logon Name Generation' policy encountered an error." — is the key here. The Generate button next to the User logon name field only appears when the MMC Console can successfully load and evaluate that policy. Since the console can't evaluate it, it doesn't render the button. The Web Interface uses a different code path, which is why it still works there.

    A few things worth checking before assuming it's a product bug:

    1. Console vs. Service version. After an upgrade this is the most common cause — the MMC Console is often left on the older build while the Administration Service is on 8.5. Check the version in the Console's Help → About and compare it to the Administration Service version; they should match. If the console wasn't upgraded, reinstall/upgrade it to 8.5.
    2. The actual exception. The General-tab message is just the surface. Look in the Application event log on the Administration Service server (source: ARAdminService) at the moment you open the policy — that entry will contain the real error (e.g. a missing attribute, a script error, or a migration issue). That's what determines whether this is a config problem or a genuine defect.
    3. Rule/attribute migration. If the generation rule references a script or a virtual/custom attribute, it's worth confirming that attribute still exists and resolves after the upgrade. Recreating the rule (which you've already tried) won't help if the underlying dependency is missing.

    If you can share the exact error from the Application event log (or the full text from the policy's General tab), it'll be much easier to pin down whether this is environmental/migration-related or something that needs to be raised with Support.

    Thanks,

    Aron