Skip to main content
simplify question
Source Link
Nico
  • 1.1k
  • 3
  • 21
  • 47

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server 2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

EDIT : to clarify, the question is : What would you advice me to do, knowing that I need both extranet/intranet, with different Auth (SQL FBA for extranet & AD for intranet).

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server 2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server 2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

EDIT : to clarify, the question is : What would you advice me to do, knowing that I need both extranet/intranet, with different Auth (SQL FBA for extranet & AD for intranet).

added 1 character in body; edited tags
Source Link

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server2server 2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server 2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

deleted 1 character in body
Source Link
Nico
  • 1.1k
  • 3
  • 21
  • 47

I'm currently working with 3 servers in dev testenv. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

I'm currently working with 3 servers in dev test. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

I'm currently working with 3 servers in dev env. The objective is to replace the current all-in-one SP server.

This is what I planned :

  • One for SQL Database (because SQL uses a lot of RAM)
  • One for SharePoint 2013 hosting Central Admin, and my intranet website
  • One for SharePoint 2013 hosting my extranet website.

Does that take any sense for you ?

I mean : I thought that if I put 2 SP servers in a farm, I could use server1 for intranet with AD auth, and server2 for extranet with FBA SQL Auth. I thought that its better to separate SQL Auth and AD Auth, same for intranet/extranet...

I set up a dev env, and when I create a web application, I cannot choose on which server it will be hosted, because I didn't understand that 2 SP servers (if i'm right) are hosting the iis site, and if 1 break, the site still up.

Can someone help me understand what I really need ? I mean, separate AD Auth/SQL Auth for security reasons are the good reasons ? Same for intranet/extranet ?

Feel free to ask for more details obviously.

Source Link
Nico
  • 1.1k
  • 3
  • 21
  • 47
Loading