Last Updated March 28, 2014
Description
This post describes how to configure the SharePoint Server 2013 Visio Graphics Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Visio Graphics
Service Application components. Document the naming convention.
Example:
Application Pool Service Account: Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPVisioServiceApplication_01
Service Application Proxy: SvcApp_SPVisioServiceApplication_01_Proxy_01
2) Open the SharePoint 2013 Management Shell as Administrator.
3) Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name
4) Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"
5) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPVisioServiceApplication -ApplicationPool $SvcAppPool02 -Name "SvcApp_SPVisioServiceApplication_01"
6) Verify the Service Application.
Get-SPServiceApplication | Select Name
5) Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPVisioServiceApplicationProxy -ServiceApplication SvcApp_SPVisioServiceApplication_01 -Name "SvcApp_SPVisioServiceApplication_01_Proxy_01"
7) Verify Service Application Proxy.
Get-SPServiceApplicationProxy | Select Name
References
Microsoft TechNet (February, 2014). New-SPVisioServiceApplication. Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/ff608096%28v=office.15%29.aspx
Microsoft TechNet (February, 2014). New-SPVisioServiceApplicationProxy. Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/ff608020%28v=office.15%29.aspx
Thursday, March 27, 2014
SharePoint 2013: How to Configure Work Management Service Application using PowerShell
Last Updated March 28, 2014
Description
This post describes how to configure the SharePoint Server 2013 Work Management Service Application using PowerShell.
Solution
1) Document the Naming Convention
Document a naming convention for each of the Work Management Service Application components.
Example:
Application Pool Service Account: Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPWorkManagementServiceApplication_01
2) Open the SharePoint 2013 Management Shell as Administrator.
3) Verify the Name of the Application Pool.
PS C:\ Get-SPServiceApplicationPool | Select Name
4) Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"
5) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPWorkManagementServiceApplication -ApplicationPool $SvcAppPool02 -Name "SvcApp_SPWorkManagementServiceApplication_01"
6) Verify the Service Application.
PS C:\ Get-SPServiceApplication | Select Name
References
Microsoft TechNet (February, 2014). New-SPWorkManagementServiceApplication. Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/fp161254%28v=office.15%29.aspx
Description
This post describes how to configure the SharePoint Server 2013 Work Management Service Application using PowerShell.
Solution
1) Document the Naming Convention
Document a naming convention for each of the Work Management Service Application components.
Example:
Application Pool Service Account: Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPWorkManagementServiceApplication_01
2) Open the SharePoint 2013 Management Shell as Administrator.
3) Verify the Name of the Application Pool.
PS C:\ Get-SPServiceApplicationPool | Select Name
4) Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"
5) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPWorkManagementServiceApplication -ApplicationPool $SvcAppPool02 -Name "SvcApp_SPWorkManagementServiceApplication_01"
6) Verify the Service Application.
PS C:\ Get-SPServiceApplication | Select Name
References
Microsoft TechNet (February, 2014). New-SPWorkManagementServiceApplication. Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/fp161254%28v=office.15%29.aspx
Monday, March 03, 2014
SPS Boston: Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server
Event:
SharePoint Saturday Boston
Saturday, April 12, 2014
Session Title:
Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server
Abstract:
First, we’ll review the architecture of SharePoint with SQL Server Reporting Services (SSRS) and SQL Server Integration Services (SSIS) and define the role that the Business Intelligence capabilities play in an organization’s Enterprise Architecture (EA). From there, we will evaluate sample business scenarios and compare and contrast different possible solution approaches. We will design a reporting solution, and then build the solution step by step using SharePoint, SSRS, and SSIS. Finally, we will reflect on the overall approach that we followed and discuss further ideas and possibilities. This session covers high-level concepts as well as practical, hands-on instructions, tips, and tricks.
Slides:
Reporting and Data Integration Methodologies and Mechanics SP2013 SQL2012.pdf
Note: the instructional slides begin at slide #23
SharePoint Saturday Boston
Saturday, April 12, 2014
Session Title:
Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server
Abstract:
First, we’ll review the architecture of SharePoint with SQL Server Reporting Services (SSRS) and SQL Server Integration Services (SSIS) and define the role that the Business Intelligence capabilities play in an organization’s Enterprise Architecture (EA). From there, we will evaluate sample business scenarios and compare and contrast different possible solution approaches. We will design a reporting solution, and then build the solution step by step using SharePoint, SSRS, and SSIS. Finally, we will reflect on the overall approach that we followed and discuss further ideas and possibilities. This session covers high-level concepts as well as practical, hands-on instructions, tips, and tricks.
Slides:
Note: the instructional slides begin at slide #23
SharePoint Server or Project Server Patch Installed Patch Missing
Description
After installing a SharePoint Server or Project Server Service Pack or Cumulative Update, the Configuration Wizard shows that the Patch is missing from servers in the farm. In this case, the Configuration Wizard on Server 1 is showing that the Project Server 2013 SP1 Patch is missing, yet it was already installed.
Error: Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard. If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.
Attempting to run the Project Server 2013 SP1 Patch installation again from the .exe verifies that the Patch is already installed on the system. Herein lies the problem. On one hand, the Configuration Wizard will not run because it thinks the patch is missing. On the other hand, it is not possible to install the patch because it is already installed on local server. Patch installed, patch missing, patch installed, patch missing.
Solution
The solution to this problem is to run a PowerShell cmdlet on each of the servers that the Configuration Wizard is reporting, patch missing.
1. Log into the SharePoint Server
2. Open the SharePoint Management Shell as Administrator
3. Get-SPProduct -local
This cmdlet retrieves a list of the SharePoint-related products installed in the farm. It also retrieves the version information for updates installed. Using the -Local switch retrieves information for local server only.
References
Microsoft TechNet (May, 2010). Document farm configuration settings (SharePoint Foundation 2010). Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645390%28v=office.14%29.aspx
Microsoft TechNet (January, 2014). Document farm configuration settings in SharePoint 2013. Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645391.aspx
Microsoft TechNet (July, 2012). Get-SPProduct. Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff607885.aspx