Security Role Name Changes when imported from AD Post-8.7 Upgrade
search cancel

Security Role Name Changes when imported from AD Post-8.7 Upgrade

book

Article ID: 263769

calendar_today

Updated On:

Products

IT Management Suite Client Management Suite

Issue/Introduction

We upgraded our new Altiris environment from 8.6 RU3 to 8.7, and now when we look at the list of roles, the domain imported ones are no longer prefixed with the domain they were imported from.

For example, before the upgrade, we had two roles:

  • R###\U_###_ROY_PolicyAdmin (imported from Active Directory from our R### domain)
  • U_###_Roy_PolicyAdmin (internal role to the console).

To keep console permissions from getting clobbered, Active Directory side, should any sync issues ever occur, we configured our desired technician's permissions using the internal U_###_ROY_PolicyAdmin role, and then we added the Active Directory imported role as a member of this internal role.

This was working great, however after upgrading to 8.7, it seems the Active Directory imported roles stripped the RADS\ prefix off, so it's confusing to tell at a glance which role is imported from Active Directory vs which one is the internal role.

Actual permissions still work as expected so this appears to be more of a visual bug/oversight, but is there a reason the domain isn't included/listed in imported Active Directory roles anymore? I can work around this with a description, as I can still figure them out based on the role memberships, but it just makes it harder to see at a glance.

Environment

8.7

Resolution

We changed the way we create User Groups when imported from AD in 8.7.  In previous versions we would bring in the Domain name and now we just bring in the Group Name. 

Possible Workarounds:

  • Bring in the group as an OU, and then the Imported Group name can be Customized in the Console.
  • Update the name in AD