Resolve TF400069: You must install either SQL Server Analysis Services version 11.0 ...

Setting up TFS AT (Application Tier) and DT (Data Tier) in separate machines (not a single server installation) might raise below error in Analysis Services configuration for TFS.
*******************************************************************************************************
TF400069: You must install either SQL Server Analysis Services version 11.0 or the SQL Server Client Tools on the application tier to ensure that the Analysis Services object model is present for warehouse processing.
*******************************************************************************************************

As the error message clearly stated setting up SQL Connectivity Tools will resolve this issue.

Fixing Warning TF255119: The Windows Service Control Manager could not be contacted on <SQLServer>

TFS setup in distributed topology might give ht below warning in configuration readiness checks.
*******************************************************************************************************
TF255119: The Windows Service Control Manager could not be contacted on <sqlserver>. The following service cannot be verified as installed, running, and set to start automatically: SQL Server Analysis Services. Manually verify that the service is functioning correctly.
*******************************************************************************************************

Proceeding the configuration with this warning may require to reconfigure reporting services later.
This can be fixed by allowing Remote Service Management in the firewall of the server running Analysis Services.

Resolve – TF250049 and TF250067

Setting up SharePoint extensions for TFS in a remote server might cause below error.
*******************************************************************************************************
TF250049: The following URL for Team Foundation Server could not be verified: <TFSUrl>. The following error was received: TF250067: No connection could be made to Team Foundation Server at the following address: <TFSUrl>. Either the specified URL does not point to a server that is running Team Foundation Server, the server is not available, or the service account for SharePoint Products does not have sufficient permissions on that server. The service account for SharePoint Products might not have been added to the required group in Team Foundation Server. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=254457).. This error must be corrected before you can grant access between Team Foundation Server and the SharePoint Web application. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=254457).
*******************************************************************************************************


SharePoint Application pool user for SharePoint central admin and SharePoint Web Application for TFS, is required to be in TFS SharePoint Web Application Services group.
Go to TFS Administration Console in TFS AT and add SharePoint Application pool user to SharePoint Web Application Services group.

This will allow to grant access to SharePoint in a remote server for TFS.

Resolve - TF255050: A connection cannot be made to the Report Server WMI provider

When setting up reporting services in a remote server for TFS below error might occur.
*******************************************************************************************************
TF255050: A connection cannot be made to the Report Server WMI provider. Verify the following:
1. You have entered the correct name for the server, including the instance name.
2. The Windows Management Instrumentation service is running on tfsssrs.
3. The service is not blocked by Windows Firewall.
4. You have the required permissions to connect.
Details:
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
*******************************************************************************************************

Verify reporting services running and all ports as specified in the “Ports required for installation of Team Foundation Server” are open.





WMI Service is running in report server.

WMI Service is allowed in Firewall of the report server.

Report server URLs populated after all above set.

Enable Excel Reports for Team Project When SSRS Configured Later for TFS

If the TFS server is setup and the reporting services are not configured, the newly created team projects will not have excel reports enabled in SharePoint project portal.

Once the TFS is configured with SSRS the Excel reports for SharePoint project portal can be configured following below instructions.
Check reporting is configured properly in TFS. Verify project collection configured for reports.



Go to the Project SharePoint portal settings.

Click Manage site features.

Deactivate Agile Dashboard.


Activate Agile Dashboard with Excel Reporting.

Excel reports are available for the SharePoint portal.



Dashboard is enabled with SSRS reports.

Passing Parameters to PS/DSC Scripts in vNext Release Templates – VS Release Management

In the vNext Release Templates there are few ways to pass parameters/configuration variables to a PS/DSC Script. Variables in five different levels can be used for this.
Global Variables – Defined at the Release Management Server level in Administration – > Settings – > Configuration Variables.

Server Variables – Defined at the Registered Target Server level in Configure Paths –> Servers –> Server –> Configuration Variables. The values defined in Server Variables will override the values of the variables defined in Global Variables.

Component Variables – Defined at the Release Component level in Configure Apps –> Components –> Component –> Configuration Variables. The values defined in Component Variables will override the values of the variables defined in Global and Server Variables.

Action Variables – Defined in the Release Template, Deploy Using PS/DSC action in Configure Apps –> vNext Release Templates –> vNext Release Template –> Deploy Using PS/DSC. The values defined in Action Variables will override the values of the variables defined in Global, Server and Component Variables.

All above four levels of Configuration Variables are supported with encrypted value by selecting the type Encrypted.

 
These variables can be managed in the release template using Configuration Variables and Resource Variables.



Variables in Configuration Script File  - These variables will be defined in a configuration script file and should be available with the build output. These files will allow to source control configuration variables for each stage. There is no encryption for the variables defined in a script file. The values defined in Script File Variables will override the values of the variables defined in Global, Server,  Component and Action Variables.


Passing Action Variables
To pass the Customer Name to the below script Action Variable can be used.

This script should be available in build output.

Component Should be setup to download the script to target server.

In the Deploy Using PS/DSC action the configuration variable CustomerName can be set like below.

When release triggered the scripts get downloaded to target server.

The value passed for CustomerName can be verified in the log.


Passing Component Variables
When component variable is only set it is getting passed to the script.



Action Variable Value Overriding Component Variable Value
When both Component and Action variable values set action variable value gets the precedence.



Setting Variables Using Script File
Configuration Variables can be set using a Script File as well.

This configuration variable script file should be available in build output.

When release triggered configuration variable script file is also copied to the target server.

Release PS/DSC script uses the configuration variable value defined in the configuration script file.


Script File Values Overriding Action and Component Variable Values
When value is defined for configuration variable in Component, Action and in a Configuration File the Configuration File get the precedence.