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 ...
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 ...
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 ...
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 ...
Sharepoint designer consider as a part of the office family so that its version should match with other installed office products.
In your case you have 64 bit of Windows and 32 bit of office so you need 32 bit of designer.
Now either reinstall the office with 64 bit or install the sharepoint designer with 32 bit
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")
If you want to check ID of the ...
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 ...
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 ...
$site = Get-SPSite http://servername/customer/questions
And you have more detailed info in http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=573
I was looking for the same information, and just found the answer here.
Here are the steps:
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 ...
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
Next, go to Central Administration site, System settings => Configure alternate access mappings, and change all the VM_1 ...
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 ...
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 ...
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 ...
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:
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 ...
As a recommended approach, you should not install the SharePoint Designer on the SharePoint server, reason is same as you mentioned.
SharePoint Designer is client application and you can connect to both farm from you local machine( as long as that machine on network) as long as you have to permission on the site collection.
This issue occurs if the available memory on the web server is low So
Try to restart Sharepoint search host controller in windows service to release all the leaked memory and consumed memory !
Or scale up your memory.
Also, check the following links to adjust minFreeMemoryPercentageToActiveService Configuration Setting as a permanent solution.
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 ...
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 ...
Everything here is correct thus far, but generally which one to use? When I'm setting up SharePoint, Single-Server setups are typically NTLM, Multi-Server setups are typically Kerberos. Usually Multi-Server setups one day will involve third party tools, etc. that wish to setup authentication integrated somewhat with SharePoint and being cognizant of that, ...
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. ...
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 ...
You need to execute Register-SPWorkflowService only once for the entire farm.
I have many cases where this did not work though due to some other factors in addition to the Proxy issue mentioned in the earlier response.
SharePoint web applications are using https and the root of their cert is not in Workflow Manager server trusted root authority (MMC Snap-...
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 ...
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.
Only Powershell is not working after detaching the DBs from Original SQL or other stuff also broked?
You can modify manually the rights associated to your account in SQL Server, but I prefer using the Add-SPShellAdmin This link is external to TechNet Wiki. It will open in a new window. cmdlet, which will do the work for you.
Launch this cmdlet by using (...
I have the same problem, and found solution - Here
Corrupted node.ini file in AdminComponent1 folder - size 2kb, but empty when open with notepad.
Solution - browse to:
C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Nodes\
For each node, open the folder and browse to \Configuration\Local\ and check the node.ini file ...
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 ...
You must use cliconfg.exe on each SharePoint server to point the 'old' SQL Server name (and instance if applicable) to the new SQL Server name (and instance if applicable). So if you had an old SQL Server name of OLDSQL and a new one of NEWSQL, you would run cliconfg.exe on each SharePoint server, go to the Alias tab, add an alias named OLDSQL. Set it to TCP/...