Tag Info

New answers tagged

1

Use chrome and create multiple users In settings you can shift to a different user using top right menu every user login will be opened in a seperate window. Each window will have its own cache, saved passwords, bookmarks etc.


0

Remember the old "log in as different user" from SP2010? Well it's still there - just browse to <yourSharePoint>/_layouts/15/closeConnection.aspx?loginasanotheruser=true


1

Personally, I use 3 browsers for testing with different users, this is the best way I think, you don't need to install a small VM, that's too dear and long to do it. Chrome, Firefox, Safari, Opera and Maxthon is your friends. Easy to install and test, just enjoy it.


1

There's a bunch of options: You can easily open up to 6 browser sessions: IE, IE InPrivate, Chrome, Chome Incognito, Firefox, Firefox Private browsing (+ Opera or else if you want!). They all have their own session/authentication information, and you can log in with 6 different users. At the same time, if you're developping in SharePoint, you can test ...


2

RIGHT click on IE hold SHIFT and then RIGHT click again on IE LEFT click "Run as different user" login Repeat 1.- 4. for other users :)


0

I have worked on the same exact environment and based on my experience there is no need to migrate the users. but i would like to highlight some key points/topics that you need to take care of. you need add trust b/w the two domains on the target site collection specific to people picker to search across different forests/domains. pls refer the below link ...


0

The People picker is configured via STSADM.exe. You can set it up with a trust to an authentication provider. If you have multiple authentication providers (Forms Based Auth, Windows Auth, ADFS etc) and the people picker has been configured for all of them, you may find multiple accounts with the same names... Please have a look at the following article ...


3

There's only one account in AD but they end up being treated like two different user profiles within SharePoint. You're on the right track when you mention the claims prefix. Most likely, this site at one point used Classic authentication and was later changed to Claims authentication (or vice versa but moving a site 'backwards' from Claims to Classic ...


0

Choices are seperated in SharePoint using ;# instead of ;. Setting your default value to DOMAIN\account1;#DOMAIN\account2;#DOMAIN\account3 should allow you to set multiple default values. Alternatively there appears to be a solution posted on Technet (link) that may work. In case the link doesn't work in future here's the contents of that: Hi Thank you ...



Top 50 recent answers are included