You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### The operating system the target node is running
<!--
Please provide as much as possible about the target node, for example
edition, version, build and language.
On OS with WMF 5.1 the following command can help get this information.
OsName : Microsoft Windows 10 Pro
OsOperatingSystemSKU : 48
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage : en-US
OsMuiLanguages : {en-US, de-DE}
-->
#### Version of the DSC module that was used ('dev' if using current dev branch)
1.22.216.1
The text was updated successfully, but these errors were encountered:
I think this issue is caused by the different attribute names for AutoExpandingArchive in Get- and Set-OrganizationConfig. In the set cmdlet, the attribute is -AutoExpandingArchive, but in the get cmdlet the property is AutoExpandingArchiveEnabled.
This line in the Get-TargetResource function looks for the property AutoExpandingArchive in the return of Get-OrganizationConfig, which never exists. This is why AutoExpandingArchive is always false.
if ($null -eq $ConfigSettings.AutoExpandingArchive) { $results.AutoExpandingArchive = $false }
Details of the scenario you tried and the problem that is occurring
When I run the following commands in the Power-Shell everything seems to be working fine for EXOOrganizationConfig:
but the following Power-Shell command
outputs the EXOOrganizationConfig not in desired state although the AutoExpandingArchiveEnabled is set from False to True
The DSC configuration that is used to reproduce the issue (as detailed as possible)
MOF file extract:
The text was updated successfully, but these errors were encountered: