Lab Project
Lab Project
ARBAMINCH, ETHIOPIA
2006 E.C
Unit of competence
1. Monitoring and Administrating system and network security &
2. Identify and Resolve Network Problems
Installing Windows
Server 2008
Hardware Requirements
Table 1.1 lists the basic system requirements for Windows Server 2008 editions.
Hardware resources would need to be increased for any systems using Hyper-V
technology and running virtual machines. For example, if you‟re running three virtual
servers within a Windows Server 2008 Enterprise edition, you would need additional
processing power, more memory, and more disk space.
It‟s common for Microsoft to provide free evaluation copies of Server operating systems
for use. Currently, you can download Windows Server 2008 30-day and 60-day
evaluation editions free of charges at :
http://www.micosoft.com/windowsserver2008/en/us/trial-software.aspx
The download is an .iso image of the actual DVD. Search with your favorite search
engine for Download Windows Server 2008, and you‟ll find the link.
Once you download the .iso image, you can burn it to a DVD. If you don‟t have the
software needed to burn it to DVD, you can use one of many freeware utilities (such as
ImgBurn) to burn the .iso image to your DVD.
EXERCISE 1.1
1. Insert the Windows Server 2008 DVD into your DVD drive. Boot your PC using
Windows Server 2008 DVD.
This allows you to specify your language and your keyboard layout. By default,
text input language and method is : US Keyboard layout (Figure 0001).
You are presented with options to Install, brief information about Server 2008 or
repair (Figure 0002).
3.1 Click Install now to start setup Windows Server 2008 on this computer.
4.1 Enter your "Product Key" for activation now or you can enter it later (Figure
0003).
4.3. If you leave the product key box blank, the warning window will appear (Figure
0004); just click No to continue.
5.1. Select Windows Server 2008 Enterprise (Full Installation), (as shown in the
Figure 0005).
5.2. Tick the box of I have selected the edition of Windows that I purchased.
If you accept (which, of course, you have to do to continue installation), tick the
box of I accept the license terms (Figure 0006).
8. Partition Options
8.6. Click Next. The partition will be formatted with NTFS as part of the installation. At
this point, take a break. The installation will continue on its own.
When you first time login, the windows warning will appear ask you to change the
user password before logging on for the first time (Figure 0013).
4.1 Enter a new password in the two test boxes (Figure 0014). Enter
Pr@ctice in this exercise. It meets complexity requirements and doesn‟t
require you to remember multiple passwords. Don‟t use this password on
a production server.
10.3 Once the password has been changed, the screen indicates success
(Figure 0015). Click OK.
Summary
In this section you installed Windows Server 2008 on a computer. In the following
exercises you will setting time zone, install Active Directory and other services, creating
a small network for you to administer.
Initial Configuration
EXERCISE 2.1
4. Click OK.
EXERCISE 2.2
Configuring Network
6. Now set your server IP address, and ensure that you are using a static IP
address. For this exercise, I‟m using number 21 as my server station number
(Figure 0025).
Tips:
Use the following IP address:
7. Click Advanced button after complete setting your IP address (Figure 0025).
9. Specify myserver.com as the DNS suffix for this connection (Figure 0026).
10. Tick Use this connection’s DNS suffix in DNS registration box (Figure 0026).
1. Monitoring and Administrating system and network security &
2. Identify and Resolve Network Problems Page 20
11. Click OK (Figure 0026).
13. Click Close button to close Local Area Connection Properties (Figure
0027).
EXERCISE 2.3
4. Windows remind you to restart your computer to apply the changes. Click OK.
Summary
In this section you have configure Time Zone, Networking and Computer Name for your
Server 2008. In the following exercises you will install Active Directory and other
services for you to administer.
Installing and
Configuring DNS
Windows DNS services can be integrated with Dynamic Host Configuration Protocol
(DHCP) services on Windows, eliminating the need to add DNS records as computers
are added to the network.
The first step is required to ensure that you are using a static IP address and that the
DNS settings on the computer have been correctly configured. Make sure your have
hook up your PC to the network and you are using a static IP address before you start.
EXERCISE 3.1
5. On the Before You Begin page, review the requirements, and click Next (Figure
0039).
7. On the DNS Server page, review the information, and click Next (Figure 0041).
10. Launch DNS Manager. Click Start ►Administrator Tools ► DNS (Figure 0045)
11. Double-click on the computer icon to expand the DNS Server (Figure 0046).
12. Click on Forward Lookup Zones first, and then right-click on it.
14. New Zone welcome wizard appear. Click Next to continue (Figure 0048).
16. The New Zone Wizard dialog box requests the name for the zone. Enter the
name that has been assigned to your domain (this example uses myserver.com).
(Figure 0050).
17. Once you have entered the correct name for the zone name, click Next button to
continue.
19. Select the option "Allow both nonsecure and secure dynamic updates". Click
Next to continue (Figure 0052).
22. Right click myserver.com and select New Host (Figure 0054).
23. Enter IP address for DNS server (myserver.com) and click Add Host (Figure
0055).
28. Right click Reverse Lookup Zones and select New Zone (Figure 0057).
29. New Zone welcome wizard appear. Click Next to continue (Figure 0058)
31. Select IPv4 Reverse Lookup Zone and click Next to continue (Figure
0060).
Enter the first 3 octets of the IP address that has been allocated to your network
domain (Figure 0061).
33. After entering the network ID, click Next button to continue.
34. The wizard will display the name of the reverse zone file that it will create. Leave
the filename as suggested, then click Next (Figure 0062).
36. Click Finish to close the wizard and create the new zone (Figure 0064).
37. In the DNS manager window, double-click the computer icon and expand the
Reverse Lookup Zone field.
39. Right-click the subnet field and select New Pointer (Figure 0065).
47. After finish configuring Reverse Lookup Zones, recheck the subnet field. The
subnet field must have minimum three(3) types resource record – (SOA), (NS)
and (PTR). (Figure 0072).
In this section you verify that the DNS Server is installed, running, and correctly
configured.
48. In the DNS manager window, right-click the computer icon and select properties
(Figure 0073).
Do not proceed till the test results for Simple Query indicate Pass. Your
recursive query result will indicate Fail because we did not configure our DNS to
query to other DNS server.
In this exercise you will use a client tool to check the operation of the DNS
server. You
will query both a forward and reverse lookup.
55. A command prompt DOS window will appear with the program nslookup running
in it (Figure 0078).
The default server name and IP address of the DNS server will be shown.
Summary
The DNS server is a database that manages computer names and their IP addresses.
Zone files are used to store this information. Within a zone, a forward lookup resolves
computer names to IP addresses. A reverse zone resolves IP addresses to computer
names.
A client tool such as NSLOOKUP can be used to test the operation of a DNS server.
Installing Active
Directory
EXERCISE 4.1
5. On the Before You Begin page, review the requirements, and click Next (Figure 0085).
7. On the Active Directory Domain Services page, review the information, and click
Next (Figure 0087).
Note : You still must run the Active Directory Domain Services Installation Wizard
(DCPromo) to make the server a fully functional domain controller.
EXERCISE 4.2
11. Click Start ►Run. At the Run line, enter DCPromo, and click OK (Figure 0091).
15. On the Name the Forest Root Domain screen, enter MYServer.com as the fully
qualified domain name.
Click Next (Figure 0095).
16. If Domain NetBIOS Name page appears, accept the default of MYSERVER.
17. On the Set Forest Functional Level screen, select the Forest functional level of
Windows Server 2008. This ensures that any new domains created in this forest
will automatically operate at the Windows Server 2008 domain functional level,
which does provide unique features. If you had a network that has a Windows
2000 Remote Access Server, you would select the compatible option (Figure
0096).
19. On the Additional Domain Controller Options screen, note that both the DNS
server and the global catalog are selected as options. Active Directory Domain
Services requires DNS, and if not available on the network, DCPromo will give
you the option of installing it. Additionally, the first domain controller within a
domain is a global catalog server.
21. On the Location for Database, Log Files, and SYSVOL screen, accept the
defaults.
Figure 0099 : Location for Database, Log Files, and SYSVOL Screen
23. On the Summary screen, review your selections, and click Next (Figure 0101).
Active Directory Domain Services will be installed.
25. If a warning message appeared same as below, just click OK. This message
appeared because we already created the DNS zone before (Figure 0103).
Once your system reboots, Active Directory Domain Services will be installed.
Now you need to recheck your network configuration because sometime after
installing Active Directory Domain Services, the network configurations change to
29. Launch Network and Sharing Center. Click Start ► Right click Network ►
Properties (Figure 0107).
31. Click Properties button to open Local Area Connection Properties (Figure 0109).
36. Specify myserver.com as the DNS suffix for this connection (Figure 0113).
37. Tick Use this connection’s DNS suffix in DNS registration box (Figure 0113).
Summary
Windows Server 2008 brings a lot of new features and benefits that will drive a
lot of migrations to the new operating system. This chapter presented many of these
new additions.
Each edition can be purchased with or without Hyper-V, which is the technology
that supports virtualization. The Standard edition supports one virtual server, the
Enterprise edition supports as many as four virtual servers, and the Datacenter edition
supports an unlimited number of virtual servers. Virtualization is supported only on 64-bit
operating systems.
In this chapter, you learned about the new features of Windows Server 2008.
These included Server Manager, Server Core, PowerShell, Windows Deployment
Services, and read-only domain controllers.
Exercises led you through the process of installing Windows Server 2008 on a
PC. After reviewing many of the basics of Active Directory Domain Services, you learned
how to promote the server to a domain controller.
Creating
Organization Units
And Users
You will create a number of organizational units. An OU acts as a container that holds
objects such as users.
EXERCISE 5.1
4. On the menu bar, click Action, New, Organizational Unit (Figure 0116).
8. Repeat step 3 to 7 to create the organizational units Sted and Sklr (Figure
0118).
Creating organizational units lets you place users directly into units and assign
permissions and rights based on these units. This leads to better administration
and delegation control than if you placed users directly into the user container.
When users move from one department to another, it is a simple matter to move
the user to the corresponding organizational unit. In this way, they inherit all the
new features and rights and of the new organizational unit, ensuring they have
full access to all the resources they are entitled to.
For proper control, it is better to create users within an OU rather than the Users
container. In the following exercise you will create a number of users, modify
their
properties, and move them from one organizational unit to another.
15. The warning below will appear. This warning appears because your password
does not meet the password policy requirements. Click OK to continue (Figure
0124).
16. Click Cancel to close new user account confirmation window (Figure 0125).
29. Double click Password must meet complexity requirements under Password
Policy to open Password must meet complexity requirements Properties.
Figure 0132 : Group Policy Management - Password Must Meet Complexity Requirements
32. Double click Minimum password length under Password Policy to open
Minimum password length Properties (Figure 0134).
35. Recheck your configuration. Your configuration should be same as figure below
(Figure 0136).
After restarting server, login as Administrator and start create user Zul Zcomby
again (follow step 10 to 14). There should be no problem anymore.
37. Now create the new user Ocah in the Stkm OU using the following properties
(Figure 0137).
Password ocah
User cannot change password
Password never expires
Figure 0137 : Ocah Blue Properties
38. Create the following user account in the Sted OU (Figure 0138).
40. Note the down arrow that appears on the icon for the user Md Saad,
indicating this account has been disabled (Figure 0142).
43. Click OK
You have now created a number of users within the organizational units created
earlier. At this stage, you cannot see the benefits of doing this. However, the later
exercises will start to illustrate why this has been done, by allocating resources to
organizational units.
In this exercise we will look at default user properties such as logon times and how often
they need to change their passwords.
Office 012-5740157
Telephone Number [email protected]
E-Mail
Job Title (Organization) Senior Instructor
Department Computer Technology Figure 0147 :
Company IKM User Details
48. Double click the user Md Saad in the Stkm OU (Figure 0150).
51. Select all areas and click Logon Denied (Figure 0153).
Configuring Client
Computer
97
Make sure that the Windows Server 2008 previously installed is running.
Name of Installer
same domain name as you did for the Server
Domain Name
192.168.2.SN
TCP/IP Address
TCP/IP Subnet mask 255.255.255.0
Use the same domain name as you did for the Server.
5. Now set your client (Windows XP) IP address, and ensure that you are using a
static IP address. For this exercise, I‟m using number 61 as my Windows XP
client station number (Figure 0159).
8. Click “OK” button (Figure 0160) and close all remaining windows.
16. Select "Member of ....... Domain" and enter the name of your Domain (Figure 0166).
19. If you get this welcome message : Windows : "Computer Name Changes" -
Welcome to the ....... domain"; it means you are successfully joining a domain.
(Figure 0168).
20. Since joining a domain is a major change in the security configuration of your
system, you will be reminded that you have to restart your system. Click OK
(Figure 0169).
Viewing Computer
In Active Directory
In this section you will use Active Directory Users and Computers to view information for
computers and servers.
Client workstations running Windows XP Professional have their own local accounts
database. This means it is possible for an administrator on the workstation to create a
local workstation account, which is not the same as the domain account, and allow
users to logon to the local computer rather than the domain.
Currently, you should have the Windows Server 2008 and a Windows XP Professional
client workstation running.
EXERCISE 7.1
In this exercise, you will use Active Directory Users and Computers to view the
workstations and servers in the domain.
Now you can see the general information about CLIENTXP61 including it DNS
name and it role.
Here you can find information about Operating System, version and service pack
using by client.
Here you can find information about Operating System, version and service pack
using by server.
11. Click OK to close the properties box and close all remaining dialog box.
In this exercise you will log on the Windows XP Professional workstation using a local
administrator account.
13. Logoff the client computer. Click Start ► Shutdown and select Logoff
Administrator (Figure 0181).
EXERCISE 7.3
In this exercise you will log on the client computer using a domain account.
15. Press CTRL+ALT+DEL to display the logon dialog box (Figure 0183).
Because zul.zcomby not created on the local client account, it was created in the
server active directory account.
Just now, you were tried to logon to the client using active directory user account.
21. Click the Logon to: box, and select MYSERVER (Figure 0187)
24. Log off the client computer. But leave it running Windows XP Professional (do
not shut the computer down yet).
25. If you are currently logged in to the Windows Server 2008, log off.
Why?
Because the user account you are using to login into server do not have
permission to login into server directly.
41. Log off server. Click Start ► Log Off (Figure 0203).
Summary
Servers do not allow normal users to logon locally. Servers run the network and provide
resources, which users connect to remotely across a network. Servers are not designed
to have users physically sitting at their keyboards trying to log on and run programs.
Users actually logon to a client computer in the network and access resources using a
network connection.
Client computers running Windows XP Professional have their own accounts database.
Delegating
Management Of
Users
EXERCISE 8.1
DelegatingControl
In this portion of the exercise you will make zul.zcomby a manager of the Stkm
organizational unit. Once he is a manager, he will be able to modify user accounts within
the Stkm OU.
4. Right click the Stkm OU and select Delegate Control (Figure 0209).
Managing Users
In this portion of the exercise you will log on to server as zul.zcomby and attempt to
manage users.
20. You will be asked to reenter your password for security measure. Just reenter
password for zul.zcomby (Figure 0224).
Figure 0232 : Logon Hours for Ocah Blue – Set Logon Permitted
33. Attemp to change the logon hours of this user. Click Account tab (Figure 0235).
Why do you think you are not able to modify this account?
Because Zul Zcomby only have permission to modify user under Stkm OU only.
He only have read permissioin for other OU‟s.
37. Close all remaining windows except Active Directory Users and Computers.
This display a reset password box that will allow the password to be changed.
In the above exercise you delegated control of an Organizational Unit to a user. You
then modified account details of users belonging to that OU as the designated
manager of the OU.
Delegating control of users using the delegation control wizard is simple. When
control of users and groups is delegated, administrators can be relieved of simple
administrative tasks such as resetting passwords and modification of user accounts.
Exploring Group
Scopes and Types
EXERCISE 9.1
In the following exercise you will create a number of groups. These groups will be used
to demonstrate group scope. From the notes, group scope determines who can be a
member and where that group can be used in the enterprise.
Group Scope
Type
Local User accounts, Global groups and Universal groups from any domain in the
forest, as well as local groups from the same domain.
Global User accounts and global groups from the same domain.
Universal User accounts, global groups and universal groups from any domain in the
forest.
The recommended strategy for using groups in Windows Server 2008 is to use both
global and domain local groups. Place users into global groups and then place the global
groups into domain local groups and assign permissions to the domain local groups.
Global groups have access to accounts in the local domain. Where the enterprise
consists of more than one domain, local groups allow the use of accounts across all the
domains. Where the enterprise has combined a number of domains into a forest,
Universal groups provide access to any accounts in the forest.
3. Right-click the domain icon and select New - Group from the list (Figure 0243).
7.1. Right-click the domain icon and select New - Group from the list (Figure
0253).
7.2. Key-in Intranet Users in the Group name: box (Figure 0254).
What happened?
1. Monitoring and Administrating system and network security &
2. Identify and Resolve Network Problems Page 156
10.7. Click OK button (Figure 0267).
Summary
Windows Server 2008 running in native mode supports the use of different group types.
Global groups have access to user accounts and other global groups in the same
domain. Local groups allow you to access accounts outside the current domain, and
universal groups provide access across organizations (forests).
Creating And
Applying Group
Policies
Group Policies
Group policies are settings or configurations that can be applied to users, groups,
organizational units and domains. An administrator can create a group policy that
configures the computer or user settings, such as menu and desktop settings, folder
locations and default password settings.
Windows NT 4 and Windows 98 introduced system policies. Windows 2000, 2003 and
2008 extends these further using group policies.
EXERCISE 10.1
Now, you will create a new group policy for the Stkm OU. This new policy will apply to all
members of the Stkm OU though in another exercise that follows, you will override this.
6. Right-click the Stkm OU and select the Create a GPO in this domain, and
Link it here… (Figure 0274).
9. Right-click the STKM Group Policy and select Edit (Figure 0276).
10. The group policy editor allows you to specify user and computer settings. In the
following steps, you will change some of these settings (Figure 0277).
14. Click the Start Menu and Taskbar folder (Figure 0281).
Figure 0281 : Group Policy Management Editor – Start Menu and Taskbar
Figure 0282 : Group Policy Management Editor – Add Logoff to the Start Menu
16. The Add Logoff to the Start Menu Properties appears. Click the Disabled button
to disable this setting (Figure 0283).
18. The setting now displays as Disabled in the Group Policy Editor (Figure 0284).
(This uses wallpaper from the Windows XP Pro installed on C drive of client PC)
21. Refresh the Group Policy Management. On the Menubar; click Action ► Refresh
(Figure 0285).
23. Launch the Run application. Click Start ► Run… (Figure 0286).
The group policy has been applied to members of the Stkm Organizational Unit. There
are two members; Zul Zcomby and Ocah Blue. You will now test this policy to see if it
works.
YES / NO
YES / NO
Now verify that the settings are also applied to the client computer. Log on to the
Client computer as ocah.blue.
30. Press CTRL+ALT+DEL to display the logon dialog box (Figure 0292).
31. Log on the client computer as ocah.blue and ocah as password (Figure 0293).
166
YES / NO
YES / NO
YES / NO
35. All the group policy setting should be applied (Figure 0294).
38. Press CTRL+ALT+DEL to display the logon dialog box (Figure 0295).
In this exercise you will disable the group policy of Stkm OU.
50. A warning box appears. The Group Policy Management remind you that you
have selected a link to a GPO and changes you make will impact all other
locations linked with the GPO (Figure 0304).
53. Now you can see under Link Enabled; the status Yes have changed to No
(Figure 0306).
55. Launch the Run application. Click Start ► Run… (Figure 0307).
59. Press CTRL+ALT+DEL to display the logon dialog box (Figure 0310).
60. Log on the Windows XP as zul.zcomby and comby as password (Figure 0311).
Summary
In this exercise you created a group policy and applied it to an organizational unit.
Only a fraction of the available settings were explored. Applying a group policy is a
way of controlling security and configuring groups of users with common settings.
This can help reduce the cost of ownership and the level of administrator support by
restricting what users can do or change on their computers.
Creating And
Sharing Resources
Preliminary Setup
Figure 0314 : Active Directory Users and Computers – Intranet Users Group
Figure 0315 : Active Directory Users and Computers – Intranet Users Properties
7. After finish adding the entire user to Intranet Users group, your Intranet Users
properties should be same as figure below (Figure 0322).
Figure 0322 : Active Directory Users and Computers – Intranet Users Properties
In this exercise, you will use Windows Explorer to create a folder and verify the NTFS file
permissions. The folder will then be shared and permissions assigned. You will then
access this shared resource from the client computer.
6. Click the Security tab. A list of security permissions is displayed. Note that the
group Administrators is given Full Control access at the folder level (Figure
0329).
Now you will restrict permissions at the share level. Remember that user permissions
to a network resource are made up of the share permissions and the NTFS
permissions.
12.1. Select the Everyone group from the list (Figure 0335).
14. Add the Tech Support group with permissions of Full Control.
14.3. Select the Technical Support from the list of Search results (Figure 0340).
14.6. Click the Full Control allow box to enable the Full Control permission
(Figure 0342).
15. Repeat steps 13 to 14 to add the Intranet Users group with Read permissions.
16. The share permissions should look like same as figure below (Figure 0343).
18. Click OK to close the advanced sharing dialog box for folder temp21 (Figure 0344).
22. Log on the client computer as ali.zul and ali as password (Figure
0347).
29. You should see the Common resource listed (Figure 0354).
30. Double-click the Common resources so that you are connected to it (Figure 0354).
31. A new window will open up and display the contents of the folder (it will be empty
as there are no files in the folder) (Figure 0355).
32.1. Right-click in the windows and select New Text Document (Figure 0356).
40. You should see the Common resource listed (Figure 0364).
41. Double-click the Common resources so that you are connected to it (Figure 0364).
42. A new window will open up and display the contents of the folder (Figure 0365).
43.1. Right-click in the windows and select New Text Document (Figure 0366).
YES / NO
Instead of using My Network Places, you can map a drive letter to the resource. This is
an alternative way of accessing the resource, but requires that you know the location of
the resource (you can use My Network Places to view the available resources, so you
don‟t really need to know the location)
45. Log on the client computer as ali.zul and ali as password (Figure 0367).
You must specify the name of the server and the share name.
49. A new window will open up and display the contents of the Common folder
(Figure 0370).
50.1. Right-click in the windows and select New Text Document (Figure 0371).
YES / NO
One of the problems of publishing shares in the way you have just done (which is the
way they done in NT 4 or 98) is that you have to browse the network or know which
server the resource is located on in order to find it. This can be time-consuming and
frustrating for users.
Resources can be published in Active Directory, making them easy to find. In the next
exercise you will publish the resource into Active Directory.
53. Launch Active Directory Users and Computers. Click Start ► Administrative
Tools ► Active Directory Users and Computers (Figure 0373).
55. Enter the name as Common Files and the Network path as your server name
and share name – in this exercise it is \\Server21\Common (Figure 0375).
57. The new shared folder appears in the right windows pane of Active Directory
(Figure 0376).
Now that the shared folder is published in Active Directory, it is easy for users to locate
and connect to the resource.
67. Select U as drive and enter the location of the network resource in the Folder:
box (Figure 0385).
Note how the location for the server share is filled in automatically.
71. There are now one additional drive appears at the bottom (Figure
0387).
Summary
Permissions are assigned at the SHARE and at the File system level. By default,
Windows Server 2003 places every use created into the group EVERYONE, and, when
creating a new directory or share, automatically assigns rights to that resource so the
group EVERYONE can access it.
If you want to secure any resources by restricting access, you should ensure that the
appropriate permissions have been set at both the share and file system level.
Publishing shared folders in Active Directory simplifies the task of locating resources.
Logon Scripts
EXERCISE 12.1
Logon Scripts
A logon script is a sequence of commands that executes when a user logs onto the
network.
6. Right-click the STKM Group Policy and select Edit (Figure 0393).
Right-click inside the new windows and select New ► Text Document (Figure
0401).
echo off
cls
echo This is a log on script for the Stkm OU
echo Welcome %USERNAME% , member of the Stkm OU
pause
16.1. From Menu bar, click File ► Save As… (Figure 0403).
18. Close the Script windows by clicking the X button at the right top corner of the
windows (Figure 0407).
20. Click Browse… button on the Add a Script window (Figure 0409).
23. Now you can see the Stkm.cmd appear in the “Script Name:” box. Click OK
button to continue (Figure 0412).
26. On the Group Policy Management window, right-click STKM Group Policy and
uncheck all options except Link Enabled (Figure 0414).
Right-click the STKM Group Policy and select Edit (Figure 0415).
28. In the Group Policy Management Editor, expand User Configuration (Figure
0416).
Figure 0421 : Group Policy Management Editor – Run logon scripts visible
34. The Run logon scripts visible Properties appear. Click the Enabled button to
enable this setting (Figure 0422).
36. In the same folder, double-click the Run logon scripts synchronously option
(Figure 0423).
Figure 0423 : Group Policy Management Editor – Run logon scripts synchronously
39. The setting now displays as Enabled in the Group Policy Editor (Figure 0425).
41. On Group Policy Management, click Refresh button and close the Group
Policy Management window.
42. Launch the Run application. Click Start ► Run… (Figure 0426).
47. The logon script should appear same as figure below (Figure 0430).
Summary
Scripts allow for both user and computer environments to be configured. The
four scripts
available are startup, shutdown, logon and logoff.