Hot answers tagged

28

NTLM does only allow 1-hop solutions because it is transferring user credentials to the first server - in most cases it is IIS on your SharePoint Front End Server. If you want to get some data from a SharePoint server code (WebPart etc) and ask another server for data (it could be external back-end system you want to integrate to), you can't pass user ...


17

One thing is missing in this discussion that is asked in the question; the difference between NTLM and Kerberos. NTLM is a properitary AuthN protocol invented by Microsoft whereas Kerberos is a standard protocol. The big difference is how the two protocols handle the authentication: NTLM uses a three-way handshake between the client and server and ...


15

For you, the big reason is that it solves the "double hop" (delegation) problem, as mentioned in another answer. In addition, the Kerberos authentication mechanism starts to become more efficient as user session time increases, and reduces the load on the domain controller. This is because Kerberos is using an authentication ticket and not having to go back ...


7

The domain that needs to be isolated is only a DNS domain not a new AD domain. This is purely such that you have a separate IIS site where Cross Site Scripting is prevented by the browser. You can add that new domain in DNS (see Configure an environment for apps for SharePoint (SharePoint 2013)) or hosts file. The High trust app still needs the same ...


7

See http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/12/09/sp2010-search-query-load-balancing-explained-part-2.aspx (see the special note on SharePoint 2013) As per the article in SP2013 you can stop SQ&SS on 3 servers, and just leave it running on the server running on Query Processing Component. you can stop it using Manage services on ...


6

You need to use one of the following: Content Search Web Part Search Web Part Content Query Web Part The two search web parts are a bit easier to use as far as customizing the queries as there is a designer you can use. You can also change their looks. Content Query Web Part requires some XSLT knowledge to get the most out of it. You will add the ...


6

You need to rename your SharePoint server as well. Start -> Run.., cmd cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\" stsadm -o renameserver -oldservername VM_1 -newservername VM_2 iisreset Next, go to Central Administration site, System settings => Configure alternate access mappings, and change all the ...


5

Here's an example of when you need it and when you don't User >> SharePoint web page with SSRS report viewer via iFrame. NTLM lets user onto the page. User goes direct to SSRS via the iFrame and uses NTLM to authenticate there. Kerberos not required. User >> SharePoint web page with SSRS report viewer in Integrated Mode. User goes to SharePoint and ...


5

You need to edit the XSLT that is used to transform the search results. You can either do this by editing the in-line XSLT in the search results web part (in the edit part of the web part), or you can export the web part and configure it to use the XSLT files found in http:///Style Library/XSL Style Sheets/ Here you will find ItemStyle.xsl, Header.xsl and ...


5

I was looking for the same information, and just found the answer here. Here are the steps: Launch regedit.exe For MOSS 2007, navigate to: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS For Sharepoint 2010, navigate to: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS Check the ServerRole key Here are the valid ...


5

Separate web applications would get you totally separated sites on the same server. I don't believe there would be a method to share content easily between the web applications. I don't know enough about content migration/deployment to know if that would be viable. An klunky alternative would be to have another separate "shared" web application where any ...


5

You want to create Search Scopes. You can create them globally though the Shared Service Provider configuration or at the Site Collection level through Site Settings. Check out: http://msdn.microsoft.com/en-us/library/bb428856.aspx


5

The procedure described in these articles should work just fine. I've done this multiple times. You don't need to install the SQL Management or Client Tools on every SharePoint server. Just us the cliconfg.exe program to setup the alias. You can find more information on my blog at: http://thomasvochten.com/archive/2009/03/using-sql-aliases-with-sharepoint/ ...


4

You need to rename the servers you can do this via a script and then modify the topology see this previous answer You should use a separate AD but you can if you have access just use the same one if you aren't running updates TO AD otherwise make a new one. But create a new domain controller (You will want to do this before step 1) The same as you would a ...


4

You can specify the properties element in your feature.xml file, which can then be accessd from the feature receiver as indicated by Thomson. But this approach will land you to the problem of compiling your WSP again and again as you change the feature.xml properties. I would suggest you to maintain any configuration in a SharePoint list. Your feature once ...


4

Create the links using a "Content Editor Web Part" and assign "Target Audiences" to that web part. So that the links can be targeted to appear only to people who are members of a particular SharePoint group or audience. Reference Links: http://msdn.microsoft.com/en-us/library/ee906649(v=office.14).aspx ...


4

You have two options, either remove the ListUrl and let the Event Receiver fire for all the custom lists and inside your event through code check if the List is the one you want, then move on else ignore, something like: if (properties.ListTitle == "MyCustomList1" || properties.ListTitle == "MyCustomList2") { //your code } If you want to check ID of ...


4

I found the solution.. This is what I did - Navigate to Document Library -> Library Settings -> Advanced Settings -> and changed the 'Default open behavior for browser-enabled documents:' to 'Open in the client application'. and Excel sheets worked smooth :)! I tried the same issue on another server without enabling the excel services and all the other ...


3

Or alternatively, you could attach the event receiver to a Content Type, which you would create and use it as the basis for your 2 (or more) lists. You get more flexibility in the future as the only thing to is simply create a custom list and attach your content type. SharePoint will do the attaching for you, so even if you rename the list, it would still ...


3

Yes, SharePoint search shows documents with "PENDING" or "Draft" state, you have a workaround but it's only affects a specific list so if you need to remove results with "PENDING" or "Draft" versions on a specific list, you'll need to follow the next steps: Go to List Settings. Versioning Settings. In the bottom section choose "Only users who can edit ...


3

I had a similar situation on a client site when you entered the website via VPN or TMG that external content was loaded, causing a prompt per item. Close to 100 prompts at one point. I later found out it was due to HTTP / HTTPS indifferences. Like for instance external links to JavaScript or the sorts of like in master pages and iFrames. This was handled by ...


3

Register the service by selecting one of your Web Applications as per the example you provided above. After you have registered it for (in this case, for "Collab"), you should be able to verify that 2013 Workflows now work within SharePoint Designer 2013 for any site residing within the "Collab" Web Application. If you have other Web Applications where you ...


3

If you have the old db-server up and running, use the following command in PowerShell: Get-SPSite -ContentDatabase <SourceContentDb> | Move-SPSite -DestinationDatabase <DestinationContentDb> This command moves all site collections from the source content database to the destination content database. Reference: Move site collections ...


3

I apologize for this post, because this is opinion based only. Opinion based on experience, however, but nevertheless - opinion. I'd go down the path of giving All Authenticated Users read access instead of elevating to some administrator level. One problem with elevating to admin is that SharePoint "help"s your code to not be your admin but rather the ...


3

A variation would be to instead impersonate an account that are setup for this special use, with the needed permissions on the root web. But in this scenario I do not really see the problem with giving the users read access on the list. So I agree fully with @Benny Skogberg in this scenario, although noting that there are scenarios where elevating ...


3

There are to choices: install Active Directory on one of your SharePoint farm servers. It will be your separate AD forest Create SharePoint Application pool with classic authentication in PowerShell without the need to connect to AD: New-SPWebApplication -Name "Contoso Internet Site" -ApplicationPool "ContosoAppPool" -AuthenticationMethod "NTLM" ...


3

It sound's like the web applications get a timeout and does not get created correctly. I've had this problem in both production and staging environment, and changing the time-out has worked perfect both times. This is usually because you either have too many Web Applications in your SharePoint Server, or because your SharePoint Server is slow! As part ...


3

You could store the connection string in an SPPersistedObject which you could then modify via PowerShell. You can also store it in the SPFarm or SPWeb property bag. I prefer the SPPersistedObject. You can see a real-world implementation of that here: https://github.com/Nauplius/FoundationSync/blob/2013/FoundationSyncSettings.cs


3

Yes you can, but be sure to try this in your test environment first. Follow the steps in the article SharePoint with more than one SQL instance: possible or not possible On the SQL server Backup the content database. Restore the database on the second instance Add the same permissions for the content database that you had on the source ...


3

You must configure your Exchange server (or any email server you use to send emails in your organization) to route emails @OurSharePointServerName-OurDomainName to the IP address of the SharePoint server where the SMTP service is enabled. See "Step2: Create Send and Receive Connectors in Exchange 2010" at ...



Only top voted, non community-wiki answers of a minimum length are eligible