Imlementing Devops Real world

The website lists all the important information about Imlementing Devops Real world

https://app.pluralsight.com/library/courses/implementing-devops-real-world/

Devops Courses- Day to day tasks

The website lists the Devops Courses- Day to day tasks. Very useful

https://www.pluralsight.com/courses/implementing-devops-real-world

DevOps

irstly, DevOps (development and operations) is an enterprise software development phrase used to mean a type of agile relationship between development and IT operations. Below is the handwritten pictorial representation. 

It is a set of practices that automates the processes between software development and IT teams, in order that we can build, test, and release software faster and more reliably. The benefits include increased trust, faster software releases, the ability to solve critical issues quickly, and better manage unplanned work.

Common Aspects of DevOps: 

(a)Automation:  Automated tasks help in faster development and deployment of software.

(b)Continuous Integration: Tools Like Jenkins can help to implement Continuous Integration in the organization. Some other Hosted products like Circle CI and Travis CI are completely hosted in the cloud and are becoming very useful for smaller organizations as it enables to make Continuous integration as fast as possible.  

It is like Plan-Code-Deploy-Test-Monitor. Below is the scanned image of handwritten pictorial representation.

Server Build Process

1.       We will receive the midrange request in email format from client.

2.      One Person from the team starts kick-off meeting.

3.       In the Kick off meeting, discussion will be about the current and new server environment

4.       Note: Before Kick-off meeting we need to take all necessary information by logging to the server. Check all the details such as roles, printers, features, OS Part.

5.       In Kick off meeting discuss about the missing/additional information.

6.       After kick off call prepare the technical solution document(TSD) according to the client requirement and share the document to the client/owner in order to confirm the document sign off.

7.       Once the sign on is approved by the owner, submit a normal change with 3 weeks’ time, and create the change task, to the respective team, such as back up, app-D, SCCM, AD.

8.       Once the change is approved, start the build in the following order:

i) Create a VM

ii) Deploy O.S

iii)Server Hardening

iv)Mcfee Installation

v)Manual Patching- Perform Windows Update and set the automatic updates to never.

vi) Hand over to AD team to join the server to domain

vii) Add ddnet1\tcs-windows, ddnet1\tcs-tools, ddnet1\tcs-backup-storage and dupontnet\ tcs-windows etc(Different in different organisations) to administrators group

viii) Perform Mcfee Licence key update by running the below commands in the Command prompt

Windows 2008 Servers: DISM /online /Set-Edition:ServerStandard /ProductKey:xxxx-GKW9T-YTKYR-xxxx-R7VHC /AcceptEula

Windows 2012 Servers: DISM /online /Set-Edition:ServerStandard /ProductKey:D2N9P-XXXX-2R39C-XXXX-MDVJX /AcceptEula

Once done reboot the server

viii) Set the local admin password to default one as per our standards

viii)Verify server checklist document

ix) After domain join and AD group additions and post completion of all the above steps hand over to back up team.

9.       Once the backup is configured,

a) Prepare the inventory

b) Update the CI Information, to DSOM & attach the DSOM template to the SOM request

10.   Prepare the server build checklist, and hand over the 3 attachments to the Refresh/New  build  Spoc

11.   Spoc will share the attachments , to the asset management team, in order to verify the inventory details and will seek the approval for monitoring and patching agents

12.   Once we get the approval “App Dynamics” and SCCM agent will be installed by the respective teams.

13.   Server build Owner will hand over the server to application team, and will be waiting for the cut over update or date from application team.

14.   Once the cut over date will be confirmed by application owner, build Team will submit the change for cut-over

15.   Once the cut-over is completed, update the information to asset management team in order to make necessary changes and ensure to maintain healthy inventory.

SRC(Service Request Calalogue) – Procedural Document in order Add User to Existing Group Instructions to Customers on Basic Ticketing tool Selection for appropriate routing of Approvals

Guide to Customers to Create SRC's- Groups And Shares Request Through Service Request Catalog In HP service Manager Ticketing tool

Please log onto the following link http://smsrcprod:8100/src/secure/main.jsp with your diebold_master credentials. Ensure that you are connected to VPN and VPN Certficate is not expired

Once you logged into Service Request catalog (SRC). Please click on Services tab à Browse catalog

1)      Please select IT Access Requests and Onboarding Services (ESOP)  à Groups and Shares.

1)      Please select the type of your request from the available list of services.

***END***

IT Help Desk Process Flow Explained Step by Step

The first step is to determine whether or not the device is broken. If it isn't, it's considered a request and usually, customers can figure it out themselves with self-help options, such as the FAQ database. If so, you don't even have to do anything.

If not, the team will create a ticket, which is added to the queue and someone will handle it when they have time.

If it is broken, it is an incident and a ticket is created by the customer technician. If the technician can fix the problem right then or can start working on it, they will do so and close the ticket.

If it isn't considered a priority, the team will wait and move to the higher-priority tickets first and then fix the problem.

Audit on Accounts to prevent security breach- Automising audit through powershell commands.

Currently working on creating scripts for 'Audit on Accounts to prevent security breach'- Automising audit through PowerShell commands.  Will Be updated soon...(Excel Vlookup is also used).. Soon will be published here

Fixing VSS Writers issue while taking Server backup in Windows

Troubleshooting VSS writers Issue-

In the Command Prompt  type:  "vssadmin list writers"  and hit enter, If see any report in Failed or Error state, try restarting their corresponding service

For example in the below screenshot  ASR Writer is in “Waiting for  Completion” state, due to which back ups normally fail.

To resolve the above issue, we should restart the “Volume Shadow Copy” service in services.msc logging in to the corresponding server, which is shown in the below screenshot.

After restarting this service, thee state becomes stable as shown below.

 

Below are the common VSS writers and their respective corresponding service – Restart these corresponding  services from “services.msc”

VSS Writer	Service Name	Service Display Name
ASR Writer	VSS	Volume Shadow Copy
BITS Writer	BITS	Background Intelligent Transfer Service
COM+ REGDB Writer	VSS	Volume Shadow Copy
DFS Replication service writer	DFSR	DFS Replication
DHCP Jet Writer	DHCPServer	DHCP Server
FRS Writer	NtFrs	File Replication
FSRM writer	srmsvc	File Server Resource Manager
IIS Config Writer	AppHostSvc	Application Host Helper Service
IIS Metabase Writer	IISADMIN	IIS Admin Service
Microsoft Exchange Writer	MSExchangeIS	Microsoft Exchange Information Store
Microsoft Hyper-V VSS Writer	vmms	Hyper-V Virtual Machine Management
NTDS	NTDS	Active Directory Domain Services
OSearch VSS Writer	OSearch	Office SharePoint Server Search
OSearch14 VSS Writer	OSearch14	SharePoint Server Search 14
Registry Writer	VSS	Volume Shadow Copy
Shadow Copy Optimization Writer	VSS	Volume Shadow Copy
SPSearch VSS Writer	SPSearch	Windows SharePoint Services Search
SPSearch4 VSS Writer	SPSearch4	SharePoint Foundation Search V4
SqlServerWriter	SQLWriter	SQL Server VSS Writer
System Writer	CryptSvc	Cryptographic Services
TermServLicensing	TermServLicensing	Remote Desktop Licensing
WMI Writer	Winmgmt	Windows Management Instrumentation

After restarting the corresponding service, again type "vssadmin list writers"  in the command prompt and hit enter,now “stable” and “no error” message is displayed beside the corresponding writer as shown in the below screenshot and thus the issue gets resolved.

ITIL Service Desk Process Internal Exam Cleared

Inspiring Quote

A dream doesn't become reality through magic; it takes sweat, determination and hard work