Friday & Sundae!

Friday & Sundae! 

Yes... Weekends are here. And I have a craving for sundae. 

Should I get myself a strawberry sundae? 


 - Pic from Internet

 - wong chee tat :)

Pickles Says November

Pickles Says November. 

Taken on 1st Nov, yup, I know... A week late.

 - wong chee tat ):

Weekends are coming soon!

Weekends are coming soon!

 - Pic from Internet

 - wong chee tat :)

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

- wong chee tat :)

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

- wong chee tat :)

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

Homage to the 36 trillion, 119 thousand, 500 Amitabha Buddhas

- wong chee tat :)

McAfee KB84419: Windows 10 compatibility with McAfee products

McAfee KB84419: Windows 10 compatibility with McAfee products

Environment

Multiple McAfee business and enterprise products

Microsoft Windows 10 (version 1507)
Microsoft Windows 10 (version 1511) - November Update (Threshold 2, first update)
Microsoft Windows 10 (version 1607) - Anniversary Update (Redstone 1 [RS1], second update)
Microsoft Windows 10 (version 1703) - Creators Update (Redstone 2 [RS2], third update)
Microsoft Windows 10 (version 1709) - Fall Creators Update (Redstone 3 [RS3], fourth update)

NOTE: This article applies only to McAfee business and enterprise products. If you need information or support for McAfee consumer or small business products, visit https://service.mcafee.com.

Summary

McAfee is committed to supporting the Microsoft release cadence for Windows 10 and is working closely with Microsoft to ensure that McAfee security software and hardware products are fully compatible with Windows 10 endpoints.

To ensure release quality, all new releases that Microsoft publishes for Windows 10 require full validation by the individual product teams. The McAfee goal is to add zero-day support for all Windows 10 releases over time for those products that do not currently offer this cadence.

NOTE: Late-breaking changes implemented by Microsoft to a release, or any unresolved compatibility issues raised by McAfee with Microsoft around a scheduled release, could lead to schedule changes that will be documented and updated in this article.

Recent updates to this article

Date	Comments
Oct 30, 2017	Updated products RTS information for Windows 10 Fall Creators Update (RS3) support.
Oct 25, 2017	Update to Application and Change Control for Fall Creators Update, to reflect support included with version 7.0.1-462 (HF6).
Oct 23, 2017	Updated details about McAfee product support for Microsoft Windows 10 (version 1709) - Fall Creators Update. Changed Management of Native Encryption 4.1.1 to 4.1.2 (Q4 2017) in the Windows 10 (Version 1709) Fall Creators Update column.
Oct 17, 2017	Updated details about McAfee product support for Microsoft Windows 10 (version 1709) - Fall Creators Update. Moved content for Windows 10 versions 1507 and 1511 to a second table in the Related Information section.
Oct 10, 2017	Corrected a typo in the Security Management Products section (Windows 10 Fall Creators Update column) for McAfee Agent (MA). MA 5.0.6 was included twice. Changed to MA 5.0.5 and 5.0.6.
Sep 25, 2017	Added to footnote 2 for support with Drive Encryption.

To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged in to subscribe.

NOTES:

• Future release dates are subject to change.
  NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.
• RTW = Released To World
• RTS = Released To Support, also called Managed Release. Contact your Technical Account Manager (TAM) or Support Account Manager (SAM) to participate in a Managed Release program.
• For details about Service Packs, patches, hotfixes, maintenance releases, and the patch release cycle, see KB51560.
• For details about a support statement for verifying and validating Microsoft patches, see KB50473.

Compatibility with Windows 10 Versions 1607, 1703, and 1709

McAfee Products	Windows 10  (Version 1607) Anniversary Update4	Windows 10  (Version 1703) Creators Update 5	Windows 10 (Version 1709) Fall Creators Update McAfee Products Status RTS
	Minimum Supported McAfee Product Version
Endpoint Protection Products 1
Active Response	1.1.0.212	2.0 2.01	2.0.1
Application and Change Control	7.0.1	8.0.x	8.0.x
Data Loss Prevention Endpoint (DLP Endpoint)	11.0 10.0.100 9.4.230 9.3.630	11.0 10.0.250 9.4.300	11.0.130 (RTS)8
			10.0.330 (RTS)8
Endpoint Security (ENS)	10.2 10.1.2	10.2.1 10.5.1	10.2.2 (RTS)8
			10.5.3 (RTS)8
ENS - Advanced Threat Protection (ATP)	10.5.1	10.5.2	10.5.3 (RTS)8
Host Intrusion Prevention (Host IPS)	8.0 Patch 8	8.0 Patch 9	8.0 Patch 10 (RTS)8
SiteAdvisor Enterprise (SAE)	3.5 Patch 5	3.5 Patch 5	3.5 Patch 5
Threat Intelligence for Endpoint Security Client	10.1 Patch 2 10.2	10.2.2	10.2.3
Threat Intelligence Exchange (TIE) Module for VSE	1.0.2	1.0.2	n/a
VirusScan Command Line Scanner	6.1.0	6.1.0	6.1.0
VirusScan Enterprise (VSE)	8.8.0 Patch 8	8.8 Patch 9	8.8 Patch 10 (RTS)8
Database Security Products
Database Activity Monitoring (Standalone Management)	4.6.0	n/a	n/a
Database Activity Monitoring (ePO Management)	5.2.0	n/a	n/a
Vulnerability Manager for Databases (Standalone Management)	4.6.0	n/a	n/a
Vulnerability Manager for Databases (ePO Management)	5.2.0	n/a	n/a
Data Center Protection Products
Management for Optimized Virtual Environment (MOVE) Multi-platform	4.0 3.6.1	4.5	4.6
Data Protection Products
Drive Encryption (DE) 2, 3	7.2.0 7.1.3 HF1148978	7.2.1	7.2.2 (RTS)8
File and Removable Media Protection (FRP) 3	5.0.1 HF1150417 5.0.2	5.0.3 6	5.0.4 (RTS)8
Management of Native Encryption (MNE)	4.1.0	4.1.1	4.1.1 4.1.2 (RTS)8
Security Management Products
Data Exchange Layer (DXL)	2.0.1	3.1.0	4.0 (RTS)8
ePO Deep Command 7	Pending Update	n/a	n/a
McAfee Agent (MA)	5.0.4 4.8.0 Patch 3	5.0.5 4.8.0 Patch 3	5.0.5 5.0.6 4.8.0 Patch 3
Policy Auditor Agent (PA)	6.2.0.309	6.2.2	6.3
Rogue System Detection	5.0.4	5.0.5	5.0.5
Web Protection
McAfee Client Proxy (MCP)	2.1.0.177	2.3	2.3.2 (RTS)8

n/a = not available
HF = hotfix
TBD = To be Decided

1	SaaS Endpoint Protection 6.0 does not support Microsoft Windows 10.0. If you try to install Windows 10.0 while running SaaS Endpoint Protection 6.0, it asks you to uninstall it. If you are running SaaS Endpoint Protection 6.0, uninstall it and install ENS 10.0. ENS 10.0 Patch 1 supports Windows 10.0.
2	IMPORTANT: Zero-day in-place upgrade to Windows 10 is fully supported with DE 7.2.1 and later, by running setup.exe (no need for scripts or command-line arguments), when setup.exe is initiated from the Microsoft WSUS mechanism. For DE 7.1.3 and 7.2.0 and later, reflect drivers parameter must be used when executing setup.exe directly. For Windows Anniversary Update (Version 1607) only, see KB87909. For Windows 10 Creators Update (Version 1703) and later, see KB89000. If the organization administrator runs the setup.exe directly, setup.exe must include the additional command-line options.   In-place upgrade to Windows 10 (versions 1507 and 1511) with DE 7.1 Patch 3 (7.1.3) or FRP 5.0.1 installed is supported, but requires specific steps to be taken as part of the Windows 10 upgrade for it to be successful. For details, see the required article: For detailed instructions and sample scripts that can be tailored to suit the customer environment for DE, see KB84962. For detailed instructions for FRP, see KB87550.   DEGO deployment to Windows 10 clients fails. This is resolved by installing DE 7.1 Patch 3 Hotfix 1087719 (build 7.1.3.554) or later. For details, see KB85514.
3	For information about support for Device Guard with DE and FRP, see KB86009.
4	KB87536 (Incompatibility between the Windows 10 Anniversary Update and multiple McAfee products) has been redirected to this article because KB87536 became obsolete. Windows 10 Anniversary Update now performs the needed upgrade and installation checks to ensure that no incompatible McAfee product versions can be installed or present, and blocks the upgrade if they are present.
5	CAUTION: If Device Guard or Credential Guard is enabled on a Windows 10 Creators Update 64-bit system, you must ensure that Microsoft KB4016251 is installed on the system before you install McAfee products. For more information, see KB89029.
6	A minimum Windows 10 Creators Update Version 1703 (OS build 15063.250) is required for support with FRP 5.0.3. For more information, see the Microsoft article KB4016240 https://support.microsoft.com/en-gb/help/4016240/windows-10-update-kb4016240 WARNING: Installation or upgrade with earlier builds of Windows 10 Creators Update fails.
7	ePO Deep Command reaches End of Life (EOL) on April 10, 2018. See KB88454 for details.
8	For customers who want to participate in a RTS/Managed Release program, contact your Technical Account Manager (TAM) or Support Account Manager (SAM).

NOTE: Additional information regarding Windows 10 support for McAfee products will use standard McAfee communication methods including the Support Notification Service (SNS).

To receive information about McAfee product updates, sign up for the Support Notification Service athttps://sns.secure.mcafee.com/signup_login.

Related Information

Windows 10 devices running version 1507 and 1511 will no longer receive security and quality updates. Microsoft recommends updating devices to the latest version of Windows 10.

Compatibility with Windows 10 Versions 1507 and 1511

McAfee Products	Windows 10 (Version 1507) Release To World	Windows 10 (Version 1511) November Update
	Minimum Supported McAfee Product Version
Endpoint Protection Products 1
Active Response	1.1.0  HF1.1.0.161	1.1.0  HF1.1.0.161
Application and Change Control	7.0	7.0
Data Loss Prevention Endpoint (DLP Endpoint)	11.0 10.0 9.4 Patch 1 9.3 Patch 6	11.0 10.0 9.4 Patch 1 9.3 Patch 6
Endpoint Security (ENS)	10.0.1 (patch) 10.1 (major release)	10.0.1 (patch) 10.1 (major release)
ENS - Advanced Threat Protection (ATP)	10.5.1	10.5.1
Host Intrusion Prevention (Host IPS)	8.0.0 Patch 6	8.0.0 Patch 6
SiteAdvisor Enterprise (SAE)	3.5 Patch 4 4	3.5 Patch 4 4
Threat Intelligence for Endpoint Security Client	10.1	10.1
Threat Intelligence Exchange (TIE) Module for VSE	1.0.1	1.0.1
VirusScan Command Line Scanner	6.0.6	6.0.6
VirusScan Enterprise (VSE)	8.8.0 Patch 6	8.8.0 Patch 6
Database Security Products
Database Activity Monitoring (Standalone Management)	4.4.9	4.4.9
Database Activity Monitoring (ePO Management)	5.1.3 Patch 2	5.1.3 Patch 2
Vulnerability Manager for Databases (Standalone Management)	4.4.9	4.4.9
Vulnerability Manager for Databases (ePO Management)	5.1.3 Patch 2	5.1.3 Patch 2
Data Center Protection Products
Management for Optimized Virtual Environment (MOVE) Multi-platform	3.6.1	3.6.1
Data Protection Products
Drive Encryption (DE) 2, 5	7.1 Patch 3 (7.1.3)	7.1.3
File and Removable Media Protection (FRP) 5	5.0.x 4.3.1 HF1062118 3	5.0.x 4.3.1 HF1062118 3
Management of Native Encryption (MNE)	3.0.0	3.0.0
Security Management Products
Data Exchange Layer (DXL)	2.0.0	2.0.1 Patch 1
ePO Deep Command 6	2.4	2.4
McAfee Agent (MA)	5.0.2 4.8.0 Patch 3	5.0.2 4.8.0 Patch 3
Policy Auditor Agent (PA)	6.2.0.309	6.2.0.2309
Rogue System Detection	5.0.3	5.0.3
Web Protection
McAfee Client Proxy (MCP)	2.1	2.1

1	SaaS Endpoint Protection 6.0 does not support Microsoft Windows 10.0. If you try to install Windows 10.0 while running SaaS Endpoint Protection 6.0, it asks you to uninstall it. If you are running SaaS Endpoint Protection 6.0, uninstall it and install ENS 10.0. ENS 10.0 Patch 1 supports Windows 10.0.
2	IMPORTANT: Zero-day in-place upgrade to Windows 10 is fully supported with DE 7.2.1 and later, by running setup.exe (no need for scripts or command-line arguments), when setup.exe is initiated from the Microsoft WSUS mechanism. For DE 7.1.3 and 7.2.0 and later, reflect drivers parameter must be used when executing setup.exe directly. For Windows Anniversary Update (Version 1607) only, see KB87909. For Windows 10 Creators Update (Version 1703) and later, see KB89000. If the organization administrator runs the setup.exe directly, setup.exe must include the additional command-line options.   In-place upgrade to Windows 10 (versions 1507 and 1511) with DE 7.1 Patch 3 (7.1.3) or FRP 5.0.1 installed is supported, but requires specific steps to be taken as part of the Windows 10 upgrade for it to be successful. For details, see the required article: For detailed instructions and sample scripts that can be tailored to suit the customer environment for DE, see KB84962. For detailed instructions for FRP, see KB87550.   DEGO deployment to Windows 10 clients fails. This is resolved by installing DE 7.1 Patch 3 Hotfix 1087719 (build 7.1.3.554) or later. For details, see KB85514.
3	For details about FRP 4.3.1 HF1062118, see KB84829. This hotfix is available on the Product Downloads site as a separate item on the FRP 4.3.1 download page.
4	SAE 3.5 Patch 4 HF1076106 adds support for Mozilla Firefox.
5	For information about support for Device Guard with DE and FRP, see KB86009.
6	ePO Deep Command reaches End of Life (EOL) on April 10, 2018. See KB88454 for details.

- Link:

- wong chee tat :)

November 1, 2017

Pokémon GO updated to version 0.81.1 for Android and 1.51.1 for iOS

Trainers,

Pokémon GO is in the process of being updated to version 0.81.1 for Android and 1.51.1 for iOS devices. Details from our development team:

• Resolved a bug that prevented Trainers from powering up Pokémon to their max CP.
• Resolved a bug that caused Trainers’ contributions to reset when rejoining a Raid Battle.
• Various bug fixes and performance updates.

—The Pokémon GO team


Updated!

- wong chee tat :)

McAfee KB66616: ePolicy Orchestrator server backup and disaster recovery procedure

McAfee KB66616: ePolicy Orchestrator server backup and disaster recovery procedure

Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Summary

This article provides information on the backup and disaster recovery process for ePO servers.

IMPORTANT:

• This procedure is intended for use by network and ePO administrators only. McAfee does not assume responsibility for any damage incurred because it is intended as a guideline for disaster recovery. All liability for use of the following information remains with the user.
• It is preferable to use the built-in Disaster Recovery feature and use these steps only if a valid Snapshot was not created and a manual recovery is required. For information about the Disaster Recovery feature, see the "Restoring McAfee ePO" section of the ePolicy Orchestrator Installation Guide.
• If you are migrating from a 32-bit to a 64-bit operating system, or installing ePO to a different path, you must follow the instructions in KB71078 instead.

NOTES:

• The agent uses either the last known IP address, DNS name, or NetBIOS name of the ePO server. If you change any one of these, ensure the agents have a way to locate the server. The easiest way to do this is to retain the existing DNS record and change it to point to the new IP address of the ePO server. After the agent is able to successfully connect to the ePO server, it downloads an updated SiteList.xml with the current information.
• You can also use this procedure if you want to migrate the ePO server to another system, though it is preferable to use the built-in Disaster Recovery feature to migrate the ePO server to another system.

Preparation
To ensure a smooth recovery, do not perform a backup while the server is in the process of installing an extension.

Before backing up

If possible, shut down the McAfee ePolicy Orchestrator Application Server service (Tomcat) entirely when performing the backup. Otherwise, ensure that no one is performing the following actions during the backup:

• Installing, uninstalling, or upgrading an extension
• Updating the ePO database configuration 

Backing up the ePO server

1. Use the following documents to back up the SQL database (normally named ePO_<ServerName>, where the <ServerName> is your ePO server name):
   • See article KB52126 for details on backing up the ePO database using SQL Server Management Studio.
   • See article KB59562 for details on backing up the ePO database using OSQL commands.
      
2. You must also back up the following folder paths:
   NOTE: The default 64-bit installation paths are listed below; however, your installation might differ (for example, the default 32-bit installation path is C:\Program Files\McAfee\ePolicy Orchestrator).

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions
The default path to ePO software extension information.

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf
The default path to required files used by the ePO software extensions.

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\keystore
These keys are for ePO agent-server communication and the repositories.

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software
All products that have been checked into the Master Repository are located here.

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Keystore
The agent-to-server communication and Repository Keys that are unique to your installation are located here. Failing to restore this folder will result in all client systems being unable to communicate with the server, and you will have to redeploy the agent to all systems. Additionally, you will have to check in all deployable packages again.

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf
The server configuration settings for Apache, the SSL certificates needed to authorize the server to handle agent requests, and console certificates are located here.

NOTE: Failure to back up and restore these directory structures will require a re-installation of ePO to create new ones and possibly require a clean database installation and redeployment of agents to all client systems.

Recover the ePO server

1. Delete the ePO database on the SQL server. If you do not know how to perform the MSSQL operation, refer to http://technet.microsoft.com/en-us/library/ms177419.aspx or contact Microsoft Support.
    
2. If restoring ePO to the same system, uninstall ePO. Ensure that there is no ePolicy Orchestrator folder in the original installation path after the software is uninstalled.
   
   NOTE: Renaming the existing ePO folder and leaving the old directory in place may interfere with the new installation; therefore, we recommend that you remove the old directory completely.
    
3. Re-install ePO to the same version and patch level as the server you are restoring.
   
   NOTE: You can verify the ePO patch level by looking at the Version field in the backed up Server.ini file (C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\) and cross-referencing it with article KB59938.
   
   IMPORTANT: You must re-install ePO to the exact same directory path as the previous installation for this article to apply (or the initialization of extensions will fail when the restore is complete). If the installation path is different, follow the steps in article KB71078 instead.
    
4. Apply any additional patches/hotfixes/POCs to ePO that had been previously applied. If you have previously installedPolicy Auditor 6.2 for use with ePO, install the same version of Policy Auditor (including any hotfix releases) that had been installed before.
    
5. Stop and disable all ePO services:
    
   1. Click Start, Run, type services.msc, and click OK.
       
   2. Right-click each of the following services and select Stop:
      McAfee ePolicy Orchestrator Application Server
      McAfee ePolicy Orchestrator Event Parser
      McAfee ePolicy Orchestrator Server
       
   3. Double-click each of the following services and change Startup type to Disabled:
      McAfee ePolicy Orchestrator Application Server
      McAfee ePolicy Orchestrator Event Parser
      McAfee ePolicy Orchestrator Server
        
6. Restore the database. See article KB52126 for details on restoring the ePO database using SQL Server Management Studio.
   NOTE: Restore the database so that you do not require the ePO database configuration to be updated (for example, same name, host, port, and so on). Otherwise, you must update the restored DB.PROPERTIES file in C:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion with the new information before starting the server.
7. Rename the following folders (for example, rename the extensions folder to extensions_old), and then replace them with the corresponding folders that were backed up earlier in step 2:
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\keystore
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Keystore
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf
    
8. Start only the McAfee ePolicy Orchestrator Application Server service. 
    
9. Access the core/config page of ePO and re-enter the DB credentials if you are using ePO 5.3 or later, or if you are unable to access the ePO console. See KB69850 for detailed instructions on how to access the core\config page and update the DB credentials if needed.
    
10. Attempt to log on to the ePO console. If you are unable to log on, review all the steps performed in this article and ensure they have been properly completed. If you cannot resolve the console logon issue, contact Technical Support for further assistance before proceeding.
     
    
    For Technical Support contact details:
    Go to http://www.mcafee.com/us/about/contact-us.aspx#ht=tab-techsupport and select your country from the drop-down list. 
    
    Alternatively:
    Log in to the ServicePortal at https://support.mcafee.com:
    • If you are a registered user, type your User Id and Password, and click Log In.
    • If you are not a registered user, click Register and complete the required fields. Your password and login instructions will be emailed to you.
    
     
    NOTE: You must be able to log on for the rest of the recovery steps to work.
      
11. Rename the SSL.CRT folder (see path below) to SSL.CRT.OLD and manually create an empty folder named SSL.CRT in the same path; otherwise the setup will fail to create a new certificate: 
     
    64-bit: "C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
    32-bit: "C:\Program Files\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
      
12. Click Start, type cmd in the search field, right-click, and select Run as administrator.
     
13. Change directories to your ePO installation directory.
    Default paths:
     
    64-bit: Program Files (x86)\McAfee\ePolicy Orchestrator\
    32-bit: Program Files\McAfee\ePolicy Orchestrator\
       
14. Run the following command:
     
    Rundll32.exe ahsetup.dll RunDllGenCerts <ePO_server_name> <console_HTTPS_port> <admin_username> <password> <"installdir\Apache2\conf\ssl.crt">
     
    where:
     
    <ePO_server_name> is your ePO server NetBIOS name
    <console_HTTPS_port> is your ePO console port (default is 8443)
    <admin_username> is admin (use the default ePO admin console account)
    <password> is the password to the ePO admin console account
    <installdir\Apache2\conf\ssl.crt> is your installation path to the Apache folder; Default installation path:
     
    64-bit: "C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
    32-bit: "C:\Program Files\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
     
    Example
    Rundll32.exe ahsetup.dll RunDllGenCerts eposervername 8443 administrator password "C:\Program Files\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
    IMPORTANT:
    • This command will fail if you have enabled User Account Control (UAC) on this server. If the server is running Windows Server 2008 or later, disable this feature. You can find more information about UAC at: http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx.
    • This command is case-sensitive. The ahsetup.log (found in <installdir\Apache2\conf\ssl.crt>) provides information about whether the command succeeded or failed and will state whether it used the files located in the ssl.crt folder.
       
15. Start the following services:
     
    McAfee ePolicy Orchestrator Event Parser 
    McAfee ePolicy Orchestrator Server
       
16. Look in the DB/logs/server.log to ensure that the Agent Handler (Apache server) started correctly. It should state something similar to the following:
     
    20090923173647        I           #4108  NAIMSRV      ePolicy Orchestrator server started.
     
    If it does not, there will be an error similar to the following: 
     
    20090923173319       E          #4736  NAIMSRV      Failed to get server key information. 

- Link

 - wong chee tat :)

The Security Update Guide

Link




- wong chee tat :)

Release Notes for Apache OpenOffice 4.1.4

Translations:  Dutch (nl) | French (fr) | German (de) | Italian (it) | Russian (ru)

• Release Notes for Apache OpenOffice 4.1.4
  • General Remarks
  • Improvements/Enhancements
  • Bug Fixes
  • Language Support
    • Updated translations available in Apache OpenOffice 4.1.4 include:
    • Updated dictionaries available in Apache OpenOffice 4.1.4 include:
  • Platform Support
  • Known Issues
  • Installation Information
  • Stay informed about Apache OpenOffice

General Remarks

Apache OpenOffice 4.1.4 is a maintenance release incorporating important bug fixes, security fixes, updated dictionaries, and build fixes. All users of Apache OpenOffice 4.1.3 or earlier are advised to upgrade. You can download Apache OpenOffice 4.1.4 at the usual place. Please review these Release Notes to learn what is new in this version as well as important remarks concerning known issues and their workarounds.

Only use the original website "https://www.openoffice.org/download/" to download. The installed software can be verified with the About box (see menu "Help - About OpenOffice) by comparing the numbers with the reference data on the download webpage (see the text in the light green box). For Apache OpenOffice 4.1.4 it has be to be "AOO414m5 | Build ID 9788 | SVN r1811857".

Improvements/Enhancements

• Several updates for language dictionaries
• Some translation fixes in the UI
• Bug fixes
• Security improvements
• Updated graphics/logos (new Apache feather)
• Enhancements to the build tools (for developers)

Bug Fixes

• BZ 119208 Cannot select a different icon set (menu "Tools - Options - View").
• BZ 125147 Crash when applying a style to a new text document.
• BZ 127176 Different installed Java Runtime Environment cannot be selected (menu "Tools - Options - Java").
• BZ 127553 Update links doesn't work for sections in 4.1.4-RC4

For a complete overview of all resolved issues please see the list in Bugzilla.

Language Support

OpenOffice 4.1.4 supports the same languages as the previous releases:

Updated translations available in Apache OpenOffice 4.1.4 include:

Basque (eu)	Galician (gl)	German (de)
Hebrew (he)	Norwegian (nb)	Valencian RACV (ca-XR)
Valencian AVL (ca-XV)	Swedish (sv)

Updated dictionaries available in Apache OpenOffice 4.1.4 include:

Asturian (ast)	Catalan (ca)	English (en-GB)
English (en-US)	German (de)	German Austria (de-AT)
German Switzerland (de-CH)	Portuguese European (pt)	Russian (ru)
Spanish (es)	Valencian RACV (ca-XR)	Valencian AVL (ca-XV)

For a complete list of available languages and language packs see the download webpage (click the language drop-down-box)

Platform Support

Binaries are still provided for the same platforms as for the previous OpenOffice 4.x releases:

• Windows
• macOS
• Linux 32-bit (RPM and DEB)
• Linux 64-bit (RPM and DEB)

Known Issues

• For macOS users:
  • Apache OpenOffice 4.1.4 will be flagged by the Gatekeeper facility in Mac OS X. This is a feature to help guard against malware on recent Mac OS X systems.
    • For Mac OS X up to 10.11 "El Capitan": There is a procedure laid out at the following link to allow applications not installed from the Mac App store to run. See the Mac support article.
    • For Mac OS X 10.12 "Sierra": In Finder, Control-click or right click the icon of the app. Select Open from the top of contextual menu that appears. Click Open in the dialog box. If prompted, enter an administrator name and password.This is needed just the first time you launch Apache OpenOffice.
  • Due to a known bug in Oracle Java installations of Apache OpenOffice on OSX that do not have the legacy Apple Java 6 installed will not be able to recognize Oracle Java 7, 8, and possibly 9. The work around until the Java bug is fixed is to install the legacy version of Apple Java from the following link: Legacy Apple Java 6. This will allow the portions of AOO that require Java to run properly.
• For Windows users:
  
  • Apache OpenOffice 4.1.4 supports Java 8, which is the recommended configuration; but (especially on 64-bit Windows) you might receive warnings about the Java version being defective. In that case, download and install the Microsoft Visual C++ 2010 Redistributable Package.
• For developers:
• The OpenOffice SDK won't build with Java 8. Either build with --disable-odk or see the dev list archives for possible solutions.

Good time to install!

- wong chee tat :)