Introduction

The xSCSR module is a part of the Windows PowerShell Desired State Configuration (DSC) Resource Kit, which is a collection of DSC Resources produced by the PowerShell Team. This module contains the following resources for deploying System Center Service Reporting (SR):

• xSCSRServerSetup for installation of the SR server.
• xSCSRServerUpdatefor updating an SR server to Update Rollup 4.

All of the resources in the DSC Resource Kit are provided AS IS, and are not supported through any Microsoft standard support program or service. The ""x" in xSCSR stands for experimental, which means that these resources will be fix forward and monitored by the module owner(s).

Please leave comments, feature requests, and bug reports in the Q & A tab for this module.

If you would like to modify xSCSR module, feel free. When modifying, please update the module name, resource friendly name, and MOF class name (instructions below). As specified in the license, you may copy or modify this resource as long as they are used on the Windows Platform.

For more information about Windows PowerShell Desired State Configuration, check out the blog posts on the PowerShell Blog (this is a good starting point). There are also great community resources, such as PowerShell.org, or PowerShell Magazine. For more information on the DSC Resource Kit, check out this blog post.

Installation

To install the xSCSR module

• If you are using WMF4 / PowerShell Version 4: Unzip the content under $env:ProgramFiles\WindowsPowerShell\Modules folder
• If you are using WMF5 Preview: From an elevated PowerShell session run ‘Install-Module xSCSR’

To confirm installation:

• Run Get-DSCResource to see that xSCSRServerSetup and xSCSRServerUpdate are among the DSC Resources listed.
  

Requirements

This module requires PowerShell v4.0, which ships in Windows 8.1 or Windows Server 2012R2. To easily use PowerShell 4.0 on older operating systems, install WMF 4.0. Please read the installation instructions that are present on both the download page and the release notes for WMF 4.0.

Description

Details

The xSCSR module contains the following modules:

xSCSRServerSetup is used for installation of the SR server, and has the following properties:

• Ensure: KEY - An enumerated value (Present, Absent) that describes if the SR server is expected to be installed on the machine.
• SourcePath: REQUIRED - UNC path to the root of the source files for installation.
• SourceFolder: Folder within the source path containing the source files for installation.
• SetupCredential: REQUIRED - Credential to be used to perform the installation.
• SendCEIPReports: Binary, indicating whether or not to participate in the Customer Experience Improvement Program.
• UseMicrosoftUpdate: Binary, indicating whether or not to use Microsoft Update.
• InstallFolder: Folder to install to.
• DatabaseServer: REQUIRED - Name of the database server.
• DatabaseServerInstance: REQUIRED - Name of the SQL Server database instance to install to.
• RepositoryDatabaseName: Name of the usage repository database that already exists, or that Setup will create.
• StagingDatabaseName: Name of the usage staging database that already exists, or that Setup will create.
• DWDatabaseName: Name of the usage data warehouse database that already exists, or that Setup will create.
• AnalysisDatabaseServer: REQUIRED - Name of the server that is running SQL Server where the analysis database already exists, or where Setup will create it.
• AnalysisDatabaseServerInstance: REQUIRED - Name of the SQL Server analysis database instance to install to.
• AnalysisDatabaseName: Name of the analysis database that already exists, or that Setup will create.

xSCSRServerUpdate has the following properties:

• Ensure: KEY - An enumerated value that describes if the update is expected to be installed on the machine.
• SourcePath: REQUIRED - UNC path to the root of the source files for installation.
• SourceFolder: Folder within the source path containing the source files for installation.
• Credential: REQUIRED - Credential to be used to perform the installation.
• Update: Output display name of the update.

Renaming Requirements

When making changes to these resources, we suggest the following practice:

1. Update the following names by replacing MSFT with your company/community name and replacing the "x" with "c" (short for "Community") or another prefix of your choice:
   • Module name (ex: xSCSR becomes cSCSR)
   • Resource folder (ex: MSFT_xSCSRServerSetup becomes Contoso_cSCSRServerSetup)
   • Resource Name (ex: MSFT_xSCSRServerSetup becomes Contoso_cSCSRServerSetup)
   • Resource Friendly Name (ex: xSCSRServerSetup becomes cSCSRServerSetup)
   • MOF class name (ex: MSFT_xSCSRServerSetup becomes Contoso_cSCSRServerSetup)
   • Filename for the <resource>.schema.mof (ex: MSFT_xSCSRServerSetup.schema.mof becomes Contoso_cSCSRServerSetup.schema.mof)
2. Update module and metadata information in the module manifest
3. Update any configuration that use these resources

We reserve resource and module names without prefixes ("x" or "c") for future use (e.g. "MSFT_SCSRServerSetup" or "SCSRServerSetup"). If the next version of Windows Server ships with "MSFT_SCSRServerSetup" resources, we don't want to break any configurations that use any community modifications. Please keep a prefix such as "c" on all community modifications.

Versions

1.3.0.0

• Increased timeout for setup process to start to 60 seconds
• Added /norestart to xSCSRUpdate to allow DSC to control reboots

1.2.0.0

• Updated release with the following resources
  • xSCSRServerUpdate

1.1.0.0

• Initial release with the following resources
  • xSCSRServerSetup

Examples

Two example configurations are included in the Examples folder. Both examples also use the xSQLServer module. Note: the samples require the use of the Windows Management Framework (WMF) 5.0 Preview.

Single Server Installation: SCSR-SingleServer.ps1 installs SR including prerequisites and SQL on a single server.

Separate SQL: SCSR-SeperateSQL.ps1 installs SR on one server and SQL on a seperate server.

Note that both examples use the exact same Configuration and just modify the behavior based on input ConfigurationData.

In the Examples folder you will see a version of each file with "-TP" appended to the name. These are the equivalent examples for deployment of System Center Technical Preview on Windows Server Technical Preview.