SQL Installation for SharePoint 2013 - Windows Firewall - Profile - domain, Public and Private - Which ones to choose?

Hi there,
I am setting up SQL Server (to be used in our SharePoint 2013 farm).
The Firewall exception for SQL server gives me three choices in Profile section as 
Domain, Public and Private profiles 
Which ones should I choose please? 
Thank you so much.

Hi,
According to your description, my understanding is that you want to set the firewall exception for SQL server.
Domain profile—This profile is active when the server is connected to an Active Directory (AD) domain via an internal network. This is the profile that's typically active, because most servers are members of an AD domain.
Private profile—This profile is active when the server is a member of a workgroup. Microsoft recommends more restrictive firewall settings for this profile than for the domain profile.
Public profile—This profile is active when the server is connected to an AD domain via a public network. Microsoft recommends the most restrictive settings for this profile.
More information, please refer to the link:
http://windowsitpro.com/windows/windows-server-2008-r2-firewall-security
Please 'propose as answer'
if it helped you, also 'vote helpful' if you like this reply.
Prabhu

Similar Messages

  • Sql 2012 for Sharepoint 2013

    What's better, SQL 2012 on a separate virtual machine running other databases too, or SharePoint having SQL all to itself on the same virtual server?
    David

    That would depend on the load. If SharePoint was in use by just a couple of users, the content was small, and SQL was limited in memory usage while the VM had enough memory, a single install would be fine.
    But in general, I would pick the first option of having SQL on a separate VM.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • SQL Server 2014 PowerPivot installation on SharePoint 2013

    Hello:
    I saw many references on the topic but one thing is still not clear.
    Is
    spPowerPivot.msi installer for SharePoint 2013 is another package that has to run after the
    “SQL Server PowerPivot for SharePoint” installation on SharePoint server via SQL Server setup?
    Or spPowerPivot.msi is the same thing as “SQL Server PowerPivot
    for SharePoint” from SQL Server setup?
    I run
    spPowerPivot.msi on my SharePoint server, but don't see the SQL Server PowerPivot Configuration manager created.
    Please advise
    -Jeff

    SQL Server PowerPivot for SharePoint is the SQL Server Analysis Services Tabular Mode instance with the instance name POWERPIVOT. The spPowerPivot.msi installs the proxy that connects to the SQL Server Analysis Services Tabular Mode instance. You run the
    SQL Server PowerPivot for SharePoint installation on the server that you want to run the SQL Server Analysis Services Tabular Mode instance whereas you run the spPowerPivot.msi installation on all of the servers in your SharePoint farm (except the database
    server.) For SQL Server 2014, this is
    a separate download and is not included in the SQL Server 2014 installation media.
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • Difference between Reporting Services Sharepoint Mode and Reporting Services Add In for Sharepoint 2013

    Hi, We are building company site with Sharepoint 2013 Enterprise Edition and were wondering what is the difference between Reporting Services Sharepoint Mode and Reporting Services Add In for Sharepoint 2013? What are the roles/purposes of each one? What
    happens if only Reporting Services Sharepoint Mode  installed or vise versa.
    Thank you in advance

    Reporting Services in SharePoint mode is a service for displaying, managing, and creating SSRS reports within SharePoint. The addin is a pre-req for SharePoint that is used to display reports and is required for Reporting Services in Native or SharePoint
    mode, but does not by itself do anything.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • SQL 2012 AlwaysON High Availability for SharePoint 2013

    Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
    We got one more Server & we don't have Storage so need to configure Always On.
    There are Some Confusions:
    1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
    2- What are the Changes need to be done on Production Server?
    3- What are the Steps to be followed While Configuring new Database Server?
    Regards,

    Hi Genius1985,
    According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
    Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
    There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
    to the following article:
    http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
    Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
    Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
    Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012.  This needs to be done on all of the SQL Server instances that we will configure as replicas in our
    Availability Group.
    For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
    http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
    If you have any question, please feel free to let me know.
    Regards,
    Jerry Li

  • The installation of this package failed" error while installing Nov 2013 CU (KB 2889944) for SharePoint 2013

    Hi,
    I'm currently installing Nov CU on my Sharepoint 2013 farm, I have 2 APPS and 2 WFE. I successfully installed the patch in 3 servers however, I got this error "The installation of this package failed” in one of my server.
    Now i cant run the configuration wizard because it of this error.
    Any advise how on to solve this issue? it's giving me headache the whole day already.
    thanks!
    JD

    Hi Trevor,
    Thank you for your reply, I just want to share with you what i found in the msi logs.
    DEBUG: Error 2746:  Transform 9010F70000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10F7-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010F70000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010F70000100015.0.4420.1017
    1: 2746 2: 9010F70000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-10F7-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010F70000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10F7-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010F70000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010FB0000100015.0.4454.1510
    1: 2746 2: 9010F70000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-10F7-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010FB0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10FB-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010FB0000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010FB0000100015.0.4420.1017
    1: 2746 2: 9010FB0000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-10FB-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010FB0000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10FB-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010FB0000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 90107F0000100015.0.4454.1510
    1: 2746 2: 9010FB0000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-10FB-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 90107F0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-107F-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:482]: Skipping validation for patch transform #90107F0000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:482]: Looking for patch transform: 90107F0000100015.0.4420.1017
    1: 2746 2: 90107F0000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-107F-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 90107F0000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-107F-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:482]: Skipping validation for patch transform #90107F0000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:482]: Looking for patch transform: 90104B0000100015.0.4454.1510
    1: 2746 2: 90107F0000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-107F-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2749:  Transform 90104B0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product version == 15.0.4454.1510, found product version 15.0.4420.1017.
    I hope you can help me shed light on this.
    Regards,
    JD

  • Windows Updates for SharePoint 2013 Environment

    Hi
    I created a visual machine for SharePoint 2013 development by following steps mentioned below.
    --Install Winows Server 2008 R2
    --SQL Server 2008 R2
    --SP2 for SQL Server 2008 R2
    --SP1 for Winows Server 2008 R2 
    --Sharepoint 2013 Pre-Requisites
    --Sharepoint 2013 Setup
    --Sharepoint 2013 Designer
    --Installed March and August 2013 Cumulative Updates for SharePoint 2013
    --Installed SP1 for SharePoint 2013
    I want to ask do i need to install Windows Updates after installing different updates as i mentioned above because everty now and then windows updates message keep pops up and i did'nt install windows updates yet.
    Why is it necessary or what impact window updates would have on my environment if i need to do it??

    Windows Updates cover security updates as well as stability improvements, and so on. You're simply patching SharePoint and SQL in the above case.
    It should be noted that any SharePoint patches that come down through Windows Update need to be manually handled as you'll need to run the Config Wizard (e.g. MS14-022 and MS14-050 which are SharePoint updates).
    When you're installing SharePoint 2013, you only need to install SP1 if that is your target. There is no requirement to install March 2013 or August 2013.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Prerequisites download location for SharePoint 2013 SP1 on Windows 2012 R2 platform

    Can any one share prerequisites download location for SharePoint 2013 SP1 on Windows 2012 R2 SP1 platform.

    Did you see this
    http://blogs.technet.com/b/cjrawson/archive/2014/04/06/offline_2d00_sharepoint2013sp1_2d00_prerequisites_2d00_server2012r2.aspx
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Installing Powerpivot for Sharepoint 2013 with SQL Server 2008 R2

    Hi,
    We are currently setting up a Sharepoint 2013 Enterprise farm with the backend database server being SQL Server 2008 R2 SP2 - my question is can you install  Powerpivot for Sharepoint 2013 in this configuration and if so what are the steps?
    Thanks in advance!

    Here is Microsoft's documentation to Configure Power Pivot for SharePoint 2013
    Jason Warren
    @jaspnwarren
    jasonwarren.ca
    habaneroconsulting.com/Insights

  • SQL server requirement for sharepoint 2013

    Hello All,
    currently i have installed SharePoint2013 in server farm mode, and i have used SQL Server 2008 R2 for DB. Can i use SQL Server 2012 for SharePoint 2013?
    Thanks

    SharePoint 2013 is compatible with SQL 2008 R2 and SQL 2012 so yes.
    What you can do is "move" the SharePoint DBs from SQL 2008 R2 to SQL 2012 without restore or backup.
    Link to msdn: https://technet.microsoft.com/en-us/library/cc512725(v=office.15).aspx
    Here you have an example for SharePoint 2010 (is the same for SharePoint 2013): http://www.codeproject.com/Articles/664029/Migrate-SharePoint-s-SQL-Server-to-another-SQL-Ser
    Here an different example: http://surya20p.blogspot.com.es/2013/09/migrate-sql-2008r2-sp2-to-sql-2012-sp1.html
    Best regards.

  • Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..

    Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..i mean enterprise version BI version or standard version.. i just need a detailed comparison if available please thank you

    As of right this very second, SQL Server 2014 is not supported. SharePoint 2013 supports:
    One of the following:
    The 64-bit edition of Microsoft SQL Server 2012.
    The 64-bit edition of SQL Server 2008 R2 Service Pack 1
    Hardware and software requirements for SharePoint 2013
    Edit: I may be mistaken. It looks like the April 2014 CU adds support for SQL Server 2014. If this is the case generally going with the latest SQL Edition provides you with the latest SQL functionality. I'm not aware of any SharePoint features that would
    make use of functionality that is new to SQL Server 2014 but this could change with a future service pack.
    Jason Warren
    @jaspnwarren
    jasonwarren.ca
    habaneroconsulting.com/Insights

  • SQL Server Web Edition for SharePoint 2013

    Dear Expert,
    I'm not sure SQL Server Web Edition is ok for SharePoint Server 2013 or not. If I do in On-Premise or Azure.
    Please suggestion.

    There is no specific document that specifies that Web edition is supported.  However, if you look at the requirements list for SharePoint 2013 you will notice that it specifies that it must be either SQL server 2008 r2  with SP1 or SQL 2012.
     It also specifies the 64 bit version.  But it doesn't specify a specific edition.  That and the fact that it will run on SQL Express suggests that it will run on any edition of SQL as long as its 64 bit and a late enough release.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Can we use SQL Server as a primary data storage for SharePoint 2013?

    Is it possible to use external SQL Server as a primary data storage for SharePoint 2013?
    Having this implemented we can generate reports, query data and it would become very very powerful to use.
    Or
    Is there a way to keep on using existing content databases and using external SQL Server as a secondary data storage at the same time. So I want it to be like redundant data in SQL Server.
    Thanks 

    Hi，
    Not sure if I understand your question correctly, SharePoint has its own content database storing SharePoint list data, we can use SSRS/SSAS integated with SharePoint mode to use sharepoint list as datasource to generate reports.
    http://technet.microsoft.com/en-us/library/bb326358(v=sql.105).aspx
    http://sqlmag.com/business-intelligence/delivering-bi-through-sql-server-and-sharepoint
    http://www.mssqltips.com/sqlservertip/2068/using-a-sharepoint-list-as-a-data-source-in-sql-server-reporting-services-2008-r2/
    Thanks
    Daniel Yang
    TechNet Community Support

  • Installation of Re-release of SP1 for SharePoint 2013 - Error message, The installation of this package failed

    Hello, 
    Is anyone else receiving this error when trying to install?
    Gene Olsen

    Hi Gene,
    Try re-downloading this re-released SP1 installation file and install it again, see if it works.
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/ef21ac40-8347-4632-9b1e-7c62986f4c2c/installation-of-new-sp1-2880552-over-the-old-one-2817429-failing?forum=sharepointadmin
    http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx?pi6847=3
    Thanks
    Daniel Yang
    TechNet Community Support

  • Installation of SP1 for SharePoint 2013

    After Installation of SP1 for SharePoint 2013,I see a new button Office 365 but when I click on it I can't go in anymore.So,Is that what i need to look to go in and work?
    is we required to connect to Internet?

    Hi,
    According to your post, my understanding is that after Installation of SP1 for SharePoint 2013, you saw a new button Office 365.
    As part of the SharePoint 2013 Service Pack 1, Microsoft has starting to provide some way to implement a sort of hybrid mode – as we can already have with Exchange – with Office 365.
    A new link/option shown in the Quick Launch menu on the left or in the Central Administration home page.
    After clicking the Office 365, the two links provide you a way to configure a first level integration with your Office 365 to use Yammer (as this now included on Office 365 Enterprise plans) or OneDrive for Business on Office 365.
    For more information, you can refer to:
    SharePoint 2013 – SharePoint 2013 SP1 includes settings to configure Office 365 integration
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

Maybe you are looking for