Release of version 2.4.0.0 of PSDscResources

DscResources/MSFT_GroupResource/MSFT_GroupResource.psm1

@@ -2156,7 +2156,7 @@ function Test-IsLocalMachine
         $Scope
     )
 
-    $localMachineScopes = @( '.', $env:computerName, 'localhost', '127.0.0.1', 'NT Authority' )
+    $localMachineScopes = @( '.', $env:computerName, 'localhost', '127.0.0.1', 'NT Authority', 'NT Service', 'BuiltIn' )
 
     if ($localMachineScopes -icontains $Scope)
     {

README.md

@@ -506,7 +506,7 @@ The following parameters will be the same for each process in the set:
     * WindowsProcess: Minor updates to integration tests
     * Registry: Fixed support for forward slashes in registry key names
 * Group:
-    * Group members in the "NT Authority" scope should now be resolved without an error. If you were seeing the error "Exception calling ".ctor" with "4" argument(s): "Server names cannot contain a space character."", this fix should resolve that error.
+    * Group members in the "NT Authority", "BuiltIn" and "NT Service" scopes should now be resolved without an error. If you were seeing the errors "Exception calling ".ctor" with "4" argument(s): "Server names cannot contain a space character."" or "Exception calling ".ctor" with "2" argument(s): "Server names cannot contain a space character."", this fix should resolve those errors. If you are still seeing one of the errors, there is probably another local scope we need to add. Please let us know.
     * The resource will no longer attempt to resolve group members if Members, MembersToInclude, and MembersToExclude are not specified.
 * Added Environment
 

Tests/Integration/MSFT_GroupResource_NoMembers.config.ps1

@@ -22,7 +22,7 @@ Configuration $ConfigurationName
 
     Import-DscResource -ModuleName 'PSDscResources'
 
-    Group Group1
+    Group Group3
     {
         GroupName = $GroupName
         Ensure = $Ensure