Tag Info

Hot answers tagged

21

NTLM is 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 context ...


13

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


11

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


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

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

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


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

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


4

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

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


4

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


3

The title of your question implies that you want to configure the connection string for each web part. To do this, you should add a web part property to your webpart. Then the user that adds the web part to the page can fill in the value for the connection string. I assume you have a user control for your web part, so just assign your web part property to a ...


3

Have you tried the following? In Central Admin > Operations > Services on Server Select your SQL server and stop the Windows SharePoint Services Web Application service (May have to select a custom role) NB - I haven't had the chance to try this out on a farm, so tread carefully!


3

Have run into this same issue many times. As an Admin, one of the ways I've tried to manage it is to make sure that every custom solution is packaged so that the packages can be deployed via stsadm (or PowerShell for future 2010 stuff). Also have also maintained that each solution should be created on a site that is in a site collection database of its own. ...


3

That's how you do it, but use the class noindex instead, like this: <div class="noindex"> footer </div>


3

From http://www.muhimbi.com/blog/2009/05/how-to-reliably-detect-moss-or-wss-at.html /// <summary> /// Method to find out if a SharePoint installation is MOSS or WSS 3.0 /// </summary> public static bool IsMOSS() { SPFeatureDefinitionCollection features = SPContext.Current.Site.WebApplication.Farm.FeatureDefinitions; if ...


3

Central Administration > Manage servers in this farm (under System Settings) Configuration database version of 14.xxx is 2010 and 12.xxx is 2007 SharePoint Products Installed will show you the product.


3

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


3

I would definately start from scratch! The account used for install has special permissions, and if these have been intertwined with farm account it is a mess. You will spend far longer time trying to undo the security related problems in the previous install than starting over. I usually define a managed account for each service application, one for each ...


3

First, to open the file in browser, go to Central Admin -> Select Your Web Application --> Select General Settings -> Select "Permissive" under browser file handling (also read the notes explaining the setting) as shown below: For PDF icons, you need to associate .pdf with an icon and upload the icon image to C:\Program Files\Common Files\Microsoft ...


3

In this case I think you will be better served at looking at a utilizing the hosting model for SharePoint. This will allow you to create 'Feature Packs' so you can have one app or site subscription configured with Enterprise or Standard features, and the other one configured for Foundation. There are other considerations here though. If, you are ...


3

You will find entries similar to the following in the section of the web.config for your web application or in the root web.config if you configured FBA at the IIS root. You can change the name(s) directly in the web.config file. <roleManager> <providers> <add name="FBARoleProvider" ...


3

This was nice quest for me. I will not ask why do you need this and I hope that you don't need warning like: Never mess with SharePoint databases directly! I didn't found many articles on net covering this specific issue (no wonder when it is bad practice). The only one was 2007 related: Determining the Configuration Database in a SharePoint 2007 Farm. ...


3

Yes, you can do a SharePoint 2010 install in a manner that will allow you to specify the names of all your SharePoint databases, so you can enforce a naming convention that you can use to distinguish between the various farms that the databases are associated with. The challenge is that you won't be able to use the Product Configuration Wizard GUI interface ...


3

SharePoint does not take kindly to cloning, be it with a disk cloning tool or copying virtual machine drives. The supported approach is to: Create a new farm on your new servers. By "create" I mean install the SharePoint binaries with setup.exe and run the configuration wizard to create the Configuration database and Central Administration site. You do not ...


3

Try to disable the firewalls for both the database server and the sharepoint front end temporarily and try again. Make sure the account you are logged onto and running the SharePoint Config Wizard has proper database access. Also, Are you bindings in IIS Manager linked to the old IP or hostname? Change that and try again. Also view my blog about this: ...


3

Make sure you have your DOMAIN ACCOUNTS ready - without this only STANDALONE will be available, meaning that many services (e.g. UPSA) will not be working as they are not provisioned!!! - DO NOT use your LOCAL Administrator to configure the farm as this will be used as the Farm Account later, rather log in with any domain account that will be using further. ...


3

Personally, If you are not strapped for space, I would both back up content and configuration as well as using your regular backups. Technically, you do not need to back up the content as well as have a backup of the sql instance, however they are really two different types of backups. One allows you to restore the site as a whole with everything on it to ...



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