PayU Payments Private Limited,

7th Floor, Pearl Tower, Plot No 51

Institutional Area, Sector 32,
Gurgaon: 122001

Summer Internship Report

Date: 21st August 2014

MOHIT SHAKYA
B.TECH 3RD YEAR
Computer Science and Engineering
12-CSE-17
SGTIET

Executive Summary
My 5 weeks Industrial Internship Program work term was with the Payu India. I was involved in the
area of IT - Support during my work term, all of which will be outlined in this report. This report will
cover some background information on the projects I was involved in, as well as details on how the
projects were developed.
There are two major projects that I had a significant role in.
The first project involved gaining a good understanding of an windows deployment services. My task
was to study its capabilities from the point of view of a multiple installations of Windows OS on
Machines.
My task was to
Understand the Technology
How to implement it on different hardware Systems.
Create a Server for the use of IT Support Team.
One of the important achievements of this project was that
It can handle more than 10-15 Systems at a time.
Allows the installation of different versions of windows OS at the same time.
It also has capabilities to add drivers directly to WIM (Windows Imaging
Format).
A Server was finally created for the testing purposes. It was a prototype solution for installation of OS
on machines and needed some more work to Function without any glitches.
The second project was on extraction of data from hardware like motherboard and bios chips. In this
project we worked on some issues as there was no official software provided by vendors (Dell, HP
etc.).Then I got introduced to the area of research and how to approach it. Most importantly, the work
experience was very good which included good fellowship, cooperative teamwork and accepting
responsibilities. Although I spent a lot of time learning new things, I found that I was well trained in
certain areas that helped me substantially in my projects. Many programming skills that I used in my
projects, such as programming style and design, were ones that I had acquired during my studies in
Computing Science.
This report concludes with my overall impressions of my work experience as well as my opinion of
the Industrial Internship Program in general.

TABLE OF CONTENTS
1. ACKNOWLEDGEMENTS.
2. INTRODUCTION AND OVERVIEW.
3. PAYU INDIA BACKGROUND INFORMATION.
4. INTRODUCTION.
5. NEED FOR IT SUPPORT.
6. PROJECT OVERVIEW.
7. PART-I: WDS (WINDOWS DEPLOYMENT SERCVICES).
8. PART-II: DATA EXTRACTION FROM MOTHERBOARDS AND BIOS.
9. PROJECT I: WDS (WINDOWS DEPLOYMENT SERVICES).
10. PROJECT BACKGROUND AND SCOPE.
11. PROJECTS RATIONALE AND GOALS.
12. TECHNICAL DETAILS AND APPLICABLE ISSUES.
13. INSTALLING WDS.
14. UNDERSTANDING WDS.
15. OVERVIEW OF THE ARCHITECTURE OF WDS.
16. FEATURES OF CONTENT WDS BRIEF SUMMARY.
17. SUMMARY.
18. PROJECT II: DATA EXTRACTION FROM MOTHERBOARD AND BIOS.

19. PROJECT BACKGROUND AND SCOPE.

20. TECHNICAL DETAILS AND APPLICABLE ISSUES.
21. EXTRACTING PREINSTALLED WINDOWS KEY.
22. SUMMARY.
23. LEARNING FROM THE INTERNSHIP PROGRAM .
24. APPLYING MY UNIVERSITY SKILLS.
25. REFRENCES.

Acknowledgements
During my summer internship, the staffs at Payu India and persons guiding
me were very helpful and extended their valuable guidance and help
whenever required for the projects which I worked on.
I am very thankful to my guide Mr. Gaurav Verma (System Engineer) for
his invaluable guidance and advice during my Summer Internship.
I am thankful to Vinay for his guidance and friendly support during my stay
at Payu.
I am also very grateful to Vinod Negi ( for great cooperation and help esp.
in the 2nd project and my final presentation ), Ajay Gupta ( for helping in my
final presentation, in developing the WDS and Data Extraction.
Neeraj Kaushik (who was always ready to extend any technical support at a
short notice ).
I also thank Mr. Dinesh Aggarwal who helped us in the 2nd project on Data
Extraction from Motherboard and Bios chips by sharing his vast experience
and giving valuable direction to the project.
Overall, the above team made my stay at Payu India an enjoyable one and I
am grateful to them for making it so.

Introduction and Overview

Payu India Background Information
As an innovator in the online payment market, PayU set out to streamline the
online purchase process. SafeNet Key Secure helps PayU India deliver
convenient online payment services, while optimizing data and transaction
security.

Introduction
PayU India is the flagship company of the PayU group, a leading online
payment solutions provider with a presence in 16 countries. The PayU group
is a subsidiary of the Naspers Group (JSE: NPN), which is a 25 billion USD
media and Internet company. PayU entered India in October 2011, and has
quickly emerged as a leading consumer payment processor, serving more
than 1000 merchants.

Need for IT Support

In the most basic terms, there is nothing in the world so utterly useless and so
utterly frustrating as a computer or network system that doesn't work.
Computer or network downtime leads to increased overhead costs, lost
productivity, lost customer satisfaction and sometimes even lost revenues.
This is especially true for business entities that are dependent upon
Information Technology and is often exacerbated for many small and
medium sized businesses (SMBs). SMB owners and managers often find
that IT problems take them away from their profit making operations
and significantly increase stress and anxiety levels because many SMBs do
not have adequate IT staff.
Professional, reliable, effective and efficient Technical Support Services are
the foundation of a well-running computer or network system and lead to
increased productivity, reduced costs and improved profitability.
Technical Support or tech support refers to a plethora of services by which
enterprises provide assistance to users of technology products such as mobile
phones, televisions , computers, software products or other electronic or
mechanical goods. In general, technical support services attempt to help the

user solve specific problems with a productrather than providing training,

customization, or other support services. Most companies offer technical
support for the products they sell, either freely available or for a fee.
Technical support may be delivered over the telephone or online by email, live support software on a website or a tool where users can log a
call/incident. Larger organizations frequently have internal technical support
available to their staff for computer related problems. The internet is also a
good source for freely available tech support, where experienced users may
provide advice and assistance with problems. In addition, some fee-based
service companies charge for premium technical support services.

Project Overview
Part-I: WDS (Windows Deployment Service)
This part of the project involved gaining a good understanding of an WDS.
My task was to study its capabilities from the point of view of a large scale
installation solution in the IT - Support. My task was to
Understand the Technology
How to implement it on different hardware Systems.
Create a Server for the use of IT Support Team.

One of the important achievements of this project was that

It can handle more than 10-15 Systems at a time.
Allows the installation of different versions of windows OS at the
same time.
It also has capabilities to add drivers directly to WIM (Windows
Imaging Format).

Part-II: Data Extraction from Motherboards and Bios chips.

The second project was on extraction of data from hardware like
motherboard and bios chips. In this project we worked on some issues as
there was no official software provided by vendors (Dell, HP etc.).
Pre-installed software (also known as bundled software or crapware is
the software already02121installed and licensed on a computer or
Smartphone bought from an original equipment manufacturer (OEM).

Project - I: WDS (Windows Deployment Service)

Project Background and Scope

Windows Deployment Services is a server technology from Microsoft for
network-based installation of Windows operating systems. It is the successor
to Remote Installation Services. WDS is intended to be used for remotely
deploying Windows Vista, Windows 7, Windows 8, Windows Server 2008,
and Windows Server 2012, but also supports other operating systems
because unlike its predecessor RIS, which was a method of automating the
installation process, WDS uses disk imaging, in particular the Windows
Imaging Format (WIM). WDS is included as a Server Role in all 32-bit and
64-bit versions of Windows Server 2008, and is included as an optionally
installable component with Windows Server 2003 Service Pack 2.

Project's Rationale and Goals

My goals regarding Content Manager were the following:
1. To Install the WDS (Windows Deployment Service)
2. To understand the WDS and its proper configuration and settings
3. To understand its WDS technology and how to develop a WIM on top of
it.
4. To develop a WIM on top of the WDS this adds functionality to WDS as
per the requirements of machine.

Technical Details and Applicable Issues

Installing the WDS
Windows Deployment Services is a technology from Microsoft for networkbased installation of Windows operating systems. In windows server 2003 it
was called as Remote Installation Services (RIS). The purpose of WDS is to
remotely deploy the windows operating systems; Windows Deployment
Services role in server 2008 R2 enables you to efficiently deploy Windows
operating systems, particularly Windows 7, Windows Vista and Windows
Server 2008 R2. Windows Deployment Services role can be used to set up
new computers through a network-based installation without the IT
Professional having to be physically present at each computer and without
having to install directly from CD or DVD media.

Lab Setup
Setup 2 virtual machines, the first virtual machine is installed with Windows
Server 2008 R2 Enterprise SP1 OS and its our domain controller. The
second virtual machine is installed with Windows Server 2008 R2 Enterprise
SP1 OS and its our WDS server. The DHCP server role has been installed
on the domain controller, this DHCP service will provide IP addresses to the
other machines.
1. On the server where you are installing Windows Deployment Services
role, launch the Server Manager, right click on Roles, and click on Add
Roles. On the Server Roles page, select Windows Deployment Services.
Click on Next.

2. On the Role Services page, the Deployment Server and Transport

Server roles are checked by default. Click on Next.

3. Once the installation is complete click on close.

4. If you are looking for command line installation of WDS server, then use
the below command.
Open the powershell and run the command ServerManagerCmd -install
WDS.

5. Click on Start, click on Administrative Tools, click on Windows

Deployment Services. On theWDS console, expand Servers, right click
on the WDS server and click on Configure Server.

6. Read the requirements once before you click next.

7. Choose the Remote Installation Folder location on other drive. The folder
contains the boot images, install images, so make sure this drive has
enough space to hold the data. Click on Next.

8. Select Respond to all client computers (known and unknown). Click

on Next.

9. Uncheck the checkbox for Add images to the server now. We will add
the images in the next step. Click Finish.

10. In this step we will add Boot Image and Install Image. Boot images are
images that you boot a client computer into to perform an operating
system installation. To add the boot image, right click Boot Images and
click on Add Boot Image.

11. Browse to the location where the operating system installation files are
stored. In this example we will importing boot.wim from windows 7
professional SP1 64 bit DVD as boot image. The boot.wim file can be
found under folder named Sources. Select boot.wim and click on Open.

12. Enter the name for the boot image. Click on Next.

13. We have imported or added a boot image to our WDS server. Click
on Finish.

14. The boot image can be seen under Boot Images folder.

15. To add the Install image, right click Install Image, click on Add Install
Image, provide a name and create a new Image Group. Click on Next.

16. Now we have to select and add the Install image. Install images are the
operating system images that you deploy to the client computer. Click
on Browse and the select Install.wim. Click on Open.

17. In the below screenshot we will select all the editions of windows 7 that
are listed. click on Next.

18. Click on Finish to close the Add Image Wizard.

19. Lets configure the WDS server properties now. Launch the Windows
Deployment Services Console, right click the WDS server and click
on Properties. Click on Boot and make sureRequire the user to press the
F12 key to continue the PXE boot is selected for known and unknown
clients.

20. Click on PXE Response and make sure that Respond to all client
computers (known and unknown) is selected. Click on Apply and Okay.

Understanding WDS
Automated image capture and apply
WDS functions in conjunction with the Preboot Execution Environment (PXE) to
load a miniature version of Windows known as Windows PE for installation and
maintenance tasks. WDS functions as both a storage repository for the PXE
network boot images as well as a repository for the actual operating system images
to be installed on the target computer.
When multiple boot images are available, PXE booting via WDS will present the
end-user with a boot menu to select the image to load.

Windows PE automation using WAIK

To simplify the tasks of capturing and applying images, two special scripted
Windows PE boot images can be created which automate these tasks. These
scripted Windows PE boot images are created using the Windows Automated
Installation Kit, in combination with Windows 7 installation media containing the
source WIM images, and then added to the WDS server's boot image repository.
The Windows PE boot images may be either 32- or 64-bit, but 32-bit tends to be
more universally compatible across all potential hardware types.
A difficulty of Windows PE booting is that it needs to include network drivers and
disk controller drivers intended to work with the target hardware to be imaged. The
process of adding drivers to the Windows PE boot image can be automated using
the WDS server console:
Select the source WIM image, which may be either a new one created from
original Windows 7 installation DVDs (32- or 64-bit), or a previously configured
WIM.
Select the drivers to install into the WIM
WDS mounts the WIM to a virtual path, adds drivers to the virtual path, and
generates a new WIM
The updated WIM image is added to the boot image section of the WDS repository
This process can be repeated at a later time when a new system type needs to be
captured but the current Windows PE Capture boot image does not include
network drivers for it. The boot image is updated with the additional drivers using

the WDS interface and automatically re-added to the WDS boot image collection
to replace the original.
For specialty one-off systems this WIM driver update process is not necessary if
the hard drive of the target system to be captured is removed from the source
system after sysprepping, and is either installed in a computer with supported
network drivers, or attached to the supported system using an external "USB to
hard drive" adapter.

Automated apply process

Applying a captured image involves running a second Windows PE "Apply" boot
image on the target system to receive the image. This boot image also needs the
appropriate network and disk controller drivers as with the Windows PE Capture
boot image.
The system is booted using PXE network booting and the Windows PE Apply
image is loaded.
The operator logs on to the domain, and selects the boot image to apply.
A disk partitioning screen appears and the location for the target image is selected.
If the target storage is unformatted, a default partition set is created. For Vista and
Windows 7, a small 100 megabyte boot partition is created for storing bootloader
data separate from the rest of the system partition. This boot partition is normally
hidden from the Windows Vista/7 user.
The image data is applied to the selected partition, and the system reboots, either
running the Sysprep manual mini-setup process or following the script created
during the initial Sysprepping.
The WDS image creator may optionally select a separate WAIK / Sysprep
installation script to be applied to the image during the first boot. This alternate
script is selected within WDS by viewing the properties of each uploaded system
image.

WDS automation and dual-boot systems

WDS automated capture and apply do not directly support dual-boot operating
systems. Only one operating system at a time can be captured and deployed, and
the automated capture process only deals with single partitions containing a
sysprepped Windows OS installation. It will not capture data-only partitions.

However, WDS automated capture and apply can be used to duplicate and create
dual-boot systems, if each OS is captured and applied separately. Generally,
Windows XP and older operating systems need to be applied to the target system
before Vista or Windows 7, due to the different boot loaders used by the newer
operating systems.

Manual image capture and deploy

It is technically possible to create scripts that manually perform the imaging,
capture, and apply processes, using command line tools provided by Microsoft.
However, the methods for doing this are complex and difficult.

In general, the tools involved are:

dism - Deployment Image Servicing and Management, used to add drivers to
Windows PE boot images.

imagex - used to capture and apply images. Creates either a single WIM
structure, or can reduplicate data using a second shared resource WIM. Does not
require a Windows Deployment Server to capture or apply images, and can work
solely with a logged-on network share or mapped drive letter.

wdsutil - used to manage the WDS server without the graphical user interface,
and to add captured images to the repository.
Using imagex to manually create a WIM does not require the source operating
system to be sysprepped or for the source partition to contain a Windows operating
system. Any type of Windows-accessible file system can be imaged, including
MSDOS, but the source system either needs to be able to run Windows PE or the
source system's hard drive is moved into a newer system that supports Windows
PE.
Microsoft generally requires Windows 2000, XP, Vista, and Windows 7 to be
sysprepped before imaging, due to certain security-related disk data that Microsoft
requires to be unique across duplicated system images. Sysprep randomizes this
data when the image is applied to a new system.

Imagex does not have any disk formatting and partitioning capabilities. Separate
Windows command line tools such as diskpart are needed to define partitions on
the target system for imagex to use.

Overview of the Architecture of WDS (Windows Deployment

Services)

Features of WDS Brief Summary

1. Allows network-based installation of Windows operating systems, which
reduces the complexity and cost when compared to manual installations.
2. Supports deploying images for mixed environments including Windows 7and
Windows Server 2008 R2 through Windows 8.1and Windows Server 2012 R2.
3. Uses standard Windows Setup technologies including Windows Preinstallation
Environment (Windows PE), .wim files, and image-based setup.
4. Transmits data and images by using multicast functionality.
5. Allows you to create images of a reference computer using the Image Capture
Wizard, which is an alternative to the ImageX tool.
6. Allows you to add driver packages to the server and configure them to be
deployed to client computers along with the install image.

Summary
WDS is a good solution for managing large no. installation at the same time.
It has a distributed architecture and provides many features.
In the above project, a new WDS Server was developed over the Virtual
Machine to provide simplicity and extensibility catering to requirements of
IT - Support. Using the above WDS, a Server was created which provided a
prototype solution for a real life problem.

Project II: Data Extraction from Motherboards and Bios chips.

Project Background and Scope
RW- Everything utility can access almost all the computer hardware,
including PCI (PCI Express), PCI Index/Data, Memory, Memory
Index/Data, I/O Space, I/O Index/Data, Super I/O, Clock Generator, DIMM
SPD, SMBus Device, CPU MSR Registers, ATA/ATAPI Identify Data,
Disk Read Write, ACPI Tables Dump (include AML decode), Embedded
Controller, USB Information, SMBIOS Structures, PCI Option ROMs, MP
Configuration Table, E820, EDID and Remote Access. And also a
Command Window is provided to access hardware manually.
Powerful utility for hardware engineers, firmware (BIOS) engineers, driver
developers, QA engineers, performance test engineers, diagnostic engineers,
etc.

Supported Hardware
All system can be used, for Super I/O and SMBus function, check below list.

Super I/O device

Winbond
1. W83627HF/F
2. W83627SF
3. W83627THF
4. W83637HF
5. W83697HF
6. W83697SF
7. W83697UF
8. W83977ATF
9. W83977EF
10. W83L517D
11. W83L518D
12. W83L519D
13. W83627EHF/EHG
14. W83L517G

15. W83627UHG
16. W83667HG
17. W83667HG-A
18. W83627DHG

ITE
1. IT8700F
2. IT8702F
3. IT8705F
4. IT8710F
5. IT8711F
6. IT8712F
7. IT8761E
8. IT8716F
9. IT8726F
10. IT8510E
11. IT8511E
12. IT8512E

SMSC
1.
2.
3.
4.
5.
6.
7.

LPC47S42x
LPC47M15x/LPC47M192
LPC47B272
LPC47M10x/LPC47M112
LPC47M14x
LPC47M172
LPC47M182
8. SCH5017

FinTek
1.
2.
3.
4.

F71872
F71805F/FG
F71862
F71882/F71883

Nuvoton
1.
2.
3.
4.
5.
6.

NCT5573D
NCT5577D
NCT6771D
NCT6772D
NCT6775D
NCT6776D

SMBus Controller

Intel
1.
2.
3.
4.
5.
6.
7.
8.
9.

SiS
1.
2.
3.
4.
5.
6.

ICH4
ICH5
ICH6
ICH7
ICH8
ICH9
ICH10
SCH
PCH
SiS962
SiS963
SiS964
SiS965
SiS966
SiS968

VIA
1.
2.
3.
4.

VT8235
VT8237
VT8237A
VT8251

ULi
1.
2.
3.
4.

M1563
M1573
M1575
M1689

ATI
1. SB400
2. SB600
3. SB700

nVidia
1. MCP2
2. nForce3 (CK8S)
3. MCP51
4. MCP55
5. MCP61
6. MCP65
7. MCP67
8. MCP68
9. CK804
10.
MCP72
11.
MCP73
12.
MCP77
13.
MCP78

Technical Details and Applicable Issues

Extracting preinstalled Windows Key
1. Open Rw everything.

2. For preinstalled Windows Key find MSDN Tab

List of Different Tables in Bios and Motherboard

1. RSDP
2. XSDT

3. RSDT
4. FACP
5. APIC
6. FPDT
7. ECDT
8. MCFG
9. HPET
10.
SSDT
11.
MSDM
12.
RACS
13.
DSDT

Summary
A detailed review of the existing state of art has been carried
out for Rw Everything various hardware. A intuitive
architecture and logical placement of the data has been
proposed which optimizes across maximum number of
benchmark issues.

Learning From the Internship Program

The Internship program was quite beneficial for me. It
helped me in improving my various technical skills and
enhanced my knowledge in new areas.

 I gained new knowledge in the area of Windows Server

technologies and Data Extraction, the various issues
involved mechanisms in these systems etc.
By studying WDS, I also learnt that how Windows
Services are useful and what are the various issues one
need to be aware of while using a windows Server.
WDS is new technology which has replaced Remote
installation.
I was working on a research topic for the first time and I
got introduced to this important area of research and
methods employed in conducting research.
I brushed up my knowledge of Windows Server and Data
Extraction, as it was required to perform the work.

Work Experience
My internship was quite satisfactory in terms of work
environment. The team I worked with was very friendly and
helped me a lot in all my problems. New experiences
include
Teamwork
In these projects 4-5 people worked together thus providing
enough opportunity for proper teamwork and coordination.
This was a good experience for me as the team was very
cooperative and understanding.
Responsibility and keeping commitments
The importance of honoring commitments and time of others
was an important thing, which I learnt as a summer Intern.
Especially, while working as a team it is very important to
keep these points in mind.

Applying My University Skills

My education at SGT was very helpful in my Internship. The
programming skills which I developed in SGT were very
helpful in developing the WDS and the Data Extraction. The
courses were especially helpful in this regard.
Course on File Systems was also very helpful as it covered
some database concepts which were required in
understanding WDS and the database concepts in the
second project as well.
Technical communications proved to be very helpful in my
final presentation and the various documents which I had to
write during my Internship. I applied the principles learnt in
the course in my final presentation which was well
appreciated by colleagues.

References
1. IT Support Team Payu India.
2. Internet Research.
3. Testing on machines.
4. University Skills.