Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

Install SharePoint 2013 using SQL Authentication?

$
0
0

My situation:

One SharePoint 2013 Server (one server which assumes both the WFE and APP role) which is located in the perimeter domain "EXTERNAL".

SQL Server is located behind a firewall in corporate domain "INTERNAL". SharePoint service accounts have been added to the EXTERNAL domain Active Directory. On the SQL server I am using mixed mode authentication. SQL Server listens to all TCP/IP traffic on port 1433  and the firewall between EXTERNAL and INTERNAL domain has been configured to pass port 1433 traffic. There are no additional firewalls which could cause issues. Both servers can ping each other. Now, here's the kicker; I want to install SharePoint 2013 WITHOUT using any sort of trust relationship between these domains as per customer request (although I don't fully agree with this setup).

Now - in SharePoint 2010 this is a supported scenario (called a 'split-back-to-back extranet topology') but I have been struggling to get anything to work correctly in this scenario. No documentation is available and the only method seems to be by using powershell and manually create config db's, services, applications, features etcetera. Also, this can break functionality in SharePoint 2013 (user profile service for example). A patch has been released by Microsoft specifically for the UPS issue, but the entire scenario seems sketchy at best. Too many unknowns and too many variables.

Questions that I have:

* Can anybody tell me if this scenario is officially supported?

* If so, what arethe steps I need to take to make this installation work?

the reason I am asking is to see whether I should put a lot more energy in this scenario or if we need to rethink our strategy.

Thanks in advance!

Gaston





Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>