After upgrading to GPOAdmin 5.22, PowerShell scripts that rely on the internal service interface method:
May no longer function as expected.
In previous releases, this method returned only the Fully Qualified Domain Name (FQDN) of the preferred domain controller. In version 5.22, the return value was modified to include additional connection information such as the LDAP protocol and port number, which can cause compatibility issues with existing automation that expects only a domain controller name.
Scripts that previously worked may fail or return unexpected results when the output of the internal method is passed directly to Active Directory cmdlets such as:
Example:
Prior to 5.22
In 5.22
As a result, scripts expecting only the FQDN may not be able to use the returned value directly.
In GPOADmin 5.22, the return value of the internal service interface method was updated to include server, protocol, and port information to support secure LDAP communications.
The affected method is part of GPOADmin's internal service interfaces and is not intended as a customer-facing API. Consequently, the format of returned values from these internal methods is subject to change between releases and is not considered a supported contract for custom scripting or integrations.
For customer-developed PowerShell scripts that require preferred domain controller information, Quest recommends using the supported GPOADmin PowerShell cmdlet:
This cmdlet is designed for customer use and continues to return preferred domain controller information in a consistent format across supported versions.
Example:
The output format of this cmdlet has not changed between versions and remains the supported method for retrieving preferred domain controller information.
Quest understands that changes to parameter and return-value formats can impact customer automation. However, only documented and supported customer-facing cmdlets and APIs provide compatibility guarantees between releases.
Internal service interface methods are intended solely for product operation and may be modified as product requirements evolve.
When developing custom automation, use supported PowerShell cmdlets and documented APIs whenever possible to ensure forward compatibility during product upgrades.
