Sync AD to 365

Synchronize domain users to Microsoft 365

Set up Active directory synchronization for Microsoft 365 

Syncing On Premise AD & Office 365 through AD connect

This session we will discuss about the steps how to synchronize ADDS to Office 365.

On Premises

ADDS

Cloud User which we wanted to sync users to Office 365

Steps:

Login to your Office 365 Subscription

Below link:

https://admin.microsoft.com/

Download Microsoft Azure Active Directory Connect

https://www.microsoft.com/en-us/download/details.aspx?id=47594

Install AD Connect to On Premises Windows Server

Administrator user office 365:-

Now installing Started

Agree the license and continue process

Here I am selecting customize installation process

 Now need to install required components

Click to install

Installation started

Have selected password hash

Converting passwords into unreadable strings of characters that are designed to be impossible to convert

Click to next step

Admin user and password required and click next

 Again required admin user credentials

Verification

Select domain and click to add directory

Now enter on premises admin username and password

Active directory added click to next

Now need to create UPN Suffixes  

User Principal Name (UPN)? In Microsoft Active Directory, a User Principal Name (UPN) is a username and domain in an email address format. In a UPN, the username is followed by a separator “at sign” (@) followed by the active directory’s internet domain. An example UPN is shariq@querypanel.co.

Go server manager

Click to active directory domain and trust

Click on domain and trust go to properties

UPN Suffixes click to add domain and apply

After creating upn suffixes getting multiple domains

Select domain suffixes

If you can check here office 365 domain is verified

Here selecting the 365 cloud user from OU click to next

User identification click to next

Optional features click to next

Now click to install

Configuration completed

Click to exit and checking the synchronization status

Synchronization status office 365

Synchronization status page

Open Synchronization service manager

Start powershell for force to sync on premises to 365 normal 30 minutes auto sync

PS C:\Users\Administrator> Get-ADSyncScheduler

PS C:\Users\Administrator> Start-ADSyncSyncCycle -PolicyType Delta

These are the simple steps to configure 365 cloud services to on premises

365 User Management

How to add users in Microsoft office 365

Here I am going to explain the steps how to add standard user and admin user in Office 365

Steps: Login to admin.microsoft.com with admin privileges.

I am creating first Standard User.

Click to active users

 Active users list will be appear

Now here creating new user in custom domain

Click to add user

Basic Details about creating user

And next

User cannot changed password and password will send to administrator account

And click to next

Have selected here Business Standard

Now to click next

Select no admin center access and click next

Finish now and login to created user or reset password

So here is the created user’s details

Login as user

Click next here will be authentication check

Download Microsoft authenticator application

Scan and authenticate

Standard User Password

Have Login to Created standard user

Click on Install apps select app and download it

MS Office Setup File Downloaded

Install Downloaded file and use the office 365 Services.

ADD Admin User IN Microsoft Office 365

Fill here required details about Administrator which you wanted to create

Here password automatic generated and Global Admin will received the admin password on registered email id

Once done next button

Select office license and click to next

Administrator account assign

Selected administrator roles and click to finish

Created admin user

Created admin user Dashboard

Custom Domain M 365

How to Add Custom Domain in Office 365 Cloud

// Youtube :

https://www.youtube.com/channel/UCnBUWkRJBp2xA6FLYlMd2EA?sub_confirmation=1

Steps:

These are the 4 steps we need to follow to add domain in Microsoft Office 365

Add Domain

Domain Name

Domain Verification

Connect Domain

and

Finish

Login to Microsoft admin portal with admin privileges

// https://admin.microsoft.com/

Once Login to admin office 365 admin center

Click to show all once expand

Now click to setting

click to domains

Once domain page will open click to add domain

Type to domain (your) name

Select TXT Record or direct login to your    domain provider

Click Continue

So, here TXT Records

Need to add in DNS TXT Record

..

I had Godaddy Domain so I need to update here.

Once records updated click to verify Domain

click continue

need to add DNS Record

adding DNS Records on Godaddy

Updating DNS Records in Godaddy

DNS Records update

And Domain Verified

These are the simple steps to add domain and verify domain in Microsoft Office 365

FSMO Roles

FSMO Roles: FSMO roles is a feature in Active Directory

FSMO roles is dependent on Replication.

Flexible single master operation is a method active directory method for replication active directory tasks.

Microsoft introduced flexible single master operation (FSMO) roles in 2003.

Introduced because if Primary DC is down no changes could be made until it will up again.

Once we have install active directory it’s automatic available to Active directory.

FSMO roles give the confidence that Active directory working perfectly

FSMO having 5 Roles:

1: SCHEMA Master.

2: Domain Naming.

3: PDC Emulator.

4: RID Master.

5: Infrastructure Master.

Note: Before starting it need to understand Replication.

Replication type:

a. intrasite replication

b. intersite replication

a. intrasite replication –it’s replicate 24*7 – its also called as live replicate

b. intersite replication — replication between domain to domain call as intersite replication – replicate time between 1 tree to another tree is 180 Minutes.

        intersite replication taking maxmix 180 Minutes to replicate between each other.

Fsmo role: divided into two categories:

1. forest wide fsmo roles

        a)   schema master – perform the Read write copy  and user login operations  of active directory ,Managing attributes, its try to avoids conflict between trust domain users

             Example: if we create same user 2 both domain and tree it will automatic delete 1 user from domain between 180 Minutes.

        b)   Domain Naming – responsible to take care of not to create any same name domain and child domain, managing domain creating modification or deletion.

2. Domain wide fsmo roles

        a) PDC Emulator – if password changed it will replicate to pdc – Password Authentication/Failure control by PDC Emulator.

            /Authentication failure / PDC Primary Domain Controller (pdc) –

            it’s a time synchronize technique  – basically PDC Emulator use to manage time synchronization to all forest domain.

        b) RID Pool: maintains the global RID space for an entire domain. CN=RID Manager$,CN=System,DC=domain_name.

           RID Master allocate unique users groups and objects and etc. if RID is not running we cannot create a user or group in DC.

        c) Infrastructure Master: Help to replication user in Infrastructure , help to control the communication between domain and child domain,

           Infrastructure resolved the Access control Lists between domain and sub domains.

Domain/Tree/Forest ?

Domain: an office infrastructure when server and client system working together –

Client services dependent on server is called domain.

Domain is a method to managing clients and Policies managed by centralize server.

CLIENTS and system working together with the help of server and dependent on server is known as domain. If there is any issues on server clients

Cannot do anything.

Like example:

SBI Bank having branches in Bihar Cities, one City Branch domain having technical issues so overall city branches facing the issues.

So, clients totally dependent on City Domain.

So, that’s why clients and server work together is known as domain.

What is Tree?

Collection of Multiple Domain is known as tree.

Multiple domain working together known as Tree.

Example: SBI having branches in Overall Bihar .In every city having separate Branches.

So here overall Bihar having multiple branches. So head office will be tree.

What is forest?

Collection of multiple Tree knows as forest.

Example: in India overall Indian States having separates branches,Bihar,Delhi,UP and etc..

So, states having multiple tree- suppose single state called as tree,

So collection of tree know as forest: suppose overall state call as forest.

Can’t Connect to Internet?

Here I will share the steps

 How to troubleshoot.

How to Troubleshoot Internet if you are not connected to internet

Once you will face any kinds of network connection issues

Open command promote

Win+r

Type cmd

So, type ipconfig or ipconfig /all

I am not getting any IP Address but adaptor displaying undefined network

So, there is multiple options to troubleshoot Network connection

First Method:

Right click to active adaptor and disable adaptor

Now enable it

Still internet is not working

Still internet is not connected showing undefined network

Now,

Checking step 2:

Sometimes same ip address assigned to multiple devices this can be a loop hole

ipconfig /release

C:\Users\shari>ipconfig /renew

domain name system (DNS)

If still not working flushdns

If still not working insert DNS like Google or Oracle dns

216.146.35.35  dns

216.146.36.36  dns

After updating static dns internet is working

Or we can also try google.com dns

IP addresses 8.8.8.8 and 8.8.4.4 as your DNS

So main cause is our DNS

So this is the process to rectify network issues

Internet pinging status

Static Internet Protocol (IP)

How to Assign Static Internet Protocol (IP) to Server and Laptop/Desktop PC

Press Win key and r

And type

Ncpa.cpl

One popup window will be open similar to this

Right Click on active Network Adaptor

Go to properties

Select IPV4 Address click select the Properties and edit

Here will apply static IP Address

Here you need to check the IP Series Class

According to you IP Series you need to assign IP to PC or Server.

We need to Assign Internet Protocol series with subnet

Note: not necessary to add Default Gateway or DNS it will auto fetch  

Once assign static IP Check the Network Status

IP Address Status

Distributed File System

DFS is a method or a process to increase the consistency of Shared file server.

DFS in a Windows Server Infrastructure & DFS Replication

It’s difficult to recall all file server in Infrastructure so, Microsoft implemented Distributed file server.

DFS is a technology to manage multiple shared files from single server but actually DFS picked the data from original location.

Distributed File System- (DFS) – DFS is a Windows Server feature which allows System Administrators to create a single namespace to provide a replicated sharing infrastructure across the network. 

Here I am going to explain how to install DFS in your Infrastructure.

Select which wins server you wanted to become Primary File shared server.

Go to windows server

Open windows server manager.

Click to add roles and features

Installation will be on Role Based feature-based installation

—Steps

Install Distributed File System from server Manager

Start DFS from tools

Create new Namespace server

    Again, create new namespace server inside created namespace server

Create new folder inside namespace

Add folder target for replication jobs

—     

Select DFS Replication and Namespace

Once selected click too next

DFS is ROLES based installation.

And roles added make all default installation.

(We need to Install DFS Roles on all File Server which will be associate with Main File Server.

Like example: I am having Primary Server I need to associate all my file server will associate with Primary server with the help of DFS ACTUALLY file server will be on his original location but they act like hosted with primary server.

)

Check the features leave as default and click too next

Now click to install

Once installation done click to tools

Now close wizard after installation done

Now click to tools and select dfs

Once DFS Wizard open click to namespace primary file server and create new namespace

Enter the host namespace server so, primary server will be hosting browse primary server

Once select server name click to next

Time the Shared file name edit permission setting click to custom permission add users and apply

Now select domain based namespace

And click to create namespace

Once done close wizard

Now adding the file server to primary server inside the created namespace

Right click on created namespace and add new namespace server

Browse file server machine name and assign permission and click to ok

Click ok Wizard

Namespace server having two now

So, now need the target folder right click and click new target folder

File Server Directory

Click to folder right click and select to folder target

Browse the target folder and select that

Once selected click okay

Replication job verification click yes

Once replication wizard change the replication name or leave as default

Now click to next

Primary member

Topology

Click to next

Now click to create replication job

Created successfully

Replication one server to another server

Now here I am checking and sharing File Server using Secondary Server (Because I don’t want to share my Primary server’s name to Infrastructure users).

Here: I am having all data to my primary server but just using to replicate and hide my primary server details to users.

Start DFS in Secondary server

Assign user permission

Domain based name space

Now click to create

Namespace created close the wizard

Right click to created namespace and create new namespace to created server

Browse server

So now here NEW namespace server creating behalf of bdc server

Namespace server status

Namespace servers

Now creating the folder

Browse the shared folder and select that

Selected folder

Click okay

Created folders

Now select the folder and add the replication target

Select the folder target

Now click okay

Now replication job will be created

Once replication started here configure it

Again, click to next

Select the primary server

Select full mesh

Schedule bandwidth

create replication job

Created replication job

Directory Structure

using DFS useful for even security complete hide the Directory Structure

Workgroup/Domain Group

:

Domai:Domain is a Group of Resource specfic by the name.
Domain is a method to organize a group with a name.

Domain is a resource management process which can be assign by the name and associated with the Internet Protocal IP Adress.

Domain is the address of Website like public domain and private domain
example: hotmail.com/gmail.com — it’s a domain but it’s associated with IP Address.

kinds of domain:
Public Domain availability to everyone
Example
google.com/facebook.com and etc.

Private Domain only authorized users.
querypanel.local
abc.local or etc

:

Workgroup: workgroup is a method to arrange self contained computers system in any network. workgroup is not connected to any server.
workgroup pc is not under centralize management system not having the any security policies.

WORKGROUP Domain collection of self contained computers
A workgroup primarily uses a pee to peer networking architecture
in which each computer is self-contained, with its user account
permissions, memory, and importance. Furthermore, the security of these systems is questionable.

no centralized control over the devices in the workgroup.

Domain group: Domain group is a process to manage Centralize pc and server. a domain controller is used to manage all connected pc server in the domain Group.

Centralize control to all devices over the domain group.

Difference Between work group and domain group:

Workgroup: all system and pc / servers is in the peer connection but there is not any centralize management.

workgroup is also knows as a Individual management system or self control system.

example workgroup: in every pc/server need to assign policies individually.
less secure workgroup infrastructure.

Domain: in Domain group a centralize server managing all connected devices like server, pc, printers, switches and etc.
Domain Group can set the centralize policies and security and assign the roles as per the profile and requirement.

example: if Domain Admin allow to use the resource then it can be use otherwise they haven’t having access.

Mostly in Offices Infrastructure having Domain Group authentications because we can apply the policies according the IT Protocol.

Antivirus

Antivirus: Antivirus is a software to protect you from unwanted thread.

Example: you can say Antivirus protect individual level protection method it’s protect you according to your Configuration of Antivirus.
Antivirus software is the process to detect the virus remove the virus or quarantine virus.

Antivirus: Antivirus is a method to protect your pc from unwanted threat. an antivirus is a individual pc protector.
qulity of antivirus dependent on the categories.
kinds of antivirus protection:
browser surfing protection.
software protection
disallow unwanted threat
safe browsing.


how does a antivirus work:

  • Signature Based detection.
  • heuristic based detection.
  • behavior based detection.

Firewall

Firewall: A network Security method to keep you safe from non authorize access and packets will receive only authorize and filter access.
Firewalls typically work on the network layer and transport layer, some are also capable of working as high as the application layer.

Firewall is a defense system of any network Firewall.
Firewall is a security method of any network firewall.
firewall always keep you safe
Firewall keep prevent from hackers and non authorize access internal and external.

A firewall performs the task of inspecting network activity, looking for cyber threats by comparing data against
an extensive catalog of known threats.
They can also detect abnormal activity, which may signal a potential threat

Firewall is a two way protection security method or protocol,
Firewall used to protect internal threat and external threat.

TYPES OF Firewall protection Hardware device and software.
hardware firewall

A hardware firewall acts as a gatekeeper and antivirus solution for your server.
It sits directly behind the router and can be configured to analyze incoming traffic,
filtering out specific threats as they come across the device.

Hardware Firewall Network protection dependent how do you configure your firewall.
which security policies you have applied.

Example: I am using PfSense firewall. Linux Kernel Firewall.
have configure according to Infrastructure.

so, allow traffic disallow traffic.
some of the customized good firewall having option to protect IT infrastructure to use Proxy Server.

Firewall is the Gatekeeper of any Network. it’s filter network traffic incoming and outgoing network traffic.
Firewall is protector of entire network associated with them.

Firewall: Firewall is used to protect your internal Network from unwanted thread.
Firewall is the protector of your internal Network from outside thread.
firewall is a two way protection method.

Hardware Firewall protect the entire firewall.
implemented on the Router Level to protect the entire network.

firewall only allow authentic traffic and block unwanted traffic.

What can firewall do?
Focus on security decision.
stop hackers to enter your network and pc.
firewall allow which program can access internet.
Authentication managed by firewall rules

every operating system having inbuilt software firewall.
example:
if you are surfing internet you have visited so many sites and application from that site
you will not get any thread or any virus software’s.

in simple language you can say a firewall is a protector of your workplace infrastructure
in every pc having default windows firewall protector.

one more example:
in infrastructure in one pc having virus and thread, so in this scenario firewall will also can deal with internal thread or virus
that’s why firewall is a two way protector.

types of firewall.

  • Hardware: in workplace or home network if you are having hardware firewall enable then
    hardware firewall will uniquely identify all pc connected and assign network address
    and cross check browsing
  • Software Firewall: Software firewall protect the individual computer or single computer.

FSMO Roles

FSMO WHY DO WE REQUIRED?

Microsoft split the responsibilities of a DC into 5 separate roles that together make a full AD system.

FSMO stands for Flexible Single Master Operations. Microsoft Active Directory is by far the most widely used domain authentication service across the globe ever since it was released in 1999 (in Windows Server 2000). Over the decades Microsoft has made many advancements in its Active Directory to transform it into the secure system we are using today.

One of these updates included the introduction of a Single Master Model. In this model- only one domain controller could make the required changes in a domain, while the other DCs would only complete authentication requests.

This model created a single point of failure, which means if the master or primary domain controller goes down, there is no way to make changes to the domain until the master DC is back up.

To remediate this issue, Microsoft separated the responsibilities of a DC into multiple roles. The administrators could then assign these roles to multiple domain controllers, and if one of the DCs would go down, the other DCs could take over the missing role and business continuity would remain intact.

This concept is named the Flexible Single Master Operation or FSMO for short, and the roles are known as FSMO roles.

FSMO stands for Flexible Single Master Operations. Microsoft Active Directory is by far the most widely used domain authentication service across the globe ever since it was released in 1999 (in Windows Server 2000).
Over the decades Microsoft has made many advancements in its Active Directory to transform it into the secure system we are using today.

One of these updates included the introduction of a Single Master Model. In this model- only one domain controller could make the required changes in a domain,
while the other DCs would only complete authentication requests.

This model created a single point of failure, which means if the master or primary domain controller goes down,
there is no way to make changes to the domain until the master DC is back up.

To remediate this issue, Microsoft separated the responsibilities of a DC into multiple roles. The administrators could then assign these roles to multiple domain controllers,
and if one of the DCs would go down, the other DCs could take over the missing role and business continuity would remain intact.

This concept is named the Flexible Single Master Operation or FSMO for short, and the roles are known as FSMO roles.

FSMO gives you confidence that your domain will be able to perform the primary function of authenticating users and
permissions without interruption (with standard caveats, like the network staying up).

FSMO Role Scope
Schema Master Forest
Domain Naming Master Forest
Primary Domain Controller Emulator Domain
RID Master Domain
Infrastructure Master Domain

Schema Master
The Schema Master role manages the read-write copy of your Active Directory schema. The AD Schema defines all the attributes –
things like employee ID, phone number, email address, and login name – that you can apply to an object in your AD database.

Domain Naming Master
The Domain Naming Master makes sure that you don’t create a second domain in the same forest with the same name as another.
It is the master of your domain names. Creating new domains isn’t something that happens often, so of all the roles,
this one is most likely to live on the same DC with another role.

RID Master
The Relative ID Master assigns blocks of Security Identifiers (SID) to different DCs they can use for newly created objects.
Each object in AD has an SID, and the last few digits of the SID are the Relative portion. In order to keep multiple objects from having the same SID,
the RID Master grants each DC the privilege of assigning certain SIDs.

PDC Emulator
The DC with the Primary Domain Controller Emulator role is the authoritative DC in the domain. The PDC Emulator responds to authentication requests,
changes passwords, and manages Group Policy Objects. And the PDC Emulator tells everyone else what time it is! It’s good to be the PDC.

Infrastructure Master
The Infrastructure Master role translates Globally Unique Identifiers (GUID), SIDs, and Distinguished Names (DN) between domains.
If you have multiple domains in your forest, the Infrastructure Master is the Babelfish that lives between them.
If the Infrastructure Master doesn’t do its job correctly you will see SIDs in place of resolved names in your Access Control Lists (ACL).

//

Flexible Single Master Operation (also known as FSMO or FSMO Roles).

Primary Server FSMO Roles

Netdom query fsmo

Secondary server will also getting same roles but secondary server not having complete authority like Primary DC

If Primary Server having issues need to seize the fsmo roles after that Backup DC will retain complete authority

So, here I used to power off Primary Server

Primary DC is not active (Server Down)

Now type in PowerShell

But still, I will get all 5 FSMO roles

In secondary server I am getting all 5 Roles

Type

In Backup DC

Ntdsutil

PS C:\Users\administrator.VRE> ntdsutil

Just type only roles  and press enter

Type connections

Now need to connect to in backup Domain Controller like—

Connect to server bdc.vre.local

Now quit from connection press type q and enter

Here we need to seize all fsmo roles from primary server

Primary server is not running but fsmo roles with primary server need to seize the roles and allocate to secondary server

netdom query fsmo

fsmo maintenance: Seize infrastructure master

And press

Yes

fsmo maintenance: Seize naming master

fsmo maintenance:  Seize PDC

Seize RID master

Seize schema master

Now type quit

And quite from fsmo maintenance

So, after seize all 5 roles from Primary DC and assign to Secondary dc

If you can check after seize all roles

Now Backup domain having all fsmo roles

netdom query fsmo

Go to Active Directory users and computers

Right click on domain and click on operation masters

Now, check there

PDC

Infrastructure

MBR/GPT Difference

MBR/GPT Difference

Bare metal server — Install OS to Direct Physical server know as bare metal server.

Master Boot Record

MBR—-

MBR Support BIOS Legecy mode

it’s old partition table

MBR Support up to 2TB Hard Disk not more then 2 TB  Hard Disk

it will support 3 Partition table

slow to boot

no unique identification

crrupt data is not recoverable

not much secure only password on BIOS

boot partition and data store in one place.

How to check boot VM running on which Firmware in VMWARE

Click to edit

Vmware machine setting in any os

Click on vm and edit machine expand BOOT options

Check and select the firmware

So here selected machine is running MBR disk Format

Master boot record support BIOS.

GPT  —–

GUID Partition Table

GPT Support for UEFI Mode -VMWARE Vsphre EXSI using EFI –UEFI and EFI is same.

it is new partition table

it is support up to 10 TB

GPT Support 128 Primary partition

Fast boot

Universally unique identifiers

Cyclic Redundancy Check (CRC) GPT notic the problem and able to recover automatic

data can easly recoverable

more secure

boot partition and data stored in multiple places

want to check which boot firmware supporting go to machine click to edit

click to VM options

expand Boot Options

Firmware is currently EFI(UEFI) mode

On-Premises sys Azure

On-Premises sys Azure

synchronize on premises ad with azure ad

Click on Azure Active Directory

Click on all users and create new user

Create new user

Basic user details

USER PROPERTIES DETAILS

IN ASSIGNEMENTS tab

Click on Add role

Need to select Global Admin

Click to create Global Admin user for syns on Premises Ad to Azure Claud

Once user Global Admin User created need to verify it

Once user created while login to first time need to reset the default password and authenticate with your phone application

Click to next

Click next

Click next

Scan phone app authenticator

Authentication done

Now need to Install Azure AD Connect to on-premises Domain

Once download done click to install AD Connect

Link : https://www.microsoft.com/en-us/download/details.aspx?id=47594

Now installing AD Connect

Click to continue

Can use customize and express but here implementing…. Custom

Click to install

If you  get error click to specify custom location

Click to next

Azure global admin user

Authenticate it

Click on add directory

Type domain admin username and password

Click and next

Click too next

Synchronization all AD and ou

Identify user and Click to next

Filtering all users

And click to next

Optional features

Configure

And click to install

So, configuration completed

Open synchronization service manager check the status

Check the adds

Status user synchronization with azure directory

Status

Check on azure portal user synchronization status

Overview

Click on azure active directory click all user

Audit logs

Sign and logs

Get-ADSyncScheduler

In every 30 Minutes it’s sync

Forcing a Delta sync on Azure AD

As illustrated above, a delta sync synchronizes all the changes made since the last sync. Forcing a delta sync is crucial, for example, when you have made key changes to users in your Active Directory, and you’d like the changes to reflect immediately. Carrying out a delta sync, for example, speeds up the sync of a new user to Microsoft 365, enabling the assignment of licenses immediately. 

Start-ADSyncSyncCycle -PolicyType Delta
Force to sync status




Forcing a Full Azure AD sync

You rarely need to do a full Azure Active Directory sync as and Azure AD administrator. A full Azure AD sync takes a lot of time to sync as it goes through all the Active Directory objects and synchronizes them again. The only use case that you need to do a full synchronization is when you change the Azure AD Connect configuration.
However, in case you’d like to run a full Azure AD sync, then use this policy type initial PowerShell command:

 
 
 
 
 
 
 
 
 
 
Verify Custom Domain to Azure Cloud
 
 

Verify Your Custom Domain in Azure Active Directory

 
 
 
 

Add your custom domain to Azure AD

  • Go to Azure portal then Sign in to the Azure portal.
  • Then Select Azure Active Directory
  • Select “Custom Domain Name” from Azure Active Directory,
  • And then Click “Add custom domain“.
·       Custom domain name field, enter your registered domain name.


 
 

The unverified domain is added. domain page appears showing your DNS information. You need it later to create a TXT record to configure DNS.

Log in to your GoDaddy account

and add field add new record in TXT format mention below

Configure DNS with a TXT Record

Then click Add to add a TXT record then add Record

Now click to verify

https://account.godaddy.com/products

Custom Domain Name is successfully verified

Custom Domain Name is successfully verified

HOW to Host web application in Azure CLOUD

CREATE NEW app services

Assign new application name and select the plan click to next

Adding Custom domains

 

 

Note:

Need to add CNAME and TXT record to hosting provider

So I am using godaddy domain services

Login to domain provider

Add the details

Cname

 

 

 

Updated records

 

 

Now need to validate domain

Domain validated and click to add

SSH Login

 

 

 

 

 

 

 

 

 

 

 

Centralize Printer Server 

How to add centralize Printer Server

Install Print and documents and services using Windows Server Manager

Once install done click on tools and start Print Management

Expand print Servers and click to printers

Now click on add printer

If printers running in your network search or add using IPV4 Address

Having multiple printers select one of them and click to add

Add printer

Click next and add it

Once done windows key + r

Type server ip or name

Right click and connect the server attached printer

Veeam Solution

Veeam replication and backup

Veeam Backup & Replication is a software solution that protects your data by performing backup, replication, and recovery operations. With this product, you can recover your data fast from all types of infrastructure: virtual, physical, and cloud.

Start the installation by mounting the Veeam Backup & Replication image downloaded from Veeam’s product download page. Use the application of your choice to mount the ISO image or burn the image to a removable device with sufficient storage.

Veeam Backup & Replication is a comprehensive data protection and disaster recovery solution that helps businesses protect their virtual, physical, and cloud workloads.

If you are looking for a comprehensive data protection and disaster recovery solution, Veeam replication and backup is a good option to consider.

Here will cover every single steps

Steps to Veeam replication and backup:

Click to Install

Select Community Edition and click to next

Installing Program Features

Veeam replication and backup Installation is Completed.

here,

First Adding Virtual bare metal Esxi Server.

Adding Esxi Server into Veeam Backup & Replication

SELCT your Vmware vSphre Virtualization 

Enter your Vsphre hosts details

Vpshre username and password

Generate Certificate

click to apply and add

Finish it and check the added Vsphre satatus

so, as you can check the screen attached Vsphre Server all vm is appearing

Hypervisor VSphres Server Attached

SO HERE I AM ADDING EXTRAL BACKUP REPOSOTORIES

Click to Veeam

Backup infrastructure

Backup Repositories

(Using this method to externalally taking backing to another server not to same server)

Now click to add

Selecting Network Storage

SMB Share

Give the name to Repository

SELECTING BACKUP Storage server

Backup Server Location

Backup Server Location

in below scree that’s the backup repository location

click to next

Mount Server

Click next

Review and check and click to next

so, Backup repositories created successfully 

Click yes and okay

newly created backup repository

now I wanted to take my VM BACKUP NOW Creating VM BACKUP

Assign VM Backup name

here, I will create backup from vsphre virtual machines

select vsphre vm

ADD MACHINE need vm username and password

Select backup repository

Incremental backup

Guest processing make as default and click to next

schedule backup synchronize time and apply

so finally finish VM Backup schedule

created vm backup

so check the vm backup status once backup done check the backup repository directory

as you can check here backup vbm and vbk file created

Here Taking Backup to Linux Apache Server Using Veeam Backup & Replication

So here I am having Apache server running on Cnetos 7 server in vpshre 6.7.

First, I will schedule the backup and also will restore the backup.

Having this running server

Running Server

Creating backup to crm application server

Click on Backup Infrastructure

Having backup repositories

Click to home and select backup job having virtual machine need to select that.

Assign the name

Virtual Machine Select EXSI Host and select VM for Backup and ADD that

Once done and click next

Select backup repositories and click to advanced for schedule backup time

Select Incremental backup days (it’s up to scenario)

And click too next

Here schedule time need to select click apply and finish

Or

backup location and click to finish

So, schedule backup job is created

Now it’s started on schedule time.

Once schedule backup done will delete the current running machine and will restore server

BACKUP IS COMPLETED

Backup stored on Backup repositories attached

Here,

CRM Server Deleting

Deleted Server

Restoring Entire VM

Click on Restore Select Vmware Vsphre

Select restore  from backup

Restoring entire vm

Entire vm

Click on from backup

Select the backup repositories and click to add

Click too next

Select the restore to original location

Click to next

Now checking files available in which location

Now click next

Verifying vm

And click to next

Now click to finish

Now need to wait and once done recheck the machine

Process still running

Restore done and close

Now, as you can check on exsi server same virtual machine restore

turn on restored server and checking the Server status

So, after restoration server running fine.

Physical Server Backup using Veeam Solution

Click on Inventory and select Physical infrastructure click on

Click on Protection Group

 Type the name and select to next

Here we can take Individual computer backup also but I need to take backup of Domain Controller

Select AD

Select DC and click to next

Click on add button

Click to Browse

And type the Domain Controller username and password

Once added click okay and next

Click to next

If will select all AD  User it will Select all computer attached to DC

So here I’m selecting Only Secondary DC

Here selected all DC Infrastructure

And click too next

Selected VM also if Hyper V if installed so it can take all Backup

Click next

Test Now

Selected Secondary DC Backup Days

Click okay and apply and click to finish

Now click to finish

Protection Group Created

Now Creating Back Schedule for Physical Server

Right click Select new backup job (Linux or Windows)

Click to new job and create

Or Individual Computer and Server

Veeam copy files

Veaam Files Level Backup

Adding Physical File Backup Server for backup.

Click on Inventory the select File Shares and click to Add File Share

Here adding file Sever select that

Add the file server Win or Linux

Server Identification

File Server Backup repositories is Added

Now here creating and Scheduling File server Backup

Apache Installation

What Is Apache?

Apache is a free and open-source software that allows users to deploy their websites on the internet. It is one of the oldest and most reliable web server software maintained by the Apache Software Foundation, with the first version released in 1995.

The job of a web server is to serve websites on the internet. To achieve that goal, it acts as a middleman between the server and client machines. It pulls content from the server on each user request and delivers it to the web.

Here are some of the reasons why Apache is so popular:

  • It is free and open-source software.
  • It is very reliable and stable.
  • It is very scalable and can handle a large amount of traffic.
  • It is very extensible and can be customized to meet the needs of different websites.

If you are looking for a reliable, scalable, and extensible web server, Apache is a great choice.

How to Install Apache Server

Steps:

Update Centos/RedHAT Linux Server

sudo yum update – y

Apache Installation

[root@qp ~]# sudo yum install httpd

Apache Services

Activate Apache

sudo systemctl start httpd

Start/ Restart/ stop

Enable

sudo systemctl enable httpd

Start Apache Services

Systemctl start httpd.services or systemctl start httpd

Verify Apache Service

Systemctl status httpd.services systemctl status httpd

Assign Ports to Apache Server

vi /etc/httpd/conf/httpd.conf

assign Public port and permanent

firewall-cmd –zone=public –permanent –add-service=http

firewall-cmd –zone=public –permanent –add-service=https

firewall-cmd –permanent –add-port=80/tcp

firewall-cmd –permanent –add-port=81/udp

firewall-cmd –permanent –add-port=81/tcp

firewall-cmd –permanent –add-port=80/udp

192.168.60.49/index.html

Public domain example

Configure firewalld to Allow Apache Traffic

Normal web traffic uses the http protocol on Port 80, while encrypted web traffic uses the https protocol, on Port 443.

Modify your firewall to allow connections on these ports

http

sudo firewall-cmd ––permanent ––add-port=80/tcp

sudo firewall-cmd ––permanent ––add-port=80/udp

https

sudo firewall-cmd ––permanent ––add-port=443/tcp

sudo firewall-cmd ––permanent ––add-port=443/tcp

Now reload the firewall

firewall-cmd –reload or sudo firewall-cmd ––reload

Tomcat Apache Installation

Tomcat Apache Installation on Centos 7

open-source Java servlet and Java Server Page container that lets developers implement an array of enterprise Java applications. Tomcat also runs an HTTP web server environment in which Java code can run.

[root@qp ~]# yum update  && upgrade -y

[root@qp ~]# yum install tomcat -y

now need to stop Apache Server

systemctl stop httpd or systemctl stop httpd.service

Next to edit

vi /usr/share/tomcat/conf/tomcat-users.xml

[root@qp ~]# vi /usr/share/tomcat/conf/tomcat.conf

At the last add these below commands java security

JAVA_OPTS=”-Djava.security.egd=file:/dev/./urandom -Djava.awt.headless=true -Xmx1026m -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC”

And save it

Now checking the all prerequisite and packages are install or not if just use * command to download like below

yum install tomcat*

[root@qp ~]# yum install tomcat*

Now add the admin user to controlling tomcat server

[root@qp ~]# vi /usr/share/tomcat/conf/tomcat-users.xml

Once edit and insert the below access scripts

Add the scripts below the line

You can use your password …

<tomcat-users>

<user username=”admin” password=”sharique” roles=”manager-gui,admin-gui”/>

Once done start the tomcat

[root@qp ~]# systemctl start tomcat

Enable tomcat – enabling because once if we restart there is no need to start the services manually

[root@qp ~]# systemctl enable tomcat

Now add the port – default port is 8080

[root@qp ~]# firewall-cmd –permanent –zone=public –add-port=8080/tcp

[root@qp ~]# firewall-cmd –permanent –zone=public –add-port=8080/udp

Reload firewall

[root@qp ~]# firewall-cmd –reload

[root@qp ~]# systemctl status tomcat

Web browser Tomcat status

Login to tomcat services

After login tomcat server status

Change Default port Tomcat

Default port Directory

/etc/tomcat/server.xml

[root@qp tomcat]# vi /etc/tomcat/server.xml

Replace with new port 8060

Once replaced

Now add the new port in firewall

[root@qp ~]# firewall-cmd –permanent –zone=public –add-port=8060/udp

[root@qp ~]# firewall-cmd –permanent –zone=public –add-port=8060/tcp

And reload firewall services

[root@qp ~]# firewall-cmd –reload

Restart the tomcat services

Systemctl restart tomcat.service

[root@qp ~]# sudo systemctl restart tomcat.service

Now tomcat is running on new port

Additional DC

Backup DC (Additional Domain CONTROLLER)

\\\

Backup Domain Controller or Secondary Domain Controller

///

Steps:

Assign Static IP address

Change name Server  

Install Wins Server with Same existing Version

Join to Domain Controller

Go to Server Manager

Click to Add feature and Install

Active Directory Domain Services

DHCP Server

And DNS  Server

Required

And don’t need to uncheck any default Installation

Once Installation Done Click to Permote DC

And Select Existing DC and type administrator account name and Password

Once installation done

Go to Active Directory Sites and services

Click to Default first site name expand

Right Click to NTDS Setting select All Taks then Check Replication Topology

Once done click to Replicate now

You will get successfully popup message

These things have to done in both Primary and Secondary DC

Once both Primary and secondary DC replicated if we create or implemented any things even any Primary or Secondary both will get the result

NOTE: Both Server Machine IP Have to Different not Same IP.

So,

In any-case Primary DC is Down need to assign active Secondary DC with Full Privileges

Need to Seize FSMO 5 Roles from Primary DC(FSMO having 5 roles)

FSMO Categories in two shapes –- Divided into two Categories

Forest Level

      —— Schema Master

      —— Domain Naming Master

And

Domain Level  

      —— Domain Level

      —— RID Master

      —— PDC emulator

So,

I need to seize the FSMO 5 roles form Primary DC and assign to Secondary DC

Open – PowerShell

Type commands

   First need to check the FSMO roles currently running

Netdom fsmo query

  • You will see 5 FSMO roles will be display

Now type

   Ntdsutil

And now

Question mark

? and press enter key

Select maintenance

Once maintenance then

Again, question mars

? and hit enter

So, now

Once roles are displaying type

Type like this cmds

Seize infracture master to all 5 FSMO roles

Install wins Server Change Name and assign Static IP Address

Primary DC IP is 192.168.20.4

Changing Default PC name press okay once done Server will be reboot

now this pc is connected to the particular domain environment.

So, after joining

open Server Manager and install Active Directory

So, now select Backup server

And click next

Select

Active Directory Domain Services

DHCP Server

DNS Server

And click next

And left or make as default click to next

Now click to install these selected features and check the restart the destination if required

once Installation done click to promote Domain Controller

So, need to configure it

Now click to promote this do domain controller

Or click to popup red flag bar promote from there also..

Select existing DC

And

Change the user perform credentials enter only Primary DC Administrator username and  Password

And click next

Now type restore mode password

why we need to Select DSRM?

BECAUSE if there is any issues generated to Domain Controller or Backup DC, DSRM always keeping one Server Images stored separately.

if this method required need to start Server as safe mode

Click next

after Directory Service Restore Mode set the password Click next

Select the primary domain

Click next

Here, database, log and sysvol directory structure

Complete Active directory Database store here.

NTDS.DIT DATABASE — NTDS is the Active Directory DATABASE – All user and computer Accounts and groups
you can say NTDS.DIT is the Backbone of any ADDS.

Ntds.dit is the main AD database file. NTDS stands for NT Directory Services. The DIT stands for Directory Information Tree.
The Ntds.dit file on a particular domain controller contains all naming contexts hosted by that domain controller, including the Configuration and Schema naming contexts.
A Global Catalog server stores the partial naming context replicas in the Ntds.dit right along with the full Domain naming context for its domain.
Command for checking NTDS details: ntdsutil

NTDS.DIT file represents the Active Directory Databases, which has the user, computer, and other AD objects including printer and faxes . It is located under C:windowssystem32NTDS.

LDAP (Lightweight Directory Access Protocol).
in the Simple Language you can say LDAP is a medium to communicate to ADDS
LDAP protocol is used for accessing directory services and provides a mechanism for applications and other systems to communicate and
interact with the directory servers. It is responsible for keeping track of what is on the network and applications can use LDAP to retrieve
any object and property of the Active Directory database and can even modify it. When we enumerate information from AD, LDAP is used in the backend.
Not only this, LDAP also allows us to modify objects, like modifying groups members, changing attributes of an object.
Many enumeration tools have used LDAP to query the information from AD- for example Powerview or Sharpound etc. Anyone who is working with active directory like administrators,
red team operators, or developers writing programs to interact with AD, then a thorough understanding of LDAP is very important to fully utilize Active Directory.

LDAP or Lightweight Directory Access Protocol is one of the oldest and most popular protocols used to retrieve information from directory services,
authenticate users, and build applications that don’t compare on security or speed. It’s one of the protocols to manage assets and data over a network
and provides secure access to them.

LDAP is one of the core protocols for developing internet applications. The protocol was designed to access and maintain directory services over the internet.

LDAP Ports
LDAP port is 389
LDAP Secure (LDAPS) port is 636

SYSVOL DIRECTORY DEFAULT: c:\windows\SYSVOL —

LOG FILE – NDTS

SYSVOL – SYSVOL Stored items suck as logon scripts and related files GPO.

SYSVOL DIRECTORY DEFAULT: c:\windows\SYSVOL —

Schema: Defines the attributes and types of objects that can be stored in the Directory.

Domain Naming: store computers and users daily operations like modification and creating directory and deleting directory or folder.
domain naming is basically monitoring daily activities.

Click next

click to install

Once installation done server will be logout

Once installation done

Two Domain Controller will appearing (Additional DC- BDC)

Now go to active Directory Sites and services

Need to apply replication in both server

First Applying in Primary Server — Central —192.168.20.4

So, here primary server replicates to secondary server.

REPLICATION: if we done the replication between servers, sometimes replicated servers will be implemented if any user or any changes appear between replicated servers.

Now..

Need to apply replication job to Secondary server

Successfully replicates

Ntds: is the main AD database file. NTDS stands for NT Directory Services. The DIT stands for Directory Information Tree.

NTDS: it’s Control complete process of DC/ADDS and Secondary DC and Replication method. an easy language you can say NT Directory Service is backbone of ADDS and any process and changes happen in DC Server having the responsibility to manages

Suppose, Creating new OU(Organizational Unit) to Secondary (Backup DC) Server

Have created new OU in Secondary DC

So, new OU Created to my Primary Server,

after replication between the Primary DC and Secondary DC: any OU ,users or any policies created in Primary or Secondary DC it will reflect in both Server

Created OU Structure and user to Backup DC – Secondary DC

So, it also replicating in Primary DC Server

If there are any problems on Primary server how to retain Secondary Backup Server

Flexible Single Master Operation (also known as FSMO or FSMO Roles).

Primary Server FSMO Roles

Netdom query fsmo

Secondary server will also getting same roles but secondary server not having complete authority like Primary DC

If Primary Server having issues need to seize the fsmo roles after that Backup DC will retain complete authority

So, here I used to power off Primary Server

Primary DC is not active (Server Down)

Now type in PowerShell

But still, I will get all 5 FSMO roles

In secondary server I am getting all 5 Roles

Type

In Backup DC

Ntdsutil

PS C:\Users\administrator.VRE> ntdsutil

Just type only roles  and press enter

Type connections

Now need to connect to in backup Domain Controller like—

Connect to server bdc.vre.local

Now quit from connection press type q and enter

Here we need to seize all fsmo roles from primary server

Primary server is not running but fsmo roles with primary server need to seize the roles and allocate to secondary server

netdom query fsmo

fsmo maintenance: Seize infrastructure master

And press

Yes

fsmo maintenance: Seize naming master

fsmo maintenance:  Seize PDC

Seize RID master

Seize schema master

Now type quit

And quite from fsmo maintenance

So, after seize all 5 roles from Primary DC and assign to Secondary dc

If you can check after seize all roles

Now Backup domain having all fsmo roles

netdom query fsmo

Go to Active Directory users and computers

Right click on domain and click on operation masters

Now, check there

PDC

Infrastructure

KEY Based Auth

Centos/RedHat Server password less authentication

Using Centos 7

First Login to your Server

Generate Authentication keys

Authentication key cmds

[root@rserver8 ~]# ssh-keygen

Once you had executed the command

So, authorized keys are generated go to ~/.ssh/ directory or cd .ssh/

2 keys had generated

Id_rsa and id_rsa.pub

Using cat cmd display  id_rsa.pub keys

[root@rserver8 .ssh]# cat id_rsa.pub

Copy this key

Create new authorized_keys file

So, using vi or vim cmd we can create

[root@rserver8 .ssh]# vi authorized_keys

Paste it here id_rsa.pub keys which you have copied using cat id_rsa.pub

Chmod 600 sets permissions so that, user / owner can read, can write and can’t execute. Group can’t read, can’t write and can’t execute. others can’t read, can’t write and can’t

So, I had created the authorized_keys now assign the permission to this particular user

So in my case root is the owner you can create user and assign the privileges

[root@rserver8 .ssh]# chmod 600 authorized_keys

So, now need to copy private key

Again, go to .ssh folder

[root@rserver8 ~]# cd .ssh/

[root@rserver8 .ssh]# cat id_rsa

Copy this and paste it to any text editor

And save it to .ppk format

PuTTY Private Key

Now to to ssh_config and disable password authentication login

And if you are using any user you can also disable root login

[root@rserver8 .ssh]# vi /etc/ssh/sshd_config

So, once authentication done restart the sshd services (Secure Shell or Secure Socket Shell).

[root@rserver8 .ssh]# sudo systemctl restart sshd

I am saving private key in notepad text editor .ppk format

So here we need to convert in putty format if we don’t do it, we will get the error.

Go to ssh tab and browse the .ppk save private here we will get error because we are not using putty format

If you can check getting the format error

Now open the putty generator

Once file .ppk is loaded save  it to same format with new or existing name

Click to save private key

And click yes

And save it

Now open the putty type username like sharique@192.168.60.10

Browse the authenticate key

Open the putty for remember login

So. successfully configured password less authentication Linux server.

  • chmod 777 foldername will give read, write, and execute permissions for everyone.
  • chmod 700 foldername will give read, write, and execute permissions for the user only.
  • chmod 327 foldername will give write and execute (3) permission for the user, w (2) for the group, and read, write, and execute for the users.
777anyone can do anything (read, write, or execute)
755you can do anything; others can only read and execute
711you can do anything; others can only execute
644you can read and write; others can only read
  Chmod 600 sets permissions so that, user / owner can read, can write and can’t execute. Group can’t read, can’t write and can’t execute. others can’t read, can’t write and can’t         

PV | VG | LV

How to Increase Logical Volume size in RedHAT/Centos

Steps to Create Logical Volume in Centos or RedHat Linux Server.

First

check the already associated disks

fdisk -l

Add the new Virtual Disk to Server

–Scan the new created disks- if you are having host1 or till host2 disk scan according to that.

i am having only host1 disk active need to scan host2 disk like

echo “- – -” > /sys/class/scsi_host/host2/scan

–now creating new partition

fdisk /dev/sdb

and follow the instruction

–now creating Physical Volume

pvcreate /dev/sdb1

— extending VG – Volume group (working on default centos – So, VG Group is centos)

vgextend centos /dev/sdb1

–now increasing the Logical volume

vgextend centos /dev/sdb1

— Increasing the Logical Volume size

lvresize -L +5G /dev/centos/home

Adding 5GB to Home Directory and 5GB to Root Directory

Extend Disk Size

Add the New Drive and scan it

Fdisk -l

[root@centos ~]# fdisk -l

[root@centos ~]# lsblk

Now scanning the new added drive

[root@centos ~]# echo “- – -” > /sys/class/scsi_host/host2/scan

New added drive sdb

lblsk

Now creating the partition

Fdisk /dev/sdb

Create a new partition type n

Create primary partition type p

In the single disk can create 4 partation so here creating only 1 partation

Type 1 single partition

And just press enter

And giving complete size

Just press enter

And type p for checking the created disk type

So, we want linux LVM type type

Type t and enter

And type p and check the type

Now press w and enter

To check newly created disk

Fdisk -l /dev/sdb

[root@centos ~]# fdisk -l /dev/sdb

So here I will increase the centos-home dir size

Will use xfs (because very fast processing speed)

Checking the current blocks size

[root@centos ~]# xfs_growfs -n /dev/centos/home

Now creating the PHYSICAL VOLUME

PVCREATE –

Pvcreate /dev/sdb1

[root@centos ~]# pvcreate /dev/sdb1

Check the volume group

[root@centos ~]# vgs

Extending logical volume size

Vgextend— volume group name / logical volume directory

[root@centos ~]# vgextend centos /dev/sdb1

After increased size

So, if you can check now having 10GB Volume Group free size

vgs

Df -h T

Increase the Home directory Size

Volume group : centos

Directory : home

Increasing disk size 5GB – Home Directory

[root@centos ~]# lvresize -L +5G /dev/centos/home

[root@centos ~]# xfs_growfs /dev/centos/home

[root@centos ~]# df -hT /home

[root@centos ~]# df -hT

Extending root size

Steps to Create Logical Volume in Centos or RedHat Linux Server.

First

check the already associated disks

fdisk -l

Add the new Virtual Disk to Server

–Scan the new created disks- if you are having host1 or till host2 disk scan according to that.

i am having only host1 disk active need to scan host2 disk like

echo “- – -” > /sys/class/scsi_host/host2/scan

–now creating new partition

fdisk /dev/sdb

and follow the instruction

–now creating Physical Volume

pvcreate /dev/sdb1

— extending VG – Volume group (working on default centos – So, VG Group is centos)

vgextend centos /dev/sdb1

–now increasing the Logical volume

vgextend centos /dev/sdb1

— Increasing the Logical Volume size

lvresize -L +5G /dev/centos/home

)

Increasing disk size 5GB – Root Directory

[root@centos ~]# lvresize -L +5G /dev/centos/root

[root@centos ~]# xfs_growfs /dev/centos/root

[root@centos ~]# df -hT /root/

Df -Ht

After extend root

Before extended root

How to Increase Logical Volume size in RedHAT/Centos

Here I am increasing the Root 30 GB size

Current Disk Structure

lsblk

[root@centos ~]# echo “- – -” > /sys/class/scsi_host/host0/scan

Lblsk

Fdisk -l

[root@centos ~]# fdisk /dev/sdc

Type n

Then p

Then 1

Then enter and enter

Then t

Then L

Then 8e

Then type p to check system type

8e

Then p

Then w exit

Now Checking the status newly created disk

[root@centos ~]# fdisk -l /dev/sdc

So, I have decided to add the disk size in root directory

Checking the blocks size

[root@centos ~]# xfs_growfs -n /dev/centos/root

Creating physical volume

Pvcreate /dev/sdc1

[root@centos ~]# pvcreate /dev/sdc1

Current volume group details

[root@centos ~]# vgs

Now increasing the volume size to volume group

[root@centos ~]# vgextend centos /dev/sdc1

After extended the volume size

So, here increasing the root directory disk size

[root@centos ~]# lvresize -L +25G /dev/centos/root

[root@centos ~]# lvresize -L +4G /dev/centos/root

Xfs_growfs /dev/centos/root

[root@centos ~]# df -hT /root/

[root@centos ~]# df -hT

Physical Volume current scenario structure

Pvs

[root@centos ~]# pvs

Volume Group current scenario structure

Vgs

Logical Volume current scenario structure

Lvs

Logical Volume Manager

Logical Volume Manager (LVM) is a Linux mechanism for dynamically managing disks and disk partitions.

How to Configure LUN or Datastore to exsi host

Check Disks

lsblk - list block devices

Check the Disk

[root@rserver8 ~]# lsblk

Need to Scan disk drive to add new storage in RedHAT/Centos Linux.

Echo “ – – – “ > /sys/class/scsi_host/host2/scan

  • (scan the channel)
  • (scan the scsi target)
  • (scan the LUN)

Here I have mention host 2 because I am having only 1 datastore activated currently so now I am adding 2nd datastore so, have selected host2 if I am having already two disk then need to target on host3

[root@rserver8 ~]# echo ” – – – ” > /sys/class/scsi_host/host2/scan

So, now after scanning disk checking the disk using lsblk

..

I am getting new disk sdb 2

Fdisk -l

[root@rserver8 ~]# fdisk -l

Now Creating the Partition for sdb drive

And press enter command

[root@rserver8 ~]# fdisk /dev/sdb

Once enter

Then press p

Then and press n

And select partition type

So here creating the default partition

And press p

Press 1 because I am creating the complete disk as default

And press 1 as default and enter and enter

Verify created Disk

Now converting to LVM Format currently this is only linux format now

So, press t

Now press L – capital L type for checking the ID (LVM ID)

Select Linux LVM

Now type 8e

Now press w for exit;

Physical Volume

PVS

[root@rserver8 ~]# pvs

Creating new Physical volume

Pvcreate /directorystrucure/and_volume_name

Df -h

Pvcreate /dev/sdb1 /dev/sdc1

[root@rserver8 ~]# pvcreate /dev/sdb1 /dev/sdc1

Creating Volume Group

Vgs

[root@rserver8 ~]# vgs

So, here I am having 59GB Volume group

Now creating new volume group

Vgcreate  volumegroup(name) /directorystructure

[root@rserver8 ~]# vgcreate vg01 /dev/sdb1

So, as you can check created volume group is appearing — vg01

Logical Volume

So,

Here creating Logical Volume

Lvcreate -L +VolumeSize -n LogicalVolumeName and created volume Group name

Like

Lvcreate -L +10G -N lv1 vg01

Logical volume created

[root@rserver8 ~]# lvcreate -L +10G -n lv1 vg01

[root@rserver8 ~]# lvcreate -L +5G -n lv2 vg01

[root@rserver8 ~]# lvs

Now formating Created Logical Volume

Mkfs.ext4 /dev/vg01/lv1

[root@rserver8 ~]# mkfs.ext4 /dev/vg01/lv1

Now need to create a directory or folder to mount the logical volume

Mkdir folder name

[root@rserver8 ~]# mkdir /lvm

Created directory

Now,need to mount the created directory

Mount /direcotry(dev)/volumegroup/logicalVolume /direcotry

Mount /dev/vg01/lv1 /lvm

[root@rserver8 ~]# mount /dev/vg01/lv1 /lvm

Df -h

Currently this is temporary mount

Using bulkid make permanent mount

Blkid

[root@rserver8 ~]# blkid

UUID=”c780f085-c01c-4f34-bfea-caf7533405bb”

So now mounting the permanent disks using uuid

Go to etc/fstab

[root@rserver8 ~]# vi /etc/fstab

Now updating the file

Mount -a

[root@rserver8 ~]# mount -a

Df -h

Pvdisplay

Volume gorup

[root@rserver8 ~]# vgdisplay

Lvdisplay

How to Increase Logical Volume size in RedHAT/Centos

Steps to Create Logical Volume in Centos or RedHat Linux Server.

First

check the already associated disks

fdisk -l

Add the new Virtual Disk to Server

–Scan the new created disks- if you are having host1 or till host2 disk scan according to that.

i am having only host1 disk active need to scan host2 disk like

echo “- – -” > /sys/class/scsi_host/host2/scan

–now creating new partition

fdisk /dev/sdb

and follow the instruction

–now creating Physical Volume

pvcreate /dev/sdb1

— extending VG – Volume group (working on default centos – So, VG Group is centos)

vgextend centos /dev/sdb1

–now increasing the Logical volume

vgextend centos /dev/sdb1

— Increasing the Logical Volume size

lvresize -L +5G /dev/centos/home

Adding 5GB to Home Directory and 5GB to Root Directory

Extend Disk Size

Add the New Drive and scan it

Fdisk -l

[root@centos ~]# fdisk -l

[root@centos ~]# lsblk

Now scanning the new added drive

[root@centos ~]# echo “- – -” > /sys/class/scsi_host/host2/scan

New added drive sdb

lblsk

Now creating the partition

Fdisk /dev/sdb

Create a new partition type n

Create primary partition type p

In the single disk can create 4 partation so here creating only 1 partation

Type 1 single partition

And just press enter

And giving complete size

Just press enter

And type p for checking the created disk type

So, we want linux LVM type type

Type t and enter

And type p and check the type

Now press w and enter

To check newly created disk

Fdisk -l /dev/sdb

[root@centos ~]# fdisk -l /dev/sdb

So here I will increase the centos-home dir size

Will use xfs (because very fast processing speed)

Checking the current blocks size

[root@centos ~]# xfs_growfs -n /dev/centos/home

Now creating the PHYSICAL VOLUME

PVCREATE –

Pvcreate /dev/sdb1

[root@centos ~]# pvcreate /dev/sdb1

Check the volume group

[root@centos ~]# vgs

Extending logical volume size

Vgextend— volume group name / logical volume directory

[root@centos ~]# vgextend centos /dev/sdb1

After increased size

vgs

So, if you can check now having 10GB Volume Group free size

Df -h T

Increase the Home directory Size

Volume group : centos

Directory : home

Increasing disk size 5GB – Home Directory

[root@centos ~]# lvresize -L +5G /dev/centos/home

[root@centos ~]# xfs_growfs /dev/centos/home

[root@centos ~]# df -hT /home

[root@centos ~]# df -hT

Extending root size

Steps to Create Logical Volume in Centos or RedHat Linux Server.

First

check the already associated disks

fdisk -l

Add the new Virtual Disk to Server

–Scan the new created disks- if you are having host1 or till host2 disk scan according to that.

i am having only host1 disk active need to scan host2 disk like

echo “- – -” > /sys/class/scsi_host/host2/scan

–now creating new partition

fdisk /dev/sdb

and follow the instruction

–now creating Physical Volume

pvcreate /dev/sdb1

— extending VG – Volume group (working on default centos – So, VG Group is centos)

vgextend centos /dev/sdb1

–now increasing the Logical volume

vgextend centos /dev/sdb1

— Increasing the Logical Volume size

lvresize -L +5G /dev/centos/home

)

Increasing disk size 5GB – Root Directory

[root@centos ~]# lvresize -L +5G /dev/centos/root

[root@centos ~]# xfs_growfs /dev/centos/root

[root@centos ~]# df -hT /root/

Df -Ht

After extend root

Before extended root

How to Increase Logical Volume size in RedHAT/Centos

Here I am increasing the Root 30 GB size

Current Disk Structure

lsblk

[root@centos ~]# echo “- – -” > /sys/class/scsi_host/host0/scan

Lblsk

Fdisk -l

[root@centos ~]# fdisk /dev/sdc

Type n

Then p

Then 1

Then enter and enter

Then t

Then L

Then 8e

Then type p to check system type

8e

Then p

Then w exit

Now Checking the status newly created disk

[root@centos ~]# fdisk -l /dev/sdc

So, I have decided to add the disk size in root directory

Checking the blocks size

[root@centos ~]# xfs_growfs -n /dev/centos/root

Creating physical volume

Pvcreate /dev/sdc1

[root@centos ~]# pvcreate /dev/sdc1

Current volume group details

[root@centos ~]# vgs

Now increasing the volume size to volume group

[root@centos ~]# vgextend centos /dev/sdc1

After extended the volume size

So, here increasing the root directory disk size

[root@centos ~]# lvresize -L +25G /dev/centos/root

[root@centos ~]# lvresize -L +4G /dev/centos/root

Xfs_growfs /dev/centos/root

[root@centos ~]# df -hT /root/

[root@centos ~]# df -hT

Physical Volume current scenario structure

Pvs

[root@centos ~]# pvs

Volume Group current scenario structure

Vgs

Logical Volume current scenario structure

Lvs

SSH KEY Based Authentication

Centos/RedHat Server password less authentication

First Login to your Server

Generate Authentication keys

Authentication key cmds

[root@rserver8 ~]# ssh-keygen

Once you had executed the command

So, authorized keys are generated go to ~/.ssh/ directory or cd .ssh/

2 keys had generated

Id_rsa and id_rsa.pub

Using cat cmd display  id_rsa.pub keys

[root@rserver8 .ssh]# cat id_rsa.pub

Copy this key

Create new authorized_keys file

So, using vi or vim cmd we can create

[root@rserver8 .ssh]# vi authorized_keys

Paste it here id_rsa.pub keys which you have copied using cat id_rsa.pub

Chmod 600 sets permissions so that, user / owner can read, can write and can’t execute. Group can’t read, can’t write and can’t execute. others can’t read, can’t write and can’t

So, I had created the authorized_keys now assign the permission to this particular user

So in my case root is the owner you can create user and assign the privileges

[root@rserver8 .ssh]# chmod 600 authorized_keys

So, now need to copy private key

Again, go to .ssh folder

[root@rserver8 ~]# cd .ssh/

[root@rserver8 .ssh]# cat id_rsa

Copy this and paste it to any text editor

And save it to .ppk format

PuTTY Private Key

Now to to ssh_config and disable password authentication login

And if you are using any user you can also disable root login

[root@rserver8 .ssh]# vi /etc/ssh/sshd_config

password authentication change it make it no.

So, once authentication done restart the sshd services (Secure Shell or Secure Socket Shell).

[root@rserver8 .ssh]# sudo systemctl restart sshd

I am saving private key in notepad text editor .ppk format

So here we need to convert in putty format if we don’t do it, we will get the error.

Go to ssh tab and browse the .ppk save private here we will get error because we are not using putty format

If you can check getting the format error

Now open the putty generator

Once file .ppk is loaded save  it to same format with new or existing name

Click to save private key

And click yes

And save it

Now open the putty type username like sharique@192.168.60.10

Browse the authenticate key

Open the putty for remember login

So, Now you have successfully configured password less authentication Linux server.

DHCP Restore/Migration

DHCP Backup / Migration / Restore

DHCP Migration windows server 2016 to windows server 2019

Before starting migration just take the backup first.

Open cmd as administrator

Type help and go to server

And export DHCP Server

Netsh>dhcp

Netsh dhcp>help

Netsh dhcp>server

Export c:\dhcp2016 all

successfully dhcp backup done.

Install DHCP in Windows server 2019 – New server for restore

go to wins server manager

Copy backup dhcp2016 to 2019 server

While restore or migration stop dhcp server

DC2

Import DHCP  to DC2

open powershell or command promt as as administrator

type netsh

then

DHCP

then help and type server

import c:\dhcp2016

so, now restoration done successfully

AD Backup & Restore

Wins Adds Backup & Restore

Full backup

Microsoft Windows Server offers the possibility to perform a ‘Full’ backup or a ‘System State’ backup. A Full backup makes a copy of the system drives of a physical or a virtual machine, including applications, operating systems, and even the System State. This backup can be used for bare metal recovery—this allows you to easily reinstall the operating system and use the backup to recover.

System State backup

System State backup on the other hand creates a backup file for critical system-related components. This backup file can be used to recover critical system components in case of a crash. Active Directory is backed up as part of the System State on a domain controller

The System State includes the following list plus some additional items depending on the roles that are installed:

  • Domain controller: Active Directory DC database files (NTDS.DIT), boot files & system protected files, COM+ class registration database, registry, system volume (SYSVOL)
  • Domain member: Boot files, COM+ class registration database, registry
  • A machine running cluster services: Additionally backs up cluster server metadata
  • A machine running certificate services: Additionally backs up certificate data

Configure the Volume Shadow Copy Service (VSS)

It is important to ensure that the AD database is backed up in a way that preserves database consistency. One way to preserve consistency is to back up the AD database when the server is in a powered-off state. However, backing up the Active Directory server in a powered-off state may not be a good idea if the server is operating in 24/7 mode.

For this reason, Microsoft recommends the use of Volume Shadow Copy Service (VSS) to back up a server running Active Directory. VSS is a technology included in Microsoft Windows that can create backup copies or snapshots of computer files or volumes, even when they are in use. VSS writers create a snapshot that freezes the System State until the backup is complete to prevent modifying active files used by Active Directory during a backup process. In this way, it is possible to back up a running server without affecting its performance.

VSS

Go to properties click on shadow and enable it

Click yes and okay

Go to setting and select no limit and press ok.

Install the Windows Server backup feature

Click to server manager and select the option once features option display select windows server backup

Once the server backup opens, click on Backup Once

 Select Backup Destination screen you can choose the actual partition where you want to store the backup. Once you are done, click Next to proceed to the next

Restore

Boot in DSRM

Start the restore process by booting your server in Directory Services Restore Mode (DSRM). To do this,

  • Reboot the server.
  • In the boot menu, press F8 for advanced options.
  • Scroll down and select the Directory Services Restore Mode.
  • Press Enter, and this will reboot the computer in a safe mode. It won’t start the directory services.

The other option is, run msconfig and select Safe Boot > Active directory repair in the boot tab. Finally, restart your server, and it will start in the DSRM mode.

Run your DC in Safe mode

Type win+r and msconfig

Click to boot option

Running server in safe mode and AD Repair mode

if cannot login in safe mode try with .\administrator whatever Server admin username

Log into the server with the local administrator account. The domain services will not be available so the local account will be the only account available.

Open Windows Server Backup.

Select Recover.

Select This Server for where the backup is stored.

Select the backup you want to restore then click next.

Select “System state” and click next.

Select Original Location You need to consider if an authoritative restore of Active Directory is needed. If you have other sites that contain healthy domain controllers then you may not need an authoritative restore. In this example, I have one site so I want to reset all replicated content.

When the restore is complete, reboot and log into the server as normal. You should get a command line showing that the restore was completed. Mine says it was completed with errors but everything seems to be working fine now

So, now have Uncheck safe mode

and restart server

so now I can check restoration done successfully  

Wins Migration

Windows Server Migration 2016 to windows server 2019.

Migration to Windows Server 2016 to  2019, including applications, profiles, shares and data.

Step-by-Step Guide: Active Directory Migration from Windows Server 2016 to Windows Server 2019

How to migrate Windows Server Essentials 2016 to Windows Server 2019 Standard, Datacenter or Essentials

Add Windows server 2019 to the existing domain as member

Log in to the Server 2019 as a member of local administrators group and join your server to domain. After restart, log in to the server as Enterprise Administrator.

Here I am Having 2016 DC Server.

FSMO COUNTROLS Authority

netdom query fsmo

Migration user domain authorization — no need to create another user– use administrator

so, here i have created a user migration with enough authority

D:

Cd support

Cd adprep

dir

Adprep.exe /forestprep

And type c

(c for continue)

adprep.exe /domainprep

Set up a new server using Windows Server 2019

The first step is to install Windows Server 2019 on a new physical device or virtual machine. If you are more technically experienced with Windows Server, you could choose to install Server Core and then perform the necessary steps using PowerShell or by remotely connecting to the new server using Server Manager or Windows Admin Center. Otherwise, install Windows Server with the Desktop Experience role enabled.

Install the Active Directory Domain Services role

Wait for the server to reboot and then sign in with a domain admin account. You can then install the Active Directory Domain Services (AD DS) server role using Server Manager and the Add Roles and Features wizard in the Manage menu. You can also use the following PowerShell command:

Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools
 

Promote the new server to a domain controller

When the AD DS server role has been installed, you’ll get a notification in Server Manager prompting you to promote the server to a domain controller. Clicking the yellow exclamation mark icon will launch the AD DS configuration wizard. You should choose to ‘Add a domain controller to an existing domain’ and follow through the on-screen instructions. And providing that you are signed in with a domain admin account, adprep will automatically prepare your existing domain.

So, after installation of 2019 server need to install Active directory click to join existing domain.

Login from authorize account

so, now available 2 DC

DC 2

DC 1

Uncheck

Now DC 1

Transfer FSMO Roles to DC2

Open Powershell

ntdsutil

And press

Enter

Roles

Connections

Connect to server dc2

quit

FSMO Roles

Upgrade Windows Server

Windows Upgradation (Windows server Migration 2016 to 2019)

How to Upgrade Windows Server 2016 to 2019 Step by Step

If you are still running Windows Server, you should upgrade to Windows Server 2019 since Windows Server 2016 will end the support.

Instructions

To upgrade Windows Server 2016 to Windows Server 2019, do the following:

Log in as an administrator on the server you want to upgrade.

Insert the Windows Server 2019 DVD or mount the installation ISO.

Browse to the root of the installation media and double-click setup.exe.
The Windows Server 2019 Setup window appears.

Follow the steps in the wizard according to the guidance in the Before You Begin section above. Note the following:

If you are upgrading from a DVD, you may be prompted to boot from DVD. You can let the request time out and the upgrade will continue.

When the upgrade is almost finished, a screen will indicate that settings are being finalized. When the upgrade is finished, you will be presented with the Windows Server 2019 login screen.

According to Microsoft, Windows Server 2016 will continue to update until Jan 12, 2027. And the end of life for Windows server 2019 is Jan 9, 2029. Windows Server 2022 has released in Sep 2021.

Even though Windows Server 2016 still acts as the main workhorse on many companies, we recommend upgrading to the latest version due to the new security function and better performance.

Before starting upgradation server first take complete server backup

So, here I am using AOMEI Software t take the complete backup

Default password:

Currently my DC is running on WINS 2016 SERVER

Adds

DOMAIN

GO TO Attached windows server 2019 Directory

2016 server having 87 schema level and 2019 having 89 so need to upgrade my schema before upgrading

Cd support

Cd adprep

dir

Adprep.exe /forestprep

And type c

(c for continue)

adprep.exe /domainprep

Don’t download and update while upgradation click on not right now.

Click and accept.

choose Keep personal files and apps – to keep data. 

Nothing -will cause all data to be deleted, including files, apps, and settings.

Next

Select the wanted Windows Server 2019 image and then choose Next

After the upgrade is completed, verify that the upgrade to Windows Server 2019 was successful by going the the System Properties.

Enable RDP ADDS Users

Enable RDP ADDS Users

How to Configuration RDP Active Directory users

So, here I am explaining steps

Configuring RDP Option in windows server ADDS

Go to Server Manager- Active Directory Users and Computers

Allow Remote Desktop Connection to Active Directory Users.

Create A New Group in ADDS Built-in

Go to Properties

Tab to Members and add the member

Built-in – Go to Remote Desktop Users.

Created new group in Built-in Active directory and users

Properties and go to member and add in the member list.

Add user in created group

I have added 2 users having RDP Access.

So, need to assign the created group to Remote Desktop users

Add the group

Click okay and go to GPO

Go to Group Policy Management.

Create a new group policy –

and edit that. once you will edit it will open in new windows.

Once open select computer configuration

Click to administrative templates expand and click to windows components

Remote Desktop Service – Remote Desktop Session Host

Connections

Edit and enable allow user

Click to administrative templates expand and click to windows components

Security

Enable requires user authentication

computer configuration – windows settings

security

Group Policy Management Editor,

Computer configuration

Windows setting – security setting – user right assignment

Add the group

local policy -user rights assignments

once you have update group policy it will replicate in local group policy also

So now need to enable RDP Default port:3389

Go to Group policy management editor

Windows settings – security settings

Windows defender firewall – click to inbound rules

Either we can use predefined rule or can use specific 3389 port

Now I m not using default predefined rule.

Click next

Click next

Click next and apply new rules  once done need to update to gpo rule

So it’s created RDP Allow port Firewall

Now just update group policy.

Can use gpupdate or gpupdate /force

Press win+r and type mstsc and press enter otherwise search remote desktop connection

So finally, RDP Connection perfectly working

Update Services-WSUS

Install and configure Windows Server Update Services (WSUS)

WSUS- Windows Server Update Services

Windows updates are released to fix bugs, fix security issues in OS and to add new features to operating system. The Windows Updates rely on Windows Update service which is set to start automatically by default.

install and configure WSUS (Windows Server Update Services) on Windows Server 2019.

Benefits of WSUS – Windows Update service downloads and installs recommended and important updates automatically.

Categories of updates:

  • Critical Updates
  • Security Updates
  • Drivers
  • Update Rollups
  • Service Packs
  • Tools
  • Feature Packs
  • Updates

Server Manager- Add Roles and Features

Select Role Based and features based installation

On the Server Selection page, verify the server name and click Next.

Server Roles – Windows Server Update Services

On the Server roles page, select the role Windows Server Update Services. You should see Add features that are required for Windows Server Update Services box. Click Add Features, and then click Next.

Next

Or Including with IIS Server

Add features

Also select HTTP Activation

Click and next

Next

Select WID Connectivity and WSUS Services. Click Next.

Create a patch folder

 The size of this folder can grow eventually and you don’t want this folder to reside on C: drive. Hence choose either a separate drive or store the updates on remote server.

OR Network folder

Next

On the Connect to Upstream Server page, click Start Connecting button.

synchronization task is completed click Next

Choose Languages screen, click Download updates only in these languages. Check English and any other additional language you wish to download updates

On the Choose products screen, check all products you wish to update. Scroll down to the Windows section and uncheck it. Then check only the Windows versions you have in your environment. 

Choose Clarifications screen offers option to determine Windows update classifications you wish to download.

Set Sync Schedule screen configure to sync manually or automatically and Next.

If you choose Synchronize manually, you must manually start the synchronization process from the WSUS Administration Console. With this option selected, you have to manually perform the sync every time. Therefore do not select this option if you are setting up the WSUS in production.

It is recommended to set the automatic sync between the primary WSUS and WSUS Replica as frequently as possible (24 syncs a day), because in scenarios where a remediation plan was activated on endpoints that communicate with WSUS Replica (Downstream WSUS) the “execute patch installation for single computer” task will only work after the Primary and Replica WSUS sync successfully. 

If the sync has yet to occur, you will see either an exit code 341 or 342 for the “execute patch installation for single computer” task.

In order to change the sync schedule to be as frequently as possible, do the following on the WSUS replica.

  1. Go to Options
  2. Open Synchronization Schedule
  3. Make sure Synchronize automatically is enabled and set to 24 synchronizations per day.

Next Begin WSUS Initial synchronization

Finally on the last page, click Finish. This completes the steps to configure WSUS

So now,

Need to configure GPO

If you wanted to connect to specific need to install IIS (Internet Information Services).

Configure Group Policy Settings for WSUS

After you install and configure WSUS, the next important task is to configure group policy settings for automatic updates.

Open the Group Policy Management console, and open an existing GPO or create a new one.

WSUS – Create as per you, Group Policy

Once created Group policy click to edit once edited – you will redirect to GPO EDIT Windows

Edit GPO

Configure WSUS Automatic Updates

Go to

Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update.

Double-click Configure Automatic Updates and set it to Enabled

Enable auto update

Intranet (Private Network).

You can design your private organization according to your need.

Locally connect to office devices environment, Like Computer, Server, Printer and etc. – office server which is only associated to only your office environment known as Intranet.

Mostly Intranet use for officially keep the data secure which is not connected to internet.

Specify Intranet Microsoft Update Service Location

The idea behind this is to ensure the client computers contact the specified intranet server instead of downloading updates from internet. Unless you configure this policy setting, the client computers

Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update.

Double-click Specify Intranet Microsoft update service location and set it to Enabled

Specify intranet Microsoft Update service location

(in your Domain Controller your attached PC – Address will be appear here)

So my wsus pc url is : wsus.vre.local

Default port for wsus: 8530

Specify intranet Microsoft Update service location

On the client computer, check the resultant set of policy to confirm if the WSUS GPO is applied

To enable the policy, click Enabled. Specify the intranet update service and intranet statistics server. Click Apply and OK

How to Start, Stop and Restart Windows Server Update WSUS Services via PowerShell and CMD
Start the WSUS service
Start-Service wsusservice
Stop the WSUS service
Stop-Service wsusservice
view the status of the WSUS service
Get-Service wsusservice

The below commands are Command line syntax used to start, stop and restart WSUS service.
net stop wsusservice
net start wsusservice

Wins Reverse DNS

How to configure a DNS Reverse Lookup Zone in Windows Server 2019

 

How To add DNS Reverse Lookup Zone in Windows Server 2019

Reverse lookup zones are used to resolve IP addresses to a hostname. For reverse lookup zones to work they use a PTR record that provides the mapping of the IP address in the zone to the hostname.

Configuring DNS Reverse Lookup zone

 Go to tools and open DNS 

DNS Manager, under your server, right-click on Reverse Lookup zones, and click on New Zone

Click on Reverse zone and create

next

How to Create PTR Records

Let’s walk through manually creating a PTR record. This is only needed if a system is not configured to dynamically update. This may be the case for systems with static IP addresses like servers

Back in the DNS console PTR record listed.

You can see in the picture above the IP returned the hostname

You can see in the picture above the IP returned the hostname

Exchange Server

Step by Step Guide for Installing Exchange Server 2019

Exchange 2019 prerequisites

Domain Controller Support

The following Active Directory writable Domain Controller(s) are supported;

  • Windows Server 2012 R2
  • Windows Server 2016 (Core and Desktop Experience)
  • Windows Server 2019 preview (Core and Desktop Experience)

Operating System Support

  • Windows Server 2016 (Core and Desktop Experience)
  • Windows Server 2019 preview (Core and Desktop Experience)

.Net Framework Support

Other requirements

Active Directory preparation

The first task in the installation of any version of Exchange is to prepare the Active Directory environment where the Exchange Server will be placed. However, prior to the preparation, it should be checked against the above Domain Controller support prerequisites mentioned earlier. Once the above requirements are verified for consistency, proceed with the following preparation tasks on the server/computer which will be used to prepare the Active Directory.

We will be using the Exchange Server itself to prepare the Active Directory.

Office 365 Exchange Server

Exchange Server 2019

Exchange server pc should be connected to Domain Controller with Domain Controller user with required permission.

Before starting installation exchange server, we need to aware about the pre requisites.

.NET Framework 4.7 or later

Unified Communications Managed API 4.0

Visual C++ 2013 or 2012

Required Permission right to Exchange Admin User:

Administrators

Domain Admins

Domain Users

Enterprise Admins

Schema Admins

pre requisites Software

Mount the disk

click to run setup file

launching exchange installation

If you looking for latest update select update option otherwise next option

click to next

So default user will be account user and password

In my scenario

Default user: shaexc (active directory user)

And password will be same as you login to server.

Create new user non exiting AD.

By default, it’s manual

Make it manual to automatic

IMAP

Here Configuring POP Services

START Exchange server PowerShell

Pop port

995/110

Type and enter cmd

Or restart from services

IMAP

PORT 993/143

Restart from here or from cmd

Once configuration done.

Allow ports to Router.

995, 110 – POP3

993, 143 – IMAP4

So, ports open.

SMTP Settings pop and imap clients.

Backup & Recovery

System state backup: Backs up operating system files, enabling you to recover when a machine starts but you’ve lost system files and registry. A system state backup includes: Domain member: Boot files, COM+ class registration database, registry

system state backup is, first of all, you need to know what a system state is. A system state contains some system settings and parameters files that are listed in the next part.

System state backup is a copy of system state data created by certain tools and stored in a safe location. Once the original system state files are damaged or missing, you can rely on the backup image to recover the previous working system.

Active Directory domain controllers (DCs) you have, you will certainly want to set up some sort of automated backup of your Active Directory. Although having two or more DCs provides redundancy and fail-over protection in the event one of them fails, you can’t really anticipate what can happen in the event of a natural disaster, a fire, or flooding of a data center

for Restore we need to Start Server in Repair Mode(Click – F8)

so, if we select bare metal recovery – we are taking complete server backup.

if we select System State taking backup only for Active directory.

Windows Server Backup.

Installation and Configuration windows server 2019 backup solution.

Click Tools

Here we are in Windows Server Backup

Daily Backup

Select window server backup

As you can see, it’s pretty bare-bones at the moment. Not a lot of action. Don’t worry, we’ll change that nice and quick. Click the ‘Local Backup‘ link on the left tree view.

here selecting the Backup schedule.

Backup schedule

only taking the C Drive Backup

Taking the backup in network folder.

So, now type the username and password central server username and password

System State taking backup only for Active directory

here i m tacking specific ADDS Backup

Click on Advanced Setting select vss setting and click to vss full backup if you’re not running any backup.

Backup scheduled

Backup once.

First, let’s do a single backup. Then, I’ll show you how to create an automated task/schedule. Click the ‘Backup Once…‘ link under the Actions menu on the right-hand side.

The ‘Backup Once Wizard‘ opens. As we haven’t created a scheduled backup yet, you can just click Next.

The ‘Full server (recommended)‘ option is selected by default – that’s what we want. Click Next.

On the ‘Specify Destination Type‘ screen, typically, you would choose the ‘Remote shared folder‘ option to use another disk.

OK, we are at the Confirmation screen. Click Backup.

We can monitor the job’s progress in the dialog box or in the main interface window.

/

Or

Custom Backup

Recovery

Cluster

In order to increase high-availability for your business-critical data using Windows Server, you need Failover Clustering in Windows Server to achieve it.

Failover clustering will enable you to make you Windows Server services highly available. In this guide we will go just through simple setup of failover clustering on Windows Server 2019 without setting up any services.

Introduction to Windows Server Failover Clustering | SpringerLink

Steps to Create HighAvailability Cluster Environment in Windows Server.

HighAvailability Server

Steps:

Windows Server.

Minimum Requirements:

Same windows server operating system.

Main Machine- example: win server 2019 DC- Domain Controller, – DC IP – 192.168.20.2

First Node 1 – win server 2019 (Active – Active) – Adaptor 1 – 192.168.20.51, Adaptor 2 – 192.168.21.51

Second Node 2 – Win Server 2019 (Active – Passive) Adaptor 2 – 192.168.20.52, Adaptor 2 – 192.168.21.52

if do you already working on DC Environment it’s okay otherwise need to install and Configure DC.

because Failover cluster will communicate with same network DC Environment.

– Suppose i am having DC Environment.

Need to install Node1 and Node 2. and join DC.

node pc name need to rename as per you. Nodes will join DC Environment

win+r = sysdm.cpl (shortcut key)

(win dc and nodes IP Will be Static)

once you will attached the NODE1 AND Multiple node pc to dc

you will login that pc from administrator account.

in Node 1,node 2 – nedeed to Network Adaptor.

IN DC

so now,

iscsi target and iscsi storage in DC.

install failover cluster.

IN DC

create storage drive using iscsi.

new isdcsi virtual disk as per need

minimum as per your requirment.

DataDisk

Log Drive

Quorumdisk

MSDT Disk

WHILE Creating Virtual Disk

Access Server- add-ENTER the node 1 and node 2 ip address.

IN All NODES

iscsi Initiator.(Default Installed)

run iscsi Initiator.

IP will be Server dc, so we created ISCSI File in DC.

find the created dc – attached machine node1 and node 2.

attached them with your node.

volume + autoconfigure.

so now available disk will be available in node 1 and node 2.

win+r – diskmgmt.msc

make the disk online and active disk.

So here,

I AM Already having DC Environment.

Now need to create NODES.

So, my Domain Controller is vre.local

And I already having nodes windows server.

Once join to the Domain Controller need to login from Same Admin User.

If you have already joined to DC your pc can login from DC Administrator.

So here,

And assign the static IP.

Implementing Failover Cluster in Windows Server 2019

So now,

GO to DC

Click add Features and roles.

Select server

Select

iSCSI Target and Storage Provider

And other make as default install it

Once install click on

File storage services

Click on Iscsi Virtual task and click on create

You can create on external drive also

So here I am creating as default.

Assign the name as per your need

I am giving here 5GB

Click on new iSCSITarget

Allocate name

Check your name attached with Cluster

Or search from ip address

Click to Next

Leave as default

So, click on create and create first iSCSI Disk

Iscsi Disk Created

We ned to create minimum  – Iscsi  Disks

Quorumdisk

DataDisk

Log Drive

So, again I m creating disks.

Assign size

Click next

Click on create disk

Created disk and close

Now,

Login to Node1 and Node 2 for Iscsi initiator

Click to quick connect

Click to Done so bellow screen connection established

Click on volume and device and click auto configuration

Right click on both disk which is not current activated make it online

Click on initialize disk

Select as default

Now assign name

Once done

So after this check DC Iscsi EMVIROMENT NOW YOU ARE CONNECTED.

Now install the Cluster in both nodes.

So, in feature select and install.

Once cluster install  need to install File Server also.

Click to start Failover Cluster. Node 1 and node 2

Click to validate and create cluster in node1 node 2.

Select both servers (in my case Failover1 and Failover2) and select Next

Next

Run all tests | Next

Next

All test were success | Finish

Confirm the next options, and we will reach the confirmation screen, where we can check the information to create the cluster before hitting Finish and really create our Cluster.

We can proceed to creating cluster

Create Failover Cluster

Once validation done in node 1 and node 2.

Now Create cluster in node 1 and node 2.

Next

Assign the Cluster IP

Next

Once the Cluster is created, we can move on to define what kind of role (resource) we’ll need to use.

Finish

So, cluster validate and created.

So, now adding Disks

Select the disks

Once disks attached the disks will be online

You can assign disk as per the need

Log Disk

Network Interface

Creating file server in cluster environment

File Server and next

As you can see I have selected file server for general use

Assign File server name and IP Address

Select Cluster Hardisks for cluster

Confirm configuration and disks

Configuring IP

Select SMB Share

Select disk volume

File Server Name

next

next

And click to create

Here, here create HighAvailablity File Server

MariaDB/PHP7.7/PHPMYADMIN

login as: root
root@192.168.60.49’s password:
Last login: Sat Apr 2 11:27:07 2022

[root@nvc ~]

#

[root@nvc ~]

#

[root@nvc ~]

# yum update -y
Loaded plugins: fastestmirror, langpacks
Determining fastest mirrors

  • base: rep-centos-il.upress.io
  • extras: rep-centos-il.upress.io
  • updates: pkg.adfinis.com
    base | 3.6 kB 00:00
    extras | 2.9 kB 00:00
    updates | 2.9 kB 00:00
    (1/4): base/7/x86_64/group_gz | 153 kB 00:01
    (2/4): extras/7/x86_64/primary_db | 246 kB 00:01
    (3/4): updates/7/x86_64/primary_db | 14 MB 00:02
    (4/4): base/7/x86_64/primary_db | 6.1 MB 00:00:04
    Resolving Dependencies
    –> Running transaction check
    —> Package NetworkManager.x86_64 1:1.18.8-1.el7 will be updated
    —> Package NetworkManager.x86_64 1:1.18.8-2.el7_9 will be an update
    —> Package NetworkManager-libnm.x86_64 1:1.18.8-1.el7 will be updated
    —> Package NetworkManager-libnm.x86_64 1:1.18.8-2.el7_9 will be an update
    —> Package NetworkManager-team.x86_64 1:1.18.8-1.el7 will be updated
    —> Package NetworkManager-team.x86_64 1:1.18.8-2.el7_9 will be an update
    —> Package NetworkManager-tui.x86_64 1:1.18.8-1.el7 will be updated
    —> Package NetworkManager-tui.x86_64 1:1.18.8-2.el7_9 will be an update
    —> Package bash.x86_64 0:4.2.46-34.el7 will be updated
    —> Package bash.x86_64 0:4.2.46-35.el7_9 will be an update
    —> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7 will be updated
    —> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.9 will be an update
    —> Package bind-libs.x86_64 32:9.11.4-26.P2.el7 will be updated
    —> Package bind-libs.x86_64 32:9.11.4-26.P2.el7_9.9 will be an update
    —> Package bind-libs-lite.x86_64 32:9.11.4-26.P2.el7 will be updated
    —> Package bind-libs-lite.x86_64 32:9.11.4-26.P2.el7_9.9 will be an update
    —> Package bind-license.noarch 32:9.11.4-26.P2.el7 will be updated
    —> Package bind-license.noarch 32:9.11.4-26.P2.el7_9.9 will be an update
    —> Package bind-utils.x86_64 32:9.11.4-26.P2.el7 will be updated
    —> Package bind-utils.x86_64 32:9.11.4-26.P2.el7_9.9 will be an update
    —> Package binutils.x86_64 0:2.27-44.base.el7 will be updated
    —> Package binutils.x86_64 0:2.27-44.base.el7_9.1 will be an update
    —> Package bpftool.x86_64 0:3.10.0-1160.el7 will be updated
    —> Package bpftool.x86_64 0:3.10.0-1160.59.1.el7 will be an update
    —> Package ca-certificates.noarch 0:2020.2.41-70.0.el7_8 will be updated
    —> Package ca-certificates.noarch 0:2021.2.50-72.el7_9 will be an update
    —> Package centos-release.x86_64 0:7-9.2009.0.el7.centos will be updated
    —> Package centos-release.x86_64 0:7-9.2009.1.el7.centos will be an update
    —> Package coreutils.x86_64 0:8.22-24.el7 will be updated
    —> Package coreutils.x86_64 0:8.22-24.el7_9.2 will be an update
    —> Package cronie.x86_64 0:1.4.11-23.el7 will be updated
    —> Package cronie.x86_64 0:1.4.11-24.el7_9 will be an update
    —> Package cronie-anacron.x86_64 0:1.4.11-23.el7 will be updated
    —> Package cronie-anacron.x86_64 0:1.4.11-24.el7_9 will be an update
    —> Package curl.x86_64 0:7.29.0-59.el7 will be updated
    —> Package curl.x86_64 0:7.29.0-59.el7_9.1 will be an update
    —> Package cyrus-sasl-lib.x86_64 0:2.1.26-23.el7 will be updated
    —> Package cyrus-sasl-lib.x86_64 0:2.1.26-24.el7_9 will be an update
    —> Package cyrus-sasl-plain.x86_64 0:2.1.26-23.el7 will be updated
    —> Package cyrus-sasl-plain.x86_64 0:2.1.26-24.el7_9 will be an update
    —> Package device-mapper.x86_64 7:1.02.170-6.el7 will be updated
    —> Package device-mapper.x86_64 7:1.02.170-6.el7_9.5 will be an update
    —> Package device-mapper-event.x86_64 7:1.02.170-6.el7 will be updated
    —> Package device-mapper-event.x86_64 7:1.02.170-6.el7_9.5 will be an update
    —> Package device-mapper-event-libs.x86_64 7:1.02.170-6.el7 will be updated
    —> Package device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
    —> Package device-mapper-libs.x86_64 7:1.02.170-6.el7 will be updated
    —> Package device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
    —> Package device-mapper-persistent-data.x86_64 0:0.8.5-3.el7 will be updated
    —> Package device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2 will be an update
    —> Package dhclient.x86_64 12:4.2.5-82.el7.centos will be updated
    —> Package dhclient.x86_64 12:4.2.5-83.el7.centos.1 will be an update
    —> Package dhcp-common.x86_64 12:4.2.5-82.el7.centos will be updated
    —> Package dhcp-common.x86_64 12:4.2.5-83.el7.centos.1 will be an update
    —> Package dhcp-libs.x86_64 12:4.2.5-82.el7.centos will be updated
    —> Package dhcp-libs.x86_64 12:4.2.5-83.el7.centos.1 will be an update
    —> Package dmidecode.x86_64 1:3.2-5.el7 will be updated
    —> Package dmidecode.x86_64 1:3.2-5.el7_9.1 will be an update
    —> Package expat.x86_64 0:2.1.0-12.el7 will be updated
    —> Package expat.x86_64 0:2.1.0-14.el7_9 will be an update
    —> Package firewalld.noarch 0:0.6.3-11.el7 will be updated
    —> Package firewalld.noarch 0:0.6.3-13.el7_9 will be an update
    —> Package firewalld-filesystem.noarch 0:0.6.3-11.el7 will be updated
    —> Package firewalld-filesystem.noarch 0:0.6.3-13.el7_9 will be an update
    —> Package freetype.x86_64 0:2.8-14.el7 will be updated
    —> Package freetype.x86_64 0:2.8-14.el7_9.1 will be an update
    —> Package glib2.x86_64 0:2.56.1-7.el7 will be updated
    —> Package glib2.x86_64 0:2.56.1-9.el7_9 will be an update
    —> Package glibc.x86_64 0:2.17-317.el7 will be updated
    —> Package glibc.x86_64 0:2.17-325.el7_9 will be an update
    —> Package glibc-common.x86_64 0:2.17-317.el7 will be updated
    —> Package glibc-common.x86_64 0:2.17-325.el7_9 will be an update
    —> Package grub2.x86_64 1:2.02-0.86.el7.centos will be updated
    —> Package grub2.x86_64 1:2.02-0.87.el7.centos.7 will be an update
    —> Package grub2-common.noarch 1:2.02-0.86.el7.centos will be updated
    —> Package grub2-common.noarch 1:2.02-0.87.el7.centos.7 will be an update
    —> Package grub2-pc.x86_64 1:2.02-0.86.el7.centos will be updated
    —> Package grub2-pc.x86_64 1:2.02-0.87.el7.centos.7 will be an update
    —> Package grub2-pc-modules.noarch 1:2.02-0.86.el7.centos will be updated
    —> Package grub2-pc-modules.noarch 1:2.02-0.87.el7.centos.7 will be an update
    —> Package grub2-tools.x86_64 1:2.02-0.86.el7.centos will be updated
    —> Package grub2-tools.x86_64 1:2.02-0.87.el7.centos.7 will be an update
    —> Package grub2-tools-extra.x86_64 1:2.02-0.86.el7.centos will be updated
    —> Package grub2-tools-extra.x86_64 1:2.02-0.87.el7.centos.7 will be an update
    —> Package grub2-tools-minimal.x86_64 1:2.02-0.86.el7.centos will be updated
    —> Package grub2-tools-minimal.x86_64 1:2.02-0.87.el7.centos.7 will be an update
    —> Package httpd.x86_64 0:2.4.6-95.el7.centos will be updated
    —> Package httpd.x86_64 0:2.4.6-97.el7.centos.5 will be an update
    —> Package httpd-manual.noarch 0:2.4.6-95.el7.centos will be updated
    —> Package httpd-manual.noarch 0:2.4.6-97.el7.centos.5 will be an update
    —> Package httpd-tools.x86_64 0:2.4.6-95.el7.centos will be updated
    —> Package httpd-tools.x86_64 0:2.4.6-97.el7.centos.5 will be an update
    —> Package initscripts.x86_64 0:9.49.53-1.el7 will be updated
    —> Package initscripts.x86_64 0:9.49.53-1.el7_9.1 will be an update
    —> Package iprutils.x86_64 0:2.4.17.1-3.el7 will be updated
    —> Package iprutils.x86_64 0:2.4.17.1-3.el7_7 will be an update
    —> Package iwl100-firmware.noarch 0:39.31.5.1-79.el7 will be updated
    —> Package iwl100-firmware.noarch 0:39.31.5.1-80.el7_9 will be an update
    —> Package iwl1000-firmware.noarch 1:39.31.5.1-79.el7 will be updated
    —> Package iwl1000-firmware.noarch 1:39.31.5.1-80.el7_9 will be an update
    —> Package iwl105-firmware.noarch 0:18.168.6.1-79.el7 will be updated
    —> Package iwl105-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
    —> Package iwl135-firmware.noarch 0:18.168.6.1-79.el7 will be updated
    —> Package iwl135-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
    —> Package iwl2000-firmware.noarch 0:18.168.6.1-79.el7 will be updated
    —> Package iwl2000-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
    —> Package iwl2030-firmware.noarch 0:18.168.6.1-79.el7 will be updated
    —> Package iwl2030-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
    —> Package iwl3160-firmware.noarch 0:25.30.13.0-79.el7 will be updated
    —> Package iwl3160-firmware.noarch 0:25.30.13.0-80.el7_9 will be an update
    —> Package iwl3945-firmware.noarch 0:15.32.2.9-79.el7 will be updated
    —> Package iwl3945-firmware.noarch 0:15.32.2.9-80.el7_9 will be an update
    —> Package iwl4965-firmware.noarch 0:228.61.2.24-79.el7 will be updated
    —> Package iwl4965-firmware.noarch 0:228.61.2.24-80.el7_9 will be an update
    —> Package iwl5000-firmware.noarch 0:8.83.5.1_1-79.el7 will be updated
    —> Package iwl5000-firmware.noarch 0:8.83.5.1_1-80.el7_9 will be an update
    —> Package iwl5150-firmware.noarch 0:8.24.2.2-79.el7 will be updated
    —> Package iwl5150-firmware.noarch 0:8.24.2.2-80.el7_9 will be an update
    —> Package iwl6000-firmware.noarch 0:9.221.4.1-79.el7 will be updated
    —> Package iwl6000-firmware.noarch 0:9.221.4.1-80.el7_9 will be an update
    —> Package iwl6000g2a-firmware.noarch 0:18.168.6.1-79.el7 will be updated
    —> Package iwl6000g2a-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
    —> Package iwl6000g2b-firmware.noarch 0:18.168.6.1-79.el7 will be updated
    —> Package iwl6000g2b-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
    —> Package iwl6050-firmware.noarch 0:41.28.5.1-79.el7 will be updated
    —> Package iwl6050-firmware.noarch 0:41.28.5.1-80.el7_9 will be an update
    —> Package iwl7260-firmware.noarch 0:25.30.13.0-79.el7 will be updated
    —> Package iwl7260-firmware.noarch 0:25.30.13.0-80.el7_9 will be an update
    —> Package kbd.x86_64 0:1.15.5-15.el7 will be updated
    —> Package kbd.x86_64 0:1.15.5-16.el7_9 will be an update
    —> Package kbd-legacy.noarch 0:1.15.5-15.el7 will be updated
    —> Package kbd-legacy.noarch 0:1.15.5-16.el7_9 will be an update
    —> Package kbd-misc.noarch 0:1.15.5-15.el7 will be updated
    —> Package kbd-misc.noarch 0:1.15.5-16.el7_9 will be an update
    —> Package kernel.x86_64 0:3.10.0-1160.59.1.el7 will be installed
    —> Package kernel-tools.x86_64 0:3.10.0-1160.el7 will be updated
    —> Package kernel-tools.x86_64 0:3.10.0-1160.59.1.el7 will be an update
    —> Package kernel-tools-libs.x86_64 0:3.10.0-1160.el7 will be updated
    —> Package kernel-tools-libs.x86_64 0:3.10.0-1160.59.1.el7 will be an update
    —> Package kexec-tools.x86_64 0:2.0.15-51.el7 will be updated
    —> Package kexec-tools.x86_64 0:2.0.15-51.el7_9.3 will be an update
    —> Package kpartx.x86_64 0:0.4.9-133.el7 will be updated
    —> Package kpartx.x86_64 0:0.4.9-135.el7_9 will be an update
    —> Package krb5-libs.x86_64 0:1.15.1-50.el7 will be updated
    —> Package krb5-libs.x86_64 0:1.15.1-51.el7_9 will be an update
    —> Package libblkid.x86_64 0:2.23.2-65.el7 will be updated
    —> Package libblkid.x86_64 0:2.23.2-65.el7_9.1 will be an update
    —> Package libcroco.x86_64 0:0.6.12-4.el7 will be updated
    —> Package libcroco.x86_64 0:0.6.12-6.el7_9 will be an update
    —> Package libcurl.x86_64 0:7.29.0-59.el7 will be updated
    —> Package libcurl.x86_64 0:7.29.0-59.el7_9.1 will be an update
    —> Package libmount.x86_64 0:2.23.2-65.el7 will be updated
    —> Package libmount.x86_64 0:2.23.2-65.el7_9.1 will be an update
    —> Package libsmartcols.x86_64 0:2.23.2-65.el7 will be updated
    —> Package libsmartcols.x86_64 0:2.23.2-65.el7_9.1 will be an update
    —> Package libsss_idmap.x86_64 0:1.16.5-10.el7 will be updated
    —> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.12 will be an update
    —> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7 will be updated
    —> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.12 will be an update
    —> Package libstoragemgmt.x86_64 0:1.8.1-1.el7 will be updated
    —> Package libstoragemgmt.x86_64 0:1.8.1-2.el7_9 will be an update
    —> Package libstoragemgmt-python.noarch 0:1.8.1-1.el7 will be updated
    —> Package libstoragemgmt-python.noarch 0:1.8.1-2.el7_9 will be an update
    —> Package libstoragemgmt-python-clibs.x86_64 0:1.8.1-1.el7 will be updated
    —> Package libstoragemgmt-python-clibs.x86_64 0:1.8.1-2.el7_9 will be an update
    —> Package libuuid.x86_64 0:2.23.2-65.el7 will be updated
    —> Package libuuid.x86_64 0:2.23.2-65.el7_9.1 will be an update
    —> Package libxml2.x86_64 0:2.9.1-6.el7.5 will be updated
    —> Package libxml2.x86_64 0:2.9.1-6.el7_9.6 will be an update
    —> Package libxml2-python.x86_64 0:2.9.1-6.el7.5 will be updated
    —> Package libxml2-python.x86_64 0:2.9.1-6.el7_9.6 will be an update
    —> Package linux-firmware.noarch 0:20200421-79.git78c0348.el7 will be updated
    —> Package linux-firmware.noarch 0:20200421-80.git78c0348.el7_9 will be an update
    —> Package lvm2.x86_64 7:2.02.187-6.el7 will be updated
    —> Package lvm2.x86_64 7:2.02.187-6.el7_9.5 will be an update
    —> Package lvm2-libs.x86_64 7:2.02.187-6.el7 will be updated
    —> Package lvm2-libs.x86_64 7:2.02.187-6.el7_9.5 will be an update
    —> Package mdadm.x86_64 0:4.1-6.el7 will be updated
    —> Package mdadm.x86_64 0:4.1-9.el7_9 will be an update
    —> Package microcode_ctl.x86_64 2:2.1-73.el7 will be updated
    —> Package microcode_ctl.x86_64 2:2.1-73.11.el7_9 will be an update
    —> Package mod_ssl.x86_64 1:2.4.6-95.el7.centos will be updated
    —> Package mod_ssl.x86_64 1:2.4.6-97.el7.centos.5 will be an update
    —> Package nspr.x86_64 0:4.21.0-1.el7 will be updated
    —> Package nspr.x86_64 0:4.32.0-1.el7_9 will be an update
    —> Package nss.x86_64 0:3.44.0-7.el7_7 will be updated
    —> Package nss.x86_64 0:3.67.0-4.el7_9 will be an update
    —> Package nss-softokn.x86_64 0:3.44.0-8.el7_7 will be updated
    —> Package nss-softokn.x86_64 0:3.67.0-3.el7_9 will be an update
    —> Package nss-softokn-freebl.x86_64 0:3.44.0-8.el7_7 will be updated
    —> Package nss-softokn-freebl.x86_64 0:3.67.0-3.el7_9 will be an update
    —> Package nss-sysinit.x86_64 0:3.44.0-7.el7_7 will be updated
    —> Package nss-sysinit.x86_64 0:3.67.0-4.el7_9 will be an update
    —> Package nss-tools.x86_64 0:3.44.0-7.el7_7 will be updated
    —> Package nss-tools.x86_64 0:3.67.0-4.el7_9 will be an update
    —> Package nss-util.x86_64 0:3.44.0-4.el7_7 will be updated
    —> Package nss-util.x86_64 0:3.67.0-1.el7_9 will be an update
    —> Package open-vm-tools.x86_64 0:11.0.5-3.el7 will be updated
    —> Package open-vm-tools.x86_64 0:11.0.5-3.el7_9.3 will be an update
    —> Package openldap.x86_64 0:2.4.44-22.el7 will be updated
    —> Package openldap.x86_64 0:2.4.44-25.el7_9 will be an update
    —> Package openssh.x86_64 0:7.4p1-21.el7 will be updated
    —> Package openssh.x86_64 0:7.4p1-22.el7_9 will be an update
    —> Package openssh-clients.x86_64 0:7.4p1-21.el7 will be updated
    —> Package openssh-clients.x86_64 0:7.4p1-22.el7_9 will be an update
    —> Package openssh-server.x86_64 0:7.4p1-21.el7 will be updated
    —> Package openssh-server.x86_64 0:7.4p1-22.el7_9 will be an update
    —> Package openssl.x86_64 1:1.0.2k-19.el7 will be updated
    —> Package openssl.x86_64 1:1.0.2k-25.el7_9 will be an update
    —> Package openssl-libs.x86_64 1:1.0.2k-19.el7 will be updated
    —> Package openssl-libs.x86_64 1:1.0.2k-25.el7_9 will be an update
    —> Package perl.x86_64 4:5.16.3-297.el7 will be updated
    —> Package perl.x86_64 4:5.16.3-299.el7_9 will be an update
    —> Package perl-Pod-Escapes.noarch 1:1.04-297.el7 will be updated
    —> Package perl-Pod-Escapes.noarch 1:1.04-299.el7_9 will be an update
    —> Package perl-libs.x86_64 4:5.16.3-297.el7 will be updated
    —> Package perl-libs.x86_64 4:5.16.3-299.el7_9 will be an update
    —> Package perl-macros.x86_64 4:5.16.3-297.el7 will be updated
    —> Package perl-macros.x86_64 4:5.16.3-299.el7_9 will be an update
    —> Package polkit.x86_64 0:0.112-26.el7 will be updated
    —> Package polkit.x86_64 0:0.112-26.el7_9.1 will be an update
    —> Package python.x86_64 0:2.7.5-89.el7 will be updated
    —> Package python.x86_64 0:2.7.5-90.el7 will be an update
    —> Package python-firewall.noarch 0:0.6.3-11.el7 will be updated
    —> Package python-firewall.noarch 0:0.6.3-13.el7_9 will be an update
    —> Package python-libs.x86_64 0:2.7.5-89.el7 will be updated
    —> Package python-libs.x86_64 0:2.7.5-90.el7 will be an update
    —> Package python-perf.x86_64 0:3.10.0-1160.el7 will be updated
    —> Package python-perf.x86_64 0:3.10.0-1160.59.1.el7 will be an update
    —> Package rpm.x86_64 0:4.11.3-45.el7 will be updated
    —> Package rpm.x86_64 0:4.11.3-48.el7_9 will be an update
    —> Package rpm-build-libs.x86_64 0:4.11.3-45.el7 will be updated
    —> Package rpm-build-libs.x86_64 0:4.11.3-48.el7_9 will be an update
    —> Package rpm-libs.x86_64 0:4.11.3-45.el7 will be updated
    —> Package rpm-libs.x86_64 0:4.11.3-48.el7_9 will be an update
    —> Package rpm-python.x86_64 0:4.11.3-45.el7 will be updated
    —> Package rpm-python.x86_64 0:4.11.3-48.el7_9 will be an update
    —> Package rsyslog.x86_64 0:8.24.0-55.el7 will be updated
    —> Package rsyslog.x86_64 0:8.24.0-57.el7_9.1 will be an update
    —> Package selinux-policy.noarch 0:3.13.1-268.el7 will be updated
    —> Package selinux-policy.noarch 0:3.13.1-268.el7_9.2 will be an update
    —> Package selinux-policy-targeted.noarch 0:3.13.1-268.el7 will be updated
    —> Package selinux-policy-targeted.noarch 0:3.13.1-268.el7_9.2 will be an update
    —> Package sos.noarch 0:3.9-2.el7.centos will be updated
    —> Package sos.noarch 0:3.9-5.el7.centos.10 will be an update
    —> Package sssd-client.x86_64 0:1.16.5-10.el7 will be updated
    —> Package sssd-client.x86_64 0:1.16.5-10.el7_9.12 will be an update
    —> Package sudo.x86_64 0:1.8.23-10.el7 will be updated
    —> Package sudo.x86_64 0:1.8.23-10.el7_9.2 will be an update
    —> Package systemd.x86_64 0:219-78.el7 will be updated
    —> Package systemd.x86_64 0:219-78.el7_9.5 will be an update
    —> Package systemd-libs.x86_64 0:219-78.el7 will be updated
    —> Package systemd-libs.x86_64 0:219-78.el7_9.5 will be an update
    —> Package systemd-python.x86_64 0:219-78.el7 will be updated
    —> Package systemd-python.x86_64 0:219-78.el7_9.5 will be an update
    —> Package systemd-sysv.x86_64 0:219-78.el7 will be updated
    —> Package systemd-sysv.x86_64 0:219-78.el7_9.5 will be an update
    —> Package tcsh.x86_64 0:6.18.01-17.el7 will be updated
    —> Package tcsh.x86_64 0:6.18.01-17.el7_9.1 will be an update
    —> Package tuned.noarch 0:2.11.0-9.el7 will be updated
    —> Package tuned.noarch 0:2.11.0-11.el7_9 will be an update
    —> Package tzdata.noarch 0:2020a-1.el7 will be updated
    —> Package tzdata.noarch 0:2022a-1.el7 will be an update
    —> Package unzip.x86_64 0:6.0-21.el7 will be updated
    —> Package unzip.x86_64 0:6.0-24.el7_9 will be an update
    —> Package util-linux.x86_64 0:2.23.2-65.el7 will be updated
    —> Package util-linux.x86_64 0:2.23.2-65.el7_9.1 will be an update
    —> Package vim-common.x86_64 2:7.4.629-7.el7 will be updated
    —> Package vim-common.x86_64 2:7.4.629-8.el7_9 will be an update
    —> Package vim-enhanced.x86_64 2:7.4.629-7.el7 will be updated
    —> Package vim-enhanced.x86_64 2:7.4.629-8.el7_9 will be an update
    —> Package vim-filesystem.x86_64 2:7.4.629-7.el7 will be updated
    —> Package vim-filesystem.x86_64 2:7.4.629-8.el7_9 will be an update
    —> Package vim-minimal.x86_64 2:7.4.629-7.el7 will be updated
    —> Package vim-minimal.x86_64 2:7.4.629-8.el7_9 will be an update
    —> Package virt-what.x86_64 0:1.18-4.el7 will be updated
    —> Package virt-what.x86_64 0:1.18-4.el7_9.1 will be an update
    —> Package wpa_supplicant.x86_64 1:2.6-12.el7 will be updated
    —> Package wpa_supplicant.x86_64 1:2.6-12.el7_9.2 will be an update
    —> Package zlib.x86_64 0:1.2.7-18.el7 will be updated
    —> Package zlib.x86_64 0:1.2.7-19.el7_9 will be an update
    updates/7/x86_64/filelists_db | 7.8 MB 00:00:01
    –> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================

Package Arch Version Repository Size

Installing:
kernel x86_64 3.10.0-1160.59.1.el7 updates 50 M
Updating:
NetworkManager x86_64 1:1.18.8-2.el7_9 updates 1.9 M
NetworkManager-libnm x86_64 1:1.18.8-2.el7_9 updates 1.7 M
NetworkManager-team x86_64 1:1.18.8-2.el7_9 updates 165 k
NetworkManager-tui x86_64 1:1.18.8-2.el7_9 updates 329 k
bash x86_64 4.2.46-35.el7_9 updates 1.0 M
bind-export-libs x86_64 32:9.11.4-26.P2.el7_9.9 updates 1.1 M
bind-libs x86_64 32:9.11.4-26.P2.el7_9.9 updates 157 k
bind-libs-lite x86_64 32:9.11.4-26.P2.el7_9.9 updates 1.1 M
bind-license noarch 32:9.11.4-26.P2.el7_9.9 updates 91 k
bind-utils x86_64 32:9.11.4-26.P2.el7_9.9 updates 261 k
binutils x86_64 2.27-44.base.el7_9.1 updates 5.9 M
bpftool x86_64 3.10.0-1160.59.1.el7 updates 8.5 M
ca-certificates noarch 2021.2.50-72.el7_9 updates 379 k
centos-release x86_64 7-9.2009.1.el7.centos updates 27 k
coreutils x86_64 8.22-24.el7_9.2 updates 3.3 M
cronie x86_64 1.4.11-24.el7_9 updates 92 k
cronie-anacron x86_64 1.4.11-24.el7_9 updates 36 k
curl x86_64 7.29.0-59.el7_9.1 updates 271 k
cyrus-sasl-lib x86_64 2.1.26-24.el7_9 updates 156 k
cyrus-sasl-plain x86_64 2.1.26-24.el7_9 updates 39 k
device-mapper x86_64 7:1.02.170-6.el7_9.5 updates 297 k
device-mapper-event x86_64 7:1.02.170-6.el7_9.5 updates 192 k
device-mapper-event-libs x86_64 7:1.02.170-6.el7_9.5 updates 192 k
device-mapper-libs x86_64 7:1.02.170-6.el7_9.5 updates 325 k
device-mapper-persistent-data x86_64 0.8.5-3.el7_9.2 updates 423 k
dhclient x86_64 12:4.2.5-83.el7.centos.1 updates 286 k
dhcp-common x86_64 12:4.2.5-83.el7.centos.1 updates 177 k
dhcp-libs x86_64 12:4.2.5-83.el7.centos.1 updates 133 k
dmidecode x86_64 1:3.2-5.el7_9.1 updates 82 k
expat x86_64 2.1.0-14.el7_9 updates 83 k
firewalld noarch 0.6.3-13.el7_9 updates 449 k
firewalld-filesystem noarch 0.6.3-13.el7_9 updates 51 k
freetype x86_64 2.8-14.el7_9.1 updates 380 k
glib2 x86_64 2.56.1-9.el7_9 updates 2.5 M
glibc x86_64 2.17-325.el7_9 updates 3.6 M
glibc-common x86_64 2.17-325.el7_9 updates 12 M
grub2 x86_64 1:2.02-0.87.el7.centos.7 updates 34 k
grub2-common noarch 1:2.02-0.87.el7.centos.7 updates 732 k
grub2-pc x86_64 1:2.02-0.87.el7.centos.7 updates 34 k
grub2-pc-modules noarch 1:2.02-0.87.el7.centos.7 updates 858 k
grub2-tools x86_64 1:2.02-0.87.el7.centos.7 updates 1.8 M
grub2-tools-extra x86_64 1:2.02-0.87.el7.centos.7 updates 1.0 M
grub2-tools-minimal x86_64 1:2.02-0.87.el7.centos.7 updates 177 k
httpd x86_64 2.4.6-97.el7.centos.5 updates 2.7 M
httpd-manual noarch 2.4.6-97.el7.centos.5 updates 1.3 M
httpd-tools x86_64 2.4.6-97.el7.centos.5 updates 94 k
initscripts x86_64 9.49.53-1.el7_9.1 updates 440 k
iprutils x86_64 2.4.17.1-3.el7_7 updates 243 k
iwl100-firmware noarch 39.31.5.1-80.el7_9 updates 155 k
iwl1000-firmware noarch 1:39.31.5.1-80.el7_9 updates 215 k
iwl105-firmware noarch 18.168.6.1-80.el7_9 updates 234 k
iwl135-firmware noarch 18.168.6.1-80.el7_9 updates 243 k
iwl2000-firmware noarch 18.168.6.1-80.el7_9 updates 237 k
iwl2030-firmware noarch 18.168.6.1-80.el7_9 updates 245 k
iwl3160-firmware noarch 25.30.13.0-80.el7_9 updates 1.5 M
iwl3945-firmware noarch 15.32.2.9-80.el7_9 updates 96 k
iwl4965-firmware noarch 228.61.2.24-80.el7_9 updates 109 k
iwl5000-firmware noarch 8.83.5.1_1-80.el7_9 updates 289 k
iwl5150-firmware noarch 8.24.2.2-80.el7_9 updates 152 k
iwl6000-firmware noarch 9.221.4.1-80.el7_9 updates 171 k
iwl6000g2a-firmware noarch 18.168.6.1-80.el7_9 updates 304 k
iwl6000g2b-firmware noarch 18.168.6.1-80.el7_9 updates 305 k
iwl6050-firmware noarch 41.28.5.1-80.el7_9 updates 241 k
iwl7260-firmware noarch 25.30.13.0-80.el7_9 updates 6.1 M
kbd x86_64 1.15.5-16.el7_9 updates 347 k
kbd-legacy noarch 1.15.5-16.el7_9 updates 466 k
kbd-misc noarch 1.15.5-16.el7_9 updates 1.4 M
kernel-tools x86_64 3.10.0-1160.59.1.el7 updates 8.2 M
kernel-tools-libs x86_64 3.10.0-1160.59.1.el7 updates 8.1 M
kexec-tools x86_64 2.0.15-51.el7_9.3 updates 351 k
kpartx x86_64 0.4.9-135.el7_9 updates 81 k
krb5-libs x86_64 1.15.1-51.el7_9 updates 809 k
libblkid x86_64 2.23.2-65.el7_9.1 updates 183 k
libcroco x86_64 0.6.12-6.el7_9 updates 105 k
libcurl x86_64 7.29.0-59.el7_9.1 updates 223 k
libmount x86_64 2.23.2-65.el7_9.1 updates 185 k
libsmartcols x86_64 2.23.2-65.el7_9.1 updates 143 k
libsss_idmap x86_64 1.16.5-10.el7_9.12 updates 162 k
libsss_nss_idmap x86_64 1.16.5-10.el7_9.12 updates 169 k
libstoragemgmt x86_64 1.8.1-2.el7_9 updates 243 k
libstoragemgmt-python noarch 1.8.1-2.el7_9 updates 167 k
libstoragemgmt-python-clibs x86_64 1.8.1-2.el7_9 updates 19 k
libuuid x86_64 2.23.2-65.el7_9.1 updates 84 k
libxml2 x86_64 2.9.1-6.el7_9.6 updates 668 k
libxml2-python x86_64 2.9.1-6.el7_9.6 updates 247 k
linux-firmware noarch 20200421-80.git78c0348.el7_9 updates 80 M
lvm2 x86_64 7:2.02.187-6.el7_9.5 updates 1.3 M
lvm2-libs x86_64 7:2.02.187-6.el7_9.5 updates 1.1 M
mdadm x86_64 4.1-9.el7_9 updates 439 k
microcode_ctl x86_64 2:2.1-73.11.el7_9 updates 4.2 M
mod_ssl x86_64 1:2.4.6-97.el7.centos.5 updates 115 k
nspr x86_64 4.32.0-1.el7_9 updates 127 k
nss x86_64 3.67.0-4.el7_9 updates 882 k
nss-softokn x86_64 3.67.0-3.el7_9 updates 358 k
nss-softokn-freebl x86_64 3.67.0-3.el7_9 updates 337 k
nss-sysinit x86_64 3.67.0-4.el7_9 updates 66 k
nss-tools x86_64 3.67.0-4.el7_9 updates 549 k
nss-util x86_64 3.67.0-1.el7_9 updates 79 k
open-vm-tools x86_64 11.0.5-3.el7_9.3 updates 676 k
openldap x86_64 2.4.44-25.el7_9 updates 356 k
openssh x86_64 7.4p1-22.el7_9 updates 510 k
openssh-clients x86_64 7.4p1-22.el7_9 updates 655 k
openssh-server x86_64 7.4p1-22.el7_9 updates 459 k
openssl x86_64 1:1.0.2k-25.el7_9 updates 494 k
openssl-libs x86_64 1:1.0.2k-25.el7_9 updates 1.2 M
perl x86_64 4:5.16.3-299.el7_9 updates 8.0 M
perl-Pod-Escapes noarch 1:1.04-299.el7_9 updates 52 k
perl-libs x86_64 4:5.16.3-299.el7_9 updates 690 k
perl-macros x86_64 4:5.16.3-299.el7_9 updates 44 k
polkit x86_64 0.112-26.el7_9.1 updates 170 k
python x86_64 2.7.5-90.el7 updates 96 k
python-firewall noarch 0.6.3-13.el7_9 updates 355 k
python-libs x86_64 2.7.5-90.el7 updates 5.6 M
python-perf x86_64 3.10.0-1160.59.1.el7 updates 8.2 M
rpm x86_64 4.11.3-48.el7_9 updates 1.2 M
rpm-build-libs x86_64 4.11.3-48.el7_9 updates 108 k
rpm-libs x86_64 4.11.3-48.el7_9 updates 279 k
rpm-python x86_64 4.11.3-48.el7_9 updates 84 k
rsyslog x86_64 8.24.0-57.el7_9.1 updates 622 k
selinux-policy noarch 3.13.1-268.el7_9.2 updates 498 k
selinux-policy-targeted noarch 3.13.1-268.el7_9.2 updates 7.0 M
sos noarch 3.9-5.el7.centos.10 updates 549 k
sssd-client x86_64 1.16.5-10.el7_9.12 updates 229 k
sudo x86_64 1.8.23-10.el7_9.2 updates 843 k
systemd x86_64 219-78.el7_9.5 updates 5.1 M
systemd-libs x86_64 219-78.el7_9.5 updates 419 k
systemd-python x86_64 219-78.el7_9.5 updates 146 k
systemd-sysv x86_64 219-78.el7_9.5 updates 97 k
tcsh x86_64 6.18.01-17.el7_9.1 updates 339 k
tuned noarch 2.11.0-11.el7_9 updates 269 k
tzdata noarch 2022a-1.el7 updates 501 k
unzip x86_64 6.0-24.el7_9 updates 172 k
util-linux x86_64 2.23.2-65.el7_9.1 updates 2.0 M
vim-common x86_64 2:7.4.629-8.el7_9 updates 5.9 M
vim-enhanced x86_64 2:7.4.629-8.el7_9 updates 1.1 M
vim-filesystem x86_64 2:7.4.629-8.el7_9 updates 11 k
vim-minimal x86_64 2:7.4.629-8.el7_9 updates 443 k
virt-what x86_64 1.18-4.el7_9.1 updates 30 k
wpa_supplicant x86_64 1:2.6-12.el7_9.2 updates 1.2 M
zlib x86_64 1.2.7-19.el7_9 updates 90 k

Transaction Summary

Install 1 Package
Upgrade 140 Packages

Total download size: 286 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
warning: /var/cache/yum/x86_64/7/updates/packages/NetworkManager-libnm-1.18.8-2.el7_9.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEYB 00:04:49 ETA
Public key for NetworkManager-libnm-1.18.8-2.el7_9.x86_64.rpm is not installed
(1/141): NetworkManager-libnm-1.18.8-2.el7_9.x86_64.rpm | 1.7 MB 00:00:01
(2/141): NetworkManager-team-1.18.8-2.el7_9.x86_64.rpm | 165 kB 00:00:00
(3/141): NetworkManager-1.18.8-2.el7_9.x86_64.rpm | 1.9 MB 00:00:01
(4/141): NetworkManager-tui-1.18.8-2.el7_9.x86_64.rpm | 329 kB 00:00:00
(5/141): bind-export-libs-9.11.4-26.P2.el7_9.9.x86_64.rpm | 1.1 MB 00:00:00
(6/141): bind-libs-9.11.4-26.P2.el7_9.9.x86_64.rpm | 157 kB 00:00:00
(7/141): bind-libs-lite-9.11.4-26.P2.el7_9.9.x86_64.rpm | 1.1 MB 00:00:00
(8/141): bind-license-9.11.4-26.P2.el7_9.9.noarch.rpm | 91 kB 00:00:00
(9/141): bash-4.2.46-35.el7_9.x86_64.rpm | 1.0 MB 00:00:01
(10/141): bind-utils-9.11.4-26.P2.el7_9.9.x86_64.rpm | 261 kB 00:00:00
(11/141): binutils-2.27-44.base.el7_9.1.x86_64.rpm | 5.9 MB 00:00:01
(12/141): ca-certificates-2021.2.50-72.el7_9.noarch.rpm | 379 kB 00:00:00
(13/141): centos-release-7-9.2009.1.el7.centos.x86_64.rpm | 27 kB 00:00:00
(14/141): coreutils-8.22-24.el7_9.2.x86_64.rpm | 3.3 MB 00:00:00
(15/141): cronie-1.4.11-24.el7_9.x86_64.rpm | 92 kB 00:00:00
(16/141): bpftool-3.10.0-1160.59.1.el7.x86_64.rpm | 8.5 MB 00:00:02
(17/141): cronie-anacron-1.4.11-24.el7_9.x86_64.rpm | 36 kB 00:00:00
(18/141): cyrus-sasl-lib-2.1.26-24.el7_9.x86_64.rpm | 156 kB 00:00:00
(19/141): curl-7.29.0-59.el7_9.1.x86_64.rpm | 271 kB 00:00:00
(20/141): cyrus-sasl-plain-2.1.26-24.el7_9.x86_64.rpm | 39 kB 00:00:00
(21/141): device-mapper-1.02.170-6.el7_9.5.x86_64.rpm | 297 kB 00:00:00
(22/141): device-mapper-event-1.02.170-6.el7_9.5.x86_64.rpm | 192 kB 00:00:00
(23/141): device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64.rpm | 192 kB 00:00:00
(24/141): device-mapper-libs-1.02.170-6.el7_9.5.x86_64.rpm | 325 kB 00:00:00
(25/141): device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64.rpm | 423 kB 00:00:00
(26/141): dhclient-4.2.5-83.el7.centos.1.x86_64.rpm | 286 kB 00:00:00
(27/141): dhcp-common-4.2.5-83.el7.centos.1.x86_64.rpm | 177 kB 00:00:00
(28/141): dhcp-libs-4.2.5-83.el7.centos.1.x86_64.rpm | 133 kB 00:00:00
(29/141): dmidecode-3.2-5.el7_9.1.x86_64.rpm | 82 kB 00:00:00
(30/141): expat-2.1.0-14.el7_9.x86_64.rpm | 83 kB 00:00:00
(31/141): firewalld-0.6.3-13.el7_9.noarch.rpm | 449 kB 00:00:00
(32/141): firewalld-filesystem-0.6.3-13.el7_9.noarch.rpm | 51 kB 00:00:00
(33/141): freetype-2.8-14.el7_9.1.x86_64.rpm | 380 kB 00:00:00
(34/141): glib2-2.56.1-9.el7_9.x86_64.rpm | 2.5 MB 00:00:00
(35/141): glibc-2.17-325.el7_9.x86_64.rpm | 3.6 MB 00:00:01
(36/141): grub2-2.02-0.87.el7.centos.7.x86_64.rpm | 34 kB 00:00:00
(37/141): grub2-common-2.02-0.87.el7.centos.7.noarch.rpm | 732 kB 00:00:00
(38/141): grub2-pc-2.02-0.87.el7.centos.7.x86_64.rpm | 34 kB 00:00:00
(39/141): grub2-pc-modules-2.02-0.87.el7.centos.7.noarch.rpm | 858 kB 00:00:00
(40/141): glibc-common-2.17-325.el7_9.x86_64.rpm | 12 MB 00:00:01
(41/141): grub2-tools-extra-2.02-0.87.el7.centos.7.x86_64.rpm | 1.0 MB 00:00:00
(42/141): grub2-tools-2.02-0.87.el7.centos.7.x86_64.rpm | 1.8 MB 00:00:00
(43/141): grub2-tools-minimal-2.02-0.87.el7.centos.7.x86_64.rpm | 177 kB 00:00:00
(44/141): httpd-manual-2.4.6-97.el7.centos.5.noarch.rpm | 1.3 MB 00:00:00
(45/141): httpd-tools-2.4.6-97.el7.centos.5.x86_64.rpm | 94 kB 00:00:00
(46/141): initscripts-9.49.53-1.el7_9.1.x86_64.rpm | 440 kB 00:00:00
(47/141): iprutils-2.4.17.1-3.el7_7.x86_64.rpm | 243 kB 00:00:00
(48/141): httpd-2.4.6-97.el7.centos.5.x86_64.rpm | 2.7 MB 00:00:01
(49/141): iwl100-firmware-39.31.5.1-80.el7_9.noarch.rpm | 155 kB 00:00:00
(50/141): iwl1000-firmware-39.31.5.1-80.el7_9.noarch.rpm | 215 kB 00:00:00
(51/141): iwl105-firmware-18.168.6.1-80.el7_9.noarch.rpm | 234 kB 00:00:00
(52/141): iwl135-firmware-18.168.6.1-80.el7_9.noarch.rpm | 243 kB 00:00:00
(53/141): iwl2000-firmware-18.168.6.1-80.el7_9.noarch.rpm | 237 kB 00:00:00
(54/141): iwl2030-firmware-18.168.6.1-80.el7_9.noarch.rpm | 245 kB 00:00:00
(55/141): iwl3945-firmware-15.32.2.9-80.el7_9.noarch.rpm | 96 kB 00:00:00
(56/141): iwl3160-firmware-25.30.13.0-80.el7_9.noarch.rpm | 1.5 MB 00:00:00
(57/141): iwl4965-firmware-228.61.2.24-80.el7_9.noarch.rpm | 109 kB 00:00:00
(58/141): iwl5000-firmware-8.83.5.1_1-80.el7_9.noarch.rpm | 289 kB 00:00:00
(59/141): iwl5150-firmware-8.24.2.2-80.el7_9.noarch.rpm | 152 kB 00:00:00
(60/141): iwl6000-firmware-9.221.4.1-80.el7_9.noarch.rpm | 171 kB 00:00:00
(61/141): iwl6000g2a-firmware-18.168.6.1-80.el7_9.noarch.rpm | 304 kB 00:00:00
(62/141): iwl6000g2b-firmware-18.168.6.1-80.el7_9.noarch.rpm | 305 kB 00:00:00
(63/141): iwl6050-firmware-41.28.5.1-80.el7_9.noarch.rpm | 241 kB 00:00:00
(64/141): kbd-1.15.5-16.el7_9.x86_64.rpm | 347 kB 00:00:00
(65/141): kbd-legacy-1.15.5-16.el7_9.noarch.rpm | 466 kB 00:00:00
(66/141): iwl7260-firmware-25.30.13.0-80.el7_9.noarch.rpm | 6.1 MB 00:00:01
(67/141): kbd-misc-1.15.5-16.el7_9.noarch.rpm | 1.4 MB 00:00:00
(68/141): kernel-tools-3.10.0-1160.59.1.el7.x86_64.rpm | 8.2 MB 00:00:04
(69/141): kernel-tools-libs-3.10.0-1160.59.1.el7.x86_64.rpm | 8.1 MB 00:00:11
(70/141): kexec-tools-2.0.15-51.el7_9.3.x86_64.rpm | 351 kB 00:00:00
(71/141): kpartx-0.4.9-135.el7_9.x86_64.rpm | 81 kB 00:00:00
(72/141): krb5-libs-1.15.1-51.el7_9.x86_64.rpm | 809 kB 00:00:00
(73/141): libblkid-2.23.2-65.el7_9.1.x86_64.rpm | 183 kB 00:00:00
(74/141): libcroco-0.6.12-6.el7_9.x86_64.rpm | 105 kB 00:00:00
(75/141): libcurl-7.29.0-59.el7_9.1.x86_64.rpm | 223 kB 00:00:00
(76/141): libmount-2.23.2-65.el7_9.1.x86_64.rpm | 185 kB 00:00:00
(77/141): libsmartcols-2.23.2-65.el7_9.1.x86_64.rpm | 143 kB 00:00:00
(78/141): libsss_idmap-1.16.5-10.el7_9.12.x86_64.rpm | 162 kB 00:00:00
(79/141): libsss_nss_idmap-1.16.5-10.el7_9.12.x86_64.rpm | 169 kB 00:00:00
(80/141): libstoragemgmt-1.8.1-2.el7_9.x86_64.rpm | 243 kB 00:00:00
(81/141): libstoragemgmt-python-1.8.1-2.el7_9.noarch.rpm | 167 kB 00:00:00
(82/141): libstoragemgmt-python-clibs-1.8.1-2.el7_9.x86_64.rpm | 19 kB 00:00:00
(83/141): libuuid-2.23.2-65.el7_9.1.x86_64.rpm | 84 kB 00:00:00
(84/141): libxml2-2.9.1-6.el7_9.6.x86_64.rpm | 668 kB 00:00:00
(85/141): libxml2-python-2.9.1-6.el7_9.6.x86_64.rpm | 247 kB 00:00:00
(86/141): kernel-3.10.0-1160.59.1.el7.x86_64.rpm | 50 MB 00:00:32
(87/141): lvm2-2.02.187-6.el7_9.5.x86_64.rpm | 1.3 MB 00:00:01
(88/141): mdadm-4.1-9.el7_9.x86_64.rpm | 439 kB 00:00:00
(89/141): lvm2-libs-2.02.187-6.el7_9.5.x86_64.rpm | 1.1 MB 00:00:01
(90/141): microcode_ctl-2.1-73.11.el7_9.x86_64.rpm | 4.2 MB 00:00:02
(91/141): mod_ssl-2.4.6-97.el7.centos.5.x86_64.rpm | 115 kB 00:00:00
(92/141): nss-3.67.0-4.el7_9.x86_64.rpm | 882 kB 00:00:00
(93/141): nss-softokn-3.67.0-3.el7_9.x86_64.rpm | 358 kB 00:00:00
(94/141): nspr-4.32.0-1.el7_9.x86_64.rpm | 127 kB 00:00:00
(95/141): nss-softokn-freebl-3.67.0-3.el7_9.x86_64.rpm | 337 kB 00:00:00
(96/141): nss-sysinit-3.67.0-4.el7_9.x86_64.rpm | 66 kB 00:00:00
(97/141): nss-tools-3.67.0-4.el7_9.x86_64.rpm | 549 kB 00:00:00
(98/141): nss-util-3.67.0-1.el7_9.x86_64.rpm | 79 kB 00:00:00
(99/141): open-vm-tools-11.0.5-3.el7_9.3.x86_64.rpm | 676 kB 00:00:00
(100/141): openldap-2.4.44-25.el7_9.x86_64.rpm | 356 kB 00:00:00
(101/141): openssh-7.4p1-22.el7_9.x86_64.rpm | 510 kB 00:00:00
(102/141): openssh-clients-7.4p1-22.el7_9.x86_64.rpm | 655 kB 00:00:00
(103/141): openssh-server-7.4p1-22.el7_9.x86_64.rpm | 459 kB 00:00:00
(104/141): openssl-1.0.2k-25.el7_9.x86_64.rpm | 494 kB 00:00:00
(105/141): openssl-libs-1.0.2k-25.el7_9.x86_64.rpm | 1.2 MB 00:00:00
(106/141): perl-Pod-Escapes-1.04-299.el7_9.noarch.rpm | 52 kB 00:00:00
(107/141): perl-5.16.3-299.el7_9.x86_64.rpm | 8.0 MB 00:00:03
(108/141): perl-libs-5.16.3-299.el7_9.x86_64.rpm | 690 kB 00:00:00
(109/141): perl-macros-5.16.3-299.el7_9.x86_64.rpm | 44 kB 00:00:00
(110/141): polkit-0.112-26.el7_9.1.x86_64.rpm | 170 kB 00:00:00
(111/141): linux-firmware-20200421-80.git78c0348.el7_9.noarch.rpm | 80 MB 00:00:23
(112/141): python-2.7.5-90.el7.x86_64.rpm | 96 kB 00:00:00
(113/141): python-firewall-0.6.3-13.el7_9.noarch.rpm | 355 kB 00:00:00
(114/141): python-perf-3.10.0-1160.59.1.el7.x86_64.rpm | 8.2 MB 00:00:01
(115/141): rpm-4.11.3-48.el7_9.x86_64.rpm | 1.2 MB 00:00:00
(116/141): rpm-build-libs-4.11.3-48.el7_9.x86_64.rpm | 108 kB 00:00:00
(117/141): rpm-libs-4.11.3-48.el7_9.x86_64.rpm | 279 kB 00:00:00
(118/141): python-libs-2.7.5-90.el7.x86_64.rpm | 5.6 MB 00:00:02
(119/141): rpm-python-4.11.3-48.el7_9.x86_64.rpm | 84 kB 00:00:00
(120/141): selinux-policy-3.13.1-268.el7_9.2.noarch.rpm | 498 kB 00:00:00
(121/141): rsyslog-8.24.0-57.el7_9.1.x86_64.rpm | 622 kB 00:00:00
(122/141): sos-3.9-5.el7.centos.10.noarch.rpm | 549 kB 00:00:00
(123/141): sssd-client-1.16.5-10.el7_9.12.x86_64.rpm | 229 kB 00:00:00
(124/141): selinux-policy-targeted-3.13.1-268.el7_9.2.noarch.rpm | 7.0 MB 00:00:00
(125/141): sudo-1.8.23-10.el7_9.2.x86_64.rpm | 843 kB 00:00:00
(126/141): systemd-libs-219-78.el7_9.5.x86_64.rpm | 419 kB 00:00:00
(127/141): systemd-python-219-78.el7_9.5.x86_64.rpm | 146 kB 00:00:00
(128/141): systemd-sysv-219-78.el7_9.5.x86_64.rpm | 97 kB 00:00:00
(129/141): systemd-219-78.el7_9.5.x86_64.rpm | 5.1 MB 00:00:00
(130/141): tcsh-6.18.01-17.el7_9.1.x86_64.rpm | 339 kB 00:00:00
(131/141): tuned-2.11.0-11.el7_9.noarch.rpm | 269 kB 00:00:00
(132/141): unzip-6.0-24.el7_9.x86_64.rpm | 172 kB 00:00:00
(133/141): tzdata-2022a-1.el7.noarch.rpm | 501 kB 00:00:00
(134/141): util-linux-2.23.2-65.el7_9.1.x86_64.rpm | 2.0 MB 00:00:00
(135/141): vim-enhanced-7.4.629-8.el7_9.x86_64.rpm | 1.1 MB 00:00:00
(136/141): vim-filesystem-7.4.629-8.el7_9.x86_64.rpm | 11 kB 00:00:00
(137/141): vim-minimal-7.4.629-8.el7_9.x86_64.rpm | 443 kB 00:00:00
(138/141): virt-what-1.18-4.el7_9.1.x86_64.rpm | 30 kB 00:00:00
(139/141): wpa_supplicant-2.6-12.el7_9.2.x86_64.rpm | 1.2 MB 00:00:00
(140/141): zlib-1.2.7-19.el7_9.x86_64.rpm | 90 kB 00:00:00

(141/141): vim-common-7.4.629-8.el7_9.x86_64.rpm | 5.9 MB 00:00:02

Total 4.5 MB/s | 286 MB 00:01:03
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Importing GPG key 0xF4A80EB5:
Userid : “CentOS-7 Key (CentOS 7 Official Signing Key) security@centos.org
Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
Package : centos-release-7-9.2009.0.el7.centos.x86_64 (@anaconda)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : 1:grub2-common-2.02-0.87.el7.centos.7.noarch 1/281
Updating : centos-release-7-9.2009.1.el7.centos.x86_64 2/281
Updating : 32:bind-license-9.11.4-26.P2.el7_9.9.noarch 3/281
Updating : 1:grub2-pc-modules-2.02-0.87.el7.centos.7.noarch 4/281
Updating : kbd-misc-1.15.5-16.el7_9.noarch 5/281
Updating : kbd-legacy-1.15.5-16.el7_9.noarch 6/281
Updating : 2:vim-filesystem-7.4.629-8.el7_9.x86_64 7/281
Updating : tzdata-2022a-1.el7.noarch 8/281
Updating : bash-4.2.46-35.el7_9.x86_64 9/281
Updating : nss-softokn-freebl-3.67.0-3.el7_9.x86_64 10/281
Updating : glibc-common-2.17-325.el7_9.x86_64 11/281
Updating : glibc-2.17-325.el7_9.x86_64 12/281
Updating : nspr-4.32.0-1.el7_9.x86_64 13/281
Updating : nss-util-3.67.0-1.el7_9.x86_64 14/281
Updating : zlib-1.2.7-19.el7_9.x86_64 15/281
Updating : systemd-libs-219-78.el7_9.5.x86_64 16/281
Updating : libxml2-2.9.1-6.el7_9.6.x86_64 17/281
Updating : libuuid-2.23.2-65.el7_9.1.x86_64 18/281
Updating : expat-2.1.0-14.el7_9.x86_64 19/281
Updating : 4:perl-macros-5.16.3-299.el7_9.x86_64 20/281
Updating : 4:perl-libs-5.16.3-299.el7_9.x86_64 21/281
Updating : 4:perl-5.16.3-299.el7_9.x86_64 22/281
Updating : nss-softokn-3.67.0-3.el7_9.x86_64 23/281
Updating : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64 24/281
Updating : freetype-2.8-14.el7_9.1.x86_64 25/281
Updating : libsss_nss_idmap-1.16.5-10.el7_9.12.x86_64 26/281
Updating : 1:dmidecode-3.2-5.el7_9.1.x86_64 27/281
Updating : kernel-tools-libs-3.10.0-1160.59.1.el7.x86_64 28/281
Updating : 2:vim-minimal-7.4.629-8.el7_9.x86_64 29/281
Updating : 2:vim-common-7.4.629-8.el7_9.x86_64 30/281
Updating : libsmartcols-2.23.2-65.el7_9.1.x86_64 31/281
Updating : libsss_idmap-1.16.5-10.el7_9.12.x86_64 32/281
Updating : linux-firmware-20200421-80.git78c0348.el7_9.noarch 33/281
Updating : ca-certificates-2021.2.50-72.el7_9.noarch 34/281
Updating : coreutils-8.22-24.el7_9.2.x86_64 35/281
Updating : 1:openssl-libs-1.0.2k-25.el7_9.x86_64 36/281
Updating : krb5-libs-1.15.1-51.el7_9.x86_64 37/281
Updating : python-libs-2.7.5-90.el7.x86_64 38/281
Updating : python-2.7.5-90.el7.x86_64 39/281
Updating : libblkid-2.23.2-65.el7_9.1.x86_64 40/281
Updating : libmount-2.23.2-65.el7_9.1.x86_64 41/281
Updating : glib2-2.56.1-9.el7_9.x86_64 42/281
Updating : util-linux-2.23.2-65.el7_9.1.x86_64 43/281
Updating : 32:bind-libs-lite-9.11.4-26.P2.el7_9.9.x86_64 44/281
Updating : cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 45/281
Updating : 32:bind-libs-9.11.4-26.P2.el7_9.9.x86_64 46/281
Updating : virt-what-1.18-4.el7_9.1.x86_64 47/281
Updating : libxml2-python-2.9.1-6.el7_9.6.x86_64 48/281
Updating : python-perf-3.10.0-1160.59.1.el7.x86_64 49/281
Updating : python-firewall-0.6.3-13.el7_9.noarch 50/281
Updating : 1:openssl-1.0.2k-25.el7_9.x86_64 51/281
Updating : 32:bind-export-libs-9.11.4-26.P2.el7_9.9.x86_64 52/281
Updating : httpd-tools-2.4.6-97.el7.centos.5.x86_64 53/281
Updating : selinux-policy-3.13.1-268.el7_9.2.noarch 54/281
Updating : nss-3.67.0-4.el7_9.x86_64 55/281
Updating : nss-sysinit-3.67.0-4.el7_9.x86_64 56/281
Updating : 1:NetworkManager-libnm-1.18.8-2.el7_9.x86_64 57/281
Updating : nss-tools-3.67.0-4.el7_9.x86_64 58/281
Updating : libcurl-7.29.0-59.el7_9.1.x86_64 59/281
Updating : curl-7.29.0-59.el7_9.1.x86_64 60/281
Updating : rpm-libs-4.11.3-48.el7_9.x86_64 61/281
Updating : rpm-4.11.3-48.el7_9.x86_64 62/281
Updating : openldap-2.4.44-25.el7_9.x86_64 63/281
Updating : systemd-219-78.el7_9.5.x86_64 64/281
Updating : initscripts-9.49.53-1.el7_9.1.x86_64 65/281
Updating : libstoragemgmt-python-clibs-1.8.1-2.el7_9.x86_64 66/281
Updating : libstoragemgmt-python-1.8.1-2.el7_9.noarch 67/281
Updating : libstoragemgmt-1.8.1-2.el7_9.x86_64 68/281
Updating : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 69/281
Updating : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 70/281
Updating : 1:grub2-tools-minimal-2.02-0.87.el7.centos.7.x86_64 71/281
Updating : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64 72/281
Updating : 1:grub2-tools-2.02-0.87.el7.centos.7.x86_64 73/281
Updating : httpd-2.4.6-97.el7.centos.5.x86_64 74/281
Updating : polkit-0.112-26.el7_9.1.x86_64 75/281
Updating : 12:dhcp-libs-4.2.5-83.el7.centos.1.x86_64 76/281
Updating : openssh-7.4p1-22.el7_9.x86_64 77/281
Updating : 12:dhcp-common-4.2.5-83.el7.centos.1.x86_64 78/281
Updating : 1:grub2-tools-extra-2.02-0.87.el7.centos.7.x86_64 79/281
Updating : 1:grub2-pc-2.02-0.87.el7.centos.7.x86_64 80/281
Updating : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64 81/281
Updating : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64 82/281
Updating : systemd-sysv-219-78.el7_9.5.x86_64 83/281
Updating : 1:wpa_supplicant-2.6-12.el7_9.2.x86_64 84/281
Updating : 1:NetworkManager-1.18.8-2.el7_9.x86_64 85/281
Updating : cronie-anacron-1.4.11-24.el7_9.x86_64 86/281
Updating : cronie-1.4.11-24.el7_9.x86_64 87/281
Updating : rpm-build-libs-4.11.3-48.el7_9.x86_64 88/281
Updating : firewalld-filesystem-0.6.3-13.el7_9.noarch 89/281
Updating : firewalld-0.6.3-13.el7_9.noarch 90/281
Updating : rpm-python-4.11.3-48.el7_9.x86_64 91/281
Updating : 1:NetworkManager-tui-1.18.8-2.el7_9.x86_64 92/281
Updating : 1:NetworkManager-team-1.18.8-2.el7_9.x86_64 93/281
Updating : 7:lvm2-2.02.187-6.el7_9.5.x86_64 94/281
Updating : 1:grub2-2.02-0.87.el7.centos.7.x86_64 95/281
Updating : 12:dhclient-4.2.5-83.el7.centos.1.x86_64 96/281
Updating : openssh-clients-7.4p1-22.el7_9.x86_64 97/281
Updating : openssh-server-7.4p1-22.el7_9.x86_64 98/281
Updating : tuned-2.11.0-11.el7_9.noarch 99/281
Updating : httpd-manual-2.4.6-97.el7.centos.5.noarch 100/281
Updating : 1:mod_ssl-2.4.6-97.el7.centos.5.x86_64 101/281
Updating : kpartx-0.4.9-135.el7_9.x86_64 102/281
Updating : kbd-1.15.5-16.el7_9.x86_64 103/281
Installing : kernel-3.10.0-1160.59.1.el7.x86_64 104/281
Updating : rsyslog-8.24.0-57.el7_9.1.x86_64 105/281
Updating : mdadm-4.1-9.el7_9.x86_64 106/281
Updating : open-vm-tools-11.0.5-3.el7_9.3.x86_64 107/281
Updating : 2:microcode_ctl-2.1-73.11.el7_9.x86_64 108/281
Updating : kexec-tools-2.0.15-51.el7_9.3.x86_64 109/281
Updating : systemd-python-219-78.el7_9.5.x86_64 110/281
Updating : sudo-1.8.23-10.el7_9.2.x86_64 111/281
Updating : selinux-policy-targeted-3.13.1-268.el7_9.2.noarch 112/281
Updating : sos-3.9-5.el7.centos.10.noarch 113/281
Updating : 32:bind-utils-9.11.4-26.P2.el7_9.9.x86_64 114/281
Updating : cyrus-sasl-plain-2.1.26-24.el7_9.x86_64 115/281
Updating : libcroco-0.6.12-6.el7_9.x86_64 116/281
Updating : sssd-client-1.16.5-10.el7_9.12.x86_64 117/281
Updating : binutils-2.27-44.base.el7_9.1.x86_64 118/281
Updating : tcsh-6.18.01-17.el7_9.1.x86_64 119/281
Updating : 2:vim-enhanced-7.4.629-8.el7_9.x86_64 120/281
Updating : kernel-tools-3.10.0-1160.59.1.el7.x86_64 121/281
Updating : 1:perl-Pod-Escapes-1.04-299.el7_9.noarch 122/281
Updating : iprutils-2.4.17.1-3.el7_7.x86_64 123/281
Updating : bpftool-3.10.0-1160.59.1.el7.x86_64 124/281
Updating : unzip-6.0-24.el7_9.x86_64 125/281
Updating : iwl2000-firmware-18.168.6.1-80.el7_9.noarch 126/281
Updating : iwl135-firmware-18.168.6.1-80.el7_9.noarch 127/281
Updating : iwl3945-firmware-15.32.2.9-80.el7_9.noarch 128/281
Updating : iwl7260-firmware-25.30.13.0-80.el7_9.noarch 129/281
Updating : iwl105-firmware-18.168.6.1-80.el7_9.noarch 130/281
Updating : iwl6000g2a-firmware-18.168.6.1-80.el7_9.noarch 131/281
Updating : iwl4965-firmware-228.61.2.24-80.el7_9.noarch 132/281
Updating : 1:iwl1000-firmware-39.31.5.1-80.el7_9.noarch 133/281
Updating : iwl6000g2b-firmware-18.168.6.1-80.el7_9.noarch 134/281
Updating : iwl5000-firmware-8.83.5.1_1-80.el7_9.noarch 135/281
Updating : iwl100-firmware-39.31.5.1-80.el7_9.noarch 136/281
Updating : iwl6050-firmware-41.28.5.1-80.el7_9.noarch 137/281
Updating : iwl2030-firmware-18.168.6.1-80.el7_9.noarch 138/281
Updating : iwl3160-firmware-25.30.13.0-80.el7_9.noarch 139/281
Updating : iwl6000-firmware-9.221.4.1-80.el7_9.noarch 140/281
Updating : iwl5150-firmware-8.24.2.2-80.el7_9.noarch 141/281
Cleanup : 12:dhclient-4.2.5-82.el7.centos.x86_64 142/281
Cleanup : 1:mod_ssl-2.4.6-95.el7.centos.x86_64 143/281
Cleanup : 2:microcode_ctl-2.1-73.el7.x86_64 144/281
Cleanup : tuned-2.11.0-9.el7.noarch 145/281
Cleanup : firewalld-0.6.3-11.el7.noarch 146/281
Cleanup : selinux-policy-targeted-3.13.1-268.el7.noarch 147/281
Cleanup : sos-3.9-2.el7.centos.noarch 148/281
Cleanup : selinux-policy-3.13.1-268.el7.noarch 149/281
Cleanup : 1:grub2-2.02-0.86.el7.centos.x86_64 150/281
Cleanup : 1:grub2-pc-2.02-0.86.el7.centos.x86_64 151/281
Cleanup : 1:grub2-pc-modules-2.02-0.86.el7.centos.noarch 152/281
Cleanup : python-firewall-0.6.3-11.el7.noarch 153/281
Cleanup : 12:dhcp-common-4.2.5-82.el7.centos.x86_64 154/281
Cleanup : 12:dhcp-libs-4.2.5-82.el7.centos.x86_64 155/281
Cleanup : 1:perl-Pod-Escapes-1.04-297.el7.noarch 156/281
Cleanup : httpd-manual-2.4.6-95.el7.centos.noarch 157/281
Cleanup : httpd-2.4.6-95.el7.centos.x86_64 158/281
Cleanup : httpd-tools-2.4.6-95.el7.centos.x86_64 159/281
Cleanup : linux-firmware-20200421-79.git78c0348.el7.noarch 160/281
Cleanup : firewalld-filesystem-0.6.3-11.el7.noarch 161/281
Cleanup : iwl2000-firmware-18.168.6.1-79.el7.noarch 162/281
Cleanup : iwl135-firmware-18.168.6.1-79.el7.noarch 163/281
Cleanup : iwl3945-firmware-15.32.2.9-79.el7.noarch 164/281
Cleanup : iwl7260-firmware-25.30.13.0-79.el7.noarch 165/281
Cleanup : iwl105-firmware-18.168.6.1-79.el7.noarch 166/281
Cleanup : iwl6000g2a-firmware-18.168.6.1-79.el7.noarch 167/281
Cleanup : iwl4965-firmware-228.61.2.24-79.el7.noarch 168/281
Cleanup : 1:iwl1000-firmware-39.31.5.1-79.el7.noarch 169/281
Cleanup : iwl6000g2b-firmware-18.168.6.1-79.el7.noarch 170/281
Cleanup : iwl5000-firmware-8.83.5.1_1-79.el7.noarch 171/281
Cleanup : iwl100-firmware-39.31.5.1-79.el7.noarch 172/281
Cleanup : iwl6050-firmware-41.28.5.1-79.el7.noarch 173/281
Cleanup : iwl2030-firmware-18.168.6.1-79.el7.noarch 174/281
Cleanup : iwl3160-firmware-25.30.13.0-79.el7.noarch 175/281
Cleanup : iwl6000-firmware-9.221.4.1-79.el7.noarch 176/281
Cleanup : iwl5150-firmware-8.24.2.2-79.el7.noarch 177/281
Cleanup : 32:bind-utils-9.11.4-26.P2.el7.x86_64 178/281
Cleanup : open-vm-tools-11.0.5-3.el7.x86_64 179/281
Cleanup : 1:NetworkManager-tui-1.18.8-1.el7.x86_64 180/281
Cleanup : 32:bind-libs-9.11.4-26.P2.el7.x86_64 181/281
Cleanup : openssh-server-7.4p1-21.el7.x86_64 182/281
Cleanup : 7:lvm2-2.02.187-6.el7.x86_64 183/281
Cleanup : libstoragemgmt-python-clibs-1.8.1-1.el7.x86_64 184/281
Cleanup : libstoragemgmt-python-1.8.1-1.el7.noarch 185/281
Cleanup : libstoragemgmt-1.8.1-1.el7.x86_64 186/281
Cleanup : rpm-python-4.11.3-45.el7.x86_64 187/281
Cleanup : 1:openssl-1.0.2k-19.el7.x86_64 188/281
Cleanup : openssh-clients-7.4p1-21.el7.x86_64 189/281
Cleanup : openssh-7.4p1-21.el7.x86_64 190/281
Cleanup : 7:lvm2-libs-2.02.187-6.el7.x86_64 191/281
Cleanup : 32:bind-libs-lite-9.11.4-26.P2.el7.x86_64 192/281
Cleanup : 7:device-mapper-event-1.02.170-6.el7.x86_64 193/281
Cleanup : 1:grub2-tools-extra-2.02-0.86.el7.centos.x86_64 194/281
Cleanup : libxml2-python-2.9.1-6.el7.5.x86_64 195/281
Cleanup : systemd-python-219-78.el7.x86_64 196/281
Cleanup : 1:grub2-tools-2.02-0.86.el7.centos.x86_64 197/281
Cleanup : rpm-build-libs-4.11.3-45.el7.x86_64 198/281
Cleanup : 2:vim-enhanced-7.4.629-7.el7.x86_64 199/281
Cleanup : kexec-tools-2.0.15-51.el7.x86_64 200/281
Cleanup : sssd-client-1.16.5-10.el7.x86_64 201/281
Cleanup : sudo-1.8.23-10.el7.x86_64 202/281
Cleanup : rsyslog-8.24.0-55.el7.x86_64 203/281
Cleanup : 1:grub2-tools-minimal-2.02-0.86.el7.centos.x86_64 204/281
Cleanup : cronie-anacron-1.4.11-23.el7.x86_64 205/281
Cleanup : cronie-1.4.11-23.el7.x86_64 206/281
Cleanup : kernel-tools-3.10.0-1160.el7.x86_64 207/281
Cleanup : binutils-2.27-44.base.el7.x86_64 208/281
Cleanup : kbd-1.15.5-15.el7.x86_64 209/281
Cleanup : initscripts-9.49.53-1.el7.x86_64 210/281
Cleanup : freetype-2.8-14.el7.x86_64 211/281
Cleanup : device-mapper-persistent-data-0.8.5-3.el7.x86_64 212/281
Cleanup : python-perf-3.10.0-1160.el7.x86_64 213/281
Cleanup : virt-what-1.18-4.el7.x86_64 214/281
Cleanup : 32:bind-export-libs-9.11.4-26.P2.el7.x86_64 215/281
Cleanup : libcroco-0.6.12-4.el7.x86_64 216/281
Cleanup : 1:NetworkManager-team-1.18.8-1.el7.x86_64 217/281
Cleanup : 1:NetworkManager-1.18.8-1.el7.x86_64 218/281
Cleanup : 1:NetworkManager-libnm-1.18.8-1.el7.x86_64 219/281
Cleanup : polkit-0.112-26.el7.x86_64 220/281
Cleanup : 1:wpa_supplicant-2.6-12.el7.x86_64 221/281
Cleanup : glib2-2.56.1-7.el7.x86_64 222/281
Cleanup : cyrus-sasl-plain-2.1.26-23.el7.x86_64 223/281
Cleanup : iprutils-2.4.17.1-3.el7.x86_64 224/281
Cleanup : mdadm-4.1-6.el7.x86_64 225/281
Cleanup : libxml2-2.9.1-6.el7.5.x86_64 226/281
Cleanup : 4:perl-libs-5.16.3-297.el7.x86_64 227/281
Cleanup : 4:perl-macros-5.16.3-297.el7.x86_64 228/281
Cleanup : 4:perl-5.16.3-297.el7.x86_64 229/281
Cleanup : 2:vim-common-7.4.629-7.el7.x86_64 230/281
Cleanup : 7:device-mapper-event-libs-1.02.170-6.el7.x86_64 231/281
Cleanup : kpartx-0.4.9-133.el7.x86_64 232/281
Cleanup : 7:device-mapper-1.02.170-6.el7.x86_64 233/281
Cleanup : 7:device-mapper-libs-1.02.170-6.el7.x86_64 234/281
Cleanup : util-linux-2.23.2-65.el7.x86_64 235/281
Cleanup : bpftool-3.10.0-1160.el7.x86_64 236/281
Cleanup : tcsh-6.18.01-17.el7.x86_64 237/281
Cleanup : systemd-sysv-219-78.el7.x86_64 238/281
Cleanup : systemd-219-78.el7.x86_64 239/281
Cleanup : curl-7.29.0-59.el7.x86_64 240/281
Cleanup : libcurl-7.29.0-59.el7.x86_64 241/281
Cleanup : openldap-2.4.44-22.el7.x86_64 242/281
Cleanup : rpm-libs-4.11.3-45.el7.x86_64 243/281
Cleanup : rpm-4.11.3-45.el7.x86_64 244/281
Cleanup : nss-tools-3.44.0-7.el7_7.x86_64 245/281
Cleanup : nss-sysinit-3.44.0-7.el7_7.x86_64 246/281
Cleanup : nss-3.44.0-7.el7_7.x86_64 247/281
Cleanup : nss-softokn-3.44.0-8.el7_7.x86_64 248/281
Cleanup : libmount-2.23.2-65.el7.x86_64 249/281
Cleanup : libblkid-2.23.2-65.el7.x86_64 250/281
Cleanup : python-2.7.5-89.el7.x86_64 251/281
Cleanup : python-libs-2.7.5-89.el7.x86_64 252/281
Cleanup : cyrus-sasl-lib-2.1.26-23.el7.x86_64 253/281
Cleanup : krb5-libs-1.15.1-50.el7.x86_64 254/281
Cleanup : coreutils-8.22-24.el7.x86_64 255/281
Cleanup : 1:openssl-libs-1.0.2k-19.el7.x86_64 256/281
Cleanup : unzip-6.0-21.el7.x86_64 257/281
Cleanup : ca-certificates-2020.2.41-70.0.el7_8.noarch 258/281
Cleanup : centos-release-7-9.2009.0.el7.centos.x86_64 259/281
Cleanup : 2:vim-filesystem-7.4.629-7.el7.x86_64 260/281
Cleanup : kbd-legacy-1.15.5-15.el7.noarch 261/281
Cleanup : kbd-misc-1.15.5-15.el7.noarch 262/281
Cleanup : 1:grub2-common-2.02-0.86.el7.centos.noarch 263/281
Cleanup : 32:bind-license-9.11.4-26.P2.el7.noarch 264/281
Cleanup : zlib-1.2.7-18.el7.x86_64 265/281
Cleanup : expat-2.1.0-12.el7.x86_64 266/281
Cleanup : libuuid-2.23.2-65.el7.x86_64 267/281
Cleanup : systemd-libs-219-78.el7.x86_64 268/281
Cleanup : libsmartcols-2.23.2-65.el7.x86_64 269/281
Cleanup : 1:dmidecode-3.2-5.el7.x86_64 270/281
Cleanup : kernel-tools-libs-3.10.0-1160.el7.x86_64 271/281
Cleanup : 2:vim-minimal-7.4.629-7.el7.x86_64 272/281
Cleanup : libsss_idmap-1.16.5-10.el7.x86_64 273/281
Cleanup : libsss_nss_idmap-1.16.5-10.el7.x86_64 274/281
Cleanup : glibc-common-2.17-317.el7.x86_64 275/281
Cleanup : bash-4.2.46-34.el7.x86_64 276/281
Cleanup : nspr-4.21.0-1.el7.x86_64 277/281
Cleanup : nss-util-3.44.0-4.el7_7.x86_64 278/281
Cleanup : nss-softokn-freebl-3.44.0-8.el7_7.x86_64 279/281
Cleanup : glibc-2.17-317.el7.x86_64 280/281
Cleanup : tzdata-2020a-1.el7.noarch 281/281
Verifying : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64 1/281
Verifying : libblkid-2.23.2-65.el7_9.1.x86_64 2/281
Verifying : linux-firmware-20200421-80.git78c0348.el7_9.noarch 3/281
Verifying : firewalld-filesystem-0.6.3-13.el7_9.noarch 4/281
Verifying : selinux-policy-3.13.1-268.el7_9.2.noarch 5/281
Verifying : iwl5150-firmware-8.24.2.2-80.el7_9.noarch 6/281
Verifying : krb5-libs-1.15.1-51.el7_9.x86_64 7/281
Verifying : 1:grub2-pc-2.02-0.87.el7.centos.7.x86_64 8/281
Verifying : 1:NetworkManager-tui-1.18.8-2.el7_9.x86_64 9/281
Verifying : rsyslog-8.24.0-57.el7_9.1.x86_64 10/281
Verifying : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64 11/281
Verifying : centos-release-7-9.2009.1.el7.centos.x86_64 12/281
Verifying : nss-tools-3.67.0-4.el7_9.x86_64 13/281
Verifying : firewalld-0.6.3-13.el7_9.noarch 14/281
Verifying : 7:lvm2-2.02.187-6.el7_9.5.x86_64 15/281
Verifying : 32:bind-libs-lite-9.11.4-26.P2.el7_9.9.x86_64 16/281
Verifying : 12:dhcp-common-4.2.5-83.el7.centos.1.x86_64 17/281
Verifying : iwl6000-firmware-9.221.4.1-80.el7_9.noarch 18/281
Verifying : iwl3160-firmware-25.30.13.0-80.el7_9.noarch 19/281
Verifying : libsss_nss_idmap-1.16.5-10.el7_9.12.x86_64 20/281
Verifying : nss-3.67.0-4.el7_9.x86_64 21/281
Verifying : systemd-sysv-219-78.el7_9.5.x86_64 22/281
Verifying : 1:openssl-1.0.2k-25.el7_9.x86_64 23/281
Verifying : libcurl-7.29.0-59.el7_9.1.x86_64 24/281
Verifying : kbd-1.15.5-16.el7_9.x86_64 25/281
Verifying : tzdata-2022a-1.el7.noarch 26/281
Verifying : python-2.7.5-90.el7.x86_64 27/281
Verifying : openldap-2.4.44-25.el7_9.x86_64 28/281
Verifying : python-libs-2.7.5-90.el7.x86_64 29/281
Verifying : mdadm-4.1-9.el7_9.x86_64 30/281
Verifying : libxml2-python-2.9.1-6.el7_9.6.x86_64 31/281
Verifying : 4:perl-5.16.3-299.el7_9.x86_64 32/281
Verifying : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 33/281
Verifying : iwl2030-firmware-18.168.6.1-80.el7_9.noarch 34/281
Verifying : freetype-2.8-14.el7_9.1.x86_64 35/281
Verifying : 1:grub2-common-2.02-0.87.el7.centos.7.noarch 36/281
Verifying : python-perf-3.10.0-1160.59.1.el7.x86_64 37/281
Verifying : libstoragemgmt-1.8.1-2.el7_9.x86_64 38/281
Verifying : libxml2-2.9.1-6.el7_9.6.x86_64 39/281
Verifying : 1:dmidecode-3.2-5.el7_9.1.x86_64 40/281
Verifying : open-vm-tools-11.0.5-3.el7_9.3.x86_64 41/281
Verifying : sudo-1.8.23-10.el7_9.2.x86_64 42/281
Verifying : binutils-2.27-44.base.el7_9.1.x86_64 43/281
Verifying : libmount-2.23.2-65.el7_9.1.x86_64 44/281
Verifying : sos-3.9-5.el7.centos.10.noarch 45/281
Verifying : tuned-2.11.0-11.el7_9.noarch 46/281
Verifying : nss-util-3.67.0-1.el7_9.x86_64 47/281
Verifying : kernel-3.10.0-1160.59.1.el7.x86_64 48/281
Verifying : selinux-policy-targeted-3.13.1-268.el7_9.2.noarch 49/281
Verifying : initscripts-9.49.53-1.el7_9.1.x86_64 50/281
Verifying : tcsh-6.18.01-17.el7_9.1.x86_64 51/281
Verifying : libstoragemgmt-python-clibs-1.8.1-2.el7_9.x86_64 52/281
Verifying : 1:grub2-tools-minimal-2.02-0.87.el7.centos.7.x86_64 53/281
Verifying : 2:vim-filesystem-7.4.629-8.el7_9.x86_64 54/281
Verifying : iwl6050-firmware-41.28.5.1-80.el7_9.noarch 55/281
Verifying : glibc-common-2.17-325.el7_9.x86_64 56/281
Verifying : expat-2.1.0-14.el7_9.x86_64 57/281
Verifying : 32:bind-utils-9.11.4-26.P2.el7_9.9.x86_64 58/281
Verifying : kernel-tools-libs-3.10.0-1160.59.1.el7.x86_64 59/281
Verifying : 12:dhcp-libs-4.2.5-83.el7.centos.1.x86_64 60/281
Verifying : bash-4.2.46-35.el7_9.x86_64 61/281
Verifying : 32:bind-libs-9.11.4-26.P2.el7_9.9.x86_64 62/281
Verifying : iprutils-2.4.17.1-3.el7_7.x86_64 63/281
Verifying : cyrus-sasl-plain-2.1.26-24.el7_9.x86_64 64/281
Verifying : curl-7.29.0-59.el7_9.1.x86_64 65/281
Verifying : 32:bind-export-libs-9.11.4-26.P2.el7_9.9.x86_64 66/281
Verifying : sssd-client-1.16.5-10.el7_9.12.x86_64 67/281
Verifying : iwl100-firmware-39.31.5.1-80.el7_9.noarch 68/281
Verifying : 2:vim-minimal-7.4.629-8.el7_9.x86_64 69/281
Verifying : cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 70/281
Verifying : zlib-1.2.7-19.el7_9.x86_64 71/281
Verifying : 2:vim-common-7.4.629-8.el7_9.x86_64 72/281
Verifying : openssh-clients-7.4p1-22.el7_9.x86_64 73/281
Verifying : unzip-6.0-24.el7_9.x86_64 74/281
Verifying : cronie-1.4.11-24.el7_9.x86_64 75/281
Verifying : cronie-anacron-1.4.11-24.el7_9.x86_64 76/281
Verifying : 1:NetworkManager-team-1.18.8-2.el7_9.x86_64 77/281
Verifying : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 78/281
Verifying : ca-certificates-2021.2.50-72.el7_9.noarch 79/281
Verifying : iwl5000-firmware-8.83.5.1_1-80.el7_9.noarch 80/281
Verifying : httpd-manual-2.4.6-97.el7.centos.5.noarch 81/281
Verifying : 1:perl-Pod-Escapes-1.04-299.el7_9.noarch 82/281
Verifying : 2:microcode_ctl-2.1-73.11.el7_9.x86_64 83/281
Verifying : kbd-legacy-1.15.5-16.el7_9.noarch 84/281
Verifying : httpd-tools-2.4.6-97.el7.centos.5.x86_64 85/281
Verifying : 1:mod_ssl-2.4.6-97.el7.centos.5.x86_64 86/281
Verifying : kexec-tools-2.0.15-51.el7_9.3.x86_64 87/281
Verifying : iwl6000g2b-firmware-18.168.6.1-80.el7_9.noarch 88/281
Verifying : libsmartcols-2.23.2-65.el7_9.1.x86_64 89/281
Verifying : coreutils-8.22-24.el7_9.2.x86_64 90/281
Verifying : rpm-libs-4.11.3-48.el7_9.x86_64 91/281
Verifying : httpd-2.4.6-97.el7.centos.5.x86_64 92/281
Verifying : 1:wpa_supplicant-2.6-12.el7_9.2.x86_64 93/281
Verifying : util-linux-2.23.2-65.el7_9.1.x86_64 94/281
Verifying : bpftool-3.10.0-1160.59.1.el7.x86_64 95/281
Verifying : 1:grub2-2.02-0.87.el7.centos.7.x86_64 96/281
Verifying : libuuid-2.23.2-65.el7_9.1.x86_64 97/281
Verifying : openssh-server-7.4p1-22.el7_9.x86_64 98/281
Verifying : 1:iwl1000-firmware-39.31.5.1-80.el7_9.noarch 99/281
Verifying : iwl4965-firmware-228.61.2.24-80.el7_9.noarch 100/281
Verifying : libsss_idmap-1.16.5-10.el7_9.12.x86_64 101/281
Verifying : kpartx-0.4.9-135.el7_9.x86_64 102/281
Verifying : 1:grub2-tools-extra-2.02-0.87.el7.centos.7.x86_64 103/281
Verifying : iwl6000g2a-firmware-18.168.6.1-80.el7_9.noarch 104/281
Verifying : virt-what-1.18-4.el7_9.1.x86_64 105/281
Verifying : iwl105-firmware-18.168.6.1-80.el7_9.noarch 106/281
Verifying : iwl7260-firmware-25.30.13.0-80.el7_9.noarch 107/281
Verifying : rpm-4.11.3-48.el7_9.x86_64 108/281
Verifying : 12:dhclient-4.2.5-83.el7.centos.1.x86_64 109/281
Verifying : 2:vim-enhanced-7.4.629-8.el7_9.x86_64 110/281
Verifying : libstoragemgmt-python-1.8.1-2.el7_9.noarch 111/281
Verifying : 1:grub2-tools-2.02-0.87.el7.centos.7.x86_64 112/281
Verifying : openssh-7.4p1-22.el7_9.x86_64 113/281
Verifying : 4:perl-macros-5.16.3-299.el7_9.x86_64 114/281
Verifying : glib2-2.56.1-9.el7_9.x86_64 115/281
Verifying : nspr-4.32.0-1.el7_9.x86_64 116/281
Verifying : systemd-python-219-78.el7_9.5.x86_64 117/281
Verifying : kbd-misc-1.15.5-16.el7_9.noarch 118/281
Verifying : kernel-tools-3.10.0-1160.59.1.el7.x86_64 119/281
Verifying : systemd-libs-219-78.el7_9.5.x86_64 120/281
Verifying : iwl3945-firmware-15.32.2.9-80.el7_9.noarch 121/281
Verifying : 1:NetworkManager-1.18.8-2.el7_9.x86_64 122/281
Verifying : iwl135-firmware-18.168.6.1-80.el7_9.noarch 123/281
Verifying : 1:openssl-libs-1.0.2k-25.el7_9.x86_64 124/281
Verifying : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64 125/281
Verifying : nss-softokn-3.67.0-3.el7_9.x86_64 126/281
Verifying : 1:NetworkManager-libnm-1.18.8-2.el7_9.x86_64 127/281
Verifying : python-firewall-0.6.3-13.el7_9.noarch 128/281
Verifying : 32:bind-license-9.11.4-26.P2.el7_9.9.noarch 129/281
Verifying : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64 130/281
Verifying : 4:perl-libs-5.16.3-299.el7_9.x86_64 131/281
Verifying : nss-softokn-freebl-3.67.0-3.el7_9.x86_64 132/281
Verifying : glibc-2.17-325.el7_9.x86_64 133/281
Verifying : libcroco-0.6.12-6.el7_9.x86_64 134/281
Verifying : rpm-python-4.11.3-48.el7_9.x86_64 135/281
Verifying : nss-sysinit-3.67.0-4.el7_9.x86_64 136/281
Verifying : iwl2000-firmware-18.168.6.1-80.el7_9.noarch 137/281
Verifying : 1:grub2-pc-modules-2.02-0.87.el7.centos.7.noarch 138/281
Verifying : polkit-0.112-26.el7_9.1.x86_64 139/281
Verifying : systemd-219-78.el7_9.5.x86_64 140/281
Verifying : rpm-build-libs-4.11.3-48.el7_9.x86_64 141/281
Verifying : rpm-4.11.3-45.el7.x86_64 142/281
Verifying : firewalld-filesystem-0.6.3-11.el7.noarch 143/281
Verifying : glibc-common-2.17-317.el7.x86_64 144/281
Verifying : selinux-policy-targeted-3.13.1-268.el7.noarch 145/281
Verifying : ca-certificates-2020.2.41-70.0.el7_8.noarch 146/281
Verifying : linux-firmware-20200421-79.git78c0348.el7.noarch 147/281
Verifying : 7:device-mapper-event-1.02.170-6.el7.x86_64 148/281
Verifying : 2:microcode_ctl-2.1-73.el7.x86_64 149/281
Verifying : iwl2000-firmware-18.168.6.1-79.el7.noarch 150/281
Verifying : sssd-client-1.16.5-10.el7.x86_64 151/281
Verifying : glib2-2.56.1-7.el7.x86_64 152/281
Verifying : 32:bind-libs-lite-9.11.4-26.P2.el7.x86_64 153/281
Verifying : 1:iwl1000-firmware-39.31.5.1-79.el7.noarch 154/281
Verifying : virt-what-1.18-4.el7.x86_64 155/281
Verifying : zlib-1.2.7-18.el7.x86_64 156/281
Verifying : iwl5150-firmware-8.24.2.2-79.el7.noarch 157/281
Verifying : iwl6000g2a-firmware-18.168.6.1-79.el7.noarch 158/281
Verifying : systemd-219-78.el7.x86_64 159/281
Verifying : 7:device-mapper-1.02.170-6.el7.x86_64 160/281
Verifying : iwl100-firmware-39.31.5.1-79.el7.noarch 161/281
Verifying : unzip-6.0-21.el7.x86_64 162/281
Verifying : libblkid-2.23.2-65.el7.x86_64 163/281
Verifying : 1:NetworkManager-1.18.8-1.el7.x86_64 164/281
Verifying : rpm-libs-4.11.3-45.el7.x86_64 165/281
Verifying : iwl6000g2b-firmware-18.168.6.1-79.el7.noarch 166/281
Verifying : 2:vim-filesystem-7.4.629-7.el7.x86_64 167/281
Verifying : httpd-2.4.6-95.el7.centos.x86_64 168/281
Verifying : 12:dhcp-libs-4.2.5-82.el7.centos.x86_64 169/281
Verifying : 1:grub2-tools-2.02-0.86.el7.centos.x86_64 170/281
Verifying : 1:openssl-libs-1.0.2k-19.el7.x86_64 171/281
Verifying : 1:NetworkManager-team-1.18.8-1.el7.x86_64 172/281
Verifying : 2:vim-common-7.4.629-7.el7.x86_64 173/281
Verifying : kernel-tools-libs-3.10.0-1160.el7.x86_64 174/281
Verifying : libxml2-python-2.9.1-6.el7.5.x86_64 175/281
Verifying : tcsh-6.18.01-17.el7.x86_64 176/281
Verifying : iwl3160-firmware-25.30.13.0-79.el7.noarch 177/281
Verifying : iwl6000-firmware-9.221.4.1-79.el7.noarch 178/281
Verifying : 1:perl-Pod-Escapes-1.04-297.el7.noarch 179/281
Verifying : sudo-1.8.23-10.el7.x86_64 180/281
Verifying : 7:lvm2-2.02.187-6.el7.x86_64 181/281
Verifying : nss-3.44.0-7.el7_7.x86_64 182/281
Verifying : iwl3945-firmware-15.32.2.9-79.el7.noarch 183/281
Verifying : selinux-policy-3.13.1-268.el7.noarch 184/281
Verifying : 1:NetworkManager-libnm-1.18.8-1.el7.x86_64 185/281
Verifying : 4:perl-macros-5.16.3-297.el7.x86_64 186/281
Verifying : libuuid-2.23.2-65.el7.x86_64 187/281
Verifying : 2:vim-minimal-7.4.629-7.el7.x86_64 188/281
Verifying : nss-tools-3.44.0-7.el7_7.x86_64 189/281
Verifying : 1:NetworkManager-tui-1.18.8-1.el7.x86_64 190/281
Verifying : 12:dhclient-4.2.5-82.el7.centos.x86_64 191/281
Verifying : 1:wpa_supplicant-2.6-12.el7.x86_64 192/281
Verifying : freetype-2.8-14.el7.x86_64 193/281
Verifying : 32:bind-utils-9.11.4-26.P2.el7.x86_64 194/281
Verifying : 1:grub2-2.02-0.86.el7.centos.x86_64 195/281
Verifying : kbd-misc-1.15.5-15.el7.noarch 196/281
Verifying : libsss_idmap-1.16.5-10.el7.x86_64 197/281
Verifying : cyrus-sasl-plain-2.1.26-23.el7.x86_64 198/281
Verifying : httpd-manual-2.4.6-95.el7.centos.noarch 199/281
Verifying : initscripts-9.49.53-1.el7.x86_64 200/281
Verifying : 32:bind-export-libs-9.11.4-26.P2.el7.x86_64 201/281
Verifying : rsyslog-8.24.0-55.el7.x86_64 202/281
Verifying : nss-sysinit-3.44.0-7.el7_7.x86_64 203/281
Verifying : iwl6050-firmware-41.28.5.1-79.el7.noarch 204/281
Verifying : iwl135-firmware-18.168.6.1-79.el7.noarch 205/281
Verifying : openssh-clients-7.4p1-21.el7.x86_64 206/281
Verifying : 1:openssl-1.0.2k-19.el7.x86_64 207/281
Verifying : 7:device-mapper-event-libs-1.02.170-6.el7.x86_64 208/281
Verifying : 1:grub2-common-2.02-0.86.el7.centos.noarch 209/281
Verifying : util-linux-2.23.2-65.el7.x86_64 210/281
Verifying : rpm-python-4.11.3-45.el7.x86_64 211/281
Verifying : tzdata-2020a-1.el7.noarch 212/281
Verifying : 7:lvm2-libs-2.02.187-6.el7.x86_64 213/281
Verifying : curl-7.29.0-59.el7.x86_64 214/281
Verifying : 1:grub2-pc-2.02-0.86.el7.centos.x86_64 215/281
Verifying : krb5-libs-1.15.1-50.el7.x86_64 216/281
Verifying : cronie-anacron-1.4.11-23.el7.x86_64 217/281
Verifying : nspr-4.21.0-1.el7.x86_64 218/281
Verifying : nss-softokn-freebl-3.44.0-8.el7_7.x86_64 219/281
Verifying : 1:grub2-pc-modules-2.02-0.86.el7.centos.noarch 220/281
Verifying : 4:perl-5.16.3-297.el7.x86_64 221/281
Verifying : iwl5000-firmware-8.83.5.1_1-79.el7.noarch 222/281
Verifying : mdadm-4.1-6.el7.x86_64 223/281
Verifying : libstoragemgmt-1.8.1-1.el7.x86_64 224/281
Verifying : 32:bind-libs-9.11.4-26.P2.el7.x86_64 225/281
Verifying : python-firewall-0.6.3-11.el7.noarch 226/281
Verifying : rpm-build-libs-4.11.3-45.el7.x86_64 227/281
Verifying : iwl4965-firmware-228.61.2.24-79.el7.noarch 228/281
Verifying : binutils-2.27-44.base.el7.x86_64 229/281
Verifying : libstoragemgmt-python-clibs-1.8.1-1.el7.x86_64 230/281
Verifying : libxml2-2.9.1-6.el7.5.x86_64 231/281
Verifying : libcroco-0.6.12-4.el7.x86_64 232/281
Verifying : 1:dmidecode-3.2-5.el7.x86_64 233/281
Verifying : centos-release-7-9.2009.0.el7.centos.x86_64 234/281
Verifying : systemd-libs-219-78.el7.x86_64 235/281
Verifying : libstoragemgmt-python-1.8.1-1.el7.noarch 236/281
Verifying : iwl7260-firmware-25.30.13.0-79.el7.noarch 237/281
Verifying : iwl105-firmware-18.168.6.1-79.el7.noarch 238/281
Verifying : cronie-1.4.11-23.el7.x86_64 239/281
Verifying : 4:perl-libs-5.16.3-297.el7.x86_64 240/281
Verifying : kbd-legacy-1.15.5-15.el7.noarch 241/281
Verifying : tuned-2.11.0-9.el7.noarch 242/281
Verifying : libcurl-7.29.0-59.el7.x86_64 243/281
Verifying : kexec-tools-2.0.15-51.el7.x86_64 244/281
Verifying : kbd-1.15.5-15.el7.x86_64 245/281
Verifying : python-perf-3.10.0-1160.el7.x86_64 246/281
Verifying : coreutils-8.22-24.el7.x86_64 247/281
Verifying : python-2.7.5-89.el7.x86_64 248/281
Verifying : polkit-0.112-26.el7.x86_64 249/281
Verifying : openldap-2.4.44-22.el7.x86_64 250/281
Verifying : openssh-server-7.4p1-21.el7.x86_64 251/281
Verifying : iprutils-2.4.17.1-3.el7.x86_64 252/281
Verifying : 1:mod_ssl-2.4.6-95.el7.centos.x86_64 253/281
Verifying : sos-3.9-2.el7.centos.noarch 254/281
Verifying : 2:vim-enhanced-7.4.629-7.el7.x86_64 255/281
Verifying : libsss_nss_idmap-1.16.5-10.el7.x86_64 256/281
Verifying : expat-2.1.0-12.el7.x86_64 257/281
Verifying : glibc-2.17-317.el7.x86_64 258/281
Verifying : open-vm-tools-11.0.5-3.el7.x86_64 259/281
Verifying : httpd-tools-2.4.6-95.el7.centos.x86_64 260/281
Verifying : bash-4.2.46-34.el7.x86_64 261/281
Verifying : openssh-7.4p1-21.el7.x86_64 262/281
Verifying : nss-util-3.44.0-4.el7_7.x86_64 263/281
Verifying : 7:device-mapper-libs-1.02.170-6.el7.x86_64 264/281
Verifying : 32:bind-license-9.11.4-26.P2.el7.noarch 265/281
Verifying : device-mapper-persistent-data-0.8.5-3.el7.x86_64 266/281
Verifying : python-libs-2.7.5-89.el7.x86_64 267/281
Verifying : kernel-tools-3.10.0-1160.el7.x86_64 268/281
Verifying : 12:dhcp-common-4.2.5-82.el7.centos.x86_64 269/281
Verifying : bpftool-3.10.0-1160.el7.x86_64 270/281
Verifying : firewalld-0.6.3-11.el7.noarch 271/281
Verifying : 1:grub2-tools-minimal-2.02-0.86.el7.centos.x86_64 272/281
Verifying : iwl2030-firmware-18.168.6.1-79.el7.noarch 273/281
Verifying : nss-softokn-3.44.0-8.el7_7.x86_64 274/281
Verifying : systemd-sysv-219-78.el7.x86_64 275/281
Verifying : 1:grub2-tools-extra-2.02-0.86.el7.centos.x86_64 276/281
Verifying : kpartx-0.4.9-133.el7.x86_64 277/281
Verifying : libsmartcols-2.23.2-65.el7.x86_64 278/281
Verifying : cyrus-sasl-lib-2.1.26-23.el7.x86_64 279/281
Verifying : systemd-python-219-78.el7.x86_64 280/281
Verifying : libmount-2.23.2-65.el7.x86_64 281/281

Installed:
kernel.x86_64 0:3.10.0-1160.59.1.el7

Updated:
NetworkManager.x86_64 1:1.18.8-2.el7_9 NetworkManager-libnm.x86_64 1:1.18.8-2.el7_9 NetworkManager-team.x86_64 1:1.18.8-2.el7_9
NetworkManager-tui.x86_64 1:1.18.8-2.el7_9 bash.x86_64 0:4.2.46-35.el7_9 bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.9
bind-libs.x86_64 32:9.11.4-26.P2.el7_9.9 bind-libs-lite.x86_64 32:9.11.4-26.P2.el7_9.9 bind-license.noarch 32:9.11.4-26.P2.el7_9.9
bind-utils.x86_64 32:9.11.4-26.P2.el7_9.9 binutils.x86_64 0:2.27-44.base.el7_9.1 bpftool.x86_64 0:3.10.0-1160.59.1.el7
ca-certificates.noarch 0:2021.2.50-72.el7_9 centos-release.x86_64 0:7-9.2009.1.el7.centos coreutils.x86_64 0:8.22-24.el7_9.2
cronie.x86_64 0:1.4.11-24.el7_9 cronie-anacron.x86_64 0:1.4.11-24.el7_9 curl.x86_64 0:7.29.0-59.el7_9.1
cyrus-sasl-lib.x86_64 0:2.1.26-24.el7_9 cyrus-sasl-plain.x86_64 0:2.1.26-24.el7_9 device-mapper.x86_64 7:1.02.170-6.el7_9.5
device-mapper-event.x86_64 7:1.02.170-6.el7_9.5 device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5 device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5
device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2 dhclient.x86_64 12:4.2.5-83.el7.centos.1 dhcp-common.x86_64 12:4.2.5-83.el7.centos.1
dhcp-libs.x86_64 12:4.2.5-83.el7.centos.1 dmidecode.x86_64 1:3.2-5.el7_9.1 expat.x86_64 0:2.1.0-14.el7_9
firewalld.noarch 0:0.6.3-13.el7_9 firewalld-filesystem.noarch 0:0.6.3-13.el7_9 freetype.x86_64 0:2.8-14.el7_9.1
glib2.x86_64 0:2.56.1-9.el7_9 glibc.x86_64 0:2.17-325.el7_9 glibc-common.x86_64 0:2.17-325.el7_9
grub2.x86_64 1:2.02-0.87.el7.centos.7 grub2-common.noarch 1:2.02-0.87.el7.centos.7 grub2-pc.x86_64 1:2.02-0.87.el7.centos.7
grub2-pc-modules.noarch 1:2.02-0.87.el7.centos.7 grub2-tools.x86_64 1:2.02-0.87.el7.centos.7 grub2-tools-extra.x86_64 1:2.02-0.87.el7.centos.7
grub2-tools-minimal.x86_64 1:2.02-0.87.el7.centos.7 httpd.x86_64 0:2.4.6-97.el7.centos.5 httpd-manual.noarch 0:2.4.6-97.el7.centos.5
httpd-tools.x86_64 0:2.4.6-97.el7.centos.5 initscripts.x86_64 0:9.49.53-1.el7_9.1 iprutils.x86_64 0:2.4.17.1-3.el7_7
iwl100-firmware.noarch 0:39.31.5.1-80.el7_9 iwl1000-firmware.noarch 1:39.31.5.1-80.el7_9 iwl105-firmware.noarch 0:18.168.6.1-80.el7_9
iwl135-firmware.noarch 0:18.168.6.1-80.el7_9 iwl2000-firmware.noarch 0:18.168.6.1-80.el7_9 iwl2030-firmware.noarch 0:18.168.6.1-80.el7_9
iwl3160-firmware.noarch 0:25.30.13.0-80.el7_9 iwl3945-firmware.noarch 0:15.32.2.9-80.el7_9 iwl4965-firmware.noarch 0:228.61.2.24-80.el7_9
iwl5000-firmware.noarch 0:8.83.5.1_1-80.el7_9 iwl5150-firmware.noarch 0:8.24.2.2-80.el7_9 iwl6000-firmware.noarch 0:9.221.4.1-80.el7_9
iwl6000g2a-firmware.noarch 0:18.168.6.1-80.el7_9 iwl6000g2b-firmware.noarch 0:18.168.6.1-80.el7_9 iwl6050-firmware.noarch 0:41.28.5.1-80.el7_9
iwl7260-firmware.noarch 0:25.30.13.0-80.el7_9 kbd.x86_64 0:1.15.5-16.el7_9 kbd-legacy.noarch 0:1.15.5-16.el7_9
kbd-misc.noarch 0:1.15.5-16.el7_9 kernel-tools.x86_64 0:3.10.0-1160.59.1.el7 kernel-tools-libs.x86_64 0:3.10.0-1160.59.1.el7
kexec-tools.x86_64 0:2.0.15-51.el7_9.3 kpartx.x86_64 0:0.4.9-135.el7_9 krb5-libs.x86_64 0:1.15.1-51.el7_9
libblkid.x86_64 0:2.23.2-65.el7_9.1 libcroco.x86_64 0:0.6.12-6.el7_9 libcurl.x86_64 0:7.29.0-59.el7_9.1
libmount.x86_64 0:2.23.2-65.el7_9.1 libsmartcols.x86_64 0:2.23.2-65.el7_9.1 libsss_idmap.x86_64 0:1.16.5-10.el7_9.12
libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.12 libstoragemgmt.x86_64 0:1.8.1-2.el7_9 libstoragemgmt-python.noarch 0:1.8.1-2.el7_9
libstoragemgmt-python-clibs.x86_64 0:1.8.1-2.el7_9 libuuid.x86_64 0:2.23.2-65.el7_9.1 libxml2.x86_64 0:2.9.1-6.el7_9.6
libxml2-python.x86_64 0:2.9.1-6.el7_9.6 linux-firmware.noarch 0:20200421-80.git78c0348.el7_9 lvm2.x86_64 7:2.02.187-6.el7_9.5
lvm2-libs.x86_64 7:2.02.187-6.el7_9.5 mdadm.x86_64 0:4.1-9.el7_9 microcode_ctl.x86_64 2:2.1-73.11.el7_9
mod_ssl.x86_64 1:2.4.6-97.el7.centos.5 nspr.x86_64 0:4.32.0-1.el7_9 nss.x86_64 0:3.67.0-4.el7_9
nss-softokn.x86_64 0:3.67.0-3.el7_9 nss-softokn-freebl.x86_64 0:3.67.0-3.el7_9 nss-sysinit.x86_64 0:3.67.0-4.el7_9
nss-tools.x86_64 0:3.67.0-4.el7_9 nss-util.x86_64 0:3.67.0-1.el7_9 open-vm-tools.x86_64 0:11.0.5-3.el7_9.3
openldap.x86_64 0:2.4.44-25.el7_9 openssh.x86_64 0:7.4p1-22.el7_9 openssh-clients.x86_64 0:7.4p1-22.el7_9
openssh-server.x86_64 0:7.4p1-22.el7_9 openssl.x86_64 1:1.0.2k-25.el7_9 openssl-libs.x86_64 1:1.0.2k-25.el7_9
perl.x86_64 4:5.16.3-299.el7_9 perl-Pod-Escapes.noarch 1:1.04-299.el7_9 perl-libs.x86_64 4:5.16.3-299.el7_9
perl-macros.x86_64 4:5.16.3-299.el7_9 polkit.x86_64 0:0.112-26.el7_9.1 python.x86_64 0:2.7.5-90.el7
python-firewall.noarch 0:0.6.3-13.el7_9 python-libs.x86_64 0:2.7.5-90.el7 python-perf.x86_64 0:3.10.0-1160.59.1.el7
rpm.x86_64 0:4.11.3-48.el7_9 rpm-build-libs.x86_64 0:4.11.3-48.el7_9 rpm-libs.x86_64 0:4.11.3-48.el7_9
rpm-python.x86_64 0:4.11.3-48.el7_9 rsyslog.x86_64 0:8.24.0-57.el7_9.1 selinux-policy.noarch 0:3.13.1-268.el7_9.2
selinux-policy-targeted.noarch 0:3.13.1-268.el7_9.2 sos.noarch 0:3.9-5.el7.centos.10 sssd-client.x86_64 0:1.16.5-10.el7_9.12
sudo.x86_64 0:1.8.23-10.el7_9.2 systemd.x86_64 0:219-78.el7_9.5 systemd-libs.x86_64 0:219-78.el7_9.5
systemd-python.x86_64 0:219-78.el7_9.5 systemd-sysv.x86_64 0:219-78.el7_9.5 tcsh.x86_64 0:6.18.01-17.el7_9.1
tuned.noarch 0:2.11.0-11.el7_9 tzdata.noarch 0:2022a-1.el7 unzip.x86_64 0:6.0-24.el7_9
util-linux.x86_64 0:2.23.2-65.el7_9.1 vim-common.x86_64 2:7.4.629-8.el7_9 vim-enhanced.x86_64 2:7.4.629-8.el7_9
vim-filesystem.x86_64 2:7.4.629-8.el7_9 vim-minimal.x86_64 2:7.4.629-8.el7_9 virt-what.x86_64 0:1.18-4.el7_9.1
wpa_supplicant.x86_64 1:2.6-12.el7_9.2 zlib.x86_64 0:1.2.7-19.el7_9

Complete!

[root@nvc ~]

# yum upgrade -y
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

  • base: rep-centos-il.upress.io
  • extras: rep-centos-il.upress.io
  • updates: pkg.adfinis.com
    No packages marked for update

[root@nvc ~]

# yum upgrade -y
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile base: rep-centos-il.upress.io extras: rep-centos-il.upress.io updates: pkg.adfinis.com
No packages marked for update

[root@nvc ~]

# yum upgrade -y
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile base: rep-centos-il.upress.io extras: rep-centos-il.upress.io updates: pkg.adfinis.com
No packages marked for update

[root@nvc ~]

# yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Loaded plugins: fastestmirror, langpacks
epel-release-latest-7.noarch.rpm | 15 kB 00:00:00
Examining /var/tmp/yum-root-pkPctP/epel-release-latest-7.noarch.rpm: epel-release-7-14.noarch
Marking /var/tmp/yum-root-pkPctP/epel-release-latest-7.noarch.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package epel-release.noarch 0:7-14 will be installed
–> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================

Package Arch Version Repository Size

Installing:
epel-release noarch 7-14 /epel-release-latest-7.noarch 25 k

Transaction Summary

Install 1 Package

Total size: 25 k
Installed size: 25 k
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : epel-release-7-14.noarch 1/1
Verifying : epel-release-7-14.noarch 1/1

Installed:
epel-release.noarch 0:7-14

Complete!

[root@nvc ~]

# yum -y install https://rpms.remirepo.net/enterprise/remi-release-7.rpm
Loaded plugins: fastestmirror, langpacks
Cannot open: https://rpms.remirepo.net/enterprise/remi-release-7.rpm. Skipping.===================================- ] 322 B/s | 16 kB 00:00:24 ETA
Error: Nothing to do

[root@nvc ~]

# yum -y install yum-utils
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 7.7 kB 00:00:00

  • base: rep-centos-il.upress.io
  • epel: my.mirrors.thegigabit.com
  • extras: rep-centos-il.upress.io
  • updates: pkg.adfinis.com
    epel | 4.7 kB 00:00:00
    (1/3): epel/x86_64/group_gz | 96 kB 00:00:00
    (2/3): epel/x86_64/updateinfo | 1.1 MB 00:00:01
    epel/x86_64/primary_db FAILED
    https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/5a1f20fbc399719a4cdce18302c340ec8e2724d9430723c78e9cb4423ef736f7-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 – Not Found
    Trying other mirror.
    To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors

If above article doesn’t help to resolve this issue please use https://bugs.centos.org/.

(3/3): epel/x86_64/primary_db | 7.0 MB 00:00:01
Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
Nothing to do

[root@nvc ~]

# yum –enablerepo=remi-php74 install php
Loaded plugins: fastestmirror, langpacks

Error getting repository data for remi-php74, repository not found

[root@nvc ~]

# sudo rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-7.rpm
Retrieving http://rpms.famillecollet.com/enterprise/remi-release-7.rpm
warning: /var/tmp/rpm-tmp.gMyn2h: Header V4 DSA/SHA1 Signature, key ID 00f97f56: NOKEY
Preparing… ################################# [100%]
Updating / installing…
1:remi-release-7.9-3.el7.remi ################################# [100%]

[root@nvc ~]

# yum –enablerepo=remi-php74 install php
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

  • base: rep-centos-il.upress.io
  • epel: download.nus.edu.sg
  • extras: rep-centos-il.upress.io
  • remi-php74: rpms.remirepo.net
  • remi-safe: rpms.remirepo.net
  • updates: pkg.adfinis.com
    remi-php74 | 3.0 kB 00:00:00
    remi-safe | 3.0 kB 00:00:00
    (1/2): remi-php74/primary_db | 254 kB 00:00:00
    (2/2): remi-safe/primary_db | 2.1 MB 00:00:01
    Resolving Dependencies
    –> Running transaction check
    —> Package php.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Processing Dependency: php-cli(x86-64) = 7.4.28-1.el7.remi for package: php-7.4.28-1.el7.remi.x86_64
    –> Processing Dependency: php-common(x86-64) = 7.4.28-1.el7.remi for package: php-7.4.28-1.el7.remi.x86_64
    –> Processing Dependency: php-sodium(x86-64) = 7.4.28-1.el7.remi for package: php-7.4.28-1.el7.remi.x86_64
    –> Running transaction check
    —> Package php-cli.x86_64 0:7.4.28-1.el7.remi will be installed
    —> Package php-common.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Processing Dependency: php-json(x86-64) = 7.4.28-1.el7.remi for package: php-common-7.4.28-1.el7.remi.x86_64
    —> Package php-sodium.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Processing Dependency: libsodium.so.23()(64bit) for package: php-sodium-7.4.28-1.el7.remi.x86_64
    –> Running transaction check
    —> Package libsodium.x86_64 0:1.0.18-1.el7 will be installed
    —> Package php-json.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================

Package Arch Version Repository Size

Installing:
php x86_64 7.4.28-1.el7.remi remi-php74 3.4 M
Installing for dependencies:
libsodium x86_64 1.0.18-1.el7 epel 147 k
php-cli x86_64 7.4.28-1.el7.remi remi-php74 5.2 M
php-common x86_64 7.4.28-1.el7.remi remi-php74 1.2 M
php-json x86_64 7.4.28-1.el7.remi remi-php74 74 k
php-sodium x86_64 7.4.28-1.el7.remi remi-php74 85 k

Transaction Summary

Install 1 Package (+5 Dependent packages)

Total download size: 10 M
Installed size: 42 M
Is this ok [y/d/N]: y
Downloading packages:
warning: /var/cache/yum/x86_64/7/epel/packages/libsodium-1.0.18-1.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY 0.0 B/s | 93 kB –:–:– ETA
Public key for libsodium-1.0.18-1.el7.x86_64.rpm is not installed
(1/6): libsodium-1.0.18-1.el7.x86_64.rpm | 147 kB 00:00:00
warning: /var/cache/yum/x86_64/7/remi-php74/packages/php-7.4.28-1.el7.remi.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 00f97f56: NOKEY MB/s | 4.3 MB 00:00:03 ETA
Public key for php-7.4.28-1.el7.remi.x86_64.rpm is not installed
(2/6): php-7.4.28-1.el7.remi.x86_64.rpm | 3.4 MB 00:00:01
(3/6): php-json-7.4.28-1.el7.remi.x86_64.rpm | 74 kB 00:00:01
(4/6): php-cli-7.4.28-1.el7.remi.x86_64.rpm | 5.2 MB 00:00:01
(5/6): php-sodium-7.4.28-1.el7.remi.x86_64.rpm | 85 kB 00:00:01

(6/6): php-common-7.4.28-1.el7.remi.x86_64.rpm | 1.2 MB 00:00:13

Total 755 kB/s | 10 MB 00:00:13
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
Importing GPG key 0x352C64E5:
Userid : “Fedora EPEL (7) epel@fedoraproject.org
Fingerprint: 91e9 7d7c 4a5e 96f1 7f3e 888f 6a2f aea2 352c 64e5
Package : epel-release-7-14.noarch (@/epel-release-latest-7.noarch)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
Is this ok [y/N]: y
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
Importing GPG key 0x00F97F56:
Userid : “Remi Collet RPMS@FamilleCollet.com
Fingerprint: 1ee0 4cce 88a4 ae4a a29a 5df5 004e 6f47 00f9 7f56
Package : remi-release-7.9-3.el7.remi.noarch (installed)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-remi
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Warning: RPMDB altered outside of yum.
Installing : php-common-7.4.28-1.el7.remi.x86_64 1/6
Installing : php-json-7.4.28-1.el7.remi.x86_64 2/6
Installing : php-cli-7.4.28-1.el7.remi.x86_64 3/6
Installing : libsodium-1.0.18-1.el7.x86_64 4/6
Installing : php-sodium-7.4.28-1.el7.remi.x86_64 5/6
Installing : php-7.4.28-1.el7.remi.x86_64 6/6
Verifying : libsodium-1.0.18-1.el7.x86_64 1/6
Verifying : php-json-7.4.28-1.el7.remi.x86_64 2/6
Verifying : php-common-7.4.28-1.el7.remi.x86_64 3/6
Verifying : php-sodium-7.4.28-1.el7.remi.x86_64 4/6
Verifying : php-7.4.28-1.el7.remi.x86_64 5/6
Verifying : php-cli-7.4.28-1.el7.remi.x86_64 6/6

Installed:
php.x86_64 0:7.4.28-1.el7.remi

Dependency Installed:
libsodium.x86_64 0:1.0.18-1.el7 php-cli.x86_64 0:7.4.28-1.el7.remi php-common.x86_64 0:7.4.28-1.el7.remi php-json.x86_64 0:7.4.28-1.el7.remi
php-sodium.x86_64 0:7.4.28-1.el7.remi

Complete!

[root@nvc ~]

# yum-config-manager –enable remi-php74
Loaded plugins: fastestmirror, langpacks
=========================================================================== repo: remi-php74 ===========================================================================

[remi-php74]

async = True
bandwidth = 0
base_persistdir = /var/lib/yum/repos/x86_64/7
baseurl =
cache = 0
cachedir = /var/cache/yum/x86_64/7/remi-php74
check_config_file_age = True
compare_providers_priority = 80
cost = 1000
deltarpm_metadata_percentage = 100
deltarpm_percentage =
enabled = 1
enablegroups = True
exclude =
failovermethod = priority
ftp_disable_epsv = False
gpgcadir = /var/lib/yum/repos/x86_64/7/remi-php74/gpgcadir
gpgcakey =
gpgcheck = True
gpgdir = /var/lib/yum/repos/x86_64/7/remi-php74/gpgdir
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
hdrdir = /var/cache/yum/x86_64/7/remi-php74/headers
http_caching = all
includepkgs =
ip_resolve =
keepalive = True
keepcache = False
mddownloadpolicy = sqlite
mdpolicy = group:small
mediaid =
metadata_expire = 21600
metadata_expire_filter = read-only:present
metalink =
minrate = 0
mirrorlist = http://cdn.remirepo.net/enterprise/7/php74/mirror
mirrorlist_expire = 86400
name = Remi’s PHP 7.4 RPM repository for Enterprise Linux 7 – x86_64
old_base_cache_dir =
password =
persistdir = /var/lib/yum/repos/x86_64/7/remi-php74
pkgdir = /var/cache/yum/x86_64/7/remi-php74/packages
proxy = False
proxy_dict =
proxy_password =
proxy_username =
repo_gpgcheck = False
retries = 10
skip_if_unavailable = False
ssl_check_cert_permissions = True
sslcacert =
sslclientcert =
sslclientkey =
sslverify = True
throttle = 0
timeout = 30.0
ui_id = remi-php74
ui_repoid_vars = releasever,
basearch
username =

[root@nvc ~]

# php -v
PHP 7.4.28 (cli) (built: Feb 15 2022 13:23:10) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies

[root@nvc ~]

# yum install php php-common php-opcache php-mcrypt php-cli php-gd php-curl php-mysql -y
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

  • base: rep-centos-il.upress.io
  • epel: download.nus.edu.sg
  • extras: rep-centos-il.upress.io
  • remi-php74: remirepo.reloumirrors.net
  • remi-safe: remirepo.reloumirrors.net
  • updates: pkg.adfinis.com
    remi-php74 | 3.0 kB 00:00:00
    Package php-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Package php-common-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Package php-mcrypt is obsoleted by php-pecl-mcrypt, trying to install php-pecl-mcrypt-1.0.4-1.el7.remi.7.4.x86_64 instead
    Package php-cli-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Package php-common-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Package php-mysql is obsoleted by php-mysqlnd, trying to install php-mysqlnd-7.4.28-1.el7.remi.x86_64 instead
    Resolving Dependencies
    –> Running transaction check
    —> Package php-gd.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Processing Dependency: libgd.so.103()(64bit) for package: php-gd-7.4.28-1.el7.remi.x86_64
    —> Package php-mysqlnd.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Processing Dependency: php-pdo(x86-64) = 7.4.28-1.el7.remi for package: php-mysqlnd-7.4.28-1.el7.remi.x86_64
    —> Package php-opcache.x86_64 0:7.4.28-1.el7.remi will be installed
    —> Package php-pecl-mcrypt.x86_64 0:1.0.4-1.el7.remi.7.4 will be installed
    –> Processing Dependency: libmcrypt.so.4()(64bit) for package: php-pecl-mcrypt-1.0.4-1.el7.remi.7.4.x86_64
    –> Running transaction check
    —> Package gd3php.x86_64 0:2.3.3-4.el7.remi will be installed
    –> Processing Dependency: libjpeg.so.62(LIBJPEG_6.2)(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libtiff.so.5(LIBTIFF_4.0)(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libX11.so.6()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libXpm.so.4()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libfontconfig.so.1()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libjpeg.so.62()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libraqm.so.0()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libtiff.so.5()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    –> Processing Dependency: libwebp.so.7()(64bit) for package: gd3php-2.3.3-4.el7.remi.x86_64
    —> Package libmcrypt.x86_64 0:2.5.8-13.el7 will be installed
    —> Package php-pdo.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Running transaction check
    —> Package fontconfig.x86_64 0:2.13.0-4.3.el7 will be installed
    –> Processing Dependency: fontpackages-filesystem for package: fontconfig-2.13.0-4.3.el7.x86_64
    –> Processing Dependency: dejavu-sans-fonts for package: fontconfig-2.13.0-4.3.el7.x86_64
    —> Package libX11.x86_64 0:1.6.7-4.el7_9 will be installed
    –> Processing Dependency: libX11-common >= 1.6.7-4.el7_9 for package: libX11-1.6.7-4.el7_9.x86_64
    –> Processing Dependency: libxcb.so.1()(64bit) for package: libX11-1.6.7-4.el7_9.x86_64
    —> Package libXpm.x86_64 0:3.5.12-1.el7 will be installed
    —> Package libjpeg-turbo.x86_64 0:1.2.90-8.el7 will be installed
    —> Package libraqm.x86_64 0:0.7.0-4.el7 will be installed
    –> Processing Dependency: libfribidi.so.0()(64bit) for package: libraqm-0.7.0-4.el7.x86_64
    –> Processing Dependency: libharfbuzz.so.0()(64bit) for package: libraqm-0.7.0-4.el7.x86_64
    —> Package libtiff.x86_64 0:4.0.3-35.el7 will be installed
    –> Processing Dependency: libjbig.so.2.0()(64bit) for package: libtiff-4.0.3-35.el7.x86_64
    —> Package libwebp7.x86_64 0:1.0.3-1.el7.remi will be installed
    –> Running transaction check
    —> Package dejavu-sans-fonts.noarch 0:2.33-6.el7 will be installed
    –> Processing Dependency: dejavu-fonts-common = 2.33-6.el7 for package: dejavu-sans-fonts-2.33-6.el7.noarch
    —> Package fontpackages-filesystem.noarch 0:1.44-8.el7 will be installed
    —> Package fribidi.x86_64 0:1.0.2-1.el7_7.1 will be installed
    —> Package harfbuzz.x86_64 0:1.7.5-2.el7 will be installed
    –> Processing Dependency: libgraphite2.so.3()(64bit) for package: harfbuzz-1.7.5-2.el7.x86_64
    —> Package jbigkit-libs.x86_64 0:2.0-11.el7 will be installed
    —> Package libX11-common.noarch 0:1.6.7-4.el7_9 will be installed
    —> Package libxcb.x86_64 0:1.13-1.el7 will be installed
    –> Processing Dependency: libXau.so.6()(64bit) for package: libxcb-1.13-1.el7.x86_64
    –> Running transaction check
    —> Package dejavu-fonts-common.noarch 0:2.33-6.el7 will be installed
    —> Package graphite2.x86_64 0:1.3.10-1.el7_3 will be installed
    —> Package libXau.x86_64 0:1.0.8-2.1.el7 will be installed
    –> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================

Package Arch Version Repository Size

Installing:
php-gd x86_64 7.4.28-1.el7.remi remi-php74 89 k
php-mysqlnd x86_64 7.4.28-1.el7.remi remi-php74 255 k
php-opcache x86_64 7.4.28-1.el7.remi remi-php74 332 k
php-pecl-mcrypt x86_64 1.0.4-1.el7.remi.7.4 remi-php74 30 k
Installing for dependencies:
dejavu-fonts-common noarch 2.33-6.el7 base 64 k
dejavu-sans-fonts noarch 2.33-6.el7 base 1.4 M
fontconfig x86_64 2.13.0-4.3.el7 base 254 k
fontpackages-filesystem noarch 1.44-8.el7 base 9.9 k
fribidi x86_64 1.0.2-1.el7_7.1 base 79 k
gd3php x86_64 2.3.3-4.el7.remi remi-safe 138 k
graphite2 x86_64 1.3.10-1.el7_3 base 115 k
harfbuzz x86_64 1.7.5-2.el7 base 267 k
jbigkit-libs x86_64 2.0-11.el7 base 46 k
libX11 x86_64 1.6.7-4.el7_9 updates 607 k
libX11-common noarch 1.6.7-4.el7_9 updates 164 k
libXau x86_64 1.0.8-2.1.el7 base 29 k
libXpm x86_64 3.5.12-1.el7 base 55 k
libjpeg-turbo x86_64 1.2.90-8.el7 base 135 k
libmcrypt x86_64 2.5.8-13.el7 epel 99 k
libraqm x86_64 0.7.0-4.el7 epel 15 k
libtiff x86_64 4.0.3-35.el7 base 172 k
libwebp7 x86_64 1.0.3-1.el7.remi remi-safe 266 k
libxcb x86_64 1.13-1.el7 base 214 k
php-pdo x86_64 7.4.28-1.el7.remi remi-php74 139 k

Transaction Summary

Install 4 Packages (+20 Dependent packages)

Total download size: 4.9 M
Installed size: 16 M
Downloading packages:
(1/24): fribidi-1.0.2-1.el7_7.1.x86_64.rpm | 79 kB 00:00:01
(2/24): dejavu-fonts-common-2.33-6.el7.noarch.rpm | 64 kB 00:00:01
(3/24): dejavu-sans-fonts-2.33-6.el7.noarch.rpm | 1.4 MB 00:00:01
(4/24): harfbuzz-1.7.5-2.el7.x86_64.rpm | 267 kB 00:00:00
(5/24): graphite2-1.3.10-1.el7_3.x86_64.rpm | 115 kB 00:00:00
(6/24): jbigkit-libs-2.0-11.el7.x86_64.rpm | 46 kB 00:00:00
(7/24): gd3php-2.3.3-4.el7.remi.x86_64.rpm | 138 kB 00:00:00
(8/24): libXau-1.0.8-2.1.el7.x86_64.rpm | 29 kB 00:00:00
(9/24): libXpm-3.5.12-1.el7.x86_64.rpm | 55 kB 00:00:00
(10/24): libjpeg-turbo-1.2.90-8.el7.x86_64.rpm | 135 kB 00:00:00
(11/24): libX11-common-1.6.7-4.el7_9.noarch.rpm | 164 kB 00:00:00
(12/24): libX11-1.6.7-4.el7_9.x86_64.rpm | 607 kB 00:00:01
(13/24): libtiff-4.0.3-35.el7.x86_64.rpm | 172 kB 00:00:00
(14/24): fontpackages-filesystem-1.44-8.el7.noarch.rpm | 9.9 kB 00:00:02
(15/24): fontconfig-2.13.0-4.3.el7.x86_64.rpm | 254 kB 00:00:03
(16/24): libxcb-1.13-1.el7.x86_64.rpm | 214 kB 00:00:00
(17/24): libmcrypt-2.5.8-13.el7.x86_64.rpm | 99 kB 00:00:00
(18/24): libwebp7-1.0.3-1.el7.remi.x86_64.rpm | 266 kB 00:00:00
(19/24): libraqm-0.7.0-4.el7.x86_64.rpm | 15 kB 00:00:00
(20/24): php-gd-7.4.28-1.el7.remi.x86_64.rpm | 89 kB 00:00:00
(21/24): php-mysqlnd-7.4.28-1.el7.remi.x86_64.rpm | 255 kB 00:00:00
(22/24): php-opcache-7.4.28-1.el7.remi.x86_64.rpm | 332 kB 00:00:00
(23/24): php-pecl-mcrypt-1.0.4-1.el7.remi.7.4.x86_64.rpm | 30 kB 00:00:00

(24/24): php-pdo-7.4.28-1.el7.remi.x86_64.rpm | 139 kB 00:00:01

Total 935 kB/s | 4.9 MB 00:00:05
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : libjpeg-turbo-1.2.90-8.el7.x86_64 1/24
Installing : fontpackages-filesystem-1.44-8.el7.noarch 2/24
Installing : dejavu-fonts-common-2.33-6.el7.noarch 3/24
Installing : dejavu-sans-fonts-2.33-6.el7.noarch 4/24
Installing : fontconfig-2.13.0-4.3.el7.x86_64 5/24
Installing : libX11-common-1.6.7-4.el7_9.noarch 6/24
Installing : libwebp7-1.0.3-1.el7.remi.x86_64 7/24
Installing : graphite2-1.3.10-1.el7_3.x86_64 8/24
Installing : harfbuzz-1.7.5-2.el7.x86_64 9/24
Installing : libXau-1.0.8-2.1.el7.x86_64 10/24
Installing : libxcb-1.13-1.el7.x86_64 11/24
Installing : libX11-1.6.7-4.el7_9.x86_64 12/24
Installing : libXpm-3.5.12-1.el7.x86_64 13/24
Installing : jbigkit-libs-2.0-11.el7.x86_64 14/24
Installing : libtiff-4.0.3-35.el7.x86_64 15/24
Installing : fribidi-1.0.2-1.el7_7.1.x86_64 16/24
Installing : libraqm-0.7.0-4.el7.x86_64 17/24
Installing : gd3php-2.3.3-4.el7.remi.x86_64 18/24
Installing : php-pdo-7.4.28-1.el7.remi.x86_64 19/24
Installing : libmcrypt-2.5.8-13.el7.x86_64 20/24
Installing : php-pecl-mcrypt-1.0.4-1.el7.remi.7.4.x86_64 21/24
Installing : php-mysqlnd-7.4.28-1.el7.remi.x86_64 22/24
Installing : php-gd-7.4.28-1.el7.remi.x86_64 23/24
Installing : php-opcache-7.4.28-1.el7.remi.x86_64 24/24
Verifying : fontconfig-2.13.0-4.3.el7.x86_64 1/24
Verifying : gd3php-2.3.3-4.el7.remi.x86_64 2/24
Verifying : libmcrypt-2.5.8-13.el7.x86_64 3/24
Verifying : fontpackages-filesystem-1.44-8.el7.noarch 4/24
Verifying : libtiff-4.0.3-35.el7.x86_64 5/24
Verifying : php-pdo-7.4.28-1.el7.remi.x86_64 6/24
Verifying : dejavu-fonts-common-2.33-6.el7.noarch 7/24
Verifying : fribidi-1.0.2-1.el7_7.1.x86_64 8/24
Verifying : libxcb-1.13-1.el7.x86_64 9/24
Verifying : php-gd-7.4.28-1.el7.remi.x86_64 10/24
Verifying : libXpm-3.5.12-1.el7.x86_64 11/24
Verifying : libjpeg-turbo-1.2.90-8.el7.x86_64 12/24
Verifying : harfbuzz-1.7.5-2.el7.x86_64 13/24
Verifying : dejavu-sans-fonts-2.33-6.el7.noarch 14/24
Verifying : jbigkit-libs-2.0-11.el7.x86_64 15/24
Verifying : libraqm-0.7.0-4.el7.x86_64 16/24
Verifying : php-pecl-mcrypt-1.0.4-1.el7.remi.7.4.x86_64 17/24
Verifying : php-opcache-7.4.28-1.el7.remi.x86_64 18/24
Verifying : libXau-1.0.8-2.1.el7.x86_64 19/24
Verifying : libX11-1.6.7-4.el7_9.x86_64 20/24
Verifying : graphite2-1.3.10-1.el7_3.x86_64 21/24
Verifying : libwebp7-1.0.3-1.el7.remi.x86_64 22/24
Verifying : libX11-common-1.6.7-4.el7_9.noarch 23/24
Verifying : php-mysqlnd-7.4.28-1.el7.remi.x86_64 24/24

Installed:
php-gd.x86_64 0:7.4.28-1.el7.remi php-mysqlnd.x86_64 0:7.4.28-1.el7.remi php-opcache.x86_64 0:7.4.28-1.el7.remi php-pecl-mcrypt.x86_64 0:1.0.4-1.el7.remi.7.4

Dependency Installed:
dejavu-fonts-common.noarch 0:2.33-6.el7 dejavu-sans-fonts.noarch 0:2.33-6.el7 fontconfig.x86_64 0:2.13.0-4.3.el7 fontpackages-filesystem.noarch 0:1.44-8.el7
fribidi.x86_64 0:1.0.2-1.el7_7.1 gd3php.x86_64 0:2.3.3-4.el7.remi graphite2.x86_64 0:1.3.10-1.el7_3 harfbuzz.x86_64 0:1.7.5-2.el7
jbigkit-libs.x86_64 0:2.0-11.el7 libX11.x86_64 0:1.6.7-4.el7_9 libX11-common.noarch 0:1.6.7-4.el7_9 libXau.x86_64 0:1.0.8-2.1.el7
libXpm.x86_64 0:3.5.12-1.el7 libjpeg-turbo.x86_64 0:1.2.90-8.el7 libmcrypt.x86_64 0:2.5.8-13.el7 libraqm.x86_64 0:0.7.0-4.el7
libtiff.x86_64 0:4.0.3-35.el7 libwebp7.x86_64 0:1.0.3-1.el7.remi libxcb.x86_64 0:1.13-1.el7 php-pdo.x86_64 0:7.4.28-1.el7.remi

Complete!

[root@nvc ~]

# sudo yum install httpd httpd-tools
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

  • base: rep-centos-il.upress.io
  • epel: download.nus.edu.sg
  • extras: rep-centos-il.upress.io
  • remi-php74: remirepo.reloumirrors.net
  • remi-safe: remirepo.reloumirrors.net
  • updates: pkg.adfinis.com
    Package httpd-2.4.6-97.el7.centos.5.x86_64 already installed and latest version
    Package httpd-tools-2.4.6-97.el7.centos.5.x86_64 already installed and latest version
    Nothing to do

[root@nvc ~]

# sudo systemctl enable httpd
Created symlink from /etc/systemd/system/multi-user.target.wants/httpd.service to /usr/lib/systemd/system/httpd.service.

[root@nvc ~]

# sudo systemctl start httpd

[root@nvc ~]

# sudo systemctl status httpd
● httpd.service – The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-04-02 11:58:18 +04; 9s ago
Docs: man:httpd(8)
man:apachectl(8)
Main PID: 55987 (httpd)
Status: “Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec”
CGroup: /system.slice/httpd.service
├─55987 /usr/sbin/httpd -DFOREGROUND
├─55988 /usr/sbin/httpd -DFOREGROUND
├─55989 /usr/sbin/httpd -DFOREGROUND
├─55990 /usr/sbin/httpd -DFOREGROUND
├─55991 /usr/sbin/httpd -DFOREGROUND
├─55992 /usr/sbin/httpd -DFOREGROUND
└─55993 /usr/sbin/httpd -DFOREGROUND

Apr 02 11:58:17 nvc systemd[1]: Starting The Apache HTTP Server…
Apr 02 11:58:18 nvc httpd[55987]: AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using fe80::c154:c121:5c98:c897. …his message
Apr 02 11:58:18 nvc systemd[1]: Started The Apache HTTP Server.
Hint: Some lines were ellipsized, use -l to show in full.

[root@nvc ~]

# setenforce 0

[root@nvc ~]

# cd /var/www/html/

[root@nvc html]

#

[root@nvc html]

# vi info.php

[root@nvc html]

# systemctl restart httpd.service

[root@nvc html]

# sudo systemctl status httpd
● httpd.service – The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-04-02 12:00:32 +04; 1min 1s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 56012 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)
Main PID: 56017 (httpd)
Status: “Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec”
CGroup: /system.slice/httpd.service
├─56017 /usr/sbin/httpd -DFOREGROUND
├─56018 /usr/sbin/httpd -DFOREGROUND
├─56019 /usr/sbin/httpd -DFOREGROUND
├─56020 /usr/sbin/httpd -DFOREGROUND
├─56021 /usr/sbin/httpd -DFOREGROUND
├─56022 /usr/sbin/httpd -DFOREGROUND
└─56023 /usr/sbin/httpd -DFOREGROUND

Apr 02 12:00:07 nvc systemd[1]: Starting The Apache HTTP Server…
Apr 02 12:00:22 nvc httpd[56017]: AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using fe80::c154:c121:5c98:c897. …his message
Apr 02 12:00:32 nvc systemd[1]: Started The Apache HTTP Server.
Hint: Some lines were ellipsized, use -l to show in full.

[root@nvc html]

# cd

[root@nvc ~]

# vi /etc/hosts

[root@nvc ~]

# systemctl restart httpd

[root@nvc ~]

# sudo systemctl status httpd
● httpd.service – The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-04-02 12:02:51 +04; 3s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 56050 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)
Main PID: 56055 (httpd)
Status: “Processing requests…”
CGroup: /system.slice/httpd.service
├─56055 /usr/sbin/httpd -DFOREGROUND
├─56056 /usr/sbin/httpd -DFOREGROUND
├─56057 /usr/sbin/httpd -DFOREGROUND
├─56058 /usr/sbin/httpd -DFOREGROUND
├─56059 /usr/sbin/httpd -DFOREGROUND
├─56060 /usr/sbin/httpd -DFOREGROUND
└─56061 /usr/sbin/httpd -DFOREGROUND

Apr 02 12:02:51 nvc systemd[1]: Starting The Apache HTTP Server…
Apr 02 12:02:51 nvc systemd[1]: Started The Apache HTTP Server.

[root@nvc ~]

# cd /etc/httpd/conf.d/

[root@nvc conf.d]

# ls
autoindex.conf fcgid.conf manual.conf php.conf README ssl.conf userdir.conf welcome.conf

[root@nvc conf.d]

# cd

[root@nvc ~]

# sudo mysql_secure_installation
sudo: mysql_secure_installation: command not found

[root@nvc ~]

# yum -y install php php-common php-mbstring php-gd
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

  • base: rep-centos-il.upress.io
  • epel: download.nus.edu.sg
  • extras: rep-centos-il.upress.io
  • remi-php74: mirror.netsite.dk
  • remi-safe: mirror.netsite.dk
  • updates: pkg.adfinis.com
    Package php-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Package php-common-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Package php-gd-7.4.28-1.el7.remi.x86_64 already installed and latest version
    Resolving Dependencies
    –> Running transaction check
    —> Package php-mbstring.x86_64 0:7.4.28-1.el7.remi will be installed
    –> Processing Dependency: libonig.so.105()(64bit) for package: php-mbstring-7.4.28-1.el7.remi.x86_64
    –> Running transaction check
    —> Package oniguruma5php.x86_64 0:6.9.7.1-1.el7.remi will be installed
    –> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================

Package Arch Version Repository Size

Installing:
php-mbstring x86_64