hey have you had any updates on this
I have a Sharepoint 2019 with the same issue
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi, I already described this problem in another microsoft community and they suggest me to ask for this problem in this community. Follows a description of the problem.
So the problem not seems due to exclusively Azure DevOps 2019 but rather to an incompatibility between:
Is the problem due to an incompatibility of schema level of domains A and B? If yes, now we cannot upgrade schema level of domains A, C, D and E because there are many critical applications that currently runs in these domains. So I hope that changing 3) point above as follows will resolve the problem
3') windows server 2012 r2 in which we will install Azure DevOps Server 2019 in domain A
Could you please confirm that incompatibility above described is the problem? Furthermore will 3') resolve the problem?
hey have you had any updates on this
I have a Sharepoint 2019 with the same issue
I apologize for my late reply.
I got the official microsoft support involved, as soon as we get the results I will share them on this forum.
Hi,
If you want add a user from another domain in one of local group of one of your member server , you should avoid to add it directly. Try to use a domain group with local domain as scope
Did you try use a ad a group instead of a user ?
Try to create a new group in same domain with the Local domain as scope to accept member from another domain, then add it in the local group in the member server .
Hello SCLANOFRANCESCO-5839,
I am sorry for the late reply.
Based on my research, we can check if ther are duplicated machine SID in your domain A or domain B with the tools below (the tools are mentioned in the following similar cases).
PsGetSid v1.45
https://learn.microsoft.com/zh-cn/sysinternals/downloads/psgetsid
Here are two similar case for your reference.
A member could not be added to or removed from the local group because the member does not exist.
https://social.technet.microsoft.com/Forums/windows/en-US/0c5222c7-7990-439b-93e3-9bc69d652588/a-member-could-not-be-added-to-or-removed-from-the-local-group-because-the-member-does-not-exist?forum=winserverDS
AD Connect Setup: A member could not be added to or removed from the local group because the member does not exist
https://learn.microsoft.com/en-us/answers/questions/40034/ad-connect-setup-a-member-could-not-be-added-to-or.html
Best Regards,
Daisy Zhou
Hello Daisy,
sorry for the delay. I was busy with this problem but I didn't find a solution yet. Please involve also your colleagues to analyze the problem and help us find a solution as soon as possible, since this problem is critical for us.
I answer you below point by point:
1)
Bsed on the description, VM19 is a member server in domain A.
Yes, I confirm that VM19, like VM17, is a member server in domain A.
2)
Or do we want to add a domain B user in Local User and Group on one DC into Users group in Local Users and Groups on VM19?
If we mean it is a domain B user in Local Users and Groups on one DC, this user is not exist.
Because once a member server is promoted to a domain controller it will no longer have local accounts. I mean when you install Active Directory, it removes any local accounts.
I well know the fact the once a member server is promoted to a domain controller it will no longer have local account. I well know when I install Active Directory, it removes any local accounts.
3)
Based on the description "if I try to add a domain B user in the local group of users", do we want to add a domain B user in domain B (not local user on any DC) into Users group in Local Users and Groups on VM19?
If we mean it is a domain B user, we can check if this user is exist.
I mean I want to add a domain B user in domain B (not local user on any DC) into Users group in Local Users and Groups on VM19.
I checked that this user exist, I did this check with many users and all of them exist.
The problem is that I successfully added domain B user in vm17
but I unsuccessfully added domain B user in vm19.
So my upgrade from TFS 2017 to DevOps 2019 is blocked because in DevOps 2019 I'm not able to add all domain B users (they are more than 100) that already succesfully used TFS 2017 for many months (these users are pm, programmers, testers etc.) .
Let me try again to schemately explain my environment and my problem. I have 4 virtual machines:
A) vm17 – windows server 2012 r2 configured in domain A (this is the vm that runs Team Foundation Server 2017 update 1 on premises)
B) vm19 - windows server 2016 configured in domain A (this is the vm that runs Azure DevOps Server 2019 update 1.1 on premises
C) domain A - windows server 2012 r2
D) domain B - windows server 2016 – this domain is exclusively used to manage users of TFS 2017 and DevOps 2019
Domain A and domain B are in trust each other (bidirectional, not transitive). Trust properly works.
Is the problem due to an incompatibility of schema level of domains A and B? If yes, now we cannot upgrade schema level of domains A because there are many critical applications that currently runs in this domain. So I hope that changing B) point above in B') as follows will resolve the problem
B') vm19 - windows server 2012 r2 configured in domain A (this is the vm that runs Azure DevOps Server 2019 update 1.1 on premises
Could you please confirm that incompatibility above described is the problem? Furthermore will B') resolve the problem? Otherwise, what could be the cause of the problem and its solution?