Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

windows_sharepoint

Module for managing SharePoint 2013
Project URLRSS FeedReport issues

12,438 downloads

11,040 latest version

1.9 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.0.7 (latest)
  • 0.0.6
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
released Feb 12th 2015
This version is compatible with:
  • Windows

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'jriviere-windows_sharepoint', '0.0.7'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jriviere-windows_sharepoint
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jriviere-windows_sharepoint --version 0.0.7

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: 2012, windwos, sharepoint, foundation, 2012r2, 2013

Documentation

jriviere/windows_sharepoint — version 0.0.7 Feb 12th 2015

windows_sharepoint

This is the windows_sharepoint module.

##Module Description

This module allow you to manage user and group in SharePoint 2013. Allow you to install and configure SharePoint 2013 You can found this module on the forge jriviere/windows_sharepoint or on GitHub

This module use the AutoSPInstaller Project to install and configure SharePoint. v3.96 (6 July 2014). This version have been modified to run with puppet.

All password will be automatically fill if you use Windows AD module and his XML file. The windows_ad module can be found in forge jriviere/windows_ad or on GitHub

The account used for installing SharePoint must be Admin local at least on each server, and SQL sysdbo or at least have SQL DB Creator and security admin rights Tested with : SharePoint Foundation 2013 SP1 SharePoint Standard 2013 SP1 SharePoint EnterPrise 2013 SP1

This module is only compatible with SharePoint 2013. Only tested with puppet agent 3.6.2, Windows Server 2012 R2

##Last Fix/Update V 0.0.7 :

  • Add -ea option on powershell command
  • Update the way to execute SharePoint installation

###Setup Requirements Depends on the following modules:

- ['puppetlabs/powershell', '>=1.0.2'](https://forge.puppetlabs.com/puppetlabs/powershell),
- ['puppetlabs/stdlib', '>= 4.2.1'](https://forge.puppetlabs.com/puppetlabs/stdlib)

##Usage

##SharePointInstall Class windows_sharepoint : Permit installation of SharePoint

class{'windows_sharepoint':
  languagepackspath     => "C:\\source\\LanguagePacks",   # path where we are going to take the updates and put them in the correct folder for autospinstaller (not yet implemented)
  updatespath           => "C:\\source\\Updates",         # path where we are going to take the extracted languagepacks and put them in the correct folder for autospinstaller. (Works)
  sppath                => "C:\\source\\sharepoint.exe",  # path where we will find the exe file of sharepoint Foundation
  dbserver              => "SQL_ALIAS",                   # the alias created by autospinstaller
  dbaliasinstance       => "COMPUTERNAME",
  setupaccountpassword  => "P@ssw0rd",
  spfarmaccount         => "spfarm",
  spapppoolaccount      => "spapppool",
  spservicesaccount     => "spservices",
  spsearchaccount       => "spsearch",
  spcrawlaccount        => "spcrawl",
  spsuperreaderaccount  => "spsuperreader",
  spsuperuseraccount    => "spsuperuser",
  spsyncaccount         => "spsyncaccount",                  # Mandatory with Standard and enterprise
  spusrprfpassword      => "spusrprfaccount",                # Mandatory with Standard and enterprise
  spexcelaccount        => "spexcelaccount",                 # Mandatory with enterprise
  key                   => "SYOUR-PRODU-CTKEY-OFSPS-2012S",
  passphrase            => "P@ssPhrase@2014",               #SharePoint Farm PassPhrase.Must be at least 8 charaters with upper character, lower character, numbers, specialcharacter (3 of this 4 categories)
  webappurl             => "https://localhost",
  applicationPool       => "Default AppPool",
  webappname            => "WebApp",
  webappport            => 443,
  webappdatabasename    => "Default_ContentDB",
  siteurl               => "https://localhost",
  sitecolname           => "Home",
  sitecollcid           => "1033",
  sitecollocale         => "en-us",
  sitecolowner          => "spfarm",
}

Parameters:

    $removedefaultwebapp         # If set to true this will delete the default created webapp

##webapplication Ressource windows_sharepoint::webapplication : Permit installation of SharePoint

windows_sharepoint::webapplication{"default - $webappname":
  url                    => "http://localhost",
  applicationpoolname    => "AppPool_TestPuppet",
  webappname             => "Test Puppet",
  databasename           => "SP2013_Content_TestPuppet",
  applicationpoolaccount => "s-spapppool",
  ensure                 => present,
  usessl                 => false,
  webappport             => 6789,
}

##user Resource: windows_sharepoint::user

windows_sharepoit{'SQLServer':
  username   => "Jerome",
  login      => 'jre',
  group      => "SharePoint Owners",
  weburl     => 'https://sharepoint/sites/jre',
  admin      => true,
}

Parameters:

    $username         # Fullname of the user
    $login            # SamAccountName
    $weburl           # URL of the site where we want to add user
    $group            # Group name where we want put the user
    $admin            # Is SiteColAdmin ? Default : false

##SP Group Resource: windows_sharepoint::group

    windows_sharepoit{'SharePoint Owners':
      group           => "SharePoint Owners",
      weburl          => 'https://sharepoint/sites/jre',
      permissionlevel => 'Full Control',
      ownername       => 'jre',
    }

Parameters:

    $weburl           # URL of the site where we want to add user
    $group            # Group name where we want put the user
    $permissionlevel  # Permissions for the group Full Control|Edit|Contribute|Read|Design
    $ownername        # Owner of the group
    $description      # group description

##webapplication Ressource windows_sharepoint::services::reporting : Allow installation and configuration of SharePoint reporting service integrated mode

    windows_sharepoint::services::reporting{"Reporting":
      databasename    => "ReportingServicesDB",
      databaseserver  => "SQL_ALIAS",
      serviceaccount  => "spservices",
    }

Parameters:

    $defaultsrvgrp    # Add the service to the default service app group. Default True
    $apppoolname      # App Pool name . The app pool will be created.
    $servicename      # Service Name. Default : SQL Server Reporting Service Application
    $proxyname        # Proxy Name. Default : SQL Server Reporting Service Application Proxy

Known issues

Please don't add a '/' after the WebApp URL and site url, if you do so AutoSpInstaller will throw an error and will not create the WebApp and site Coll.

The User profile Service Application will be installed but the synchronisation will not work. You have to remove the UPA Service and create another one manually. (Puppet can't get back the control with infinite powershell start-process instance :(, so I have to disable this steps. ). (Don't forget to give Replicate Right to the sync user.)

License

Apache License, Version 2.0

Contact

Jerome RIVIERE

Support

Please log tickets and issues at Github site