Change Control 7.0.1 の既知の問題

CRITICAL: There are no critical issues.

Non-critical:

Solidcore Extension

Reference	Article	Found in Version	Resolved in Version	Description
608618		5.0.0		Issue: When you try to upload the Windows Solidcore Agent Deployment Package (~100 MB) to ePO through Internet Explorer, the file upload times out if the network upload speed is slow. Workaround: If this error displays in Internet Explorer 6, try using Internet Explorer 7 (or later). If you encounter the error in Internet Explorer 7 or later, copy the package to a local directory on the ePO server. Access the ePO console, on the ePO server, and upload the file from the local path. Doing so avoids possible network delays.
607517				Issue: PDF reports have minor data display and formatting issues if more than 50,000 records are reported.
608347				Issue: The Solidcore Policies Applied on Hosts report displays all policies derived from the root, regardless of the SKUs enabled on the platform.
609304		5.0.2		Issue: It is not possible to export data from the Reporting, Solidcore Events page. Workaround: Use Queries (Reporting, Queries) to export event data.
636769		5.1.1		Issue: If you upgrade from Solidcore 5.1.0 to 5.1.1 or later, existing Solidcore events in the Solidcore Events table are not migrated to the ePO Events table.
636352		5.1.1		Issue: After removing the Solidcore Extension, all Solidcore-related events are retained in the ePO table. When you view the events in the Threat Event Log, some fields might display erroneous data.
607554				Issue: Solidcore policies cannot be duplicated using the Policy Details page because the OK button is disabled. Workaround: Use the Policy Catalog page to duplicate policies.
608374		5.0.0		Issue: When you try to enable an already enabled Solidcore Agent, the error displayed is not translated.
607908				Issue: It is not possible to export more than 50,000 records from any table or report.
608025				Issue: Reports, tasks, and policies for all SKUs are listed even if the license for that SKU is not added.
609911		5.1.0		Issue: Export of rule groups does not work in Internet Explorer when opened from the ePO server. Workaround: Use Internet Explorer from a different computer and export rule groups.
608753		5.0.0		Issue: Sometimes, using the user name field of reported events on the ePO server as a trusted user might not work if the client system is part of an Active Directory domain. This issue happens because the domain name reported in the events is not the full AD domain. Workaround: Use the environment variable USERDNSDOMAIN as the domain name for AD clients. You can also review the properties of the My Computer icon to identify the complete user name to specify as the trusted user.
608390				Issue: When viewing an Integrity Monitor policy, the My Rules tab is not translated.
607950		5.0.0		Issue: User-defined system variables in policies are resolved at the endpoint only after the endpoint is restarted.
719796		5.2.0		Issue: Global Catalog search for Active Directory (AD) groups is not supported. Workaround: Search for a group in a specific AD server instead of using the Global Catalog. To add a specific group: Log on to the ePO console. Add the AD server with the group as a registered server. Search for the group by selecting the registered AD server. Make sure that the Global Catalog Search option is deselected. Add the group to a policy as a trusted group.
722045		5.2.0		Issue: Adding new columns, such as Solidcore Status and Solidification Status, for an endpoint by clicking Actions, Choose columns, Non Compliant Solidcore Agent might not display values for all endpoints. This issue happens because the Non Compliant Solidcore Agent section includes only noncompliant agent properties. Workaround: When adding new columns for an endpoint, click Actions, Choose columns, Solidcore Client Properties instead of Actions, Choose columns, Non Compliant Solidcore Agent.
695769		5.2.0		Issue: Under the Content Change Tracking feature, the view file page goes blank for a file size of around 1 MB.
800014		6.1.0		Issue: Extra events are reconciled when manual reconciliation is performed from custom queries. Workaround: To perform the manual reconciliation for multiple events by selecting either All in this page or Select All in all pages, open the Solidcore events page directly by clicking Menu, Reporting, Solidcore Events. NOTE: This option does not work well if you reach Solidcore Events by drilling down from a Query page.
882821		6.1.1		Issue: Sorting is not supported on the Last Modification Time column on the Content Change Tracking page.
1033281		6.2.0		Issue: Upgrading to Solidcore Extension 6.2.0 or later can fail immediately after the extension restart while performing an upgrade from a version older than 6.1.2.
1043052		6.2.0		Issue: You can't upgrade the Solidcore help extension from previous versions to 6.2 (or later). Workaround: Uninstall the old help extension and install the new one.
1109570		7.0.0		Issue: The MAC, MCC, and IM dashboards are editable after you migrate from ePO 4.6.9 to ePO 5.1.3.
1107754		7.0.0		Issue: The following queries related to Automatic Reconciliation are not removed after you upgrade to Solidcore Extension 7.0.0: Systems in Update Window due to TBE History of Update Windows opened by TBE Ticket Manifest Deviation (All Change Events per Object like File or Registry) Ticket Manifest Deviation (Only Unique Change Events per Object like File or Registry)
1148388		7.0.0		Issue: Advance Filters on the Solidcore Events page are not working. Workaround: Click the Advanced Filters link. From left pane, select the Available Property for the filter (Example: System Name). Type the Value for the selected property. Click the drop-down list for comparison and change the selection from Equals to Not Equals and then change it back to Equals. Click Update Filter. NOTE: These steps have to be performed for each of the filter criteria being used. Make sure that the steps are performed in the order listed. Deviation results in the filter not saving.

Windows (all versions)

Reference	Article	Found in Version	Resolved in Version	Description
608418		5.0.0		Issue: The Original user name reported in events is the same as the user name.
600805		4.7.0		Issue: While opening a write-protected network share in Windows Explorer, a few deny-write errors are observed.
603747		4.8.0		Issue: The trusted, solidified, and write-protect features do not work correctly for folder-mounted volumes. Workaround: Contact Technical Support for assistance if the setup uses folder-mounted volumes.
608036		5.0.0		Issue: Mapped drive names can't be used in commands issued by remote users/ePO.
598002		4.5.0		Issue: Registry key protection does not work for all registry key hives, it works only for HKEY_LOCAL_MACHINE.
599240		4.5.3		Issue: A subkey registry does not get added to a protected registry key when using the reg command.
601500		4.7.0		Issue: Creating a shortcut in a read-protected directory is not allowed.
602122		4.7.0		Issue: Any file operation performed on a read-protected file generates deny-read events that correspond to the file even when the file operation is allowed.
603032		4.8.0		Issue: Changes to folder-mounted volumes that do not have an associated drive letter can't be monitored. Workaround: Assign a drive letter to a volume before mounting it on any other folder.
603628		4.8.0		Issue: On 64-bit platforms, ACL change events are not generated when the update mechanism supersedes the deny-write policies for registries.
605371		4.8.3		Issue: When you try to read a read-protected file with certain file flags set through Windows Explorer, read-denied events might not be written to the event viewer. The events are still written to the Solidcore Agent log file.
606496		4.9.0		Issue: Only full long names are supported with commands that accept file or folder names. For example, names such as c:\myPackages\SETUP-~1.EXE are not supported.
606532		4.9.0		Issue: Virtual drive paths are not supported as path values in Solidcore Agent commands, such as write-protect, read-protect, and monitor.
600748		4.6.4		Issue: Multiple deny write events might be generated for a single deny write action. For example, on deletion of a file using Windows Explorer, up to 8 file deletion events are reported. When the application denies deletion of a file, Windows Explorer tries multiple methods to delete the file, resulting in an event for each attempt.
691196		5.2.0		Issue: For a file where you are tracking content changes, you receive an unknown error if connectivity issues occur while sending metadata for the file from the endpoint to the ePO console. Workaround: When network connectivity resumes, the next change to the file is reflected accurately on the ePO console.
724796		5.2.0		Issue: Although you can track content changes for a read-protected file, you can't view the actual changes. This issue happens because the read protection rule prevents the software from fetching file contents from the endpoint.
799559		6.1.0		Issue: If you exclude the .bat extension from monitoring, events for batch file operations are generated.
812964		6.1.0		Issue: If the Updater flag is removed for a cert rule in ePO, the certificate is listed as an Updater on the endpoint.
876430		6.1.1		Issue: For monitoring and change control rules with an asterisk (), the longest path* rule is not given precedence for conflicting rules.
881480		6.1.1		Issue: Revisions are not reported for Content Change tracking if user events are filtered using the filter rules. Workaround: Exclude the user from event filtering and apply advanced filters for the user for exclusion of unwanted events about files and directories.
894237		6.1.1		Issue: For a directory-based Content Change Tracking rule, renaming of the directory or its subdirectory can generate spurious monitor events.
920568	KB79987	6.1.2	6.1.3	Issue: The version is not updated in the ePO server and the McTray About box after an endpoint upgrade. Workaround: See the Knowledge Base article for details.
940085	KB73484	6.1.2		Issue: There is a known incompatibility between McAfee Change Control and SafeNet ProtectFile: File Encryption and Protection software.
1027687	KB84043	6.2.0		Issue: Upgrade to Application Control or Change Control 6.2 (or later) fails for endpoints. Workaround: See the Knowledge Base article for details.
1146803		7.0.0		Issue: Change Control event REG_KEY_CREATED is not generated for New Key #1.

Windows 2008 R2 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
608636		5.0.0		Issue: During manual installation of the Solidcore Agent on Windows 2008 R2 (64-bit), a Windows installer encountered a validation error message displays for the msiexec.exe and kernelbase.dll files. Workaround: Click Ignore once or Ignore always on the error pop-up to continue installation.

Windows 2008 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
609780		5.0.2		Issue: On Windows 2008 (64-bit), the rundll32.exe file crashes if an application is uninstalled via Add/Remove Programs after the SetupInstallFromInfSection() function was used to install the application.

Windows 7 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
708226		5.1.5		Issue: MCC is functionally incompatible with Avecto Privilege guard.

Knowledge Center

Change Control 7.x Known Issues

環境

概要

影響を受ける製品

言語:

技術用語集

Title

Title

Knowledge Center

Change Control 7.x Known Issues

環境

概要

影響を受ける製品

言語:

技術用語集

地域を選択してください

Title

Title