New release: SharePoint v4.0, the next major release!

This post has been republished via RSS; it originally appeared at: SharePointDsc articles.

The goal was to release a new version of SharePointDsc a little sooner, but the transition to the new CD/CI pipeline messed up our planning a little :) Finally the time has come to release this new version.

 

The largest change to SharePointDsc v4.0  is the addition of SQL authentication support. This addition allows SharePoint to be installed on Azure SQL Managed Instances.

 

A major release also gives us the possibility to implement breaking changes. If you kept an eye on the SharePointDsc issue list, there have been a few of them which all got implemented in this release. This does however mean that v3.x configuration might break! So please make sure you test you configurations well before deploying this new version to your production environments!

 

You can find the SharePointDsc v4.0 in the PowerShell Gallery!

 

NOTE: We can always use additional help in making SharePointDsc even better. So if you are interested in contributing to SharePointDsc, check-out the open issues in the issue list, check-out this post in our Wiki or leave a comment on this blog post.

Improvement/Fixes in v4.0:

 

Added

  • SharePointDsc
    • Added verbose logging of the test results in the Test method
    • Added function to create SharePointDsc event log and add log entries
    • Added the logging of all test results to the new SharePointDsc event log
    • Added support in several resources for creating/connecting to farm and service applications using a (single) SQL-based credential instead of the default Windows credentials. Needed when e.g. using Azure SQL Managed Instance as SharePoint's database server. UseSQLAuthentication and DatabaseCredentials parameters will need to be considered.

Changed

  • SPTrustedRootAuthority
    • It is now possible to specify both CertificateFilePath and CertificateThumbprint so that the certificate thumbprint can be verified before importing.
  • SPTrustedSecurityTokenIssuer
    • It is now possible to specify both SigningCertificateFilePath and SigningCertificateThumbprint so that the certificate thumbprint can be verified before importing.

The following changes will break v3.x and earlier configurations that use these resources:

  • SPManagedMetaDataServiceAppDefault
    • Updated resource to allow the configuration of default per service application proxy groups instead of per farm
  • SPSearchContentSource
    • Discontinued CrawlEverything, CrawlFirstOnly and null as allowable CrawlSetting values for a SharePoint based content source, requiring CrawlVirtualServers or CrawlSites
  • SPUserProfileServiceApp
    • Changed the MySiteHostLocation parameter to a required parameter
  • SPWebAppAuthentication
    • Updated resource to add support for Basic Authentication

Fixed

  • SPFarmSolution
    • Corrected bug running Solution Job wait for an Absent solution.
    • Corrected bug trying to remove an already Absent solution.
  • SPSearchAuthoritativePage
    • Corrected bug when checking for an existing Demoted Action
  • SPWebAppAuthentication
    • Updated to support passing of null/empty collections for zones not utilized.

Removed

The following changes will break v3.x and earlier configurations that use these resources:

  • SPSearchServiceApp
    • Removed the WindowsServiceAccount parameter that was depricated in v3.1
  • SPUserProfileSyncService
    • Removed the FarmAccount parameter that was depricated in v2.2

 

A huge thanks to the following guys for contributing to this project:
Jens Otto Hatlevold, Brian Lalancette and Russel Anderson

 

Also a huge thanks to everybody who submitted issues and all that support this project. It wasn’t possible without all of your help!

 

For more information about how to install SharePointDsc, check our Readme.md.

Let us know in the comments what you think of this release! If you find any issues, please submit them in the issue list on GitHub.

 

Happy SharePointing!!

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.