Muhammad SYahmi

CIT-0553
OPERATING SYSTEM (PBL 2)

STUDENT NAME : MUHAMMAD SYAHMI BIN RAIM

STUDENT ID : NWS19010052

SEMESTER/GROUP : SEM 3

TTO NAME : MS NURUL RAFIDZA RASHID

SUBMISSION DATE : 18/06/2020

1

TABLE OF CONTENT
1. Introduction......................................................................................................................................3
2. Disaster Recovery Plan ............................................................................................................4-11
3. Patch Management Plan.........................................................................................................12-16
4. Conclusion...................................................................................................................................... 17
5. References......................................................................................................................................18

2

INTRODUCTION
In this PBL, I have to do Disaster Recovery and Patch Management in Windows Server 2012. I
will show step by step how to do this efficiently and work smoothly.

3

Disaster Recovery Plan
Disaster Recovery (DR) is the process an organization uses to access the software, data
hardware that needed to resume the performance of normal business operations in the event
of natural disaster or disaster caused by humans. In other words, DR is automatic transfer of
data or other digital assets to a secondary server.
The purpose of these plans is to schedule data backups. Despite the disaster happen, business
operations can resume as normal on backup server - at least until power is restored to the
primary data center.

There are various triggers which can result in the failure of Exchange Server:
 Virus Infections
 Hardware Failure
 Frequent power surges
 Abnormal shutdown of system
 Human Errors

When the Microsoft Exchange Server fails, working of the entire organization is affected
resulting in the loss of productivity. Organizations cannot accept such loss, therefore, it
becomes crucial for the organizations to have such Exchange 2016, 2013, 2010 or 2007
Disaster Recovery plan to bounce back from these calamities.

4

Steps for Microsoft Exchange Server Disaster Recovery.
1) Open the Server Manager and click manage and then click Add Roles and Features
.
2) Click Next thoroughly.

5

2) In the Feature section, scroll down and click for Window Server Backup. Then click Next.
3) Click Install and wait for the installation finish.

6

4) After finish the installation, click close and go to Local Backup.
5) Right click the Local Backup and click on the backup once.
5) Click Next.

7

6) Tick on the Custom and the click next.
7) Click the Add items
8) Expand the Local (C:) and search for Important Data(Example).

8

9) The items has been added, then click the Advanced Setting go to VSS Setting section.

10) Tick on the VSS copy Backup and click Ok.
11) Click Next.
12) Tick on Local drives and click Next.

9

13) Click Next.

14) Click the Backup and wait for the scanning finish and after that you can click close.

15) Click Next.

10

16) Click the Backup and wait for the scanning finish and after that you can click close.

11

Patch Management.
Windows patch management is the process of managing patches for Windows, from scanning
for and detecting missing patches to downloading and deploying them. Using a patch
management solution, the entire Windows patch management process can be automated, so
you don't need to go around to every computer and manually check whether all missing
patches were identified and applied. Many Windows patch management tools also generate
reports for you to confirm whether Windows patches have been deployed properly using
Windows Server Update Security (WSUS).

Elements of a Good Patch Management Program
Several key practices or elements are recommended for any good patch management
program. These elements are mentioned in the sections that follow.

Configuration Management Program
A configuration management program should consider the following elements:
• The asset owner should maintain a current, functional software code library
containing the most recent, stable, deployed software versions used in the ICS (including
configuration files for switches, routers, file servers, database servers, and printers).
Controls should prevent unauthorized access or
changes to operational code.
• A current hardware inventory of all control systems equipment should be maintained
and made available to authorized personnel only. This inventory should be
cross-referenced to the software code library.
• A current network schematic map locating wiring, junction boxes, and connections
for data communications should be maintained.
• Configuration documentation including schematics and inventory lists should be
controlled to prevent public or casual access. Access, including update capabilities, should
be limited to authorized staff.

12

• An archive of at least one or more revisions of the older production code should be
maintained in a separate and secure location.
• An archive of the software library, hardware inventory, current configuration, and
schematics should be maintained on a separate server and in a separate physical location
than the production system.
• The policies and procedures related to the configuration management plan are
disseminated, reviewed, and updated on a periodic basis.
• It is recommended that a Configuration Control Board be used to monitor, authorize,
and control changes to the control systems configuration.
Backup/Archive Plan
The asset owner should maintain a current and functional backup/archive. This archive
should becreated and/or updated prior to any patching activities and provides a last,
“good” snapshot of the functional, production system. The plan should describe:
• The frequency of the backup
• The process and functional requirements of creating the archive
• The backup verification procedures
• The backup retention period
• The physical storage (location, duplication, etc.) requirements.

13

Steps for Microsoft Exchange Server Disaster Recovery.
 Open window update

 Click to change setting

14

 Click update automatically(recommended)
 Then click ok and the program will be installed.

15

 The window is install and restart

16

CONCLUSION
In this PBL, I know how to do the Disaster Recovery and Patch Management work in

windows server. Backup is the most fundamental DR technology thats been a part of Windows
Server since the beginning. Windows Server Backup can be used within a virtual machine
environment in the same manner that it is used on a physical server to provide backup and
recovery services. It can also be used from within a Windows Azure virtual machine for Bare
Metal Backup & Recovery, System State Backup & Recovery, File Folder Backup and recovery.

For the Patch Management, Microsoft Windows is the most widely-used OS, but
manually applying Windows updates to all endpoints in a network can be headache. What’s
more, deploying Feature Packs in particular can be tricky, as you have to download the
dependency files first and the deploy the Feature Pack. Patch Management software creates a
consistently configured environment that is secure against known vulnerabilities found in
Windows and your applications.

17

REFERENCE
1. Windows Server Backup
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2
-and-2012/jj614621(v=ws.11)
2. What is Windows Patch Management?.
https://www.manageengine.com/patch-management/windows-patch-management.html#:~:
text=Windows%20patch%20management%20strategies.,important%20or%20critical%20se
verity%20level.

18