Skip to main content

server build checklist

 Network configuration completed.


Register to RHΝ.


Apply updates and reboot.


Setup time synchronization.


Sentinel one installed on all the 2 servers.


AD configuration has been done.


Sudo to root access has been given to Linux team


selinux has been disabled.


Rsyslog has been enable


Ip address has been reserved.


Computers has been added to Linuxoid OU.


SNMPV3 setup done on 2 servers.


Firewall has been enabled on 2 servers.


Servers have been added to Solarwinds using SNMP polling method.


ure Subtask created DNS entry.


Subtask created for sentinelone


Subtask created for Backup.






************************************************

Build a server


DNS entry has been added for the VM


uln_register


selinux (/etc/selinux/config) has been disabled Rsyslog has been enable


Added Disk and created file-system


Mount disk u01, u02


Sentinel-one has been installed on the VM


SNMP has been configured & Solarwind monitoring enabled


Added VM to AD group and user has been added in the group for


login using AD credential


Sudoers has been configured


DHCP reservation has been done for IP


yum update --security


OU Movement has been completed


Subtask created DNS entry


Subtask created for sentinelone


Subtask created for Backup.

Comments

Post a Comment

Popular posts from this blog

patching tasks

 Patching a Linux system is a critical task to ensure that the system remains secure, stable, and up-to-date with the latest features and fixes. Here’s a comprehensive guide to the tasks involved in Linux patching: 1. Pre-Patching Preparation Backup System : Ensure you have a full system backup, including critical data, configuration files, and applications. Test the backup to verify its integrity. Check Disk Space : Verify that you have enough disk space, particularly on /var , /tmp , and /boot partitions. Review Current Patch Level : Determine the current patch level and installed packages using package management tools like yum , apt , dpkg , or rpm . Check System Logs : Review system logs to identify any issues that might affect the patching process. Test in a Staging Environment : If possible, apply patches in a staging environment that mirrors production to identify potential issues. Notify Stakeholders : Inform stakeholders about the scheduled maintenance window and expecte...
Post a Comment
Read more

Linux Prepatching tasks

 Pre-patching tasks in a Linux environment are critical to ensuring a smooth and successful patching process. These tasks help in minimizing downtime, preventing issues during the patching, and ensuring the system's stability. Here’s a checklist of common pre-patching tasks you should perform: 1. Backup Critical Data Full System Backup : Perform a full system backup, including configuration files, databases, and critical application data. Verify Backup Integrity : Ensure that the backup is complete and can be restored if necessary. 2. Review Patch Notes Understand the Patch : Review the release notes and documentation for the patches you plan to apply. Understand what is being updated and any potential impact on your system. Check Dependencies : Verify that all dependencies for the patches are met, including hardware, software, and configuration requirements. 3. Check System Health Disk Space : Ensure there is sufficient disk space available, especially on /var , /tmp , and /boot ...
Post a Comment
Read more