Tag Info

New answers tagged

0

The minimal architecture I usually recommend is 2 servers: one for SQL and one for SP (hosting all SP roles). For 30 users, a single "all-in-one" server would be enough in terms of performances (by far), but a two-servers architecture is much more clean if you can afford it.


0

In SharePoint 2010 you don't have this option "adding external user". but you have couple of options. simply add him into the active directory and grant him access. AD LDS is a feature of Windows Server. While AD LDS itself is free, remember that your external users must have both Windows and SharePoint CALs. check this ...


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 ...


0

its depend upon the tools, usually if you migrate the users using the tools and then migrate the content it works like a charm. we did the same thing with sharegate for small set of user and no issue at all. Update: I used tsunami tool to migrated from non sharepoint to cloud. In that project we migrate content then mapped the user...that help us in ...


0

A different approach would be to enrich the SharePoint user profiles with additional data from your HR system using a custom BCS connector. Here is an article describing that for SharePoint 2010: ...


0

I beleive you are building the People Directory from the peopleresults.aspx using Search results webpart. The search results are rendered via display templates (SharePoint 2013 and Office 365), these display templates can be customized to inject/hide or data. In your case, make a copy of display template under Site Settings ->Master Pages and Page Layouts ...


0

Here's something to start with in C#: $lists = $ctx.Web.Lists $ctx.Load($Lists) $ctx.ExecuteQuery() foreach($list in $lists) { $ras = $list.RoleAssignments $ctx.Load($ras) $ctx.ExecuteQuery() foreach($ra in $ras) { $ctx.Load($ra) $ctx.ExecuteQuery() if ($ra.PrincipalId -eq $everoneUserId) { ...


0

I would suggest you do the following in that order: You might find more information by checking timer job history under Monitoring in Central Administration. Check ULS logs. Stop-Start User Profile/Synchronization Service. Reprovision User Profile Service via PowerShell. If that doesn't help and you don't find the cause of the issue, you could recreate ...


0

I got the solution with the help of this link here is the complete method function getInformation(userEmailId) { var url = _spPageContextInfo.siteAbsoluteUrl + "/_api/SP.UserProfiles.PeopleManager/GetPropertiesFor(accountName=@v)?@v='i:0%23.f|membership|" + userEmailId + "'"; $.ajax({ url: url, method: "GET", async: false, ...



Top 50 recent answers are included