admin/PowerShell-PSDscResources
1
0
Fork 0
mirror of https://github.com/PowerShell/PSDscResources synced 2026-06-21 13:45:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add BuiltIn to list of local scopes

Browse Source
This commit is contained in:
Katie Keim
2017-02-02 17:47:37 -08:00
parent e9df7cde0f
commit ffd2a3ef7b
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DscResources/MSFT_GroupResource/MSFT_GroupResource.psm1
+1 -1
View File
@@ -2156,7 +2156,7 @@ function Test-IsLocalMachine
$Scope
)
$localMachineScopes = @( '.', $env:computerName, 'localhost', '127.0.0.1', 'NT Authority', 'NT Service' )
$localMachineScopes = @( '.', $env:computerName, 'localhost', '127.0.0.1', 'NT Authority', 'NT Service', 'BuiltIn' )
if ($localMachineScopes -icontains $Scope)
{
README.md
+1 -1
View File
@@ -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" 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.
* 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