dsccommunity / dsccommunity/SharePointDsc
Least-privileged security model enabled after Oct 22 CU
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 246
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Problem description
After October 2022 CU we should run the following command after farm is created because the least-privileged model is automatically enabled. If this is not done then deleting web application in CA will fail to access denied error at least for setup account.
Get-SPDatabase | %{$_.GrantOwnerAccessToDatabaseAccount()}
Verbose logs
-
DSC configuration
-
Suggested solution
Could we add this command maybe to the SPFarm resource as a last part after farm is created
SharePoint version and build
SPSE October 2023 CU
Operating system the target node is running
-
PowerShell version and build the target node is running
-
SharePointDsc version
5.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SPFarm resource and the point where farm creation completes. Review the linked Microsoft guidance and determine how the requested Get-SPDatabase command fits into that lifecycle. Done means the command is handled after farm creation and the reported access-denied behavior can be checked against the October 2022 CU scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100