This post has been republished via RSS; it originally appeared at: SharePointDsc articles.
On Monday October 22nd 2018, Microsoft released SharePoint 2019. Over the past months we have been working hard behind the scenes on testing SharePointDsc with this new version and making sure SharePointDsc is updated where required.
So, I am pleased to announce that, almost a year after the v2.0 release, the moment we have all been waiting for is finally here:
SharePointDsc v3.0 has been released this morning!
It will be published to the PowerShell Gallery later today.
This new major release contains many improvements/fixes, including several breaking changes! So, if you are upgrading from an earlier version of SharePointDsc, please make sure you update your existing configurations!
Improvement/Fixes in v3.0:
- Changes to SharePointDsc
- Added support for SharePoint 2019
- Added CredSSP requirement to the Readme files
- Added VSCode Support for running SharePoint 2019 unit tests
- Removed the deprecated resources SPCreateFarm and SPJoinFarm (replaced in v2.0 by SPFarm)
- Updated the Service Instance retrieval to be language independent
- Fixed check for Ensure=Absent in the Set method
- Added support for detecting updated installation of Microsoft Visual C++ 2015/2017 Redistributable (x64) for SharePoint 2016 and SharePoint 2019.
- Added support for Business Content Source Type
- New resource added
- Updated resource to make sure the presence of the service app proxy is checked and created if it does not exist
- The resource only tested for the Ensure parameter. Added more parameters
- Added support for specifying array of access levels.
- Changed implementation to use Grant-SPObjectSecurity with Replace switch instead of using a combination of Revoke-SPObjectSecurity and Grant-SPObjectSecurity
- Added all supported access levels as available values.
- Removed unknown access levels: Change Permissions, Write, and Read
- Removed obsolete parameters (MappingConnectionName, MappingPropertyName, MappingDirection) and introduced new parameter PropertyMappings
- Updated the check for successful creation of the service app to throw an error if this is not done correctly
Breaking changes in v3.0
The following changes will break v2.x and earlier configurations that use these
- Implemented IsSingleInstance parameter to force that the resource can only be used once in a configuration for the following resources:
- Standardized Url/WebApplication parameter to default WebAppUrl parameter for the following resources:
- Introduced new mandatory parameters
- SPSearchResultSource: Added option to create Result Sources at different scopes.
- SPServiceAppSecurity: Changed parameter AccessLevel to AccessLevels in MSFT_SPServiceAppSecurityEntry to support array of access levels.
- SPUserProfileProperty: New parameter PropertyMappings
A huge thanks to the following guys for contributing to this project:
Nik Charlebois, Brian Lalancette, Andi Krüger, Jens Otto Hatlevold, and Dave Wollerman
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.