0 votes

When the UPN being created is the same as an existing one except for the case. For instance, the new UPN is sally.fields but there's an existing Sally.Fields. The script does not recognize these as being equal so it allows the UPN to be stored as sally.fields but then fails to create the AD account indicating that the UPN is not unique forestwide.

by (820 points)
0

Hello,

As per our check, the script works as intended and takes into account such cases. Please, post here or send us (support@adaxes.com) in TXT format the script you are using. Also, please, provide all the possible details about the workflow where the script is executed. Screenshots of the corresponding business rules will be much appreciated.

0

I think I may have figured out the answer... The existing account is in a different domain that is not included in the Activity Scope of the business rule (Before creating a user). This would explain why it doesn't find the duplicate UPN. We need to leave the activity scope as is because we can't create accounts in the other domain. I'm okay with closing out this question.

Please log in or register to answer this question.

Related questions

0 votes
1 answer

Or is there another solution to solve this?

asked Sep 15, 2022 by boris (300 points)
0 votes
1 answer

Thanks for the info. I'm now grabbing the %adm-ManagerUserName% value, but need to remove the final 21 characters of it so it contains only their username and not our ... this in the PowerShell Script Editor for my business rule, I get the following error:

asked Mar 11, 2021 by mkvidera (60 points)
0 votes
1 answer

I want to make a custom field in which you can select a person from the active directory, is this possible? For example, as in the field manager

asked Nov 18, 2022 by Alvares (80 points)
0 votes
1 answer

Can you clarify the answer as it's a bit confusing? Will there be new major release available this month?

asked Nov 17, 2022 by ColinB (180 points)
2,931 questions
2,647 answers
6,860 comments
157,452 users