profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ykuijs/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Yorick Kuijs ykuijs @Microsoft The Netherlands SharePoint/Microsoft 365 Customer Engineer

microsoft/Microsoft365DSC 508

Manages, configures, extracts and monitors Microsoft 365 tenant configurations

microsoft/xDownloadFile 7

PowerShell DSC module to download a file from the web

ykuijs/Powershell 3

Various Powershell scripts

ykuijs/azure-quickstart-templates 0

Azure Quickstart Templates

ykuijs/CertificateDsc 0

DSC resources to simplify administration of certificates on a Windows Server.

ykuijs/CommonTasks 0

DSC Configuration (Composite Resource) for demo DSC and Datum

ykuijs/ComputerManagementDsc 0

DSC resources for for configuration of a Windows computer. These DSC resources allow you to perform computer management tasks, such as renaming the computer, joining a domain and scheduling tasks as well as configuring items such as virtual memory, event logs, time zones and power settings.

ykuijs/cSchannel 0

cSchannel Dsc Resource to modify SSL endpoint configuration

issue commentdsccommunity/SharePointDsc

SPFarmAdministrators: Resource fails with error message: An item with the same key has already been added

Hi @luigilink, do you have the possibility to test the following update: Replace the content in Import-SPPowerShellSnapIn.ps1 file with the following code and reproduce the issue

$stack = Get-PSCallStack

if ($stack[1].Position.Text -eq 'Export-SPConfiguration')
{
    if (-not (Get-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue))
    {
        Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
    }
}

PwrKjll

comment created time in 9 days

issue commentdsccommunity/SharePointDsc

SPFarmAdministrators: Resource fails with error message: An item with the same key has already been added

Hi @luigilink, the issue here is that SharePoint is still using snapins (to be changed in SharePoint Server Subscription Edition!!!).

So far I do not have a solution yet, but might have an idea how to resolve this issue. Have to find some time to test if this will work.

The workaround you are describing will work

PwrKjll

comment created time in 10 days

PullRequestReviewEvent
GollumEvent
GollumEvent

push eventykuijs/SharePointDsc

dscbot

commit sha 19d44588c1cb7dcb881ffd736cba0eaacf969abd

Updating ChangeLog since v4.8.0 +semver:skip

view details

Yorick Kuijs

commit sha fbd52e9c6e81e6d26e4c62768f9956603da51c86

Merge pull request #1344 from dsccommunity/updateChangelogAfterv4.8.0 Updating ChangeLog since release of v4.8.0

view details

push time in 16 days

push eventdsccommunity/SharePointDsc

dscbot

commit sha 19d44588c1cb7dcb881ffd736cba0eaacf969abd

Updating ChangeLog since v4.8.0 +semver:skip

view details

Yorick Kuijs

commit sha fbd52e9c6e81e6d26e4c62768f9956603da51c86

Merge pull request #1344 from dsccommunity/updateChangelogAfterv4.8.0 Updating ChangeLog since release of v4.8.0

view details

push time in 16 days

created tagdsccommunity/SharePointDsc

tagv4.8.0

The SharePointDsc PowerShell module provides DSC resources that can be used to deploy and manage a SharePoint farm

created time in 16 days

push eventykuijs/SharePointDsc

Yorick Kuijs

commit sha 5e150dfc38d1d732ec444cfd4a4ea146a2381fb8

Merge pull request #1343 from ykuijs/master [SPTrustedIdentityTokenIssuer] Fixes issue with checking incorrect IdentifierClaim

view details

push time in 16 days

push eventdsccommunity/SharePointDsc

Yorick Kuijs

commit sha 478c65f9075bec4e8fa48e2597e3662af090cf31

Fixes #1238

view details

Yorick Kuijs

commit sha 5e150dfc38d1d732ec444cfd4a4ea146a2381fb8

Merge pull request #1343 from ykuijs/master [SPTrustedIdentityTokenIssuer] Fixes issue with checking incorrect IdentifierClaim

view details

push time in 16 days

PR merged dsccommunity/SharePointDsc

[SPTrustedIdentityTokenIssuer] Fixes issue with checking incorrect IdentifierClaim

<!-- Thanks for submitting a Pull Request (PR) to this project. Your contribution to this project is greatly appreciated!

Please prefix the PR title with the resource name, e.g. 'ResourceName: My short description'.
If this is a breaking change, then also prefix the PR title with 'BREAKING CHANGE:',
e.g. 'BREAKING CHANGE: ResourceName: My short description'.

You may remove this comment block, and the other comment blocks, but please keep the headers
and the task list.

-->

Pull Request (PR) description

This PR fixes an issue with checking incorrect IdentifierClaim in SPTrustedIdentityTokenIssuer

This Pull Request (PR) fixes the following issues

  • Fixes #1328

Task list

<!-- To aid community reviewers in reviewing and merging your PR, please take the time to run through the below checklist and make sure your PR has everything updated as required.

Change to [x] for each task in the task list that applies to your PR. For those task that
don't apply to you PR, leave those as is.

-->

  • [x] Added an entry to the change log under the Unreleased section of the file CHANGELOG.md. Entry should say what was changed and how that affects users (if applicable), and reference the issue being resolved (if applicable).
  • [x] Resource documentation added/updated in README.md.
  • [x] Resource parameter descriptions added/updated in README.md, schema.mof and comment-based help.
  • [x] Comment-based help added/updated.
  • [x] Localization strings added/updated in all localization files as appropriate.
  • [x] Examples appropriately added/updated.
  • [x] Unit tests added/updated. See DSC Community Testing Guidelines.
  • [x] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
  • [x] New/changed code adheres to DSC Community Style Guidelines.

<!-- Reviewable:start -->

This change is <img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/> <!-- Reviewable:end -->

+7 -5

1 comment

3 changed files

ykuijs

pr closed time in 16 days

issue closeddsccommunity/SharePointDsc

Identifierclaim in SPTrustedIdentityTokenIssuer

I'm trying to configure an SPTrustedIdentityTokenIssuer but I always get the error:

IdentifierClaim does not match any claim type specified in ClaimsMappings.

What am I missing?

       SPTrustedIdentityTokenIssuer AzureAD
        {
            Name                = "AzureAD";
            Description         = "Azure AD Identity provider";
            Realm               = "urn:sharepoint:sp1";
            SignInUrl           = "https://login.microsoftonline.com/[GUID removed]/wsfed";
            IdentifierClaim     = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name";
            ClaimsMappings        = @(
                MSFT_SPClaimTypeMapping{
                    Name = "name";
                    IncomingClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name";
                    LocalClaimType ="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn";
                }
                MSFT_SPClaimTypeMapping{
                    Name = "Email";
                    IncomingClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress";
                }
                MSFT_SPClaimTypeMapping{
                    Name = "Role";
                    IncomingClaimType = "http://schemas.microsoft.com/ws/2008/06/identity/claims/role";
                }
            )
            SigningCertificateFilePath = "C:\cert.cer";
            Ensure                = "Present";
            PsDscRunAsCredential  = $SPSetupAccount;
        }

closed time in 16 days

bartvermeersch

issue commentdsccommunity/SharePointDsc

SPUserProfileServiceApp: Error with Test or Get after successfull Set with no MySiteHostLocation

Hi @julmsy, thanks for providing such a detailed report. One question though: Can you please share the full Verbose output for this resource? I would like to see where exactly this goes wrong.

wmaniek123

comment created time in 17 days

PR opened dsccommunity/SharePointDsc

[SPTrustedIdentityTokenIssuer] Fixes issue with checking incorrect IdentifierClaim

<!-- Thanks for submitting a Pull Request (PR) to this project. Your contribution to this project is greatly appreciated!

Please prefix the PR title with the resource name, e.g. 'ResourceName: My short description'.
If this is a breaking change, then also prefix the PR title with 'BREAKING CHANGE:',
e.g. 'BREAKING CHANGE: ResourceName: My short description'.

You may remove this comment block, and the other comment blocks, but please keep the headers
and the task list.

-->

Pull Request (PR) description

This PR fixes an issue with checking incorrect IdentifierClaim in SPTrustedIdentityTokenIssuer

This Pull Request (PR) fixes the following issues

  • Fixes #1328

Task list

<!-- To aid community reviewers in reviewing and merging your PR, please take the time to run through the below checklist and make sure your PR has everything updated as required.

Change to [x] for each task in the task list that applies to your PR. For those task that
don't apply to you PR, leave those as is.

-->

  • [x] Added an entry to the change log under the Unreleased section of the file CHANGELOG.md. Entry should say what was changed and how that affects users (if applicable), and reference the issue being resolved (if applicable).
  • [x] Resource documentation added/updated in README.md.
  • [x] Resource parameter descriptions added/updated in README.md, schema.mof and comment-based help.
  • [x] Comment-based help added/updated.
  • [x] Localization strings added/updated in all localization files as appropriate.
  • [x] Examples appropriately added/updated.
  • [x] Unit tests added/updated. See DSC Community Testing Guidelines.
  • [x] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
  • [x] New/changed code adheres to DSC Community Style Guidelines.
+7 -5

0 comment

3 changed files

pr created time in 17 days

push eventykuijs/SharePointDsc

Yorick Kuijs

commit sha 478c65f9075bec4e8fa48e2597e3662af090cf31

Fixes #1238

view details

push time in 17 days

issue commentdsccommunity/SharePointDsc

Identifierclaim in SPTrustedIdentityTokenIssuer

Found the root cause for this issue:

In the Set method, this code creates an array with Claims Mappings: https://github.com/dsccommunity/SharePointDsc/blob/8214236e27d0a67c1fd5acea64d889dd38373c0e/SharePointDsc/DSCResources/MSFT_SPTrustedIdentityTokenIssuer/MSFT_SPTrustedIdentityTokenIssuer.psm1#L283-L299

The next block of code then checks if the specified IdentifierClaim matches a MappedClaimType in any of the claims in the array: https://github.com/dsccommunity/SharePointDsc/blob/8214236e27d0a67c1fd5acea64d889dd38373c0e/SharePointDsc/DSCResources/MSFT_SPTrustedIdentityTokenIssuer/MSFT_SPTrustedIdentityTokenIssuer.psm1#L283-L299

This is where the code fails. In the desired config specified by the user, the value of property InputClaimType matches the IdentifierClaim, but the LocalClaimType matches the property MappedClaimType, so $mappings is $null and an exception is thrown:

Desired Configuration:

    IdentifierClaim     = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name";
    ClaimsMappings        = @(
        @{
            Name = "name";
            IncomingClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name";
            LocalClaimType ="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn";
        }
        @{
            Name = "Email";
            IncomingClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress";
        }
        @{
            Name = "Role";
            IncomingClaimType = "http://schemas.microsoft.com/ws/2008/06/identity/claims/role";
        }
    )

Created claims in array:

DisplayName                    : name
InputClaimType                 : http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
MappedClaimType                : http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn
IsIdentityClaim                : False
AcceptOnlyKnownClaimValues     : False
ClaimValueModificationAction   : None
ClaimValueModificationArgument :
KnownClaimValues               : {}
UpgradedPersistedProperties    :

Just check with a colleague and according to him you should use the upn claim as identifier instead of the name claim. So your config should be:

       SPTrustedIdentityTokenIssuer AzureAD
        {
            Name                = "AzureAD";
            Description         = "Azure AD Identity provider";
            Realm               = "urn:sharepoint:sp1";
            SignInUrl           = "https://login.microsoftonline.com/[GUID removed]/wsfed";
            IdentifierClaim     = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn";
            ClaimsMappings        = @(
                MSFT_SPClaimTypeMapping{
                    Name = "name";
                    IncomingClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name";
                    LocalClaimType ="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn";
                }
                MSFT_SPClaimTypeMapping{
                    Name = "Email";
                    IncomingClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress";
                }
                MSFT_SPClaimTypeMapping{
                    Name = "Role";
                    IncomingClaimType = "http://schemas.microsoft.com/ws/2008/06/identity/claims/role";
                }
            )
            SigningCertificateFilePath = "C:\cert.cer";
            Ensure                = "Present";
            PsDscRunAsCredential  = $SPSetupAccount;
        }

@bartvermeersch, can you change your config can validate that deploying your config then works?

bartvermeersch

comment created time in 17 days

issue commentdsccommunity/SharePointDsc

Identifierclaim in SPTrustedIdentityTokenIssuer

@bartvermeersch Could you provide the Verbose output, so I can check the code where this goes wrong?

bartvermeersch

comment created time in 17 days

issue commentdsccommunity/SharePointDsc

SP_List - New Resource Proposal

Agree with Andi, really interested in the examples.

In general: I understand that there are use cases where having this resource will be usable, but at the same time the resource will then also be used by other admins to create lists who will end up in conflicts with users: The admin configures a list and a user updates that same list. Implementing these use cases with solutions like PnP PowerShell sounds like a better solution here.

kilasuit

comment created time in 17 days

issue commentdsccommunity/SharePointDsc

Can't create Site Collection in SharePoint 2019

Issue will be fixed in v4.8, which will be released later today.

pstork

comment created time in 17 days

push eventykuijs/SharePointDsc

Yorick Kuijs

commit sha 7de1e46d3caa2f9755a50af72a811803f1d668d2

Fixed #990 and added logging to SPSearchServiceApp

view details

Yorick Kuijs

commit sha 8214236e27d0a67c1fd5acea64d889dd38373c0e

Merge pull request #1342 from ykuijs/bugfix Fixed #990 and added logging to SPSearchServiceApp

view details

push time in 17 days

PR merged dsccommunity/SharePointDsc

Fixed #990 and added logging to SPSearchServiceApp

<!-- Thanks for submitting a Pull Request (PR) to this project. Your contribution to this project is greatly appreciated!

Please prefix the PR title with the resource name, e.g. 'ResourceName: My short description'.
If this is a breaking change, then also prefix the PR title with 'BREAKING CHANGE:',
e.g. 'BREAKING CHANGE: ResourceName: My short description'.

You may remove this comment block, and the other comment blocks, but please keep the headers
and the task list.

-->

Pull Request (PR) description

This PR fixes issue 990, where the following error was thrown if a site collection was created immediately after the farm was created: "Invalid field name. {cbb92da4-fd46-4c7d-af6c-3128c2a5576e}"

This Pull Request (PR) fixes the following issues

  • Fixes #990

Task list

<!-- To aid community reviewers in reviewing and merging your PR, please take the time to run through the below checklist and make sure your PR has everything updated as required.

Change to [x] for each task in the task list that applies to your PR. For those task that
don't apply to you PR, leave those as is.

-->

  • [x] Added an entry to the change log under the Unreleased section of the file CHANGELOG.md. Entry should say what was changed and how that affects users (if applicable), and reference the issue being resolved (if applicable).
  • [x] Resource documentation added/updated in README.md.
  • [x] Resource parameter descriptions added/updated in README.md, schema.mof and comment-based help.
  • [x] Comment-based help added/updated.
  • [x] Localization strings added/updated in all localization files as appropriate.
  • [x] Examples appropriately added/updated.
  • [x] Unit tests added/updated. See DSC Community Testing Guidelines.
  • [x] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
  • [x] New/changed code adheres to DSC Community Style Guidelines.

<!-- Reviewable:start -->

This change is <img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/> <!-- Reviewable:end -->

+65 -3

1 comment

4 changed files

ykuijs

pr closed time in 17 days

push eventdsccommunity/SharePointDsc

Yorick Kuijs

commit sha 7de1e46d3caa2f9755a50af72a811803f1d668d2

Fixed #990 and added logging to SPSearchServiceApp

view details

Yorick Kuijs

commit sha 8214236e27d0a67c1fd5acea64d889dd38373c0e

Merge pull request #1342 from ykuijs/bugfix Fixed #990 and added logging to SPSearchServiceApp

view details

push time in 17 days

issue closeddsccommunity/SharePointDsc

Can't create Site Collection in SharePoint 2019

<!-- Your feedback and support is greatly appreciated, thanks for contributing!

ISSUE TITLE:
SPSite: Creating a new site collection in SharePoint 2019 throws an Invalid field name error

ISSUE DESCRIPTION (this template):
NOTE! Sensitive information should be obfuscated.

PLEASE KEEP THE HEADERS.

-->

Details of the scenario you tried and the problem that is occurring

When using SharePointDSC to create a Custom minrole server using the Azure SharePoint 2019 image it throws an error for every Site Collection I try to create. New-SPSite works normally outside of DSC. Site Collections with the same settings can be built using New-SPSite in PowerShell or Central Admin

Verbose logs showing the problem

VERBOSE: [2018-11-29 14:11:35Z] [VERBOSE] [SPT019]:
[[SPSite]TeamSite] Performing the operation "New-SPSite" on target "http://Portal2019.Actualdomainname.com". VERBOSE: [2018-11-29 14:11:58Z] [ERROR] Invalid field name. {cbb92da4-fd46-4c7d-af6c-3128c2a5576e} http://portal2019.Actualdomainname.com

Suggested solution to the issue

This works fine in SharePoint 2013 and 2016. It only happens in 2019

The DSC configuration that is used to reproduce the issue (as detailed as possible)

           SPWebApplication SharePointSites
            {
                Name = "SharePoint Sites"
                ApplicationPool = $WebAppPoolName
                ApplicationPoolAccount = $WebPoolManagedAccountCreds.UserName
                AllowAnonymous = $false
                DatabaseName = "SP$($ReleaseYear)_Sites_Content"
                WebAppUrl = $PortalUrl
                Port = 80
                PsDscRunAsCredential = $SharePointSetupUserAccountcreds
                DependsOn = "[SPFarm]CreateSPFarm"
            }
        
            SPWebApplication OneDriveSites
            {
                Name = "OneDrive"
                ApplicationPool = $webAppPoolName
                ApplicationPoolAccount = $WebPoolManagedAccountCreds.UserName
                AllowAnonymous = $false
                DatabaseName = "SP$($ReleaseYear)_Sites_OneDrive" 
                HostHeader = "OneDrive$($ReleaseYear).$($AdDomainName)"
                WebAppUrl = $OneDriveUrl
                Port = 80
                PsDscRunAsCredential = $SharePointSetupUserAccountcreds
                DependsOn = "[SPFarm]CreateSPFarm"
            }

            SPCacheAccounts WebAppCacheAccounts
            {
                WebAppUrl = "http://Portal$($ReleaseYear).$($AdDomainName)"
                SuperUserAlias = "$DomainNetbiosName\$SuperUserAlias"
                SuperReaderAlias = "$DomainNetbiosName\$SuperReaderAlias"
                PsDscRunAsCredential = $SharePointSetupUserAccountcreds
                DependsOn = "[SPWebApplication]SharePointSites"
            }

            SPCacheAccounts OneDriveCacheAccounts
            {
                WebAppUrl = "http://oneDrive$($ReleaseYear).$($AdDomainName)"
                SuperUserAlias = "$DomainNetbiosName\$SuperUserAlias"
                SuperReaderAlias = "$DomainNetbiosName\$SuperReaderAlias"
                PsDscRunAsCredential = $SharePointSetupUserAccountcreds
                DependsOn = "[SPWebApplication]OneDriveSites"
            }

            SPSite TeamSite
            {
                Url = $PortalUrl
                OwnerAlias = "$($DomainNetbiosName)\$($SharePointSetupUserName)"
                Name = "Root Demo Site"
                Template = "STS#0"
                PsDscRunAsCredential = $SharePointSetupUserAccountcreds
                DependsOn = "[SPCacheAccounts]WebAppCacheAccounts"
            }

            SPSite MySiteHost
            {                             
                Url = $OneDriveUrl
                OwnerAlias = "$($DomainNetbiosName)\$($SharePointSetupUserName)"
                Name = "OneDrive"
                Template = "SPSMSITEHOST#0"
                PsDscRunAsCredential = $SharePointSetupUserAccountcreds
                DependsOn = "[SPCacheAccounts]OneDriveCacheAccounts"
            }
        }

The operating system the target node is running

<!-- I am using the regular SharePoint 2019 VM image in Azure.

OsName : Microsoft Windows Server 2016 Datacenter OsOperatingSystemSKU : DatacenterServerEdition OsArchitecture : 64-bit WindowsBuildLabEx : 14393.2551.amd64fre.rs1_release.181004-1309 OsLanguage : en-US OsMuiLanguages : {en-US} -->

Version of SharePoint that is used (e.g. SharePoint 2016)

SharePoint 2019

Version and build of PowerShell the target node is running

<!-- Name Value


PSVersion 5.1.14393.2515 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.14393.2515 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 -->

Version of the DSC module that was used ('dev' if using current dev branch)

SharePoint DSC 3.0.0.0

closed time in 17 days

pstork

PR opened dsccommunity/SharePointDsc

Fixed #990 and added logging to SPSearchServiceApp

<!-- Thanks for submitting a Pull Request (PR) to this project. Your contribution to this project is greatly appreciated!

Please prefix the PR title with the resource name, e.g. 'ResourceName: My short description'.
If this is a breaking change, then also prefix the PR title with 'BREAKING CHANGE:',
e.g. 'BREAKING CHANGE: ResourceName: My short description'.

You may remove this comment block, and the other comment blocks, but please keep the headers
and the task list.

-->

Pull Request (PR) description

This PR fixes issue 990, where the following error was thrown if a site collection was created immediately after the farm was created: "Invalid field name. {cbb92da4-fd46-4c7d-af6c-3128c2a5576e}"

This Pull Request (PR) fixes the following issues

  • Fixes #990

Task list

<!-- To aid community reviewers in reviewing and merging your PR, please take the time to run through the below checklist and make sure your PR has everything updated as required.

Change to [x] for each task in the task list that applies to your PR. For those task that
don't apply to you PR, leave those as is.

-->

  • [x] Added an entry to the change log under the Unreleased section of the file CHANGELOG.md. Entry should say what was changed and how that affects users (if applicable), and reference the issue being resolved (if applicable).
  • [x] Resource documentation added/updated in README.md.
  • [x] Resource parameter descriptions added/updated in README.md, schema.mof and comment-based help.
  • [x] Comment-based help added/updated.
  • [x] Localization strings added/updated in all localization files as appropriate.
  • [x] Examples appropriately added/updated.
  • [x] Unit tests added/updated. See DSC Community Testing Guidelines.
  • [x] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
  • [x] New/changed code adheres to DSC Community Style Guidelines.
+65 -3

0 comment

4 changed files

pr created time in 17 days

push eventykuijs/SharePointDsc

Yorick Kuijs

commit sha 7de1e46d3caa2f9755a50af72a811803f1d668d2

Fixed #990 and added logging to SPSearchServiceApp

view details

push time in 17 days

issue commentdsccommunity/SharePointDsc

Resource to upgrade content databases

That is what I said in the last paragraph 😉

The only way you have is to connect to SQL directly, which means you need permissions in SQL to request these sizes (not sure what permissions you need to request database sizes).

This requires permissions in SQL server to request these values, however not sure exactly what. I think we can use the sp_databases stored procedure to request the size (size column is in KB). More info can be found here: https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-databases-transact-sql?view=sql-server-ver15

This article indicates: Permissions: Requires CREATE DATABASE, or ALTER ANY DATABASE, or VIEW ANY DEFINITION permission, and must have access permission to the database. Cannot be denied VIEW ANY DEFINITION permission.

So we need to test if a default admin/setup account (which has dbcreator and securityadmin permissions) is able to execute this stored procedure.

ykuijs

comment created time in 20 days

push eventykuijs/SharePointDsc

Brian Farnhill

commit sha a1cb2718cee12ba75a995ba3a477907fe57010f6

Merge branch 'master' of https://github.com/PowerShell/SharePointDsc into release-1.2

view details

Brian Farnhill

commit sha 6c9d79d310faa4e1d1177b651283f4e5635702ac

Added doco

view details

Brian Farnhill

commit sha 869d9b6c6575864ba695d936bc73bf59307b7d2f

Removed preview

view details

Katie Keim

commit sha 08718bf1f6a12fdc6a204f5b2aa863c31909a586

Merge pull request #378 from PowerShell/release-1.2 Release 1.2

view details

Brian Farnhill

commit sha 1e447fd793ff1dd1476148a35c54c1219f3aa423

Merge branch 'master' of https://github.com/PowerShell/SharePointDsc into release-1.3

view details

Brian Farnhill

commit sha b6ba5320b00357365fa87a2fdd36c614fdb1a7d0

Updated documentation

view details

Katie Keim

commit sha 58559dedfc9756c0255a4c6564d9b62295bac33d

Merge pull request #409 from PowerShell/release-1.3 Release 1.3

view details

Brian Farnhill

commit sha f224287e87818c9884a4c45bf0b3bc4bf59e99b4

Merge branch 'master' of https://github.com/PowerShell/SharePointDsc into release-1.4

view details

Brian Farnhill

commit sha 80c192af69c5d63e13fecf3fd4ad0e33908d39aa

Updated documentation

view details

Brian Farnhill

commit sha 83e158415c8df671cdf449a92e3a59fd0dabbad5

Fixed version number

view details

Katie Keim

commit sha c4553e8e641ed5629ef7986ab48ac24539fc1511

Merge pull request #441 from PowerShell/release-1.4 Release 1.4

view details

Brian Farnhill

commit sha dfeb91928ce0c250682831a80d895c2985ad77fa

Merge branch 'master' of https://github.com/PowerShell/SharePointDsc into release-1.5

view details

Brian Farnhill

commit sha 67accd43e17277b8422005556c996d6bb7dc9726

Updates for release 1.5

view details

Katie Keim

commit sha 89d8949b90a237ddd134907e5f5d79befb354fb0

Merge pull request #471 from PowerShell/release-1.5 Release 1.5

view details

Brian Farnhill

commit sha 308530c637e6eb1ac7c7411f6fe91baf79e337de

Merge branch 'master' of https://github.com/PowerShell/SharePointDsc into release-1.6

view details

Brian Farnhill

commit sha 3e6426f23b2d6c9d136a551d752209ce3364a515

Updated module help

view details

Katie Keim

commit sha f247aa5efa15c6087c36baa8222af0ffe2474ece

Update release notes in manifest for 1.6

view details

Katie Keim

commit sha e693edb96ee25d4b3d7dbecd195a6fada8409184

Merge pull request #524 from PowerShell/release-1.6 Release 1.6

view details

Brian Farnhill

commit sha 726304a9ec47bc6ed6b4dbdd35846ffe2c3ede70

Merge from PowerShell/master

view details

Brian Farnhill

commit sha 211c0f457325204e03c1bcc096a724ba4eeb86e6

doco updates

view details

push time in 21 days

push eventykuijs/SharePointDsc

Yorick Kuijs

commit sha 2e8a6a8f1d723dabbd2c1220773b5ac0c6d83443

Fixing issue #1317

view details

Yorick Kuijs

commit sha e5117525b3ad63cc2fa36bde1dea701d1a18afb3

Fixed #1326

view details

Yorick Kuijs

commit sha 5e9635dd362f3bff08f14385c275e44af4255f17

Fixing #1322

view details

Yorick Kuijs

commit sha 7936d42cc86e69ae8d72a00dcd7c2ea63bcb1e2d

Fixing #1031

view details

Jens Otto Hatlevold

commit sha e29ed1e684ce18eaa66317c1a0fa065b89fe59ae

Fixed issue twith hardcoded database name and space

view details

Yorick Kuijs

commit sha 7df4f7da18960c949e6cc5bd9385aed8824a9db6

Updated review results

view details

Yorick Kuijs

commit sha 6e734374587e81912ff00694a27c159f95ba001d

Merge pull request #1330 from ykuijs/bugfix Bugfix PR

view details

Yorick Kuijs

commit sha 76d51bb9632b9b76282fa47a6651099fb429869a

Adds SPWebAppHttpThrottlingMonitor resource (no tests yet)

view details

Yorick Kuijs

commit sha 781026d595845813f46b5929493913a92c2b4c19

Added unit tests and various other updates

view details

Yorick Kuijs

commit sha 68584a4f4f7e7bee813320af884fc6f63f79f6fd

Updated DevOps agents to Windows Server 2022

view details

Yorick Kuijs

commit sha 8eb096a1da05ab74b665423cfe698da715b69e33

Corrected example

view details

Yorick Kuijs

commit sha 59601b60f4c4af4e0febaef50874e71d2203ebac

Merge pull request #1341 from ykuijs/SPWebAppHttpThrottlingMonitor

view details

Jens Otto Hatlevold

commit sha 2be61dd063d5ecf8cb49df185937a134a946c0d6

Fixed issue twith hardcoded database name and space

view details

Yorick Kuijs

commit sha 4040dfa79a44dbc9d1690f07608bbd0c3b5cd8ff

Fix unit tests

view details

Yorick Kuijs

commit sha 18b6deff35d2a03df9acf8d75125760ed2a720c2

Merge branch 'fix-spsearchserviceapp-dbname' of https://github.com/jensotto/SharePointDsc into fix-spsearchserviceapp-dbname

view details

Yorick Kuijs

commit sha 106cadebb191e2cc6d30ad8f58c09068900d1715

Merge pull request #1331 from jensotto/fix-spsearchserviceapp-dbname SPSearchServiceApp: Fixed issue with hardcoded database name and space

view details

Yorick Kuijs

commit sha 52d6d26c45149c4caac79cac143e8760593c18d1

First draft of SPSearchQueryRule

view details

Yorick Kuijs

commit sha e2640b08409492482906f87420e6809ff14d0906

Merge branch 'NewResource' of https://github.com/ykuijs/SharePointDsc into NewResource

view details

push time in 21 days

push eventykuijs/SharePointDsc

Jens Otto Hatlevold

commit sha e29ed1e684ce18eaa66317c1a0fa065b89fe59ae

Fixed issue twith hardcoded database name and space

view details

Yorick Kuijs

commit sha 6e734374587e81912ff00694a27c159f95ba001d

Merge pull request #1330 from ykuijs/bugfix Bugfix PR

view details

Yorick Kuijs

commit sha 76d51bb9632b9b76282fa47a6651099fb429869a

Adds SPWebAppHttpThrottlingMonitor resource (no tests yet)

view details

Yorick Kuijs

commit sha 781026d595845813f46b5929493913a92c2b4c19

Added unit tests and various other updates

view details

Yorick Kuijs

commit sha 68584a4f4f7e7bee813320af884fc6f63f79f6fd

Updated DevOps agents to Windows Server 2022

view details

Yorick Kuijs

commit sha 8eb096a1da05ab74b665423cfe698da715b69e33

Corrected example

view details

Yorick Kuijs

commit sha 59601b60f4c4af4e0febaef50874e71d2203ebac

Merge pull request #1341 from ykuijs/SPWebAppHttpThrottlingMonitor

view details

Jens Otto Hatlevold

commit sha 2be61dd063d5ecf8cb49df185937a134a946c0d6

Fixed issue twith hardcoded database name and space

view details

Yorick Kuijs

commit sha 4040dfa79a44dbc9d1690f07608bbd0c3b5cd8ff

Fix unit tests

view details

Yorick Kuijs

commit sha 18b6deff35d2a03df9acf8d75125760ed2a720c2

Merge branch 'fix-spsearchserviceapp-dbname' of https://github.com/jensotto/SharePointDsc into fix-spsearchserviceapp-dbname

view details

Yorick Kuijs

commit sha 106cadebb191e2cc6d30ad8f58c09068900d1715

Merge pull request #1331 from jensotto/fix-spsearchserviceapp-dbname SPSearchServiceApp: Fixed issue with hardcoded database name and space

view details

push time in 21 days