JumpCloudModule v2.18 (Re-release)

[kmaranionjc]

Issues

• CUT-4565 - CUT-4565-Windows-Custom-Policy-Support

What does this solve?

The New/Set/Get-JCPolicy cmdlets now support the management of Windows - Custom MDM (OMA-URI) Policy. Multiple OMA-URI configurations can be specified using the -uriList parameter, for instance:
-uriList (@( @{format = "int"; uri = "a"; value = "5" }, @{format = "boolean"; uri = "b"; value = "true" } ))

Furthermore, administrators can edit, add, or remove individual OMA-URI settings within existing custom MDM policies.

Is there anything particularly tricky?

m/a

How should this be tested?

First, run these commands to get the templateId:
$policyTemplates = Get-JcSdkPolicyTemplate
$policyTemplate = $policyTemplates | Where-Object { $_.name -eq "custom_oma_uri_mdm_windows" }
$templateId = $policyTemplate.id
New-JCPolicy

1. Create a policy by passing a uriList:

$uriList = @(
                @{ uri = "a"; format = "int"; value = 2 },
                @{ uri = "b"; format = "string"; value = "test" },
                @{ uri = "c"; format = "boolean"; value = "true" }, # Corrected: $true is the boolean literal
                @{ uri = "d"; format = "float"; value = 2.5 } # Corrected: 2.5 is the float literal
                @{ uri = "e"; format = "xml"; value = "<xml>test</xml>" },
                @{ uri = "f"; format = "base64"; value = "dGVzdA==" }
            )

$newPolicy = New-JCPolicy -templateID $templateId -Name "Windows - Custom MDM Policy" -uriList $uriList

2. Test policy creation for each format with valid and invalid values. Invalid values should cause errors and stop policy creation.
3. Create policies without passing a uriList:
   New-JCPolicy -templateID $templateId -Name "Missing URI Policy"
   This utilizes the new private function, New-UriListItem.

Set-JCPolicy

1. Edit the first policy you created from using the New-JCPolicy with -uriList param

$testUriList = @(
                @{ uri = "testA"; format = "int"; value = 100 },
                @{ uri = "testB"; format = "string"; value = "example string" },
                @{ uri = "testC"; format = "boolean"; value = "false" },
                @{ uri = "testD"; format = "float"; value = 3.14159 },
                @{ uri = "testE"; format = "xml"; value = "<data><item>test data</item></data>" },
                @{ uri = "testF"; format = "base64"; value = "SGVsbG8gV29ybGQh" } # Base64 for "Hello World!"
            )
Set-JCPolicy -PolicyID $newPolicy.id -uriList $testUriList

Validate that each each values are edited
2. Edit policy with invalid values and format, ensure it throws an error and not continue.
3. Edit policy using the menu system

Get-JCPolicy

1. Get policy:

$getPolicy = Get-JCPolicy -id $newPolicy.id 
$getPolicy.values.value

[gweinjc]

Dont see any glaring issues with the release workflow