This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
After several last minutes improvements and bugfixes this week, SharePointDsc v4.4 saw the daylight on Saturday November 14th. This version contains a lot of bugfixes that were fixed over the last period.
The biggest changes in this release are:
- The switch in SPFarm from a Lock database to a Lock table in the TempDB. This is done to fully support pre-created databases and the fact that most of the time this means that SharePoint admins don't have dbcreator permissions and therefore cannot create the Lock database.
- More diagnostic logging to the event log. When the code throws an exception, the error is now also logged to the custom SPDsc event log. This functionality will be extended over time. For more information see our previous blog post.
You can find the SharePointDsc v4.4 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.4:
- Added logging to the event log when the code throws an exception
- Added support for trusted domains to Test-SPDscIsADUser helper function
- Added documentation about a SharePoint 2019 installer issue
- Updated Convert-SPDscHashtableToString to output the username when parameter is a PSCredential
- Switched from creating a Lock database to a Lock table in the TempDB. This to allow the use of precreated databases.
- Updated code to properly output used credential parameters to verbose logging
- Added more explanation to documentation on which parameters are checked
- Added more explanation to documentation on using this resource
- Fixes issue where a CU installation wasn't registered properly in the config database. Added logic to run the Product Version timer job
- Fixes issue where applying a topology failed when the search service instance was disabled instead of offline
- Fixes issue where custom database name was no longer used since v4.3
- Fixed issue with Get-DscConfiguration which threw an error when only one item was returned by the Get method
- Fixed issue where provisioning the service app requires a second run to update all specified parameters
- Fixed issue configuring workflow service when no workflow service is currently configured
A huge thanks to the following guy for contributing to this project:
Jens Otto Hatlevold
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.