I'm not saying that there is no problem with current EEM, but why on earth, would you want superadmin accounts to be a part of installation set?
That user is stored on a token which is in the safe together with the token password and is used for worst case recovery purposes only.
1 of 1 people found this helpful
Use lover level account (that is still many levels higher than users and regular support accounts) and assign that (if you have to). Level 32 should not be used or assigned anywhere (except database itself).
I suspect there has been a change in the EEM to prevent the admin being assigned in this manner somewhere in the past.
Would be great if anyone could confirm this.
I guess we'll have to switch to a level 31 admin for now, then.
Thank you for your reply, Peter.
it's simple - you don't have enough rights. You can't create an install set which contains someone with higher rights than you do.
Ok, that's confirmation enough.