Asked by:
hide i:0#.w from user name sharepoint 2013

Question
-
We had migrated our portal from Sharepoint 2010 to Sharepoint 2013. The user profile service is configured and user profile synchronization service is running correctly and all of the valid user profiles are fetched from AD and updated in SharePoint server.
However, when I go to site permission of our web application the display names are showing correctly but the login name are showing with claim based tokens ("i:0#w|<domainname>\<username>". Please see below snapshot taken from site permission page for few users:
I need to know if we can somehow hide the special characters and display only <domainname>\<username>.
Regards,
Waliullah
Saturday, January 21, 2017 9:27 AM
All replies
-
This might be due to the fact you went from 2010 to 2013 which is claims based.
Can you confirm the accounts have a name or display name (forget which one) populated in AD and in the profile sync?
If this is helpful please mark it so. Also if this solved your problem mark as answer.
- Edited by taylor.l Saturday, January 21, 2017 6:59 PM
Saturday, January 21, 2017 6:56 PM -
Yes, I migrated from 2010 to 2013.
These accounts have display name in the AD and these are properly showing in user profile. e.g. for Sharepoint1 account,
- Account Name: <domainname>\Sharepoint1
- Display Name: Sharepoint1
Regards,
Waliullah Bukhari
Monday, January 23, 2017 4:40 AM -
Hi,
Please check if the user profile service application is connected to this problematical web application: Access CA > Application Management > Manage web applications > highlight web application > click Service Connections and check if the user profile service application is checked.
Thanks,
Dean Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.comMonday, January 23, 2017 10:16 AM -
Hi Dean,
Yes, I confirmed that User profile service is marked checked in the service connections.
Regards,
Waliullah Bukhari
Monday, January 23, 2017 12:54 PM -
Hi
please check this solution
Romeo Donca, Orange Romania (MCSE, MCITP, CCNA) Please Mark As Answer if my post solves your problem or Vote As Helpful if the post has been helpful for you.
Monday, January 23, 2017 3:01 PM -
This has nothing to do with AD. You need to clean up the DisplayName property for each one of these users stored in SharePoint. Use PowerShell. See this reference for details: SharePoint 2013: PowerShell automation of user and group reconfigurations.Monday, January 23, 2017 5:25 PM
-
I have also run the clean up script for Display Name property as mentioned in the above link. However, the system is still showing display name as e.g.
- Sharepoint1 (i:0#w|<domainname>\sharepoint1)
- Waliullah Bukhari (i:0#w|<domainname>\wbukhari)
Even, if I remove the user and add again it shows in the same way. I need to know if this is a default behavior for any migrated site from Sharepoint 2010 to Sharepoint 2013.
Regards,
Waliullah Bukhari
Wednesday, January 25, 2017 7:10 AM -
Hi,
It seems that the issue is caused that SharePoint assumes all users to be claim users and renders them so. Therefore, a normal windows user – “Domain\UserName” appears as “i:0#.w|Domain\UserName”.
You need to converted SharePoint 2010 to claims format before migrating to SharePoint 2013.
Try to run the following command:
$WebApp = Get-SPWebApplication "WebAppURL"
Convert-SPWebApplication -Identity $WebApp -To Claims –RetainPermissions -Verbose
$WebApp.MigrateUsers($true)
Detailed explanation for your reference:
http://www.winwire.com/access-denied-error-after-migrating-to-sharepoint-2013/
Thanks,
Dean Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- Proposed as answer by Victoria Xia Tuesday, January 31, 2017 1:11 PM
Wednesday, January 25, 2017 1:13 PM -
Hi Waliullah,
You got any option to hide these extra character from the Display name\login name.
Regards,
Venkat
Wednesday, May 8, 2019 11:51 AM -
Hi,
I did the same, still the issue is same.
Regards,
Venkat
Wednesday, May 8, 2019 11:53 AM