Hello All,
Has anyone managed to create ARS scheduled task using New-QADObject cmdlet?
I tried to use following:
New-QADObject -Name $taskName -ParentContainer 'CN=Custom,CN=Scheduled Tasks,CN=Server Configuration,CN=Configuration' -Type edsScheduledTask -ObjectAttributes @{'edsaXMLSchedule' = $taskSchedule; 'edsaModule' = $taskModule}
The problem is with edsaModule value - it should be a GUID of script module, but it seems it's wrongly converted to OctetString.
For example, let's define script GUID as follows:
$taskModule = '5C798069-485C-49C3-B970-509EFB5D481B'
Active Roles sees following data in the request:
Details:
Attributes:
edsaModule
35-43-37-39-38-30-36-39-2D-34-38-35-43-2D-34-39-43-33-2D-42-39-37-30-2D-35-30-39-45-46-42-35-44-34-38-31-42
edsaXMLSchedule
<?xml version="1.0"?>
<Schedule><Daily><Every>1</Every><Start><Time>01:00:00.000</Time><Date>2022-09-13</Date></Start></Daily><MaxTime><Hours>0</Hours><Minutes>10</Minutes></MaxTime></Schedule>
objectClass
edsScheduledTask
This triggers an error: "Administrative Policy returned an error. Value does not fall within the expected range."
I would expect GUID to be converted to OctetString in this way:
5C798069-485C-49C3-B970-509EFB5D481B -> 69-80-79-5C-5C-48-C3-49-B9-70-50-9E-FB-5D-48-1B
When task is created manually, proper data is included in the request:
Details:
Attributes:
edsaModule
69-80-79-5C-5C-48-C3-49-B9-70-50-9E-FB-5D-48-1B
edsaXMLSchedule
<?xml version="1.0"?>
<Schedule><Daily><Every>1</Every><Start><Time>01:00:00.000</Time><Date>2022-09-13</Date></Start></Daily><MaxTime><Hours>0</Hours><Minutes>10</Minutes></MaxTime></Schedule>
objectClass
edsScheduledTask
Has anyone faced the same issue?