Hello Leo_0601,
Thank you for posting in Microsoft Community forum.
It seems the specific display issue about this object occurs, we can try to troubleshoot it instead of converting the SID to the original display name.
1.Please confirm how many DCs are there in your domain?
2.Is this SID occur on all the DCs (if you have more than one DCs in the same domain) or only one DC?
You can try to check:
The first thing:
1.Connect to configuration as below.
2.Open ADSI Edit and right click it and select "Connect to".
3.Selcet "Configuration" under "Select a well know Naming Context".
4.It will display like this.
The second thing:
1.You can try to close the ADSI edit windows and reopen it.
2.Right click this Configuration partition and remove it.
3.Connect this Configuration partition you want again to see if the SID disappear.
The third thing:
1.Connect to other partition (such as Schema partition) to see if it is normal.
Best Regards,
Daisy Zhou
@Daisy Zhou
Hi Zhou
First I would like to thank you for your brief explanation. Means a lot.
Its an AD LDS instance. We have faced an issue with AD LDS in our setup earlier. Then we raised a case with Microsoft.
Then they suggested to add one service account (carestream user) to local server (Not in domain) to fix this issue. We tried the same whatever Microsoft suggested. It started working fine. We dont have multiple domain. We dont have any problem with domain. All working fine, Below solution was suggested by microsoft.
In member server:
-> ADSI edit
-> Configuration[localhost 3890]
-> CN=Roles
-> CN=Administrators
-> Right Click -> Properties (CN=Administrators)
-> Member -> Edit
-> Add Windows Account
-> Search the account (Carestream user) & Add it if the account not exists.
Actually now we have to just add the existing windows account (Carestream user) in ADSI through powershell, since we are getting SID or GUID we dont have any idea how to convert and automate.
Below the code we are trying out. But no luck. If you help us to do the same via powershell. It means a lot and so much helpful for us.
Kindly reply me.
I am looking forward to hear from you.
Get-ADObject "CN=Administrators,CN=Roles,CN=Configuration" -Properties member |Set-ADObject -add @{member="$((get-aduser CarestreamUser).distinguishedname)"}
-