CHAPTER-1

COMPANY PROFILE

1.1 HISTORY OF HINDALCO:

Hindalco was set up in collaboration with Kaiser Aluminium and Chemicals Collaboration,
USA, in a record time of 18 months. The plant started its commercial production in the year
1962 with a capacity of 20,000 tones per annum.

The company is managed by Board of Directors, with Shri Kumar Mangalam Birla as the
chairman of the Board of Directors. Day to day affairs of the company is managed by a team
of professionals Executives headed by Shri Ratan Shah as the Director (Whole Time).

1.2 HINDALCO BUSINESS

Fig 1.1: Hindalco’s Integrated Aluminium Complex at Renukoot

Hindalco in India enjoys a leadership position in aluminium and copper. The Company's
aluminium units across the country encompass the entire gamut of operations from bauxite
mining, alumina refining, aluminium smelting to downstream rolling, extrusions, foils and
alloy wheels, along with captive
power plants and coal mines. The Birla Copper unit produces copper cathodes, continuous
cast copper rods along with other by-products, including gold, silver and DAP fertilisers.
All of Hindalco's units are ISO 9001:2000, ISO 14001:2004 and OHSAS 18001 certified.
Several units have gone a step further with an Integrated Management System (IMS),
combining ISO 9001, ISO 14001 and OHSAS 18001 into one Business Excellence Model.
The company has been accorded the Star Trading House status in India. Its aluminium metal
is accepted for delivery under the High Grade Aluminium Contract on the LME (London
Metal Exchange), while its copper quality standards are also internationally recognised and
registered on the LME with
Grade “A” accreditation.

1
 In Aluminum Market:

1. World's largest aluminium rolling company:

2. One of the biggest products of primary aluminium in Asia.
3. Market share of 48 per cent.
4. One of the lowest-cost producers of aluminium in the world.
5. Over 58 per cent of sales in value-added products.
6. Fully integrated aluminium plant at Renukoot, UP.
7. Aluminium wheels plant at Silvassa, in Dadra & Nagar Haveli.
8. .Foil plants at Silvassa and Kalwa.
9. Foil unit of Indal at Kollur.
10. Alumina refining capacity of 1,160,000 TPA going up to 1,500,000 TPA.
11. Aluminum metal producing capacity of 445,000 TPA.
12. Captive power generation of 1087.2 mw.

1.3 WEB TECHNOLOGY

J2EE, Cold Fusion, ASP, Java (JSP, Servelet, EJB & Applet), JavaScript, PHP, XML,
VoiceXML, WAP.

Web Servers
· All popular web servers.

Database
· Sql server, MS SQL & Access, Cache.

1.4 JOINT VENTURE COMPANIES OF HINDALCO:

Indo-Gulf fertilizers and chemicals Corp. Ltd.
Bihar Caustic and Chemicals Ltd.
Tanbac Industries Ltd.
Mangalore Refinery and Petrochemicals Ltd.
Birla AT&T and Tata Companies Ltd-BPL
Bina Power Supply Co.Ltd.
Birla Global Finance Ltd.
Birla Capital International AMC Ltd.
Century Enka
Indal Ltd.

2
1.5 POSITION OF ADITYA BIRLA GROUP:

(1) Largest producer of Viscose Staple Fiber with 20% global market share.
(2) Third largest manufacturer of Insulators.
(3) Fifth largest producer of Carbon Black.
(4)India’s largest integrated aluminum producer and among the world’s lowest cost
producers.
(5) Apparel/Garments- India’s premium branded apparel brand includes Louis Phillipe, Van
Hausan, Byford, Peter England & San Frisco.
(6) The group also has a significant presence in the Financial Sector, Power and
Telecommunications Sector in tie ups with giants like Birla Sun life Insurance (Canada),
Powergen Ltd. (U.K.) and AT&T (USA), Idea Cellular Limited.

1.6 HINDALCO- LOCATION

Location of Renukoot:

Lying in the foothills of the Vindhya Range, Renukoot is about 160 km From Varanasi, and
260 km from Allahabad. It is well connected to these cities by beautiful metalled rods
passing through green forests.

Phone: (05446) 252077/8/9

Fax: (05446) 0252107
E- mail: hindalco.rkt@ adityabirla.com
For Online Information about the group, please visit our group’s website:
1.www.adityabirla.com
2.www.adityadisha.com

3
 CHAPTER-2
DOMAIN CONTROLLER

2.1 INTRODUCTION
On Windows Server Systems, a domain controller (DC) is a server that responds to security
authentication requests (logging in, checking permissions, etc.) within the Windows Server
domain.
In Windows NT, one domain controller per domain was configured as the Primary Domain
Controller (PDC); all other domain controllers were Backup Domain Controllers (BDC). A
BDC could authenticate the users in a domain, but all updates to the domain (new users,
changed passwords, group membership, etc) could only be made via the PDC, which would
then propagate these changes to all BDCs in the domain. If the PDC was unavailable (or
unable to communicate with the user requesting the change), the update would fail. If the
PDC was permanently unavailable (e.g. if the machine failed), an existing BDC could be
promoted to PDC. Because of the critical nature of the PDC, best practices dictated that the
PDC should be dedicated solely to domain services, and not used for file/print/application
services that could slow down or crash the system. Some network administrators took the
additional step of having a dedicated BDC online for the express purpose of being available
for promotion if the PDC failed.
Windows 2000 and later introduced Active Directory ("AD"), which largely eliminated the
concept of primary and backup domain controllers in favor of multi-master replication.
However, there are still a number of roles that only one domain controller can perform, called
the "Flexible Single Master Operation" roles (some of these roles must be filled by one DC
per domain, while others only require one DC per AD Forest). If the server performing one of
these roles is lost the domain can still function, and if the server will not be available again,
an administrator can designate an alternate DC to assume the role (a process known as
"seizing" the role). This is a procedure used at some schools and buisnesses.

Fig2.1:Domain Controller
2.2 SCOPE:
The scope of the project is to implement the Domain controller and Additional Domain
Controller. The Domain Controller would be used to implement the Desktops level security
through Group Policy objects centrally. This system will help us to manage the Password
Policy, Screen Saver lockout policy, Time Synchronization at desktop levels. The system will
also utilize to authenticate user at Domain Level.

4
2.2.1 PROJECT CATEGORY:
Implementation of Desktop level security through group policy.
2.2.2 PROJECT OBJECTIVE:
User level authentication and Implementation of Information Security Policy centrally.
2.3 SCHEDULE
Refer / attach/ embed project schedule.

2.4 TOOLS AND METHODS:

1. Migration of Windows 98 Clients from Workgroup to Domain.
2. Migration of Windows Xp Clients from Workgroup to Domain.
3. Testing of Applications.

2.5 PROCESS METHODOLOGY

1. Identify all the activities.
2. Prepare the project schedule
3. Track plan vs. actual schedule
2.6 RELEASE PLAN
Process of releasing: Process for adding Windows client on Domain Controlle
2.7 IMPLEMENTATION OF GROUP POLICIES
2.7.1 ACCEPTANCE AND CLOSURE CRITERIA
All the desktops should be member of Domain Controller.
2.7.2 DELIVERABLES
 Desktop should be member of DC.
 Password Policy Implementation.
 Screen Saver Policy Implementation.
 Time Synchronization.
 Administration Rights revoked from users.
2.8 PROCEDURE FOR MIGRATION FROM WORKGROUP TO DOMAIN
CONTROLLER

2.8.1 WINDOWS XP CLIENT:

1. Change the setting from Workgroup to Domain

i) Right Click on My Computer and select properties.
ii) Select the Computer Name tab page.
iii) Click on Change.
iv) Select the Domain option and give “hil.com” in text box.
v) Click on Apply and Ok.
vi) The system will ask for Administrator ID and Password.
vii) The system will give the welcome message after adding to DC.
viii) Now system will reboot.
ix) Login with Users Id and Password.

5
 2. Now Logoff and Login with Administrator Id and Password.

3. Now copy the profile setting to new profile.

4. Check the following applications:

i) Lotus Notes
ii) Printers
iii) Microsoft Office
iv) WinZip and Acrobat Reader (if required)
v) Internet (If already given) – Put the Proxy settings and bypass entry for
intranet sites.

2.8.2) Windows 98 Client:

1. Right Click on Network Neighborhood and select Properties.

2. Select “Client for Microsoft Networks” option and click on properties.
3. Change “HIL-RKT-DOMZ” with “HILRKTADC” and click Ok button.
4. Now select the Identification Tab Page and repeat the 3 point.
5. Now close the Network Neighborhood and system will ask for reboot.
6. After rebooting the system you will get the login screen.
7. Check “HILRKTADC” is appearing in Domain column.
8. Put the Emp. Code of user in User Column and left blank for password.
9. The system will give a message for password expired, click on Ok button.
10. Now the system will ask for new password.
i) Leave the old password column blank.
ii) Put the password of at least 8 characters in New Password column.
iii) Same password should be typed in Confirm Password column.
11. Now system will login with users Id and password.
12. Map the Network Drive for Mail server.
i) Click on start  Run  \\10.190.0.16
ii) The system will show two share folder like IDS and Software.
iii) Map the IDS folder and ensure that “Reconnect at login” is checked.

13. Check the application are working or not.

i) Lotus Notes
ii) Oracle Application
iii) Aditydisha
iv) Poornata
v) Renugyanganga

2.9) IMPLEMENTATION OF INFORMATION SECURITY THROUGH DOMAIN

CONTROLLER
Protecting your system and network:

6
Do not use personal media i.e. USBs, external hard-drives, CDs/DVDs etc. on workstations
connected to the Corporate Network.
1. Screen Lockout Policy: The screen should be lockout after 10 minutes of idle.
2. Use is not able to add/remove software from systems.
3. All the systems are synchronize the time from server.
4. Password policy like

1 : Minimum 8 characters,
2 : If the password is worng more then 5 times then account has been locked out.
3: password must be change after 90 days.
2.10) SCREEN SHOTS OF THE DOMAIN CONTROLLER STEPS :

1 Change the domain in computer name change option and give the domain name as
Hil.com

Snapshot 2.1

2. Then reboot and give the EMP code and connect to our domain (HILRKTADC)
and change the password.

3. Then logon to administrator and then copy the old profile to new EMP Code profile.

7
 Snapshot 2.2

4. Go to control panel then security center and then off the window firewall.

Snapshot 2.3

1. Give full control to everyone the NTFS partitioning.

8
 Snapshot 2.4
6. Lock the Local user and set the password of the local administrator.

9
 Snapshot 2.5

7. Then reboot the system and logon to Emp code user and password and check the each
application of LAN like Oracle application. Lotus notes and maximo etc.

CHAPTER-3

DOMAIN CONTROLLER SECURITY POLICY

3.1 INTRODUCTION

The previous subsection reviewed the domain policy configured by default for all new
domains. This subsection reviews the default DC policy, which specifies security settings for
all machines in the DC OU. By default, Windows 2000 DC computers are added to the DC
OU.

3.2 DEMONSTRATION
In this subsection, the Group Policy snap-in is demonstrated rather than the Active Directory
Users and Computers snap-in as the path to the default DC GPO.

To load the Group Policy MMC snap-in:

1. Click Start, click Run, and in the text box, type mmc /s and then click OK.

2. From the Console menu, select Add/Remove Snap-in, and click the Add button.

3. From the Available Standalone Snap-in list, select Group Policy, and click the Add
button.

10
 Snapshot 3.1

4. In the Select Group Policy Object dialog box, click the Browse button.

The default GPO selected when the group policy snap-in is added is the one for the local
computer. Double-click the GPO for the DC OU as shown in below.

Snapshot 3.2

Note that the default domain policy (reviewed in the previous subsection) is also listed here,
as well as a folder containing Group Policy objects for the DC OU.
1. In the Browse for a Group Policy Object dialog box, double-click the folder
containing the GPOs associated with the DC OU.

2. Select the Default Domain Controllers Policy, and click OK.

3. In the Select Group Policy Object dialog box, click Finish.

11
 4. In the Add Standalone Snap-in dialog box, click Close.

5. In the Add/Remove Snap-in dialog box, click OK.

To review security policies in the default DC GPO:

1. In the Default Domain Controllers Policy console, expand Computer Configuration;
navigate to Windows Settings, then to Security Settings, and then to Account Policies.

2. Select Password Policy.

In the results pane, notice that a Password Policy is not defined in the default DC
GPO, because password policy is defined for the entire domain in the default domain
GPO.

Snapshot 3.3

3. In the Console, navigate to Local Policies, and select User Rights Assignments.

In the results pane, note that user rights are configured in the default DC GPO. As
seen in the previous subsection, user rights are not defined in the default domain
GPO.

12
 Snapshot 3.4

3.3 SYMANTEC ANTIVIRUS IMPLEMENTATION

Step2:- Second step is to Installation of Symantec 11.0

Go to Start -> Run

13
 Snapshot 3.5

The below screen will appear.

Type \\10.190.30.2 or \\antivirus-serv

Snapshot 3.6

The below screen will appear.

14
 Snapshot 3.7

Type User name: guest1

Password : guest5002
Click :- OK

Snapshot 3.8

15
The below screen will appear.
Click on SEP-Packages

Snapshot 3.9
The below screen will appear.
Click on:- 256mb users Package

Snapshot 3.10

16
The below screen will appear.
Click on setup

Snapshot 3.11

The below screen will appear.

Click on Run

Snapshot 3.12

The Symantec Antivirus will start to install.

17
 Snapshot 3.13

Do not cancel any screen , wait till it’s installed.

CHAPTER-4
REQUIREMENTS OF DOMAIN CONTROLLER

4.1 HARDWARE REQUIREMENT:

Component 32-bit 64-bit

18
Processor Intel 3 GHz on x64 only with the following
Pentium IV
3.0 GHz or
Above processors:

■ Intel Xeon with Intel EM64T support

■ Intel Pentium IV ith Intel EM64T support
■ AMD 64-bit Opteron™
■ AMD 64-bit Athlon™
Note: Itanium is not supported. The management components are 32-bit
applications.
Memory 4 GB of 4 GB of RAM (Minimum)
RAM
(Minimum
)
Hard disk 80 GB 80 GB
Table 4.1: Hardware Requirements

4.2 SOFTWARE REQUIREMENTS

Operating The following operating systems are The following operating systems
system supported: are supported:
■ Windows® 2000 ■ Windows XP Professional x64
Professional/Server/Advanced Edition with Service Pack 1 or later
Server with Service Pack 3 or later
■ Windows XP Professional with ■ Windows Server 2003 x64
Service Pack 1 or later Edition with Service Pack 1 or later
■ Windows Server 2003 Note: The management server,
Web/Standard/Enterprise/Datacenter console, and embedded database
Editions are 32-bit applications.
Table 4.2: Software Requirements

4.3 MANPOWER BUDGET

As per Training center proposal ‘UPGRADATION OF ANTIVIRUS’

19
 Training should be provided to Trainee.
The IT- skill development Program.
4.4 RESOURCE PLANNING AND MANAGEMENT
 H/w - New Procrument.
 S/w - Existing
 Manpower - IT Staff and Trainee.
4.5 MANPOWER – TRAINING AND / OR RECRUITEMENT:
Training should be provided to Trainee.
The IT- skill development Program to conduct by IT Team.

4.6 INTERFACES
Internal Interfaces: Amol Anand, Jitendra Diwakar.
Team meetings—Periodicity: as per requirement.
Network administrator for Software CDs / Shared folder: Amol Anand,
Jitendra Diwakar..
Project Manager will interact with his reporting officer regarding progress of
the project.
External Interfaces: Head – IT Department (V K Dogra)

4.7 PROCESS METHODOLOGY

1. Identify all the activities.
2. Prepare the project schedule
3. Track plan vs. actual schedule
4. Client Installation Refer:-3.1 and 3.2.
4.8 RELEASE PLAN
4.8.1 PROCESS OF RELEASING
1. Installation of Windows 2003 Advance Server – Swadhin Neema
2. Installation of Symantec EndPoint Protection11.0 Server- Swadhin Neema
3. Installation of Symantec Antivirus 9.0 Server- Swadhin Neema
4. Installation of Symantec EndPoint Protection Client – IT Trainee
5. Installation of Symantec Antivirus 9.0 Client. – IT Trainee
6. Implementation of Group Policies.
4.8.2 PERIODICITY OF RELEASING THE CIS/ DELIVERABLE ITEMS:
Implementation will be roll out once will go live.
4.9 ACCEPTANCE AND CLOSURE CRITERIA
All the desktops should be member of Domain Controller for Installation of client
through Altiris server.
4.10 DELIVERABLES
1. Desktop protected from Virus.

20
 2. Desktop protected from Spyware.
3. Automated scanning Scheduled.
4. Automated Update Scheduled.
5. Administration Rights for uninstallation of antivirus revoked from users.

4.11 RISK MANAGEMENT

Ghost copy will be kept for Server and Backup of Data will be kept on Network.
Scheduled backup of server done.
Learning
1. To check the IP configuration.
2. To uninstallation the Trend micro antivirus.
3. To installation the Symantec antivirus.
4. To facing the different types of problem. Of PCs.
5. To implementing the domain control into System.
6. To works on clients node in Industries.

21
 CHAPTER-5
CONCLUSION

5.1 SCOPE

Scope of Domain Controller is as far as the internetworking concept goes.

1.The Password Policy

2.Screen Saver lockout policy

3.Time Synchronization at desktop levels.

Its application is in every industry that has a network established and needs to implement
security measures.

5.2 RELIABILITY:

Reliability of the software is the extent to which a program satisfies its specification and
fulfills the customer’s objectives. Reliable software is expected to perform its intended
function with required precision.

Reliability is evaluated by measuring following parameters: -

1.Measuring the frequency and severity of the system.
2.The accuracy of the output results.
3.The mean time of failure.
4. Ability to recover the failure.
5. The predictability of the program.

5.3 SCALIBITY:

Scalability is the extent to which the software can tolerate the external overweight without its
performance getting affected. These overweight can be number of users, processors speed
etc.
The techniques and control allied to small web applications do not scale upward well. It is not
uncommon for a simple web application grows significantly interconnections with existing
information’s systems, databases, and portal gateway are implemented. As size and
complexity grows, can have small change can have far-reaching and unintended effect that
can be problematic. Therefore the rigor of configuration control mechanisms should be
directly proportional to application scale.

22
Thus delatailed study of Domain Controller has been conducted and checked with the
implementation of Symantec Antivirus installation.

CHAPTER-6

BIBLIOGRAPHY AND REFRENCES

23
1. Windows Server 2003 Deployment Kit: Designing and Deploying Directory and Security
Services http://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-
4394-92ED-2147C3A9EBBE&displaylang=en#filelist

2. NetWare to Windows Server 2003 Migration Planning

Guide http://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspx

3. Microsoft Windows Storage Server

2003 http://www.microsoft.com/windowsserversystem/wss2003/default.mspx

4. Windows Servers in a Storage Area Network

Environment http://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandepl
oy/mssans.mspx

5. Microsoft Windows Services for NetWare Technology

Center http://www.microsoft.com/windowsserver2003/sfn/default.mspx

6. Microsoft Windows Services for NetWare 5.03 Overview

http://www.microsoft.com/windowsserver2003/techinfo/overview/sfncd.mspx

7. MSDSS Technical Overview

http://www.microsoft.com/windows2000/sfn/msdss.asp

8. How to Migrate or Deploy a Novell NetWare Environment to

Windows http://support.microsoft.com/kb/q274279/

9. NetWare Add-on
Services http://www.microsoft.com/ntserver/techresources/interop/netware/AddonService
s.asp

10. Microsoft Operations Manager

2005 http://www.microsoft.com/technet/prodtechnol/mom/mom2005/default.mspx

11. DcDiag.exe: Domain Controller Diagnostic

Tool http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/dcdiag-o.asp

12. Chkdsk http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard

/proddocs/en-us/Default.asp?
url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asp

13. How ASR

Works http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?
url=/resources/documentation/windowsserv/2003/all/deployguide/en-
us/sdcbc_sto_axho.asp

14. Hindalco Sandesh

15. Wikipedia(The Free Encylcopedia)

24