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

Import fails when an included OU has been removed from AD #26

Open
kcrosby opened this issue Jan 2, 2019 · 3 comments
Open

Import fails when an included OU has been removed from AD #26

kcrosby opened this issue Jan 2, 2019 · 3 comments

Comments

@kcrosby
Copy link

kcrosby commented Jan 2, 2019

When an included OU has been removed from AD (or moved), Get-OrganizationalUnitHierarchy fails when calling FindAll. Need to either test for existence first, or handle the exception. Should probably just ignore it. As a workaround, the Inclusion OU list is updated and the offending OU removed when re-visiting the "containers" selection screen on the MA.

@NileshGhodekar
Copy link
Contributor

Thanks @kcrosby! I'll keep this open as a know issue and workaround. The whole codebase needs upgrade to PowerShell 3.0 at the minimum, so if someone from the community is willing to spend efforts on the upgrade, they can fix this and other previously reported issues as well.

@kcrosby
Copy link
Author

kcrosby commented Jan 18, 2019

When you say "upgrade to PowerShell 3.0" what are you referring to? Just the "Set-StrictMode -Version Latest" or something else?

@NileshGhodekar
Copy link
Contributor

This is much more than that! At a high level this is discussed in Issue #21. There are also various bugs and bugfixes reported that can be incorporated as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants