- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Application and Resource Management
- Resource Management
-
Application Management
- Creating an Application
- Modifying an Application
- Deleting an Application
- Editing an Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating Resources with a Group
- Intelligently Associating Resources with a Group
- Transferring Resources
- Disassociating a Resource from an Application Group
- Viewing Resource Details
- Viewing Capacity Rankings
- Multi-cloud Configurations
- Cross-Account Resources
- Resource O&M
- Automated O&M
- Faults
- Change Management
- Resilience Center
- Task Management
- Basic Configurations
- Viewing Logs
- Best Practices
- API Reference
-
FAQs
- Product Consulting
- Resource Management FAQs
-
FAQs About Resource O&M
-
Patch Management FAQs
- What Can I Do If the Patch Baselines Do Not Take Effect?
- What Are the Differences Between the Installation Rule Baselines And User-defined Baselines?
- What Can I Do If Exception all mirrors were tried Is Recorded in the Patch Service Ticket Log?
- Why Can't I Select a Node?
- What Can I Do If the Compliance Report Still Reports Non-compliance for a Patch After the Patch Has Been Repaired?
- What Can I Do If the lsb_release not found Error Occurs During Patch Operations?
- Automation FAQs
- Batch Operation FAQs
- FAQs About Parameter Management
- Resource O&M Permissions and Supported Actions
-
Patch Management FAQs
- FAQs About Fault Management
- FAQs About Change Ticket Management
- Resilience Center FAQs
- Change History
- General Reference
Show all
Copied.
Account Baseline
Creating an Account Baseline
- Log in to COC.
- In the navigation pane on the left, choose Resource O&M > Automated O&M. In the Routine O&M area, click Account Management.
- Click the Account Baselines tab on the Change Account Password tab page.
- For hosts that are not bound to components, the system uses the built-in global baseline to manage host accounts by default. You can also click Create Account Baseline (recommended) to define the host accounts to be managed. The prerequisite is that the hosts have been bound to components. For hosts that are not bound to components, you can perform Creating an Application and then Creating a Component on CloudCMDB.
Figure 1 Creating an account baseline
- Set the baseline name, and add baseline accounts based on service requirements. For example, set Account to root and Account Class to Non-read-only account. Then associate the baseline with components. The associated components use the account baseline to manage hosts.
Figure 2 Baseline information
NOTE:
The prerequisites for an account to be successfully managed are as follows:
1. The UniAgent has been installed and is in the running state.
2. The host is in the running state.
3. The account configured in the baseline exists on the host and can be used to log in to the host.
CAUTION:
To ensure that incremental host instances of a component can be automatically managed, you need to enable Password Change Policy for Component Baseline in Component Baseline Dimension on the Change Account Password > Password Change Policies tab page.
- Click Delete or Modify in the Operation column to modify or delete the baseline as needed.
Figure 3 Deleting and modifying a baseline
CAUTION:
Before deleting a baseline, you need to unbind all associated components.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot