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

Lithnet Service Account permissions cause warnings in Exchange ECP when editing groups. #165

Open
grumpymojo opened this issue Aug 10, 2022 · 2 comments
Assignees
Labels
bug Something isn't working pinned

Comments

@grumpymojo
Copy link

Describe the bug
When editing a group in on premise Exchange ECP you get a warning that group is corrupted because object "43061ac1-c8ad-4ccc-b785-2bfac20fc60a" can't be resolved

To Reproduce
Steps to reproduce the behavior:

  1. Go to on premise Exchange ECP
  2. Click on 'Groups'
  3. Select a group and click edit.
  4. See error

Expected behavior
No warning

Screenshots
Lithnet_service_account

Access Manager installation

  • OS: Windows Server 2019
  • Version 1.0.7941.0

Additional context
The object mentioned above is the Lithnet Service Account created during setup.
I'm guessing the powershell script that sets permissions, doesn't limit itself to just computer objects.
I'm guessing the way around this issue is to only apply the permissions to OU's that contain computers, instead of the domain root but I thought it was worth logging a bug in case you have any other suggestions.

@grumpymojo grumpymojo added the bug Something isn't working label Aug 10, 2022
@grumpymojo grumpymojo changed the title Lithent Service Account permissions cause warnings in Exchange ECP when editing groups. Lithnet Service Account permissions cause warnings in Exchange ECP when editing groups. Aug 10, 2022
@grumpymojo
Copy link
Author

Just some additional information. It's specifically the permissions for Bit Locker Recovery Password recovery that cause this issue.
I have solved this my self by removing these permissions from the root of the domain and then running the permission script only against OUs with computer objects.

There is probably nothing for you to fix but it might be worth mentioning in the documentation.

@stale
Copy link

stale bot commented Aug 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

@stale stale bot added the stale label Aug 30, 2022
@stale stale bot closed this as completed Sep 6, 2022
@ryannewington ryannewington self-assigned this Sep 6, 2022
@ryannewington ryannewington added pinned and removed stale labels Sep 6, 2022
@ryannewington ryannewington reopened this Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pinned
Projects
None yet
Development

No branches or pull requests

2 participants