0% found this document useful (0 votes)
0 views

OperatingSystem-Lab9

This lab manual provides instructions for creating and configuring Group Policy Objects (GPOs) using Windows Server 2012. It covers the installation of Group Policy Management, the creation of Starter GPOs, and the linking of GPOs to organizational units. The manual includes step-by-step exercises for implementing security policies and managing user access within a network environment.

Uploaded by

227p4k4my7
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
0 views

OperatingSystem-Lab9

This lab manual provides instructions for creating and configuring Group Policy Objects (GPOs) using Windows Server 2012. It covers the installation of Group Policy Management, the creation of Starter GPOs, and the linking of GPOs to organizational units. The manual includes step-by-step exercises for implementing security policies and managing user access within a network environment.

Uploaded by

227p4k4my7
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 24

ABU DHABI POLYTECHNIC

INFORMATION SECURITY ENGINEERING


TECHNOLOGY

Operating System Security

Lab Manual 9

CREATING GROUP POLICY OBJECTS

Semester 2, A.Y. 2021-2022


Objective: After completing this lab student will be able to create and configure Group Policy

1 Creating a Starter GPO


2 Creating Group Policy Objects
3 Linking a Group Policy Object
Tools Required: Windows Server 2012

1. Installing Group Policy Management


1. Log on to the Server computer, using the domain Administrator account and the password Pa$
$w0rd.
In Server Manager, click Manage > Add Roles and Features. The Add Roles and Features
Wizard appears, displaying the Before you begin page.

2. Click Next. The Select installation type page appears.


3. Click Next. The Select destination server page appears.
4. Click Next. The Select server roles page appears
5. Click Next. The Select features page appears.
6. Scroll down and select the Group Policy Management check box.
7. Click Next. The Confirm installation selections page appears.
8. Click Install. The Installation progress page appears as the wizard installs the selected
features.
9. Click Close. The wizard closes.
10. Click Tools. The Tools menu appears, which now contains the Group Policy
Management console.
11. Press Alt+Prt Scr to take a screen shot of the Tools menu. Press Ctrl+V to paste the
image on the page provided in the Lab 16 worksheet file
Exercise 2 Creating a Starter GPO
1. On SVR-MBR-B, in Server Manager, click Tools > Group Policy Management.
2. The Group Policy Management console appears.

2. In the left pane, expand the Forest: AdpolyTest.com node, the Domains node, and the
adpoly.com node
3. Right-click the Starter GPOs node and, from the context menu, click New. The New Starter
GPO dialog box appears.
4. In the Name text box, type Branch Office and click OK. The new starter GPO appears in the
console.

5. Expand the Starter GPOs node, right-click the Branch Office GPO, and, from the context
menu, select Edit. The Group Policy Starter GPO Editor console appears.

6. In the left pane, browse to the Computer Configuration > Policies>Administrative Templates
> Network > Offline Files folder.
7. In the right pane, double-click the Prohibit user configuration of offline files policy. The
Prohibit user configuration of offline files dialog box appears.
8. Select the Enabled option and click OK.

9. Open the Remove “Make Available Offline” Command dialog box and enable it as you did
before, clicking OK when finished.
10. Press Alt+Prt Scr to take a screen shot of the Group Policy Starter GPO Editor console,
showing the two policies you configured.
3 Creating Group Policy Objects
1. On the same server, in the Group Policy Management console, right-click the Branch Office
Starter GPO you created , and from the context menu, select New GPO from Starter GPO. The
New GPO dialog box appears.

2. In the Name text box, type Paris Lockdown and click OK.

3. Expand the Group Policy Objects node. The new Paris Lockdown GPO appears.

4. Right-click the Paris Lockdown GPO and, from the context menu, select Edit. The Group
Policy Management Editor console appears
5. Now, browse to the Computer Configuration > Policies > Windows Settings > Security
Settings > Account Policies > Account Lockout Policy folder.

6. Open the following three policies, click the Define this policy setting check box, and configure
them with the specified values:
• Account lockout duration – 30 minutes
• Account lockout threshold – 5 invalid Logon attempts
• Reset account lockout after – 30 minutes
7. Press Alt+Prt Scr to take a screen shot of the Reset account lockout after Properties
sheet, showing the changes you made to its configuration. Close the Group Policy
Management Editor console.
End of exercise. Leave all windows open for the next exercise.

4. Linking a Group Policy Object


1. On Same Server in the Group Policy Management console, right-click the Paris OU and, in the
context menu, select Link an Existing GPO. The Select GPO dialog box appears
2. In the Group Policy Objects list, select Paris Lockdown and click OK. The GPO appears in the
right pane, on the Linked Group Policy Objects tab of Paris OU.

3. Click the Group Policy Inheritance tab. The list of GPOs now contains the Paris
Lockdown and the Default Doman Policy GPO.

4. In the Group Policy Objects node, select the Paris Lockdown GPO (click OK if a message
appears) and, in the right pane, look at the Scope tab.
5. Press Alt+Prt Scr to take a screen shot of the Group Policy Management console,
showing the changes you made to the Security Filtering configuration.
Lab Exercise:

1. Create an OU called LabExercise


2. Add two users in it.
3. Create a group policy name ISET_policies with policies given below
• Deny logon locally

• Add workstations to domain


• Force shutdown from a remote system
• Enable computer and user accounts to be trusted for delegation

• Manage auditing and security log


• Shut down the system
4. Link the ISET_policies with the LabExercise organizational unit

You might also like