NOTE: This hotfix depends on having GPOADmin version 5.20 previously installed, If you are using a version earlier than 5.20, please first upgrade to 5.20 and then download and apply the 5.20.2.5 Update 2. If you are not severely affected by the issue this update addresses, Quest recommends that you wait for the next release of GPOADmin as it will include this update. If you are in version 5.20, please download the 5.20.2.5 Update 2 by Clicking Here. Once downloaded, follow the instructions in the included Release Notes PDF to upgrade to 5.20.2.5 Update 2
Resolved Issues in Update 2
- GPOADmin 5.20 Update 1 Client and Server installer not updating GPOADmin.Snapin.dll causing GPOADmin to close unexpectedly when attempting to delete a GPO. - 539896
- When deleting GPOs a warning that the GPO is still linked to an OU is shown even after the link has been removed. - 540059
- Documentation enhanced for manual database upgrade when using replicated database. - 540047
Resolved Issues in Update 1
- Setting the default link state to Enabled when adding new links option is not working properly. - 527434
- Deleting a 0.0 copied version of an object and choosing "delete backups" object generates a reference error. - 524356
- The Clear-ActionAccounts functionality for a single item does not obey the -SkipCleared switch. - 524277
- Group approvals using distribution groups are not moved to Pending Deployment after approvals. - 529245
- Duplicate container notifications are generated when using an On-premises Exchange Server. - 529794
- The path value is missing from deployment notifications. - 527664
- Editing an OU fails if a GPO exists in the environment without a set display name. - 533077
