UCCE - Multidomain

[CoDeC]

Hello,

our current ucce deployment is on Domain A. Our company move all users to a new domain B.

we don't have been impacted until we have tried to create (or move an agent role to) Supervisors.

we got the following error.

after check the staging guide, if I am not wrong seem that it is not supported, is it correct? are there some solution for our case? 

thanks by advance.

we have UCCE 12.5(1).

[bill.king1]

Hi, you mentioned old users as well as new. Do you get the error above for when you promote existing agents to supervisors? Does it also happen when you try and create a new agent/supervisor?
Can you share a screenshot of how the user looks in UCCE config manager as well as the AD entry?

[CoDeC]

hi,

the migration of the user to new domain, had a change of their samaccountname too. we move from "first_name.last_name" to "random letters/numbers".

So, doesn't matter new users or existing agents, the login name is different in the old domain. 

regards,

[bill.king1]

Right, but the question is, is the issue you're having with the error message happening for all users you're trying to make supervisors? Or only the new ones/only the old ones? And you verified that the account names match what you're trying to use in AD for instance?

[CoDeC]

hi,

yes, same error for all users that I try to make them supervisors. yes, the account names match with the value typed in LoginName field.

regards,

[bill.king1]

And your agent is say login abc1234 but the supervisor login you're trying to update them to is abc1234@xyz.com?
There are a couple defects somewhat around what you're describing but not quite, like this https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvn33915 .
I imagine you'll need to open a TAC case, please let us know what the fix/issue was.

[CoDeC]

when I tried the UPN (samaccountname@domain) if got a different error:

yes, I guess that I need open a TAC case. thanks for your comments.

thanks.

[bill.king1]

If you look in AD here, do you see entries/text in both lines under User logon name? We've seen users not fully setup as an example in AD for whatever reason, and that could cause the issue your issue.
The red circle doesn't mean anything here, that's just an image from the Micrsoft website, but figured this way you had a visual re: what I meant.

[CoDeC]

Hi,

Yes, it is full correctly.

The new domain is a Single Domain. There is a trust relationship (AD Trust) between both domains (old and new one) but when I tried to add the new domain with Domain Manager tooI, I got the following error:

regards,

[bill.king1]

Ahh, so it isn't the user supervisor creation at all, you can't even run domain manager, OK that points to a larger problem.

Have you checked the requirements in the guide, like all the domains are in the same forest for instance, even if they are trusted?

[piyush aghera]

I think you're right Bill.. it seems like they have created a NEW domain, which is not part of the forest of existing one. Hence Domain Manager is still looking at the old domain and is not able to identify users from new domain which they are trying to promote to supervisor. I am not too sure, but it seems like a bigger problem and domain management was not handled well here.