-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
[BUG] Python Error at Compliance Update #218
Comments
I did some new Tests (obvious ones I should have done before). I removed the Compliance Policy jsons and tried again. That worked with out any errors. Out of the 3 we use, I added them by their own and it failed everytime. One of them is typical one which checks if bitlocker, antivirus and the firewall is activated and the other two are with custom scripts. I also don't think they have something special that other Policies don't have (similiar names, similiar or same assignments, also use filters). It also makes no difference if the compliance policy is created in the tenant already or not at all. |
Are you able to give me the JSON of some of the policies so I can test them in my tenant? |
I attached the security compliance profile, I changed the displayname for privacy reasons. |
I was able to replicate the issue and it seems to happen when |
I tried it with the new beta version and it still gave me the same error. |
Specifically this error?
|
Try beta 2 -> |
It worked with beta 2. Thanks! Something i now saw is a seperate Error with the Update Policies, I also tested it with 2.3.6, might make Sense to create a new Issue. It doesnt stop the script like the Error in this Issue The Error is following: |
Can you do a run with |
Hope this helps: [Fri Feb 7 09:42:35 2025] - Updating Device Configuration: Windows Update Policy [Prod], list changes: |
Thanks, are you also able to share that configs JSON? |
What version were these backed up with? |
I'm pretty sure it was 2.3.6. I checked the other Policies and all of them them also say 0, should I change them all to Default? Or only the update policies? |
Are you by any chance excluding |
I checked the command and yes it seems like I did. So I should just rebackup the Policies and try to run the update again? |
Try a new backup with scope tags included, then you should not see that error above |
That did the Trick. Thanks a lot for the Help! |
Problem/Bug
Last Week I rebackuped a Configuration with the newest Version, the Configuration is meant to be used for multiple of our customers.
When we (me or a colleague) try to update a customers tenant we get following Error:
Filters and Compliant Scripts work
Wed Jan 22 10:39:06 2025 [INFO] Updating Compliance Script Policy: first endpoint update - update discovery script, list changes:
Wed Jan 22 10:39:06 2025 [INFO] Setting: roleScopeTagIds, Added Value: , Removed Value: ['0']
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "C:\Program Files\Python313\Scripts\IntuneCD-startupdate.exe_main.py", line 7, in
sys.exit(start())
~~~~~^^
File "C:\Program Files\Python313\Lib\site-packages\IntuneCD\run_update.py", line 314, in start
run_update(
~~~~~~~~~~^
args.path,
^^^^^^^^^^
...<5 lines>...
args.remove,
^^^^^^^^^^^^
)
^
File "C:\Program Files\Python313\Lib\site-packages\IntuneCD\run_update.py", line 244, in run_update
update_intune(
~~~~~~~~~~~~~^
diff_summary,
^^^^^^^^^^^^^
...<7 lines>...
args,
^^^^^
)
^
File "C:\Program Files\Python313\Lib\site-packages\IntuneCD\update_intune.py", line 78, in update_intune
diff_summary.append(DeviceComplianceUpdateModule(**params).main())
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "C:\Program Files\Python313\Lib\site-packages\IntuneCD\update\Intune\DeviceCompliance.py", line 176, in main
for action in item["scheduledActionsForRule"][0][
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range
Info:
I'm not sure if its actually a bug, because I'm not a Developer and don't understand the Module that deeply, but I can't figure out what would be wrong with our setup, especially with it working with some tenants.
Thanks for the help.
The text was updated successfully, but these errors were encountered: