-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intune Windows Feature Update Profile - Handling for rollout settings #4614
Comments
This one is an oldie, I forgot you raised an issue for it since I also had raised another issue even earlier #3438. Even when creating this profile through the admin portal with start and end dates it's a pain in the neck, lots of trial and error until you select the correct dates and it let's you save so I'm OK with all your changes. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the issue
The resource
IntuneWindowsUpdateForbusinessFeatureUpdateProfileWindows10
is responsible for making Windows 10/11 upgrades available for a subset of devices. It contains a propertyRolloutSettigs
, that holds the following values:When exporting an existing policy with a
OfferStartDateTimeInUTC
(and optionally end time and interval) and reimporting the configuration in another tenant, the following exception will be thrown:The error occurs because the start time in the exported configuration is behind (current time + 2 days), which is required by the API to make the update available. This requirement cannot be changed. In my opinion, we should adjust the start time to the minimum required time and then create the policy.
Additionally, two more question arise with the handling:
Test-TargetResource
a better idea, with returningTrue
if both times are in the past?True
in that case means that the policy would have no effect on the environment and thus is compliant with when no policies exist.Test-TargetResource
would returnfalse
, which leads to us trying to update the policy's start time. But that won't work if the start time is in the past.I'm proposing the following resource handling changes:
Set-TargetResource
:Test-TargetResource
:Absent
, returnTrue
because creating a policy with start/end times in the past does not have any impact.True
because changing the start time to a date less than two days in the future is not possible.Microsoft 365 DSC Version
V1.24.417.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: