Adding a server to provide only excel services to an existing sharepoint farm, what kind of installation do we need to perform on the server?

By • What is a SharePoint farm? A SharePoint farm is a collection of servers that work in concert to provide a set of basic A SharePoint farm can be hosted in a cloud, in a company's private Components of a SharePoint farm Servers in a SharePoint farm make up the back-end infrastructure, which supports SharePoint features, including collaboration, uploading files, tracking tasks and managing content. Traditional SharePoint farms are made up of application servers, database servers and web servers. A small SharePoint server farm often includes a A large SharePoint server farm might include two or more database servers, a number of front-end A traditional SharePoint farm consists of web, application and database servers. SharePoint farm topology Up through SharePoint 2013, keeping the server deployment simple was crucial. There were three main roles for servers that factored into a SharePoint farm topology: web server, application server and database server. The web servers were servers to which end users could connect. The applications server runs various services to help optimize the architecture of the farm. The database server role runs the SQL Server services across the farm. Within a farm, there are several services that run on one or more servers. The ability of multiple servers to work in conjunction and provide redundancy is important in the cloud, especially for large data centers. One value of such a system is its These services provide basic functionality for Sha...

We are aware of how Microsoft SharePoint 2010 and 2013 are role agnostic farms i.e. any service can run on any server in the farm. This offers flexibility and scale-out options to its users. In order to manage load balancing, we can execute similar types of Additionally, one can choose to run lightweight services on the front-end or application servers. One can easily add or remove a server in the farm and also one can move services to newly added servers without torment. That’s really great for the farm but this leads to some questions like below: • How many servers are required on the farm? • On which server service is required to configure and run? Microsoft has answered these questions for users in its MinRole. The basic concept of this topology is to explicitly run the set of services based on a server role in the SharePoint farm i.e. no other service can be run. In other words – on predefined server roles set-up, MinRole farm topology depends. This farm topology is applicable in both servers – SharePoint 2016 and 2019. This alternative farm topology to the traditional farm design is designed to optimize the system resources and to maximize performance for users via the predefined server roles. A SharePoint Administrator can assign a server’s role in the SharePoint farm without much effort using this new farm topology. To create a SharePoint farm or to join a server to an existing farm, a server role is required to specify. SharePoint consequently configures the servi...

My question is about adding an application server into a SharePoint 2013 farm which was, initially, a 2 servers environment dedicated for development. It had one server working as WFE / App server and one server dedicated for SQL Server (using an instance). The WFE / app server began to struggle with all the services running and all the application pools required for all the services to running. Unfortunately, as it's a DEV and QAS environment, we had to create separate web applications and application pools to be able to develop the custom solutions, resulting to 14 applications pools that have to run all the time (very bad for the performance). As stated, we decided to add an application server so we could move all the services to the second server (Search, Excel Calculation, Business Connectivity, Central Admin, ...). The installation of SharePoint 2013 SP1 was ok after some struggle on the Language Packs. To add the new server in the farm, we followed the steps in PowerShell located here Because of all these issues and lack of solutions, we decided to move back all the services to the WFE server, remove the app server from the farm then put it back in the farm step by step. After following the same steps as the first time, we can see that the psconfig is failing directly now, saying there is an error but doesn't show any error in the upgrade log. I guess something went wrong again or was not cleaned at the removal of the server from the farm. The question I have is wha...

You can publish a workbook to a Microsoft SharePoint library so that people can view or edit it in a web browser without needing Excel installed on their computers. Publishing is essentially the same as saving, but with some built-in options that let you control what people can see when they open the workbook in a browser. Adopting an organization-wide practice of saving or publishing a workbook to a central SharePoint site can help you ensure that slightly different versions of the same workbook don't start popping up all over your organization when it's sent around in email. By setting some publish options, you can emphasize specific parts of your workbook, such as charts, or exclude other parts from being viewed in the browser. For example, you can show a chart but not its underlying data. Or, you can show only certain worksheets to those people who need to see them and hide the other worksheets. This article shows you how to publish a workbook from Excel for Windows and does not cover connecting a workbook or workbook data to an Excel Web Access Web Part on a SharePoint page. When you publish a workbook to a SharePoint site, the entire workbook is saved to SharePoint. A user with the needed SharePoint permissions can view and work with the entire workbook either in the browser or in the Excel desktop program. If Office for the web is deployed on SharePoint, viewing and working with your data in the browser can be very much like working with your data in the Excel deskt...

My Client is adding a WFE Server to their SharePoint Farm. Their current setup is 1 App Server, 1 DB Server. I have installed SharePoint on the new WFE Server but when I try to add it to the existing Farm I get the error :- 'The current server cannot be joined to this farm because the set of installed products does not match the products installed in the farm. The license state for the current server doesn't match the farm's license state.' Convinced they are patched to the same level so followed the advice here to see what licenses are on what servers :- Existing App Server : SharePoint Foundation 2013 and SharePoint Server 2013 New WFE Server : SharePoint Foundation 2013 and SharePoint Server 2013 Enterprise Is there any way around this other than flattening the WFE and installing SharePoint Server 2013 ? For example can I activate Enterprise features on the App Server and then add the WFE to the Farm ? What are the licensing implications (if any) of doing this ? I really don't want to start again unless I have to. All advise greatly appreciated. Thanks. Dan. The existing App-Server has a SharePoint 2013 Standard license enabled and you accidentally installed your new WFE-Server with an Enterprise-Key. Do NOT upgrade the existing App-Server to an Enterprise License. The customer would have to buy Enterprise-CALS for all users. Those are not cheap :-) You cannot "downgrade" the enterprise-key if installation is completed. If you do not want to start completely from scratc...

You can publish a workbook to a Microsoft SharePoint library so that people can view or edit it in a web browser without needing Excel installed on their computers. Publishing is essentially the same as saving, but with some built-in options that let you control what people can see when they open the workbook in a browser. Adopting an organization-wide practice of saving or publishing a workbook to a central SharePoint site can help you ensure that slightly different versions of the same workbook don't start popping up all over your organization when it's sent around in email. By setting some publish options, you can emphasize specific parts of your workbook, such as charts, or exclude other parts from being viewed in the browser. For example, you can show a chart but not its underlying data. Or, you can show only certain worksheets to those people who need to see them and hide the other worksheets. This article shows you how to publish a workbook from Excel for Windows and does not cover connecting a workbook or workbook data to an Excel Web Access Web Part on a SharePoint page. When you publish a workbook to a SharePoint site, the entire workbook is saved to SharePoint. A user with the needed SharePoint permissions can view and work with the entire workbook either in the browser or in the Excel desktop program. If Office for the web is deployed on SharePoint, viewing and working with your data in the browser can be very much like working with your data in the Excel deskt...

My Client is adding a WFE Server to their SharePoint Farm. Their current setup is 1 App Server, 1 DB Server. I have installed SharePoint on the new WFE Server but when I try to add it to the existing Farm I get the error :- 'The current server cannot be joined to this farm because the set of installed products does not match the products installed in the farm. The license state for the current server doesn't match the farm's license state.' Convinced they are patched to the same level so followed the advice here to see what licenses are on what servers :- Existing App Server : SharePoint Foundation 2013 and SharePoint Server 2013 New WFE Server : SharePoint Foundation 2013 and SharePoint Server 2013 Enterprise Is there any way around this other than flattening the WFE and installing SharePoint Server 2013 ? For example can I activate Enterprise features on the App Server and then add the WFE to the Farm ? What are the licensing implications (if any) of doing this ? I really don't want to start again unless I have to. All advise greatly appreciated. Thanks. Dan. The existing App-Server has a SharePoint 2013 Standard license enabled and you accidentally installed your new WFE-Server with an Enterprise-Key. Do NOT upgrade the existing App-Server to an Enterprise License. The customer would have to buy Enterprise-CALS for all users. Those are not cheap :-) You cannot "downgrade" the enterprise-key if installation is completed. If you do not want to start completely from scratc...

My question is about adding an application server into a SharePoint 2013 farm which was, initially, a 2 servers environment dedicated for development. It had one server working as WFE / App server and one server dedicated for SQL Server (using an instance). The WFE / app server began to struggle with all the services running and all the application pools required for all the services to running. Unfortunately, as it's a DEV and QAS environment, we had to create separate web applications and application pools to be able to develop the custom solutions, resulting to 14 applications pools that have to run all the time (very bad for the performance). As stated, we decided to add an application server so we could move all the services to the second server (Search, Excel Calculation, Business Connectivity, Central Admin, ...). The installation of SharePoint 2013 SP1 was ok after some struggle on the Language Packs. To add the new server in the farm, we followed the steps in PowerShell located here Because of all these issues and lack of solutions, we decided to move back all the services to the WFE server, remove the app server from the farm then put it back in the farm step by step. After following the same steps as the first time, we can see that the psconfig is failing directly now, saying there is an error but doesn't show any error in the upgrade log. I guess something went wrong again or was not cleaned at the removal of the server from the farm. The question I have is wha...

We are aware of how Microsoft SharePoint 2010 and 2013 are role agnostic farms i.e. any service can run on any server in the farm. This offers flexibility and scale-out options to its users. In order to manage load balancing, we can execute similar types of Additionally, one can choose to run lightweight services on the front-end or application servers. One can easily add or remove a server in the farm and also one can move services to newly added servers without torment. That’s really great for the farm but this leads to some questions like below: • How many servers are required on the farm? • On which server service is required to configure and run? Microsoft has answered these questions for users in its MinRole. The basic concept of this topology is to explicitly run the set of services based on a server role in the SharePoint farm i.e. no other service can be run. In other words – on predefined server roles set-up, MinRole farm topology depends. This farm topology is applicable in both servers – SharePoint 2016 and 2019. This alternative farm topology to the traditional farm design is designed to optimize the system resources and to maximize performance for users via the predefined server roles. A SharePoint Administrator can assign a server’s role in the SharePoint farm without much effort using this new farm topology. To create a SharePoint farm or to join a server to an existing farm, a server role is required to specify. SharePoint consequently configures the servi...

By • What is a SharePoint farm? A SharePoint farm is a collection of servers that work in concert to provide a set of basic A SharePoint farm can be hosted in a cloud, in a company's private Components of a SharePoint farm Servers in a SharePoint farm make up the back-end infrastructure, which supports SharePoint features, including collaboration, uploading files, tracking tasks and managing content. Traditional SharePoint farms are made up of application servers, database servers and web servers. A small SharePoint server farm often includes a A large SharePoint server farm might include two or more database servers, a number of front-end A traditional SharePoint farm consists of web, application and database servers. SharePoint farm topology Up through SharePoint 2013, keeping the server deployment simple was crucial. There were three main roles for servers that factored into a SharePoint farm topology: web server, application server and database server. The web servers were servers to which end users could connect. The applications server runs various services to help optimize the architecture of the farm. The database server role runs the SQL Server services across the farm. Within a farm, there are several services that run on one or more servers. The ability of multiple servers to work in conjunction and provide redundancy is important in the cloud, especially for large data centers. One value of such a system is its These services provide basic functionality for Sha...