This post has been republished via RSS; it originally appeared at: SharePointDsc articles.
With the release of SharePointDsc v3.5, we implemented several logging/troubleshooting improvements. Besides adding more detailed logging output to several resources, all resources now also output the "Configured Values" and the "Desired Values". This makes it easier to spot any differences and the reason why the test method failed or succeeded.
This release is part of the DSC Resource Kit which was released on June 26th 2019.
Improvement/Fixes in v3.5:
Improvement/Fixes in v3.5:
- SharePointDsc generic
- Improved logging in all resource. They are now outputting the current and targeted values in the Test method.
- Updated various resources to comply with coding style guidelines.
- Updated the following resources to not return Null from the Get method anymore, but an hashtable which contains null values: SPDesignerSettings, SPDiagnosticLoggingSettings, SPFarmAdministrators, SPHealthAnalyzerRuleState, SPIrmSettings, SPOutgoingEmailSettings, SPPasswordChangeSettings, SPSearchTopology, SPServiceAppProxyGroup, SPTimerJobState, SPUserProfileSection, SPUserProfileSyncConnection, SPWebAppBlockedFileTypes, SPWebApplicationAppDomain, SPWebAppPolicy, SPWebAppSiteUseAndDeletion, SPWebAppThrottlingSettings, SPWordAutomationServiceApp.
- SPConfigWizard
- Added check to make sure the Config Wizard is only executed when all servers have the binaries installed.
- SPDistributedCacheService
- Added ability to check for incorrect service account.
- SPExcelServiceApp
- Fixes issue where Get method throws an error when the value of PrivateBytesMax and UnusedObjectAgeMax are negative values.
- SPFarm
- Throw error in Get method if CentralAdministrationUrl is HTTP.
- SPInstallPrereqs
- Fixed bug in version check, where lower versions would be detected as higher versions.
- SPProductUpdate
- Updated Readme to reflect the new patching possibilities added in v3.3.
- SPSecureStore
- Fixed issue where the test issue returned false is the service application didn't exist, but the database name/server parameter was specified.
- SPUserProfileSyncConnection
- Fixed issue where the parameter Server was checked in SP2016 but isn't used there and therefore always fails.
- SPWebAppAuthentication
- Updated the documentation to better explain the use of this resource when using Classic authentication.
A huge thanks to the following guys for contributing to this project:
Rob Christie and Jean-Cyril Drouhin
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!!