Home » business intelligence » sharepoint » Why Use Power Shell to Create, Configure, and Manage Excel Services for SharePoint 2013?

Why Use Power Shell to Create, Configure, and Manage Excel Services for SharePoint 2013?

SharePoint administrators will want to provide Business Intelligence (BI) stakeholders with as functional an interface to Excel Services from SharePoint Server 2013 as possible.

Jason Himmelstein demonstrates some of the important steps required to enable and configure this service with SharePoint Management Shell (Power Shell) in a video tutorial titled Excel Services Configuration

This video tutorial is intended for an audience of SharePoint administrators, developers, designers and architects.

For those administrators who would rather not use Power Shell to set up this service, the alternative is to use Central Administration in SharePoint 2013. The next step is to select “Application Management”, and then “Manage Service Applications”.

From “Manage Service Applications” the next step is to create the Excel Services application. From this set of screens it is possible to set all of the parameters required for Excel Services, and even “the proxy for the farm”.

Opting to use Power Shell to create the service, on the other hand, does streamline the process of getting the service up and running. It’s not possible to run the service from Central Administration, whereas it’s very easy to initiate the service from Power Shell.

For administrators tasked with managing a lot of farms, Power Shell offers an important additional advantage. Reusable scripts can certainly be written to streamline creation, configuration and initiation of service. Since the scripts will likely include variables, these placeholders can certainly be reused, over and over again, to substantially reduce the amount of time it takes to get the Excel Service up and running.

Jason also demonstrates the power of the “Read Host” function, which permits an administrator to query the farm configuration to obtain the file names, server names, locations, etc, to quickly customize an existing script for use in an otherwise new environment. Of course, sufficient permissions will have to be in place for this function to work correctly and in a secure manner.