Month: December 2019

Posted in AWS, Linux, Windows

AMAZON EC2

Posted on by Akhil

Amazon elastic cloud computing is used to create cloud virtual instances and many other operations related to the servers like backup, security, maintaining and monitoring the servers. This can be configured both in console and also aws-cli.

AWS – CONSOLE

  • Sign in to the console using log on credentials and access ec2 under services.
  • ec2 > Instances > Launch instance > select the desired ami image and follow on screen commands to launch an instance.
  • ec2 > Instances > Actions > Instance state > Terminate // To terminate the instances.
  • ec2 > Instances > Launch Instances > look after the predefined or self created ami images.

AWS – CLI

  • aws configure > sign in using access key ID and secret access key ID.
  • aws ec2 run-instances --image-id ********* --count 1 --instance-type t2.micro --key-name **** --security-group-id **** // To launch an instance.
  • aws ec2 describe-instances --instance-id **** // To check the status and details of the instance.
  • aws ec2 terminate-instances --instance-ids **** // To terminate the instance and results as shown.
  • aws ec2 describe-images --owners self amazon --filters "Name=platform,Values=Windows // To search for a numerous amount of windows platformed ami images.

Upcoming..

More comparisons between aws-cli and aws console environment.

Posted in AWS, LAMP Stack, Linux, Windows

CREATING MY AIMs IN AWS

Posted on by Akhil

A fantasy or even might be a necessity in some cases to have our own created AMIs. The use of different resources in EC2 in AWS allows an individual to reach their desired targets. An individual can create a clown image of a server in two different ways.

  • An instance of Ubuntu 18.04 is created for a reference in the following practical.
  • An Apache server and also a database with some data were installed and created for the cross verification purpose.

Method One :

  • Select the instance that needed to be clowned > Actions > Image > Create image. // As shown below.
  • The clowned image can be seen in the My AIMs, while launching an instance.
  • Launch the number of instances using the created AIM and connect to any of the instance created.
  • Compare to the original instance // If needed.

Method Two :

  • EC2 > Volumes (Elastic Block Store) > Select the volume > Actions > Create Snapshot as shown below.
  • Created snapshots can be seen in the EC2 > snapshots (Elastic Block Store).
  • Select the desired snapshot > Actions > Create image.
  • The clowned image can be seen in the My AIMs, while launching an instance or in EC2 > AMIs (Images).
  • Launch the number of instances using the created AIM and connect to any of the instance created.
  • Compare to the original instance // If needed.

Posted in Active Directory, AWS, Patch Management, Windows

CONFIGURATION OF WSUS

Posted on by Akhil
  • After confirming with the desired language continue to select the products and the updates that are required for the servers to which the process of patch management should be done.
  • Option of synchronization is up to individual.
  • Begin with the initial synchronization as shown below.
  • Which results in a pop-up of the WSUS Console.
  • All the updates that are obtained once after the server gets in contact with the Microsoft cop. can be seen in this console.
  • Console > Updates > All Updates // Make sure the option (Unapproved and any) to be turned on as shown below.
  • As it is shown that these updates needed to be approved, select all the updates that are visible in the console and right click to approve them which will lead to a confirmation pop-up window as shown.
  • Right click on the group or the computers to which the patch management need to be done and approve for the installation.

Group policy management

Once the updates were approved by the PMS server, to push the desired updates to the client servers one need to update their group policy. This can be done in the Group Policy Management.

  • Windows Start > Server Manager > Tools > Group policy management // In the PMS server.
  • Create a GPO in this domain and Link it here.. by right clicking on the domain to which the patches need to be pushed.
  • Right click on the created group policy to edit which results in Group policy management editor.
  • Expand Computer configurations > Policies > Administrative Templates > Windows Components > Windows Updates.
  • Double click Configure Automatic Updates and set it to Enabled.
  • One has a freedom of selecting an option of how to configure the updates as shown below.
  • Click on Apply and then OK.
  • Double click Specify Intranet Microsoft Update Service Location and set it to Enabled.
  • Specify the intranet statistics server below in the format [http:Servername:8530] as shown.
  • Click on Apply and OK.
  • Proceed to the client server’s command prompt and force the server to update the group policy as shown below and wait for the servers to get appeared in the WSUS console under unassigned computers.

THE BLOG WILL BE CONTINUED

Posted in Active Directory, AWS, Patch Management, Windows

WINDOWS UPDATE CATEGORIES

Posted on by Akhil

There are various kinds of updates that are provided by Microsoft corporation. Few of them were listed below.

  • Critical Updates
  • Security Updates
  • Definition Updates
  • Update Rollup
  • Service pack
  • Tool
  • Feature pack
  • Update

Critical Updates are updates which fixes specific, non-security related, critical bug. That bug can cause for example serious execution degradation, interoperability malfunction or disturb application compatibility.

Security Updates are one of the important type of updates which makes the the complete corporation to be safe against the world of hackers.

WSUS (Windows Server Update Services)

The concept of patch management is one of the significant service that a firm need to run periodically to update themselves and be strong in every single viewpoint. WSUS is a service developed by the Microsoft, which helps in managing and distribution of the patches to multiple servers from the main server. In the point of practicality a server (Windows 2019) is launched as an instance in AWS and connected remotely

A new role Windows server update services and its features were added to the server accordingly and installed.

  • Windows start > Server manager > Add roles and features //follow the default options on the screen to add a role windows server update service and install the corresponding role.
  • Before configuring the role, Launch the post installation tasks (from the notification bar as shown below).
  • Server manager > Tools > Windows server update service > Create a folder name WSUS in the drive and mention the desired file location and click Run. \\ A dialogue box for the file confirmation appears on the screen as shown.
  • Click close to launch WSUS console.
  • Follow the on screen commands to configure the WSUS.
  • As it is the main server to which the the updates needed to be synchronized from the Microsoft, select the option of synchronize from Microsoft Update as shown.
  • Use the proxy details if needed or else continue further to start connecting with the Microsoft for updating with the details of our server.
  • Select the desired language and click Finish.

Patience is the key for success

Patience is the other important role and feature that needed to be added for success to be followed in this configuration.

CLICK TO CONTINUE THE BLOG