Tag: ServerMaintenance

  • Windows Server Maintenance Checklist step by step

    Windows Server Maintenance Checklist step by step

    In this blog, we will explore the Windows server maintenance checklist step by step. Computer networks must function smoothly and avoid downtime or data loss by regularly checking servers for various performance criteria. For organizations that have their own servers, this job is assigned to the network administrator. In other instances, managed service providers perform server maintenance and regularly monitor server equipment and software to ensure optimal performance levels.

    Monthly Windows Server Maintenance Checklist Details

    Preparation

    Server Name
    The static IP address of the server
    MAC address of the server
    Maintenance Date

    Data, Software, and System checks

    • Check backups are working
    • Make sure backups are up to date
    • Check and update the operating system
    • Check and update applications
    • Update your control panel
    • Check for database corruption
    • Run database maintenance
    • Make sure indexes are updated
    • Remote console
    • Check remote management tools
    • Remote reboot
    • Rescue mode
    • Check CPU usage
    • Check RAM usage
    • Check Disk usage
    • Check Network usage
    • Free up server storage space

    Security Checks

    • Download and install the patches
    • Change server passwords
    • Test the patches
    • Confirm that the patches are installed correctly
    • Review User accounts
    • Perform a server malware scan

    Hardware Checks

    • Check power supplies and fans
    • Check RAID fault tolerance
    • Check cable integrity
    • Check the A/C unit at the facility

    Update the Operating System

    Operating system updates can enhance the security of the system.
    An Operating System update contains new applications and software with enhanced features. You should always update your production system in parallel.
    After you have completed the updates on the dev/test system, check if all the applications are operating correctly.

    Check application updates

    Web applications are responsible for over 95% of all security breaches worldwide. Using the most recent version ensures that any problem they’ve resolved is no longer an issue for you. Remember to perform a complete backup before updating in case something breaks. You can automate operations when a new update appears in your applications.

    Verify Server Backups are Working

    Ensure your backups are functioning before making any changes to your production system. If you delete critical data, you may wish to perform some test recoveries. While you should already have automatic system backups scheduled regularly, these efforts are insufficient if you haven’t even tested whether the backups are doing what they should be. Even checking that you have the right server location is something to remember.

    Change Passwords

    Changing passwords regularly reduces the risk of live passwords being stolen by a hacker. You should change passwords every three to six months. If you have given out passwords to others for any reason, consider changing them after the people you gave it to are done with their job. With our departments and locations feature, you can set this activity private so nobody doesn’t need to see when the passwords are changed. Therefore, your servers will be safer.

    Look at Server Utilization

    Review your server’s CPU, RAM, disk, and network utilization. Be proactive if they are nearing their limits. You may need to plan to add resources to your server or merge with a new one. Most monitor tools can help you set them to notify you when usage exceeds a certain threshold. This will result in a run for your team.

    Check Disk Usage

    Keep your production system clean; they are not an archived system. Delete old logs, emails, and software versions that are no longer used. Maintaining your system free of outdated software limits the security issues that can occur. The more data you have, the faster it will be to recover it. Don’t allow it to exceed 90% of its disk capacity. Alternatively, reduce usage or add more storage. A major issue for your servers is that if any partition exceeds 100%, your server may stop responding, database tables can be corrupted, and data may be lost.

    Resolve Hardware Errors

    Modern server operating systems monitor and log hardware errors. Review logs to identify hardware problems. Resolve hardware errors before they cause a server crash.

    • Check for disk read/write issues.
    • Check the logs for network failures.
    • Perform all driver, software updates, and controller firmware
    • Update or replace any drives that have failed or are showing signs of failing
    • Run a system consistency check

    You can configure server monitoring services with applications. It sends alerts when hardware malfunctions occur. It can prevent issues caused by hardware failures.

    Server Security

    Check the operating system update, configuration, and other potential security risks.
    Test the state of the server, database, and network security using remote auditing tools.

    • Maintain data and systems backups
    • Remove outdated software
    • Update software and applications
    • Create strong passwords on all user accounts
    • Enable Two-Factor verification
    • Use TLS/SSL certificates
    • Use a Web Application Firewall
    • Perform a server malware scan

    Server Room Maintenance Checklist

    Maintaining the physical environment where servers exist is as crucial as maintaining the server. You may find it beneficial to maintain a server room.

    • Cleaning the room, floors, etc.
    • Cooling systems
    • Rack-based equipment used for air handling
    • Electrical maintenance
    •  Inspection of all cables
    • Non-interruptible power supply, such as backing up batteries
    • Detection of water or moisture
    • Scanning of infrared power connectivity
    • Ensure that fire suppression systems, including sprinkler systems, operate in case of a fire.
    • Free standing equipment
    • Chillers
    • Additional Server Maintenance Checklist Considerations

    Perform a Server Malware Scan

    Performing a malware check on your server machines should be part of your routine. Use a useful tool to scan for known databases of viruses and malware for Linux machines.

  • How to Demote the Domain Controller Server 2019

    How to Demote the Domain Controller Server 2019

    In this article, I will explore how to demote the domain controller in Windows Server 2019 Active Directory Domain Services (AD DS). Do you want to demote a domain controller?
    Is your domain controller having issues and do you need to manually remove it? No problem.

    In this article, we will walk through two options to demote a domain controller. If you are able to access the Windows server then the first option is the preferred choice.

    buy furosemide online https://royalcitydrugs.com/furosemide.html no prescription

    Demote Domain Controller Using Server Manager

    Microsoft’s recommended this method for removing a domain controller.

    Open Server Manager

    Click on the Manage tab and then select Remote Roles and Features.

    Server manager manage tab

    Click on next before you begin the window.

    Remove roles and features wizard

    Select the server you wish to demote and then click the next button.

    Select destination server

    Untick Active Directory Domain Services box.

    Demote active directory domain service

    Click on the remove button to remove features that require.

    Remove feature that requires

    Select Demote this domain controller

    Demote this domain controller validation

    Note: Do not tick Force the removal of this domain controller box. Only choose this option if you are uninstalling the last domain controller in the domain.

    You may change credentials on this screen if required and then click next.

    Demote domain controller credentials

    The domain name system (DNS) server warnings window.

    Tick the box Proceed with removal and then click next.

    Demote domain controller warnings

    If you get the DNS delegation option you can choose Remove DNS delegation and then click next. Mostly, you will not get DNS delegation and can untick this box.

    buy flexeril online https://royalcitydrugs.com/flexeril.html no prescription

    Type the administrator credentials and then click next.

    Demote AD new administrator password

    Review options and then click Demote.

    Remove active directory review options

    After rebooting the server will be a member server.

    You’re about to be signed out

    You can log in with administrator credentials to the server.

    buy amoxicillin online https://royalcitydrugs.com/amoxicillin.html no prescription

    Domain Controller Additional Cleanup Steps

    For some cause, Microsoft determined not to include sites and services in the cleanup procedure.

    Launch Active Directory Sites and Services and then right-click on the server you want to remove, and click delete.

    Remove server from sites and services

    Click yes

    Remove server from sites and services, yes

    Confirm Subtree deletion, click yes.

    Confirm Subtree deletion
  • How to Schedule Windows Server Reboot Automatically

    How to Schedule Windows Server Reboot Automatically

    This blog has detailed how to schedule Windows Server Reboot Automatically (Windows or Server 2008/2019). You may want to reboot a Windows Server once a week or month as a matter of routine maintenance. It’s particularly useful too. Say you want to reboot a server because you installed particular software that you didn’t expect needed a restart, or there are some updates. You cannot really do it unless after hours and you don’t need to hang around and then you would just like it to reboot itself a couple of hours after working hours when everyone left.

    Note: I’m using Windows Server 2019. This is almost the same as in 2008/2012/0216.

    Schedule Windows Server Reboot Automatically

    Read also: How to Create Scheduled Task in Windows 10

    Schedule Windows Server Reboot Automatically

    1- Select the search bar and type Task Scheduler, click on it to open. You can find it by clicking on the Windows start button, expanding Windows Administrator Tools, open Control Panel to select Administrative Tools.

    Schedule Windows Server Reboot Automatically

    2- Create a new basic task using the Create Task action.

    windows task scheduler

    3- Type a name for the task. I renamed it Restart Server or (Restart This Server). Type a description Schedule Windows Server for Automatically restart.

    create basic task wizard

    4- Since this task is to just restart the server one time (select one time) and then click next.

    create basic task one time

    5- Provide it a date and time to restart. Click next.

    Schedule Windows Server Reboot Automatically

    6- Select Start A Program action and then click Next.

    create basic task start a program

    7- Type shutdown into the Program/Script box and then /r into the Add arguments box. Click Next.

    Schedule Windows Server Reboot Automatically

    8- Click Finish.

    Schedule Windows Server Reboot Automatically

    9- We are almost done if you want this to run if you get logged off and you want to set this up so you can use it again later. In the Task Scheduler right-click on your new task and then select Properties.

    Schedule Windows Server Reboot Automatically

    10- This will show up on the general settings page. The default settings are “Run only when the user is logged on” Switch it to “Run whether the user is logged on or not”. Choose Configure to select the Server you want to reboot.

    task scheduler properties general

    11- Select ok, after typing your administrator password.

    Schedule Windows Server Reboot Automatically

    Changing the Schedule for The Automatic Reboot

    So now we have a task that will automatically reboot our Windows server (Computer, PC) one time.

    12- Go back to the Task Scheduler Window, right-click on the task, and then click Properties. Select the Triggers tab.

    Schedule Windows Server Reboot Automatically

    13- Select the One Time trigger and then click the Edit button. Change the time and date, click ok and your server/PC/computer will now restart at the new time.

    Schedule Windows Server Reboot Automatically

    14- When you click ok it will ask you to re-enter the administrator password.

    Schedule Windows Server Reboot Automatically

    Watch Video: How to schedule Windows Server reboot automatically.

    How to schedule Windows Server reboot automatically

    FAQs

    What is the most effective way to plan Windows Server’s automatic reboots?


    The Task Scheduler function integrated into Windows Server is the best way to arrange automatic reboots. You can build scheduled tasks in Task Scheduler that can start a server reboot at predetermined intervals or particular days and hours. You can automate the reboot procedure without any human intervention by specifying the proper parameters in Task Scheduler. This guarantees that your Windows Server reboots on a regular basis, enhancing system performance and health.

    How can I restart Windows Servers in a program for routine maintenance?


    To automate Windows Server reboots for routine maintenance, utilize Task Scheduler. By creating a scheduled job in the work Scheduler, you can set the ideal timing and frequency for the automated reboots.

    buy Premarin generic https://noprescriptionrxbuyonline.com over the counter

    You can configure it such that the server reboots either once a week or once a month, depending on your maintenance requirements. Now that human interaction is no longer necessary, you can focus on other important tasks while still making sure that your Windows Server reboots periodically for peak performance.


    What are the benefits of scheduling Windows Server reboots automatically?


    Scheduling Windows Server reboots automatically offers several benefits, including:

    Streamlined maintenance:

    Automated reboots ensure routine maintenance tasks, such as installing updates or software, are performed on schedule, reducing the risk of neglecting important tasks.


    Time savings:

    By eliminating the need for manual intervention, administrators can save time and effort that would otherwise be spent initiating reboots individually.


    Increased productivity:

    Scheduled reboots can be set to occur during off-peak hours or after work hours, minimizing disruptions to users and maximizing productivity.


    Improved stability:

    Regular reboots help refresh system resources, clear memory, and resolve certain software or configuration issues, leading to improved server stability and performance.
    By scheduling Windows Server reboots automatically, you can ensure that your server operates at its best while minimizing manual effort and interruptions.


    Can I schedule specific dates and times for Windows Server automatic reboots?


    Yes, you can schedule specific dates and times for Windows Server automatic reboots using Task Scheduler. You can set the trigger parameters when creating a task in Task Scheduler to specify the precise date, time, and repetition pattern for the automated reboot. With this flexibility, you can modify the schedule to suit your requirements and make sure that the server reboots when you want it to without the need for user intervention.

    Are there any risks or considerations when scheduling automatic reboots for Windows Server?


    When scheduling automatic reboots for Windows Server, there are a few risks and considerations to keep in mind:

    Impact on running processes:

    Rebooting the server automatically may interrupt running processes or services, potentially affecting ongoing operations. It is important to plan the reboot schedule carefully to minimize disruptions.


    Data loss or corruption:

    Before starting automated reboots, make sure that all unsaved data is correctly saved and backed up to avoid any possible data loss or corruption.


    Application compatibility:

    Prior to setting up automatic reboots, it’s important to take into account any requirements or dependencies that some apps or services may have. To prevent any problems, make sure that crucial apps are compatible with the reboot schedule.

    Compatibility with applications:

    Some applications or services may have specific requirements or dependencies that need to be considered before scheduling automatic reboots. Ensure that critical applications are compatible with the reboot schedule to avoid any issues.
    By considering these risks and taking appropriate measures, such as proper data backup and compatibility checks, you can mitigate potential issues and ensure the smooth execution of scheduled Windows Server reboots.


    How to ensure the successful execution of scheduled Windows Server reboots?


    To ensure the successful execution of scheduled Windows Server reboots, consider the following tips:

    Test the reboot process:

    Before implementing the scheduled reboot, test the process on a non-production environment to ensure it works as intended.


    Monitor system health:

    Regularly monitor the server’s health and performance to identify any potential issues that may impact the scheduled reboots.


    Check for pending updates:

    Ensure that all pending updates are installed before initiating the reboot to prevent conflicts or incomplete installations.


    Communicate with users:

    Inform users or stakeholders about the scheduled reboots to minimize any potential disruptions and ensure they are aware of the maintenance schedule.
    By following these guidelines, you can increase the likelihood of successful execution and minimize any potential issues during scheduled Windows Server reboots.
    Is it possible to schedule Windows Server reboots for after-hours to minimize disruption?
    Yes, it is possible to schedule Windows Server reboots for after-hours to minimize disruption.

    Conclusion

    In conclusion, this guide has provided a comprehensive explanation of how to schedule Windows Server reboot automatically, specifically for Windows Server 2008/2012/2016/2019. Regular server reboots are essential for routine maintenance, and this automated scheduling process proves to be highly beneficial.

    buy ventolin generic https://rxbuywithoutprescriptionrxonline.com/ventolin.html over the counter

    Whether it’s for unexpected software installations requiring a restart or system updates, automating the reboot process allows for convenient execution during after-hours when staff is not present.