Let's increase the diameter of the cash inflow pipe!
Simplistic example: The bigger the cash inflow pipe, the fast the cash in hand.
But should we also tighten cash outflow? If so, how much to tighten?
- Pic from Internet
- wong chee tat :)
Ads
Tuesday, 17 October 2017
Increase Cash Inflow
Let's increase the diameter of the cash inflow pipe!
Simplistic example: The bigger the cash inflow pipe, the fast the cash in hand.
But should we also tighten cash outflow? If so, how much to tighten?
- Pic from Internet
- wong chee tat :)
Blog Updates: Minor updates:
Blog Updates: Minor updates:
- Update labels
Will continue to make minor improvements for this blog!
- wong chee tat :)
- Update labels
Will continue to make minor improvements for this blog!
- 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
- 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
- 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
- wong chee tat :)
McAfee KB71825: ePolicy Orchestrator installation/patch upgrade checklist for known issues
Environment
McAfee ePolicy Orchestrator (ePO) 5.x
Summary
The following is a checklist for known issues with full product installations and patch upgrades for ePO.
IMPORTANT: It is necessary to follow each step in this document exactly as it appears to reduce the chance of an upgrade or migration failure.
(Optional) Reduce the drive space requirement by purging log files and temp files from the ePO installation directory prior to upgrading:
See KB78121 to determine whether the id="orion.server.https" attribute is missing from the server.xml file. The article contains instructions to add id="orion.server.https" to the list of attributes if it is missing.
Disable run immediately client tasks:
When the McAfee Agent extension is upgraded in ePO, previously executed tasks that are configured to "Run Immediately" execute again on the next agent-to-server communication. This can cause various products to be redeployed to clients. To prevent this issue, before you upgrade, disable any tasks configured to "Run Immediately." For more information, see KB74420.
Disable ePO server tasks and any Windows scheduled tasks that may be set to run on the ePO server:
Disable any tasks that would interfere with the installation (such as purge events, pull tasks, and replication tasks). If you are using Drive Encryption, it is important to disable all LDAP Sync tasks before initiating the upgrade of the ePO server. Ensure that there are no LDAP Sync tasks running. If any are running, wait for them to complete. For more information see KB84690.
For information on editing tasks, see the "Server Tasks" section of the product guide for your current version of ePO:
Disable Windows updates:
Disable Windows updates to ensure they do not interfere with your ePO installation or upgrade. For more information, see https://support.microsoft.com/en-us/help/12373/windows-update-faq.
Disable third-party software:
The 8.3 naming convention must be enabled on the drive where ePO is going to be installed. For instructions to enable the 8.3 naming convention, see Solution 1 in KB51431.
The following steps should be performed on the server hosting the ePO Database:
Ensure that the ePO database has enough space for the upgrade:
It is recommended for the ePO database to have 1.5 to 2 GB of free space for an upgrade. If you are using SQL Server Express, which supports a maximum of 10 GB, you should upgrade to SQL Server if the existing ePO database is 8 GB or more in size.
Eliminate unprocessed events:
Ensure that the DB\Events folder (including Debug) is empty or has minimal events stored before the upgrade. During the upgrade, this folder will be scanned and if there are more than 10,000 events that are not processed yet, it will interrupt the upgrade with a pop-up message stating: "This ePolicy Orchestrator server has more than 10,000 unprocessed events, which may cause the upgrade process to take an exceptionally long amount of time".
Back to Contents
IMPORTANT: It is necessary to follow each step in this document exactly as it appears to reduce the chance of an upgrade or migration failure.
| Getting Started | Important Knowledge Base articles to review before starting your upgrade. |
| ePO Server Pre-Check | Tasks to perform on the ePO server. |
| Database Pre-Check | Tasks to perform in SQL Management Studio and on the SQL database. |
| General Considerations | Best practices that should be completed before starting the setup. |
Review the supported upgrade paths for ePO
See KB86693 for a list of supported upgrade paths.
Review the product or patch release notes for new features
Click here for a list of ePO release notes.
Review the product or patch known issues articles
Review the articles to understand both general known issues and upgrade-related known issues. Click here for a list of ePO known issues articles.
Back up your ePO server
For more information, see KB66616 and follow the steps in the "Backing up the ePO server" section.
See KB86693 for a list of supported upgrade paths.
Review the product or patch release notes for new features
Click here for a list of ePO release notes.
Review the product or patch known issues articles
Review the articles to understand both general known issues and upgrade-related known issues. Click here for a list of ePO known issues articles.
Back up your ePO server
For more information, see KB66616 and follow the steps in the "Backing up the ePO server" section.
Perform the following steps on servers that have ePO installed.
Ensure that the ePO server has enough hard disk space for the upgrade:
Ensure that the ePO server has enough hard disk space for the upgrade:
- System temp drive: Requires 2 GB or more of free disk space.
- ePO installation drive: Could require up to three times the size of the McAfee\ePolicy Orchestrator folder or 20 GB, whichever is greater.
NOTE: If the ePO server is installed on the same drive as the system temp folder, and the ePO installation directory is 15 GB in size, the required available hard disk space in the C drive will be more than 45 GB to account for the system temp folder. In that scenario, you would need 15 GB X 3 + 2 GB = 47 GB of free space. In the same scenario, if the ePO installation directory is 2 GB in size, the minimum size requirement means that the drive must have 20 GB + 2 GB = 22 GB of free space.
(Optional) Reduce the drive space requirement by purging log files and temp files from the ePO installation directory prior to upgrading:
- Stop the ePO services:
- Press Windows+R, type services.msc, and click OK.
- Right-click the following services and select Stop:
McAfee ePolicy Orchestrator x.x.x Application Server
McAfee ePolicy Orchestrator x.x.x Server
McAfee ePolicy Orchestrator x.x.x Event Parser
- Delete the files in the following folders:
IMPORTANT: Do not delete the folders. Delete only the files within these folders.- <epo_installation_directory>\Server\Temp
- <epo_installation_directory>\Server\Logs
- <epo_installation_directory>\DB\Logs
- <epo_installation_directory>\Apache2\Logs
- Start the ePO services:
- Press Windows+R, type services.msc, and click OK.
- Right-click the following services and select Start:
McAfee ePolicy Orchestrator x.x.x Application Server
McAfee ePolicy Orchestrator x.x.x Server
McAfee ePolicy Orchestrator x.x.x Event Parser
See KB78121 to determine whether the id="orion.server.https" attribute is missing from the server.xml file. The article contains instructions to add id="orion.server.https" to the list of attributes if it is missing.
Disable run immediately client tasks:
When the McAfee Agent extension is upgraded in ePO, previously executed tasks that are configured to "Run Immediately" execute again on the next agent-to-server communication. This can cause various products to be redeployed to clients. To prevent this issue, before you upgrade, disable any tasks configured to "Run Immediately." For more information, see KB74420.
Disable ePO server tasks and any Windows scheduled tasks that may be set to run on the ePO server:
Disable any tasks that would interfere with the installation (such as purge events, pull tasks, and replication tasks). If you are using Drive Encryption, it is important to disable all LDAP Sync tasks before initiating the upgrade of the ePO server. Ensure that there are no LDAP Sync tasks running. If any are running, wait for them to complete. For more information see KB84690.
For information on editing tasks, see the "Server Tasks" section of the product guide for your current version of ePO:
- PD26914 - ePolicy Orchestrator 5.9 Product Guide
- PD25504 - ePolicy Orchestrator 5.3 Product Guide
- PD24808 - ePolicy Orchestrator 5.1 Product Guide
Disable Windows updates:
Disable Windows updates to ensure they do not interfere with your ePO installation or upgrade. For more information, see https://support.microsoft.com/en-us/help/12373/windows-update-faq.
Disable third-party software:
- Disable any software that automatically restarts services on your ePO server. This includes disabling monitoring software (such as Microsoft System Center Operations Manager) that might affect the ePO services starting and stopping for the duration of the installation or upgrade.
- Disable any third-party security software that could potentially introduce permissions issues.
The 8.3 naming convention must be enabled on the drive where ePO is going to be installed. For instructions to enable the 8.3 naming convention, see Solution 1 in KB51431.
Run the following steps using SQL Management Studio:
- Click Start, Programs, Microsoft SQL Server, and select SQL Server Management Studio.
- Verify the SQL instance that ePO is using.
Perform either of the following to verify the SQL instance that ePO is using:
- Check the SQL server service name by opening services.msc:
Example: SQL Server (SQLEXPRESS)
- Run the following query in SQL Server Management Studio:
select @@servername
go
- Check the SQL server service name by opening services.msc:
- Ensure correct account permissions.
The account used to access the SQL server must have the following permissions:
- Default database must be master:
- Expand Security, Logins.
- Right-click the account and select Properties.
- Ensure the default database is set to Master.
- Expand User Mapping and ensure that the account has dbo in the schema for the database.
- This account must be the db_owner in the database security properties:
- Expand Databases, your ePO database, Security, Users.
- Right-click the dbo account and select Properties.
- Ensure that the account has dbo in the Default schema for the database.
If you use an NT account to authenticate to the ePO database, ensure that the account has Local Admin rights on the ePO server.
See KB75766 for detailed information on the required SQL permissions.
- Default database must be master:
- Verify the Database Options Properties:
- Right-click the ePO database and select Properties.
- Select Options on the properties page.
- Verify the correct DB collation is set on the SQL server.
See KB73717 for detailed information on supported collation types for ePO.
- Ensure the Compatibility level is set to 100 or higher for the ePO database.
Click Options and ensure Compatibility level is set to 100 rather than 80 or 90. If it is not, select 100 from the Compatibility level drop-down list and click OK.
- Ensure Auto Close is set to False.
If it is not, click Auto Close, select False, and click OK.
- Ensure Arithmetic Abort Enabled is set to True.
If it is not, click Arithmetic Abort Enabled, select True, and click OK.
- Disable SQL database mirroring or Always on, if it is used.
See KB86152 for detailed information about how to verify if it is enabled.
The following steps should be performed on the server hosting the ePO Database:
- Ensure the SQL browser service is running:
- Press Windows+R, type services.msc, and click OK.
- Locate the SQL Server Browser service and ensure that it is started and running.
If it is not, right-click the SQL Server Browser service and select Start.
- Ensure that Microsoft KB 2653857 is applied on the SQL server. If that is not possible, disable SQL Force Encryption before upgrading (if it is enabled):
- Click Start, All Programs, Configuration Tools, SQL Server Configuration Manager.
- Right-click Protocols for <instance_name> (MSSQLSERVER by default) under SQL Server Network Configuration, and click Properties.
- Click the Force Encryption drop-down list and select No.
- Click OK.
Ensure that the ePO database has enough space for the upgrade:
It is recommended for the ePO database to have 1.5 to 2 GB of free space for an upgrade. If you are using SQL Server Express, which supports a maximum of 10 GB, you should upgrade to SQL Server if the existing ePO database is 8 GB or more in size.
Eliminate unprocessed events:
Ensure that the DB\Events folder (including Debug) is empty or has minimal events stored before the upgrade. During the upgrade, this folder will be scanned and if there are more than 10,000 events that are not processed yet, it will interrupt the upgrade with a pop-up message stating: "This ePolicy Orchestrator server has more than 10,000 unprocessed events, which may cause the upgrade process to take an exceptionally long amount of time".
Back to Contents
- Review the documentation correction article KB83298 regarding stopping ePO services on remote Agent Handlers instead of disabling them in the Handler List page.
- Ensure that the ePO administrator and SQL account usernames and passwords meet the criteria described inKB66286.
- Perform a preventative measure to avoid Tomcat failing to stop.
NOTE: Perform this procedure only when you are ready to start the installation:
- Press Windows+R, type services.msc, and click OK.
- Stop the ePolicy Orchestrator Server Service and ePolicy Orchestrator Event Parser Service.
- Restart the ePolicy Orchestrator Application Server Service.
- Back up your ePO server. See KB66616 for detailed steps.
Related Information
- Link
- wong chee tat :)
McAfee KB86693: Supported upgrade paths for ePolicy Orchestrator
Environment
McAfee ePolicy Orchestrator (ePO) 5.9, 5.3.x, 5.1.x
Summary
The following table shows the supported upgrade paths for the current versions of ePO:
| Upgrade from version: | Upgrade to version: | |||||||
| 5.1.1 | 5.1.2 | 5.1.3 | 5.3.0 | 5.3.1 | 5.3.2 | 5.3.3 | 5.9.0 | |
| 5.1.0 | Supported | Blocked | Supported | Supported | Supported | Supported | Supported | Blocked |
| 5.1.1 | N/A | Supported | Supported | Supported | Supported | Supported | Supported | Blocked |
| 5.1.2 | N/A | N/A | Supported | N/A | Supported | Supported | Supported | Blocked |
| 5.1.3 | N/A | N/A | N/A | N/A | Supported | Supported | Supported | Supported |
| 5.3.0 | N/A | N/A | N/A | N/A | Supported | Supported | Blocked | Blocked |
| 5.3.1 | N/A | N/A | N/A | N/A | N/A | Supported | Supported | Supported |
| 5.3.2 | N/A | N/A | N/A | N/A | N/A | N/A | Supported | Supported |
| 5.3.3 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | Blocked |
- Link:
- wong chee tat :)
Subscribe to:
Posts (Atom)