Академический Документы
Профессиональный Документы
Культура Документы
January 2020
ii
DECLARATION
We hereby declare that this project report is based on our original work except for
citations and quotations which have been duly acknowledged. We also declare that it
has not been previously and concurrently submitted for any other degree or award at
Bahria University or other institutions.
Approved by,
Signature : _________________________
Date : _________________________
iv
The copyright of this report belongs to the author under the terms of the
copyright Ordinance 1962 as qualified by Intellectual Property Policy of Bahria
University. Due acknowledgement shall always be made of the use of any material
contained in, or derived from, this report.
ACKNOWLEDGEMENTS
We would like to thank everyone who had contributed to the successful completion
of this project. We would like to express my gratitude to my research supervisor,
Mr. MUHAMMAD AWAIS for his invaluable advice, guidance and his enormous
patience throughout the development of the research.
ABSTRACT
In today’s era, every organization whether it’s a company or a college wants to have
look on activities performed by employees/students on their respective computers.
To solve this problem, Desktop Monitoring System comes into picture, It allows to
continuously monitor every computer connected to the main computer which act as a
server. Through this, an administrator or a faculty can see concerned client’s
activities by taking continuous pictures (with a specific time interval) of the client
desktop and showing it on the administrator desktop and store those pictures as well.
In this project we have two applications one is for administrator where all the
screenshot of the connected client system is shown and stored, the other application
is for the client system which get the screenshot of that client system and send it to
the administrator application for monitoring.
vii
TABLE OF CONTENTS
DECLARATION ii
APPROVAL FOR SUBMISSION iii
ACKNOWLEDGEMENTS vi
ABSTRACT vii
TABLE OF CONTENTS viii
LIST OF TABLES x
LIST OF FIGURES xi
LIST OF SYMBOLS / ABBREVIATIONS xii
LIST OF APPENDICES xiii
CHAPTER
1 INTRODUCTION 1
1.1 Background 1
1.2 Problem Statements 1
1.3 Aims and Objectives 2
1.4 Scope of Project 3
2 LITERATURE REVIEW 4
2.1 Related work 4
2.2 Problem statement 4
2.3 Proposed System 5
2.3.1 Connectivity Figure 5
2.4 Remote monitoring 6
REFERENCES 10
APPENDICES 12
ix
LIST OF FIGURES
LIST OF APPENDICES
A Graphs 18
INTRODUCTION
1.1 Background
Initially, we are presented with desktop applications which provide only one to one
communication between server and client which means a server can monitor only
one desktop screen. In these applications, if you want to have one to many
connections between server and client, these applications don’t provide such
communication simultaneously. It means you can monitor only one desktop screen at
a time. At the same time, they don’t provide functionalities of monitoring desktops.
ii) To monitor all the connected client at the same time by taking picture of the
iii) To store those pictures on administrator system for future investigations and
without the knowledge of the clients/users and store those pictures of the client/users
activity on the administrator system with a specific time interval for future use.
3
CHAPTER 2
LITERATURE REVIEW
The system provides monitoring of client’s screen but uses embedded sensors for
providing the functionality of monitoring. But, in Remote Desktop Monitoring
System we are not using any type of sensors and it is purely based on the concept of
socket programming.
This system runs on a Java RMI mechanism in order to monitor the LAN
network which pings continuously to get list of running process on Remote Desktop.
But Remote Desktop Monitoring System will live monitor the desktop, so it becomes
easy to detect the client’s activities without actually getting present physically neat to
client..
This figure shows the connectivity of six clients to a server at a time through LAN.
Spacing between title of subsection and first line of text is 1.5 lines. The first
paragraph in a subsection should align with left margin. General alignment for texts
in paragraph should be “justified” [4].
Spacing between title of subsection and first line of text is 1.5 lines. The first
paragraph in a subsection should align with left margin. General alignment for texts
in paragraph should be “justified”.
6
A new paragraph should not begin on the last line of a page. A subsection
title should not begin on the last line of a page.
Spacing between title of subsection and first line of text is 1.5 lines. Spacing
between the last line of text and table is 1.5 lines.
Table 3.1: Processing Time (in hours) of Board for Different Machines
Machine
Board
1 2 3 4 5
A 30 18 26 17 15
B 23 22 32 25 30
C 17 31 24 22 29
Spacing between the table and first line of text is 3.0 lines. Spacing between
the last line of text and figure is 1.5 lines.
Spacing between the figure and first line of text is 3.0 lines. Subsequence
paragraphs should be indented 1.27 cm (0.5 inch) from the left margin.
CHAPTER 4
8
REFERENCES
[1] Harsh Mittal, Manoj Jain and Latha Banda, Harsh Mittal, Manoj Jain and Latha
Banda, “monitoring local area network using remote method invocation”, IJCSMC,
Vol. 2, Issue. 5, May 2013.
[2] Wang ping, wany Zheng, “IEEE, Design and Implementation of Open Computer
Lab Monitoring and Management system”.Computer and
modernization,IEEE.11.pp.125-128,2007.
9
APPENDICES
APPENDIX A: Graphs
Spacing between chapter title and first line of text is 4.5 lines. The first paragraph in
a subsection should align with left margin. General alignment for texts in paragraph
should be “justified”.
Spacing between chapter title and first line of text is 4.5 lines. The first paragraph in
a subsection should align with left margin. General alignment for texts in paragraph
should be “justified”.