The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
After you verify that the target server meets the requirements described in “Requirements and Dependencies,” you can use these checklists to prepare and optimize your server for installation:
A framework of best practices, recommendations, and other preparatory tasks can enable your Security Manager server to run faster and more reliably.
You can use this checklist to track your progress while you complete the recommended tasks.
![]() |
|
---|---|
![]() |
1. |
![]() |
|
![]() |
3. If you plan to install Security Manager on a server that you have used for any other purpose, first back up all important server data, then use a boot CD or DVD to wipe all data from the server. We do not support installation or coexistence on one server of Security Manager 4.9 and any release of Common Services earlier than 4.2.2. Nor do we support coexistence with any third-party software or other Cisco software, unless we state explicitly otherwise in this guide or at http://www.cisco.com/go/csmanager. |
![]() |
4. |
![]() |
5. |
![]() |
6. Note Back up your Security Manager Server and stop Security Manager services before any patches or Windows updates are applied. Cisco recommends that you apply patches and Windows updates during the maintenance window, when Security Manager is not running. |
![]() |
7. |
![]() |
8. |
![]() |
9. |
![]() |
10. |
![]() |
11. |
![]() |
12.
|
![]() |
13. Check your software and server hardware documentation to learn if your particular server requires any other services. |
![]() |
14. |
![]() |
15. |
![]() |
16. Note We strongly discourage network shares. We recommend that you disable NETBIOS completely. |
![]() |
17. |
You must complete the following tasks before you install Security Manager.
![]() |
|
---|---|
![]() |
![]() 1. Note Re-enable your antivirus software after installation, but you must exclude the NMSROOT directory and the eventing folder from scanning as long as Security Manager is installed on the server. |
![]() |
2. |
![]() |
3. |
![]() |
4. If Terminal Services is enabled on the target server in Application mode when you try to install Security Manager, an error will stop the installation. |
![]() |
5. |
![]() |
6. |
![]() |
7. Note The path to the license file must not contain special characters such as the ampersand (&). |
![]() |
8. |
![]() |
9. |
![]() |
10. |
![]() |
11. To enable or disable FIPS on Windows Server 2008, follow these steps: a. b. c. d. e. |
![]() |
12. To disable IE ESC on the server where you are preparing to install Security Manager, follow these steps: a. b. |
![]() |
13. |