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
Details of the scenario you tried and the problem that is occurring
The issue seems to happen when I try to put more than one language using a string array. It works fine for one language or "*" but as soon as I use an array with multiple languages the following happens :
No matter if the inital test of the ressource is true or false, it will go for the set script (even if languages are already in the desired state, in which case each language can be seen in the verbose log).
When the set script is applied, it goes without errors and WSUS configuration is actually changed to the desired language parameter.
The final test script returns false in any case, making the whole run return in error.
Verbose logs showing the problem
VERBOSE: [MyServerName]: LCM: [ StartResource ] [[UpdateServicesServer]WSUS_Service]
VERBOSE: [MyServerName]: LCM: [ StartTest ] [[UpdateServicesServer]WSUS_Service]
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer is Present
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer configuration
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer subscription
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer SQL Server
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer SQL Server is MICROSOFT##WID
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer content directory
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer content directory is F:\WSUS
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer update improvement program
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer content update improvement program is False
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer upstream server
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer upstream server is upstream.domain.com,
port 8530, use SSL False, replica True
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer languages
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer languages are fr
en
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer classifications
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer classifications are e6cf1350-c01b-414d-a61f-263d14d133b4 e0789628-ce08-4437-be74-2495b842f43b 0fa1201d-4330-4fa8-8ae9-b877473b6441
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer products
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer products are Office Windows
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer synchronization settings
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer synchronize automatically is True
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer synchronize automatically time of day is 00:00:00
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer number of synchronizations per day is 1
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer client targeting mode is Client
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Languages test failed
VERBOSE: [MyServerName]: LCM: [ EndTest ] [[UpdateServicesServer]WSUS_Service] in2.2350 seconds.
VERBOSE: [MyServerName]: LCM: [ StartSet ] [[UpdateServicesServer]WSUS_Service]
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Configuring WSUS
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Check for previous configuration change
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Configuring WSUS Update Improvement Program
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Configuring WSUS Upstream Server
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Configuring WSUS no proxy server
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Setting WSUS languages
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Setting WSUS products
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Setting WSUS classifications
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Setting WSUS synchronization schedule
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer is Present
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer configuration
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer subscription
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer SQL Server
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer SQL Server is MICROSOFT##WID
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer content directory
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer content directory is F:\WSUS
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer update improvement program
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer content update improvement program is False
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer upstream server
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer upstream server is upstream.domain.com,
port 8530, use SSL False, replica True
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer languages
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer languages are fr
en
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer classifications
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer classifications are e6cf1350-c01b-414d-a61f-263d14d133b4 e0789628-ce08-4437-be74-2495b842f43b 0fa1201d-4330-4fa8-8ae9-b877473b6441
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer products
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer products are Office Windows
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Getting WSUSServer synchronization settings
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer synchronize automatically is True
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer synchronize automatically time of day is 00:00:00
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer number of synchronizations per day is 1
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] WSUSServer client targeting mode is Client
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Languages test failed
VERBOSE: [MyServerName]: [[UpdateServicesServer]WSUS_Service] Test-TargetResouce returned false after calling set. | ErrorType: MSFT_UpdateServicesServer.TestFailedAfterSet
VERBOSE: [MyServerName]: LCM: [ EndSet ] [[UpdateServicesServer]WSUS_Service] in0.7030 seconds.
PowerShell DSC resource MSFT_UpdateServicesServer failed to execute Set-TargetResource functionality with error message: Test-TargetResouce returned false after calling set.
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : localhost
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
UpdateServicesServer "WSUS_Service" {
Ensure ="Present"
ContentDir ="F:\WSUS"
Languages =$Languages# This is a verified string array
UpdateImprovementProgram =$false
SynchronizeAutomatically =$true
SynchronizationsPerDay =1
SynchronizeAutomaticallyTimeOfDay = (New-TimeSpan-Hours 0).ToString()
UpstreamServerName ="upstream.domain.com"
UpstreamServerPort =8530
UpstreamServerReplica =$true
DependsOn =@("[WindowsFeature]WSUS_Feature","[File]WSUS_Folder")
}
In the previous DSC log the desired languages are "fr" and "en".
The operating system the target node is running
OsName : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture : 64-bit
WindowsVersion : 1809
WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage : en-US
OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
Name Value
---------
PSVersion 5.1.17763.771
PSEdition Desktop
PSCompatibleVersions {1.0,2.0,3.0,4.0...}
BuildVersion 10.0.17763.771
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)
1.1.0.0
The text was updated successfully, but these errors were encountered:
Details of the scenario you tried and the problem that is occurring
The issue seems to happen when I try to put more than one language using a string array. It works fine for one language or "*" but as soon as I use an array with multiple languages the following happens :
No matter if the inital test of the ressource is true or false, it will go for the set script (even if languages are already in the desired state, in which case each language can be seen in the verbose log).
When the set script is applied, it goes without errors and WSUS configuration is actually changed to the desired language parameter.
The final test script returns false in any case, making the whole run return in error.
Verbose logs showing the problem
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
In the previous DSC log the desired languages are "fr" and "en".
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
1.1.0.0
The text was updated successfully, but these errors were encountered: