Skip to content
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

Un-ticking Export Assignments still exports Settings Catalog Assignments #171

Open
SkipToTheEndpoint opened this issue Oct 27, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@SkipToTheEndpoint
Copy link

Hey there!

It was brought to my attention that the export I'd made for my OpenIntuneBaseline project using the tool still imported some "All Users" and "All Devices" assignments for Settings Catalog policies even though I had "Export Assignments" disabled.

It only seems to be if they're assigned to the virtual All Users/Devices groups, if they have an actual group assigned this is not exported, which I don't imagine is the intended behaviour.

Thanks!

@Micke-K
Copy link
Owner

Micke-K commented Oct 29, 2023

Hello!

Thank you for reporting this.

I think I found the reason. Some parts doesn't make sense though. Like why it only happens when deployed to All Users/All Devices.

Can you try the attached update?

BTW...great GitHub repo! Do you mind if I start looking into supporting import directly from the tool? I have been thinking about it for a while. Not sure when/if I get the time and if it would be used but just as an option. I've been thinking about adding support for GitHub import a long time now.

Cheers!

EndpointManager.zip

@Micke-K Micke-K added the bug Something isn't working label Oct 29, 2023
@SkipToTheEndpoint
Copy link
Author

From a quick test and glance whatever you've done there seems to have resolved it, and it's not exporting the All Users/Devices assignments on a bulk export. I'm going to try another export/import cycle just to be sure.

Thanks for your kind words! As for the functionality of being able to import directly from a repo, and there's definitely other projects which are focused around doing similar things via CI/CD. I think it'd make an interesting option to have, though I'm not sure how much time it would save people.
I'd also always discourage people yeeting something straight into their production environment, though I wouldn't have known about this bug if someone I know didn't do exactly that and very quickly tell me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants