Chatta subito con l'assistenza
Chat con il supporto

GPOADmin 5.18 - Release Notes

Known issues

* 
NOTE: Defects with leading zeros (0) are from the Clarify system.
The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.
 
 
Table 2. Installation and upgrade
Known issue
Issue ID

Change Window restrictions will not apply after upgrade until the Change Window actions list settings are reapplied.

428460

Index out of range exception is generated in the event log for the Watcher Service after upgrading. This will be resolved once the database is upgraded.

217430

 
Table 3. Cross-forest support
Known issue
Issue ID

If you create a SOM backup in one forest and import it to another, the links will appear as deleted GPOs if those GPOs cannot be accessed from the second forest.

0228454

Table 4. Version Control system
Known issue
Issue ID

Validation of the Service Connection Point for the GPOADmin service account does not function for Group Managed Service Accounts.

380823

Export As Desired State Configuration requires users to have the Write permission on the Desired State Configuration Root directory.

377548

Compliance checks on a configuration profile which has had an assignment deleted from it in Azure do not show noncompliant differences in the Difference report.

286622

The Applications Preference extension is not supported during Group Policy Object merging.

265012

When synchronizing GPOs with the Use Migration Table Exclusively and Migrate Security Filter options set, GPOADmin may shutdown unexpectedly if an error occurs and the message exceeds 1024 characters.

244657

The context menu on the Linked Group Policy Objects page of the Group Policy Modeling Wizard results in the wizard loosing focus when launched via Citrix XenDesktop.

611801

Backups will not be removed for unregistered objects when running the Remove-Backups PowerShell command.

591669

Rolling back a moved OU does not move the OU back to it original location.

458939

Each time that you change the Enable workflow approval through email option, you must restart the service for the change to take effect.

360005

Compliance actions may result in an unhandled exception in the GPMC Extension.

Workaround: To avoid this issue, you can either perform the compliance actions in the client or by running the Check compliance wizard.

322839

If users do not have the User role assigned on the Version Control root, they may not have the required rights to successfully run the User Activity report.

238909

If an object is renamed or deleted within Active Directory, the Approvals tab does not reflect the change.

246579

Some GPO settings are not backwards compatible between operating systems.

122825

When you edit GPOs, you are notified of persistent registry values through a flashing icon on the Registry Cleanup button in the GPO Editor. For this notification to display, you must first close and then open the GPO Settings property page by selecting the Edit menu.

240689

The Watcher Service needs to be restarted after changing Configuration Stores.

65408

Deploying a GPO containing existing Software Installation packages may cause each of those packages to be reinstalled on target workstations.

0222515

When checking for compliance, GPOADmin will not perform a backup if the unauthorized changes result in an object in the same state as the currently stored version.

106505

After changing storage locations, the individual version information is not transferred from the old storage location to the new. You must keep the old storage server online if you want to still access those individual versions.

0229309

When using the SeizeVCRole.exe utility, if a port is specified with the new server name, the utility assumes that the new server is an AD LDS instance. When using an Active Directory Version Control server, the default port of 389 does not need to be specified.

0229311

When you are editing a GPO with both the GPOADmin console and the GPMC Extension open, closing the Group Policy Object Editor may not return you to the expected interface.

91914

 

Table 5. Reports
Known issue
Issue ID

The Change Auditor Working Copies report displays a non-functional "placeholder" link instead of the "Show/Hide" link that is used to expand and collapse the report details.

428685

For GPO difference reports to run properly when they contain Authentication Services settings, Quest Authentication Services must be installed on the GPOADmin client and the GPOADmin server.

284883

In the Difference Report, filters are not supported for GPO Preference settings.

151065

In the Group Policy Settings and Resultant Set of Policies reports, some dates (for example, Created, Modified and Applied date) will display with the time zone of the GPOADmin Server.

102486

Pre-existing GPO settings are being displayed in the Change Auditor Working Copies report.

194922

When viewing Preference settings in the Difference Report, the values displayed for text entries may have a capital letter when the actual value is a lower-case letter. This may cause some date settings to be incorrect. 

150634

Table 6. User Account Control
Known issue
Issue ID

When installing the GPOADmin service on a system with User Account Control turned on, the installer must be launched using elevated privileges. To do this, run the 'Quest GPOADmin.msi' file from an elevated command prompt.

41286

Table 7. Third Party
Known issue
Issue ID

"Object reference not set to an instance of an object" error message when you view the GPO backup settings in the Group Policy Management Console.

http://support.microsoft.com/kb/2379592

System requirements

Before installing GPOADmin 5.18, ensure that your system meets the following hardware and software requirements.
 
Table 8. Hardware requirements
Requirement
Details

Processor

2Ghz CPU

Memory

8Gb RAM

Hard disk space

1 Gb (prefer 50Gb if backups and reports stored on the same drive) hard disk space

Operating systems

Windows 10

Windows 11

Windows Server 2012

Windows Server 2012 R2

Windows Server 2016

Windows Server 2019

Windows Server 2022

GPOADmin requirements
•
.NET Framework 4.8
•
GPMC Extension compatible for the system where you are installing GPOADmin.
•
Microsoft Edge WebView2 Evergreen Bootstrapper 97.0.1072.69
Microsoft Exchange requirements
•
Microsoft Exchange 2013
•
Microsoft Exchange 2016
•
Microsoft Exchange 2019
Configuration store requirements
•
Active Directory (Not recommended)
•
AD LDS
•
SQL Server (Supported version include 2012, 2012R2, 2014, 2016, 2017, 2019, and 2022)
* 
NOTE: GPOADmin supports SQL AlwaysOn Availability Groups and SQL Clusters for SQL data.
•
Azure SQL managed instance
Backup store requirements
•
Network Share (recommended)
•
Active Directory (not recommended)
•
AD LDS
•
SQL Server (Supported version include 2012, 2012R2, 2014, 2016, 2017, 2019, and 2022)
* 
NOTE: GPOADmin supports SQL AlwaysOn Availability Groups and SQL Clusters for SQL data.
•
Azure SQL managed instance
Watcher service

Same system requirements as GPOADmin.

Upgrade and compatibility

Note the following when upgrading GPOADmin:

•
All registered objects should be in the available state prior to any upgrade.
•
If you are running GPMC during an upgrade, you must close and re-open it before the GPO Management tab will display. 
•
If you set a custom report folder path in a previous version, you must change the reports folder path in the User Preferences to point to the existing folder.
•
Due to an upgraded encryption algorithm, the service account cannot decrypt previously encrypted passwords. If you are upgrading and using SQL as your configuration store, accessed with SQL authentication, you must re-enter the password for the connection account the first time you connect to the service.
The following pre-configured passwords will also need to be re-entered: the SQL Server Backup Store account, the SMTP notifications account, and the Exchange notifications account.
•
In a minimum permissions environment, Group Policy Objects with a version of 0.x may fail to deploy correctly. To solve this, make a copy of the GPO and deploy the copy. Once this has been verified as successful, delete the original.
•
After upgrading ensure the “Ensure service account has access prior to deployment” service option is checked in the Options dialog.
•
When you upgrade the Server, you must also upgrade the Client, GPMC Extension, and Watcher Service.
•
GPOADmin runs under the security context of a privileged service account that must have full access to GPOs in the managed forest. If you plan to change this account, you must unlock all GPOs before making the change.
•
The supported upgrade paths are from versions 5.16 and later.
•
The live environment will only be visible for GPOADmin Administrators and users who have been explicitly granted access.
As a GPOADmin administrator, however, you may want to allow users to see the live environment from within the GPOAdmin console. This will, for example, enable you to delegate GPO, OU, or SOM object registration (and recursive registration) to specific users in your organization.
To permit a user to see the live environment:

1 Login to GPOADmin as a GPOADmin administrator.
2 Right-click the Live Environment node and select Properties.
3 On the Security tab, add one or more users who require access to the live environment.
4 Click OK.

Authentication Services integration

•
To view Unix settings in GPOADmin, Authentication Services must be installed after GPOADmin is installed. See Support Knowledge Article 82383.

 

* 
NOTE: Authentication Services and GPOADmin integration

Due to rebranding, changes are required in the registry setting for the integration to function correctly.

Authentication Services installs to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Group Policy Manager\Extensions\vgp

 

GPOADmin requires the settings to be installed under this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Quest\GPOADmin\Extensions\vgp

 

To import the settings into the registry at the correct location:
1
Export the key to a file, and change the key path (the bolded line) to the new path.
Old path:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Group Policy Manager\Extensions\vgp]
"CLSID"="{F0648064-537A-45AF-98A4-74D2AABE867C}"
"ReportingDLL"="C:\\Program Files (x86)\\Quest Software\\Authentication Services\\x64\\SettingsProvider.dll"
"DisplayName"="QAS Group Policy for Unix"
"NamespaceUri"="urn:schemas-quest-com:vgp"
 
The new path:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Quest\GPOADmin\Extensions\vgp]
"CLSID"="{F0648064-537A-45AF-98A4-74D2AABE867C}"
"ReportingDLL"="C:\\Program Files (x86)\\Quest Software\\Authentication Services\\x64\\SettingsProvider.dll"
"DisplayName"="QAS Group Policy for Unix"
"NamespaceUri"="urn:schemas-quest-com:vgp"
2
Save the file.
3
Right-click the file, and select Merge. (You can also double-click it and select Yes on the warning dialog.)
This settings will now be in the correct location required for the integration to function.

Compatible Products

GPOADmin 5.18 is compatible with the following software:

•
Change Auditor 7.3
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione