CSS NC2

LIBON AGRO-INDUSTRIAL HIGH SCOOL
Tinago St., Zone 2, Libon, Albay
TABLE OF CONTENTS
1. Creating a bootable USB installer using Rufus
2. Create a bootable USB Flash Drive using the diskpart utility
3. Installing Microsoft Windows Server 2008 R2 enterprise
4. Assign Static IP Address (in Windows Server 2008 R2)
5. Installing Active Directory Domain Services on Windows Server 2008 R2 Enterprise 64-bit
6. Add the Active Directory Domain Services Role (DCPROMO)
7. Installing DHCP Server on Windows Server 2008 R2
8. Create New User Account in Active Directory
9. To Create a User Template in Active Directory
10. Group Policy in Windows 2008 Server R2
11. Folder Redirection
12. Configuring Primary Computers for Folder Redirection and Roaming Profiles in Windows Server
13. Set up Remote Desktop Services on Windows 2008 R2
14. To install and configure File Server
15. Installing the Print Server
16. Install printer server using dedicated printer server
17. How to install printer using TCP/IP Port
18. Managing Remote Print Servers
19. Install, setup and manage Linux a file server, DHCP server and printer server
20. Installing Linux (make USB installer using DVD or ISO and save it to your USB Flash drive using
Rufus)
21. To Configure TPLINK Range Extender
22. To Set Up a Tenda Access Point as a Repeater
23. How to Configure TP-LINK N router as a wireless Access Point?
1|Page
COMPUTER SYSTEMS SERVICING NC 2 Mrs. Maybelle M. Regalado
1. Creating a bootable USB installer using Rufus

Things you will need:
1. Unit of Desktop PC with windows 7 Operating System.

2. Bootable ISO/Imageof Windows 7 ultimate, Windows Server 2008 R2 enterprise,
Linux OpeSUSE.
3. USB Flash Drive 8 GB (empty)
4. Rufus application software use to create bootable USB installer.
Procedure:
1. Connect your empty USB flash drive to your Computer where the Rufus and
ISO/Image saved.
2. Open the Rufus
2|Page
3. Select/Click the icon highlighted as shown below, which will let you browse for the
required ISO file.
Your USB Flash Drive
4. Select the ISO/Image. (Windows 7/Server 2008 r2 ISO/Linux)
5. Select the file by left clicking on it once and then clicking on Open.
3|Page
Rufus will now have filled out the fields

for you. All you have to do now is hit
Start.
Note, if you are using a USB stick that is

too small, like using a 4GB USB for an ISO
that is larger than 4GB you will get the
following error:
If your USB is the correct size then

you will get a standard warning
telling you that any data/partitions
that was on the USB before
starting the process will be
permanently deleted
6. Click OK, to start.
7. Click close, eject USB flash drive
4|Page
2. Create a bootable USB Flash Drive using the

diskpart utility
WARNING: All data on the USB flash drive will be lost, make sure you save in other
media any data before proceeding.
1. Insert your USB flash drive (8Gb + preferable) into your system
2. Navigate to the Command Prompt. Select Start and type CMD in the search
field, right click on CMD.exe and select Run as administrator
Alternatively, navigate to Start > All programs > Accessories > right click on
Command Prompt and select Run as administrator
3. A User Account Control (UAC) dialog Window may appear. Click Yes to Continue.
4. When the Command Prompt opens, enter the following commands followed
by Enter
5. DISKPART - This will start the utility
5|Page
6. LIST DISK - This will show the disk number of your USB flash drive. In the image
below the USB flash drive shows as Disk 2.
7. SELECT DISK X (Replace X with your USB flash drive number, we are using 2 in
this example)
8. CLEAN - This wipes the drive
9. CREATE PARTITION PRIMARY- Creates partition
10. SELECT PARTITION 1- Selects partition 1
11. ACTIVE- Marks the current partition as active
12. FORMAT FS=NTFS QUICK - This formats the partition
13. ASSIGN- Assigns a drive letter.
14. EXIT
Insert your Windows DVD into the optical drive.

From the command prompt, enter the following:
6|Page
g: <enter> (Where "g" is your DVD drive letter)

cd boot <enter> (changes to boot directory)
G:\boot bootsect /nt60 d: <enter> (Where "d" is your USB drive letter)
Copy all files from the Windows CD to the USB flash drive using xcopy
cd\ <enter>
G:\xcopy g:\*.* /s/h/f f:\ <enter>
This will copy the Windows installation files onto the USB flash drive, it may take
several minutes.
xcopy switches are as follows:
/s - Copies directories and subdirectories except empty ones.

/h - Copies hidden and system files.
/f - Displays full source and destination filenames while copying.
To display the full list of switches, type xcopy /? <enter>

This makes the USB drive bootable and when selected at startup, will boot straight into
the Windows installation.
7|Page
3. Installing Microsoft Windows Server 2008 R2 enterprise

About Windows Server 2008 R2
Windows Server 2008 R2 is a network operating system Microsoft, and

can be deployed in medium to large scale industries in order to allow
administrators to centrally manage the entire network setup right from a
single location. The main difference between a client operating system, such
as Microsoft Windows 8, Microsoft Windows 7, etc. and a network operating
system such as Microsoft Windows Server 2008 RTM/R2, Windows Server
2003 and Windows 2000 Server is that the network operating system (NOS)
has some additional server specific features integrated in it. These additional
features include:
 Active Directory Domain Services (AD DS)

 Dynamic Host Configuration Protocol (DHCP)
 Domain Name System (DNS)
 Active Directory Certificate Services (AD CS)
 Active Directory Federation Services (AD FS)
 Distributed File System (DFS)
 etc.
Although Windows Server 2008 R2 is a network operating system, it is

initially installed just as a normal client operating system, i.e. without any
additional server oriented services or features installed in it. In order to make
the installed network operating system work as a typical server, systems
administrators must install the server services and/or features according to
the role that they want the computer to play in the network.
System Requirements
Before installing Windows Server 2008 R2, the computer must meet the
following minimum system requirements
 1.4 GHz x86/x64 or Itanium 2 processor

 512 MB RAM (2 GB recommended)
 Super VGA or higher display
 32 GB disk space (10 GB for Foundation Edition)
 DVD drive
 Keyboard and pointing device
8|Page
Procedure:
Once the above discussed minimum system requirements are met,
administrators must follow the steps given below to install Windows Server
2008 R2:
1. Power on the computer on which Microsoft Windows Server 2008 R2 is to

be installed.
2. Enter into the BIOS setup to make the computer boot from DVD/from
USB.
3. Insert Microsoft Windows Server 2008 R2 bootable installation media.
(DVD/USB)
4. Once inserted, reboot the computer.
5. On the Install Windows screen, click Next.
Install Windows
6. On the next page, click Install now.

7. On Select the Operating System you want to install page, from the
displayed Windows Server 2008 R2 editions, select the appropriate edition
that is to be installed.
9|Page
Select Appropriate Edition
8. On the next page, type the 25-character product key and click Next.
9. On Please read the License terms page, check I accept the license
terms checkbox and click Next.
10. On Which type of installation do you want page, click Custom
(advanced).
Click Custom (Advance)
10 | P a g e
11. On Where do you want to install Windows page, ensure that the
hard disk drive on which Windows Server 2008 R2 is to be installed is
selected.
12. Once selected, click Drive options (advanced).
Click Drive Options
13. From the enabled options, click New to create a new disk drive
partition.
14. On the Size field, specify the size of the new volume in MB.
Specify Volume Size
11 | P a g e
15. On the displayed Install Windows message box, click OK.

16. Back on the same page, click to select the hard disk drive partition (E.
g.Disk 0 Partition 2, in this demonstration) where Windows Server 2008
R2 is to be installed and click Next.
Select Disk Partition
17. On the Installing Windowspage, wait till the Windows Server 2008
R2 installed and the computer get restarted.
Installing Windows
12 | P a g e
Note: Do not press any key if the screen displays the message, ‘Press any
key to boot from CD or DVD’ while computer restarts for the first time, to
resume the installation process.
18. After second restart, on the displayed screen, click OK to change the
user password before logging on for the first time.
19. On the available fields, type and retype the new password and
press Enter.
Change Password
20. On the next confirmation screen, click OK to log on to the Windows

Server 2008 R2 computer.
13 | P a g e
4. Assign Static IP Address (in Windows Server 2008 R2)

An IP address comprises of two sections namely network ID and host ID. In order to make
two computers in a local area network communicate with each other network IDs of the IP
addresses of both the computers must be common and each computer must have unique host
IDs. In case administrators assign common host IDs to two computers in a common subnet
(computers that have common network IDs), IP conflict occurs and none of the machines can then
communicate with the network.
Subnet mask (which also is a 32-bit number divided in 4 octal numbers and every octal is
separated by a period) is yet another important part in a complete IP address. At is subnet mask
that separates network ID of an IP address from its host ID. Technically, when talking about IP
addresses every IP address is only considered complete if it has its corresponding subnet mask.
While specifying static IP addresses to the computers when administrators type IP addresses in
their respective fields, fields of subnet masks automatically get populated according to the classes
to which the IP addresses belong. An example of IP address and its corresponding subnet mask
can be:
IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
List given below shows the classes of IP addresses according to their first octal numbers and the
default subnet mask for each class:
 Class A – IP Address: 0-126, Default Subnet Mask: 255.0.0.0

 Class B – IP Address: 128-191, Default Subnet Mask: 255.255.0.0
 Class C – IP Address: 192-223, Default Subnet Mask: 255.255.255.0
 Class D – IP Address: 224-239, Default Subnet Mask: N/A
 Class D – IP Address: 240-255, Default Subnet Mask: N/A
(Note: 127 is a loopback address and therefore cannot be assigned to any computer as its unique
IP address.)
14 | P a g e
The very first octal number of an IP address specifies the class to which the IP address
belongs. In an example given above, since the first octal number of the IP address is 192, it
belongs to Class C and therefore it has 255.255.255.0 as its default subnet mask.
Procedure in assigning a Static IP Address

Assigning a static IP address to a
computer requires elevated privileges and
therefore administrator account must be used to
log on to Windows Server 2008 R2 computer
while following the steps below:
1. Log on to Windows Server 2008 R2

computer with Administrator account.
2. Click Start and then click Run from the
menu.
3. In the opened Run command box type
NCPA.CPL command and press Enter
key.
4. On the opened window right-click on
the NIC on which static IP address has to be assigned and from the available context menu
click Properties.
5. On Local Area Network Properties box make sure that Networking tab is selected and
from the available list of options in the middle box double-click Internet Protocol
Version 4 (TCP/IPv4).
6. On Internet Protocol Version 4 (TCP/IPv4) Properties box make sure that General tab
is selected and click to select Use the following IP address radio button.
7. Populate the enabled IP address and Subnet mask fields with appropriate values, i.e. IP
address and subnet mask and click OK button.
8. Back on Local Area Connection Properties box click OK to save the changes.
15 | P a g e
5. Installing Active Directory Domain Services on

Windows Server 2008 R2 Enterprise 64-bit
(This will also assign static IP address if the above procedure does not performed)
Note: “Disable the DHCP server of the router before you proceed”.
This will also assign static IP address disregard the above
procedure if you will follow this procedure.
Prepare for Active Directory
Before you install AD DS on a Rackspace Cloud Server running Windows Server

2008 R2 Enterprise 64-bit (W2K8), you must perform the following prerequisite tasks.
Select Domain Name and Password
Select your domain name and know the domain administrator password that you want to
use.
Note: Your domain name should be reliably unique. Do not use the same domain as
your website, for example, and avoid extensions like “.local” unless you have registered
that domain name in DNS. We suggest a domain name that is not used for anything
else, like "internal.example.com"..
Specify the Preferred DNS Server
Windows Server 2008 can properly install and configure DNS during the AD DS
installation if it knows that the DNS is local. You can accomplish this by having the
private network adapter’s preferred DNS server address point to the already assigned IP
address of the same private network adapter, as follows:
1. From the Windows Start menu, open Administrative Tools > Server Manager.
2. In the Server Summary section of the Server Manager window, click View
Network Connections.
16 | P a g e
3. In the Network Connections window, right-click the private adapter and

select Properties.
4. Select Internet Protocol Version 4, and then click Properties.
17 | P a g e
5. Copy the IP address that is displayed in the IP address box and paste it into
the Preferred DNS server box. Then, click OK.
6. Click OK in the Properties dialog box, and close the Network Connections
window.
NOTE: The last step for prepping W2K8 for AD is adding the proper Server Role.
The “Active Directory Domain Services” Role will be added. This only
installs the framework for W2K8 to become a DC and run AD. It does not
promote the server to DC or install AD.
18 | P a g e
6. Add the Active Directory Domain Services Role

(DCPROMO)
Adding the Active Directory Domain Services role installs the framework for Windows
Server 2008 to become a DC and run AD DS. It does not promote the server to a DC or
install AD DS.
1. In the Server Manager window, open the Roles directory and in the Roles
Summary section, click Add Roles
2. On the Before You Begin page of the Add Roles Wizard, click Next.
3. On the Select Server Roles page, select the Active Directory Domain
Services check box, and then click Next on this page and on the Confirmation
page.
19 | P a g e
4. On the Installation Progress page, click Install.
20 | P a g e
5. On the Results page, after the role is successfully added, click Close.
Enable the Remote Registry
1. Open the Server Manager window if it is not already open.

2. In the Properties area of the Local Servers page, click Remote Management.
3. Select the Enable remote management of this server from other
computers check box.
Install Active Directory Domain Services (DCPROMO)
Now that you have prepared the server, you can install AD DS.
Tip: As an alternative to performing steps 1 through 3, you can type dcpromo.exe at the
command prompt. Then, skip to step 4.
1. If it is not already open, open the Server Manager window.

2. Select Roles > Active Directory Domain Services.
3. In the Summary section, click Run the Active Directory Domain Services
Installation Wizard (dcpromo.exe).
21 | P a g e
4. On the Welcome page of the Active Directory Domain Services Installation

Wizard, ensure that the Use advanced mode installation check box is cleared,
and then click Next.
22 | P a g e
5. On the Operating System Capability page, click Next.
6. On the Choose a Deployment Configuration page, select Create a new domain

in a new forest and then clickNext.
23 | P a g e
7. On the Name the Forest Root Domain page, enter the domain name that you
choose during preparation steps. Then, click Next.
8. After the installation verifies the NetBIOS name, on the Set Forest Functional
Level page, select Windows Server 2008 R2 in the Forest function level list.
Then, click Next.
24 | P a g e
The installation examines and verifies your DNS setting.
9. On the Additional Domain Controller Options page, ensure that the DNS
server check box is selected, and then click Next.
10. In the message dialog box that appears, click Yes.
25 | P a g e
11. On the Location for Database, Log Files, and SYSVOL page, accept the default
values and then click Next.
12. On the Directory Services Restore Mode Administrator Password page, enter the
domain administrator password that you chose during the preparation steps. This
is not your admin password that was emailed to you during the creation of your
server, although you can use that password if you want to. Then, click Next.
26 | P a g e
13. On the Summary page, review your selections and then click Next.
The installation begins.
14. If you want the server to restart automatically after the installation is completed,
select the Reboot on completion check box.
15. If you did not select the Reboot on completion check box, click Finish in the
wizard. Then, restart the server.
27 | P a g e
16. After a few minutes, reconnect to your server by using the Console in your Control
Panel or RDP.
17. To log in, perform the following steps:
a. Click Switch User, and then click Other User.
b. For the user, enter the full domain name that you chose, followed by a back
slash and Administrator (for example, Example.com\Administrator).
c. Enter the password that was emailed to you when you first built the server. If
you changed your password
for the local admin account to this server before you began the installation
of Active Directory Domain Services, use that password.
d. Click the log in button.
The installation of Active Directory Domain Services on your server is complete.
28 | P a g e
7. Installing DHCP Server on

Windows Server 2008 R2
About Dynamic Host Configuration Protocol (DHCP) Server
A Dynamic Host Configuration Protocol (DHCP) server is a computer that

has Windows Server 2008 R2 installed on it, and is responsible for assigning
IP addresses to the computers automatically. IP addresses assigned to the
computers by DHCP server are known as dynamic IP addresses, and the
computers that are configured to obtain the IP addresses automatically from
the DHCP server are called DHCP client computers.
During DHCP server configuration, administrators specify a range of IP

addresses in the DHCP scope. All IP addresses that fall within the specified
range are stored in IP Address Pool. Every time a DHCP client computer
requests an IP address from a DHCP server, the server randomly picks up any
one of the available IP addresses from its address pool and assigns it to the
requesting client computer. This process is known as dynamic IP address
assignment.
Dynamic Host Configuration Protocol (DHCP) IP Address

Assignment Process
The process of IP address assignment completes in four steps called DORA

where D represents DHCP Discover, O represents DHCP Offer, R represents
DHCP Request and A represents DHCP Acknowledge. Description of DORA is
as below:
1. DHCP Discover – DHCP Discover is a broadcast packet that is sent from a DHCP client
computer. DHCP Discover packet is broadcasted to search for all available DHCP servers
in the network. Since it is a broadcast packet, it is received by all the computers
connected to the network (including all available DHCP servers) without exceptions.
2. DHCP Offer – DHCP Offer is a unicast packet that is sent from the DHCP server to the
requesting DHCP client computer in response to the received broadcasted DHCP Discover
packet. DHCP Offer packet contains an available IP address from the address pool,
offering it to the requesting DHCP client computer.
29 | P a g e
3. DHCP Request – DHCP Request is a unicast packet sent from a DHCP client computer to
a DHCP server from which it has received DHCP Offer packet. DHCP client computer
sends DHCP Request packet requesting the DHCP server to assign the offered IP address.
4. DHCP Acknowledge – DHCP Acknowledge is a unicast packet sent from the DHCP
server to the DHCP client computer confirming the successful assignment of the
requested IP address.
Prerequisites for Installing DHCP Server Role
Before DHCP server role is installed on a Windows Server 2008 R2 computer,

administrators must verify that:
 The computer that is to be configured as DHCP server has been assigned with a static
IP address.
 A DNS zone has been created on any network operating system in the network if no
domain controller is present.
Procedure in DHCP server in Windows Server 2008 R2
To install and configure Dynamic Host Configuration Protocol (DHCP) on

Windows Server 2008 R2, administrators must follow the steps given as
below:
1. Log on to Windows Server 2008 R2 computer with the domain administrator or enterprise
administrator account credentials on which DHCP server is to be installed and configured.
2. Make sure that the computer has been assigned with a static IP address.
3. Ensure that the DNS server is available anywhere in the network and is properly
configured.
4. On the desktop screen, click Server Manager icon from the taskbar.
5. On the Server Manager window, from the console tree in the left, make sure
that Roles option is selected.
6. On the right pane, make sure that the Roles Summary section is expanded.
7. From the expanded section, click Add Roles.
30 | P a g e
Click Add Roles
8. On Add Roles Wizard window, click Next.

9. On Select Server Roles page, from the Roles list, check DHCP Servercheckbox and
click Next.
Check DHCP Server Checkbox
31 | P a g e
10. On the DHCP Server page, click Next.

11. On Select Network Connection Bindings page, make sure that the IP address
representing the network connection that is to be bound is checked from the Network
Connectionslist.
Select Network Connection
12. Click Next to continue.

13. On Specify IPv4 DNS Server Settings page, populate the Preferred DNS serer IPv4
address and optional Alternate DNS server IPv4 addressfields with the correct
values.
14. Once specified, click Validate to confirm the availability of DNS server and click Next.
32 | P a g e
Specify DNS Server
15. On Specify IPv4 WINS Server Settings page, leave everything as default and
click Next.
16. On Add or Edit DHCP Scopes page, click Add.
17. On Add Scope box, populate the Scope name, Starting IP address, andEnding IP
address fields with the desired values and click OK.
33 | P a g e
Add Scope
18. Back on Add or Edit DHCP Scope page, click Next.

19. On Configure DHCPv6 Stateless Mode page, leave everything as default and
click Next.
20. On Specify IPv6 DNS Server Settings page, leave everything as default (assuming
that the network setup doesn’t have IPv6 addressing scheme) and click Next to proceed.
21. On Authorize DHCP Server page, make sure that the Use current credentials radio
button is selected. Alternatively, Use alternate credentialsradio button can also be
selected to specify the domain admin credentials that is to be allowed to authorize DHCP
server in AD DS.
34 | P a g e
Authorize DHCP
Note:Authorize DHCP Server page will be displayed only when an
Active Directory Domain Controller is present in the network.
In case the Active Directory Domain Controller is absent, the page

is
not displayed.
22. Click Next to proceed.

23. On Confirm Installation Selections page, review the settings and clickInstall to start
the DHCP installation and configuration process.
24. Once installed, click Close on the Installation Results page.
25. Close Server Manager window when done.
35 | P a g e
8. Create New User Account in Active Directory

1. To start let’s go ahead and open up Server Manager
2. Next we will open up the Roles section, next to Active Directory Users and
Computers section and finally the Active Directory Users and Computers. You
should now see your domain name.
36 | P a g e
3. We are going to click on our Users section where we are going to create a new
User Account. To do so, right-click on the blank section, point to New and
select User.
37 | P a g e
4. In this window you need to type in the user’s first name, middle initial and last name.
Next you will need to create a user’s logon name.
In our example we are going to create a user account for Billy Miles and his logon name
will be bmiles. When done, click on the Next button.
38 | P a g e
5. In the next window you will need to create a password for your new user and select
appropriate options.
In our example we are going to have the user change his password at his next logon.
You can also prevent a user from changing his password, set the password so that it will
never expire or completely disable the account.
When you are done making your selections, click the Next button.
39 | P a g e
Select this option
6. And finally, click on the Finish button to complete the creation of new User Account.
40 | P a g e
9. To Create a User Template in Active Directory

A user template in Active Directory will make your life a little easier, especially if you are
creating users for a specific department, with exactly the same properties, and
membership to the same user groups. A user template is nothing more than a disabled
user account that has all these settings already in place. The only thing you are doing is
copying this account, adding a new name and a password.
You may have multiple user templates for multiple purposes with different settings and
properties. There is no limit on the number of user templates, but keep in mind that they
are there to help you, not to confuse you, so keep in mind less is better.
To create a user template, we are going to create a regular user account just like we did
above. A little note here, you may want to add an * as the first character of the name so it
floats at the top in AD and is much easier to find.
1. To start out, right-click on the empty space, point to new, and select User.
2. Type in the user’s name (with asterisks if so desired) and click Next.
41 | P a g e
3. Create the template’s password and do not forget to check the box next to
the Account is disabled option. When ready, click Next.
42 | P a g e
4. Once the account is created, you can go ahead and add all the properties you need for
that template. To do so, double-click on that account and navigate to a specific tab. Once
done click OK.
43 | P a g e
How to Use a User Template in Active Directory

1. Now in order to use that user template, we are going to select it, copy it and add the
unique information such as user name, password, etc.
We can do that for as many users as needed. Let’s start by right-clicking on the template
and selecting Copy.
2. Next we are going to enter the user’s name, login and password information while
making sure the checkbox next to Account is disabled is unchecked.
44 | P a g e
4. Once we finish, our new user account is created with all the properties of the
template account. Now wasn’t that easy!
45 | P a g e
10. Group Policy in Windows 2008 Server R2

Overview of Group Policy
Group Policy is simply the easiest way to reach out and configure computer and user settings on
networks based on Active Directory Domain Services (AD DS). If your business is not using Group
Policy, you are missing a huge opportunity to reduce costs, control configurations, keep users
productive and happy, and harden security. Think of Group Policy as “touch once, configure
many.”
The requirements for using Group Policy and following the instructions that this white paper
provides are straightforward:
The network must be based on AD DS (that is, at least one server must have the AD DS role
installed). To learn more about AD DS, see Active Directory Domain Services Overview on TechNet.
Computers that you want to manage must be joined to the domain, and users that you want to
manage must use domain credentials to log on to their computers.
You must have permission to edit Group Policy in the domain.
Although this white paper focuses on using Group Policy in AD DS, you can also configure Group
Policy settings locally on each computer. This capability is great for one-off scenarios or workgroup
computers, but using local Group Policy is not recommended for business networks based on AD
DS. The reason is simple: Domain-based Group Policy centralizes management, so you can touch
many computers from one place. Local Group Policy requires that you touch each computer—not
an ideal scenario in a large environment. For more information about configuring local Group
Policy, see Local Group Policy Editor on TechNet.
Windows 7 enforces the policy settings that you define by using Group Policy. In most cases, it
disables the user interface for those settings. Additionally, because Windows 7 stores Group Policy
settings in secure locations in the registry, standard user accounts cannot change those settings.
So, by touching a setting one time, you can configure and enforce that setting on many computers.
When a setting no longer applies to a computer or user, Group Policy removes the policy setting,
restoring the original setting and enabling its user interface. The functionality is all quite amazing
and extremely powerful.
46 | P a g e
Essential Group Policy Concepts
You can manage all aspects of Group Policy by using the Group Policy Management Console
(GPMC). Figure 1 shows the GPMC, and this white paper will refer to this figure many times as you
learn about important Group Policy concepts.
Figure1. Group Policy Management Console
You start the GPMC from the Start menu: Click Start, All Programs, Administrative Tools, Group
Policy Management. You can also click Start, type Group Policy Management, and then click Group
Policy Management in the Programs section of the Start menu. Windows Server 2008 and
Windows Server 2008 R2 include the GPMC when they are running the AD DS role. Otherwise, you
can install the GPMC on Windows Server 2008, Windows Server 2008 R2, or Windows 7 as
described in the section “Installing the GPMC in Windows 7,” later in this white paper.
Group Policy objects
GPOs contain policy settings. You can think of GPOs as policy documents that apply their settings
to the computers and users within their control. If GPOs are policy documents, then the GPMC is
like Windows Explorer. You use the GPMC to create, move, and delete GPOs just as you use
Windows Explorer to create, move, and delete files.
In the GPMC, you see all the domain’s GPOs in the Group Policy objects folder. In Figure 1, the
callout number 1 shows three GPOs for the domain corp.contoso.com domain. These GPOs are:
Accounting Security. This is a custom GPO created specifically for Contoso, Ltd.
Default Domain Controller Policy. Installing the AD DS server role creates this policy by default. It
contains policy settings that apply specifically to domain controllers.
47 | P a g e
Default Domain Policy. Installing the AD DS server role creates this policy by default. It contains
policy settings that apply to all computers and users in the domain.
Group Policy Links
At the top level of AD DS are sites and domains. Simple implementations will have a single site and
a single domain. Within a domain, you can create organizational units (OUs). OUs are like folders
in Windows Explorer. Instead of containing files and subfolders, however, they can contain
computers, users, and other objects.
For example, in Figure 1 you see an OU named Departments. Below the Departments OU, you see
four subfolders: Accounting, Engineering, Management, and Marketing. These are child OUs.
Other than the Domain Controllers OU that you see in Figure 1, nothing else in the figure is an OU.
What does this have to do with Group Policy links? Well, GPOs in the Group Policy objects folder
have no impact unless you link them to a site, domain, or OU. When you link a GPO to a container,
Group Policy applies the GPO’s settings to the computers and users in that container. In Figure 1,
the callout number 1 points to two GPOs linked to OUs:
The first GPO is named Default Domain Policy, and this GPO is linked to the domain
corp.contoso.com. This GPO applies to every computer and user in the domain.
The second GPO is named Accounting Security, and this GPO is linked to the OU named
Accounting. This GPO applies to every computer and user in the Accounting OU.
In the GPMC, you can create GPOs in the Group Policy objects folder and then link them—two
steps. You can also create and link a GPO in one step. Most of the time, you will simply create and
link a GPO in a single step, which the section “Creating a GPO,” later in this white paper, describes.
Group Policy Inheritance
As the previous section hinted, when you link a GPO to the domain, the GPO applies to the
computers and users in every OU and child OU in the domain. Likewise, when you link a GPO to
an OU, the GPO applies to the computers and users in every child OU. This concept is called
inheritance.
For example, if you create a GPO named Windows Firewall Settings and link it to the
corp.contoso.com domain in Figure 1, the settings in that GPO apply to all of the OUs you see in
the figure: Departments, Accounting, Engineering, Management, Marketing, and Domain
48 | P a g e
Controllers. If instead you link the GPO to the Departments OU, the settings in the GPO apply
only to the Departments, Accounting, Engineering, Management, and Marketing OUs. It does not
apply to the entire domain or the Domain Controllers OU. Moving down one level, if you link the
same GPO to the Accounting OU in Figure 1, the settings in the GPO apply only to the Accounting
OU, as it has no child OUs. In the GPMC, you can see what GPOs a container is inheriting by
clicking the Group Policy Inheritance tab (callout number 1 in Figure 2).
Figure 2. Group Policy inheritance and precedence
So, what happens if multiple GPOs contain the same setting? This is where order of precedence
comes into play. In general, the order in which Group Policy applies GPOs determines
precedence. The order is site, domain, OU, and child OUs. As a result, GPOs in child OUs have a
higher precedence than GPOs linked to parent OUs, which have a higher precedence than GPOs
49 | P a g e
linked to the domain, which have a higher precedence than GPOs linked to the site. An easy way
to think of this is that Group Policy applies GPOs from the top down, overwriting settings
along the way. In more advanced scenarios, however, you can override the order of precedence.
You can also have—within a single OU—multiple GPOs that contain the same setting. Like
before, the order in which Group Policy applies GPOs determines the order of precedence. In
Figure 2, you see two GPOs linked to the domain corp.contoso.com: Windows Firewall Settings
and Default Domain Policy. Group Policy applies GPOs with a lower link order after applying
GPOs with a higher link order. In this case, it will apply Windows Firewall Settings after Default
Domain Policy. Just remember that a link order of 1 is first priority, and a link order of 2 is second
priority. You can change the link order for a container by clicking the up and down arrows as
shown by callout number 2 in Figure 2.
Group Policy Settings
To this point, you have learned about GPOs. You have learned that GPMC is to GPOs and OUs as
Windows Explorer is to files and folders. GPOs are the policy documents. At some point, you are
going to have to edit one of those documents, though, and the editor you use is the Group Policy
Management Editor (GPME), which Figure 3 shows. You open a GPO in the GPME by right-
clicking it in the GPMC and clicking Edit. Once you are finished, you simply close the window. The
GPME saves your changes automatically, so you do not have to save.
Figure 3. Group Policy Management Editor
In Figure 3, callout numbers 1 and 2 point to Computer Configuration and User Configuration,
respectively. The Computer Configuration folder contains settings that apply to computers,
50 | P a g e
regardless of which users log on to them. These tend to be system and security settings that
configure and control the computer. The User Configuration folder contains settings that apply
to users, regardless of which computer they use. These tend to affect the user experience.
Within the Computer Configuration and User Configuration folders, you see two subfolders
(callout numbers 3 and 4 in Figure 3):
Policies.Policies contain policy settings that Group Policy enforces.
Preferences.Preferences contains preference settings that you can use to change almost any
registry setting, file, folder, or other item. By using preference settings, you can configure
applications and Windows features that are not Group Policy–aware. For example, you can
create a preference setting that configures a registry value for a third-party application, deletes
the Sample Pictures folder from user profiles, or configures an .ini file. You can also choose
whether Group Policy enforces each preference setting or not. However, standard user accounts
can change most preference settings that you define in the User Configuration folder between
Group Policy refreshes. You can learn more about preference settings by reading the Group
Policy Preferences Overview.
When you are first learning Group Policy, most of the settings that you will configure will be in
the Administrative Templates folders. These are registry-based policy settings that Group Policy
enforces. They are different from other policy settings for two reasons. First, Group Policy stores
these settings in specific registry locations, called the Policies branches, which standard user
accounts cannot change. Group Policy–aware Windows features and applications look for these
settings in the registry. If they find these policy settings, they use the policy settings instead of
the regular settings. They often disable the user interface for those settings as well.
Second, administrative template files, which have the .admx extension, define templates for
these settings. These templates not only define where policy settings go in the registry but also
describe how to prompt for them in the GPME. In the Group Policy setting that Figure 4 shows,
for example, an administrative template file defines help text, available options, supported
operating systems, and so on.
51 | P a g e
Figure 4. Group Policy setting
When you edit a policy setting, you are usually confronted with the choices that callout numbers
1 to 3 indicate in Figure 4. In general, clicking:
Enabled writes the policy setting to the registry with a value that enables it.
Disabled writes the policy setting to the registry with a value that disables it.
Not Configured leaves the policy setting undefined. Group Policy does not write the policy
setting to the registry, and so it has no impact on computers or users.
Generalizing what enabled and disabled means for every policy setting is not possible. You can
usually read the help text, shown in callout number 5, to determine exactly what these choices
mean. You must also be careful to read the name of the policy setting. For example, some policy
settings say, “Turn on feature X,” whereas other policy settings say, “Turn off feature Y.” Enabled
and disabled have different meanings in each case. Until you are comfortable, make sure you
read the help text for policy settings you configure.
52 | P a g e
Some policy settings have additional options that you can configure. Callout number 4 in Figure 4
shows the options that are available for the Group Policy refresh interval policy setting. In most
cases, the default values match the default values for Windows. As well, the help text usually
gives detailed information about the options you can configure.
Group Policy Refresh
As you learned in the previous section, GPOs contain both computer and user settings. Group
Policy applies: Computer settings when Windows starts. User settings after the user logs on to
the computer.
Group Policy also refreshes GPOs on a regular basis, ensuring that Group Policy applies new and
changed GPOs without waiting for the computer to restart or the user to log off. The period of
time between these refreshes is called the Group Policy refresh interval, and the default is 90
minutes with a bit of randomness built in to prevent all computers from refreshing at the same
time. If you change a GPO in the middle of the day, Group Policy will apply your changes within
about 90 minutes. You don’t have to wait until the end of the day, when users have logged off of
or restarted their computers. In advanced scenarios, you can change the default refresh interval.
Essential Group Policy Tasks
You have now learned the essential Group Policy concepts. You know that a GPO is like a
document that contains policy settings. You manage GPOs by using the GPMC and you edit them
by using the GPME.
You also know that you link GPOs to AD DS sites, domains, and OUs to apply the GPOs’ settings
to those containers. Domains, OUs, and child OUs inherit settings from their parents, but
duplicate settings in GPOs linked to child OUs have precedence over the same settings in GPOs
linked to parent OUs, which have precedence over GPOs linked to the domain, and so on.
You also know that within a site, domain, or OU, the link order determines the order of
precedence (the smaller the number, the higher the precedence). Last, you have an essential
understanding of how to edit GPOs and what types of settings they contain.
Now that you know the essential concepts, you are ready to learn the essential tasks. This
section describes how to create, edit, and delete GPOs. It describes many other tasks, as well.
For each task, you’ll find an explanation of its purpose and step-by-step instructions with
screenshots at each step.
53 | P a g e
Creating a GPO
You create a GPO by using the GPMC. There are two ways to create a GPO:
Create and link a GPO in one step.
Create a GPO in the Group Policy objects folder, and then link it to the domain or OU.
The instructions in this section describe how to create and link a GPO in one step.
You can start with a blank GPO, which the instructions describe, or you can use a starter GPO.
Starter GPOs are an advanced topic that you can learn about in Working with Starter GPOs.
To create and link a GPO in the domain or an OU
In the GPMC, right-click the domain

or OU in which you want to create
and link a GPO, and click Create a
GPO in this domain, and Link it
here.
In the Name box on the New

GPO dialog box, type a descriptive
name for the GPO, and then
click OK.
54 | P a g e
Editing a GPO
In the GPMC, you can open GPOs in the GPME to edit them within any container. To see all of
your GPOs, regardless of where you link them, use the Group Policy objects folder to edit them.
To edit a GPO in the domain, an OU, or the Group Policy objects folder
In the left pane of the GPMC, click Group

Policy objects to display all the domain’s
GPOs in the right pane. Alternatively, you
can click the domain or any OU to display
that container’s GPOs in the right pane.
In the right pane of the GPMC, right-click

the GPO that you want to edit, and
click Edit to open the GPO in the GPME.
55 | P a g e
In the GPME, edit the Group Policy settings

that you want to change, and close the
GPME window when finished. You do not
have to save your changes, because the
GPME saves your changes automatically.
Linking a GPO
If you create and link GPOs in one step, you do not have to manually link GPOs to the domain or
OUs. However, if you create a GPO in the Group Policy objects folder or unlink a GPO and want
to restore it, you will need to manually link the GPO. The easy way to link a GPO is to simply drag
the GPO from the Group Policy objects folder and drop it onto the domain or OU to which you
want to link it.
To link a GPO to a domain or OU
56 | P a g e
In the GPMC, right-click the domain or OU

to which you want to link the GPO, and then
click Link an Existing GPO.
In the Select GPO dialog box, click the GPO

that you want to link to the domain or OU,
and then click OK.
Updating Clients
While editing, testing, or troubleshooting GPOs, you do not need to wait for the Group Policy
refresh interval (90 minutes, by default). You can manually update Group Policy on any client
computer by running Gpupdate.exe. Gpupdate.exe supports many command-line options, which
you can learn about by typing gpupdate.exe /? in a Command Prompt windows In most cases,
however, you can follow the instructions in this section to update Group Policy.
To manually update Group Policy by using Gpupdate.exe
57 | P a g e
Click Start, type cmd, and press Enter to

open a Command Prompt window.
At the Command Prompt, type gpupdate

and press Enter. Gpupdate.exe will update
any changed settings. You can force
Gpupdate.exe to update all settings,
whether or not they have changed recently,
by typing gpupdate /force and pressing
Enter.
58 | P a g e
11. FOLDER REDIRECTION

On Server PC
1. Create Folder on drive C:\
2. Rename the Folder (Example: Shared Files)

3. Right click on folder, click properties
59 | P a g e
4. Click sharing, Click advance sharing
60 | P a g e
5. Check share this folder, click apply, click ok

6. Copy the net path (\\WIN-MK0008AD2KT\Shared Files)
61 | P a g e
7. Click close
8. Close Local disk C:\
9. Click start
10. Point to Administrative Tool
11. Go to Group Policy Management
62 | P a g e
12. Under Group Policy Management go to Forest

13. Go to Domain
14. Go to local user (example: oloroso.local)
15. Right click on default domain policy, click Edit
63 | P a g e
16. Under user configurations, click policies

17. Click windows settings
18. Click folder Redirection
64 | P a g e
19. Right click on Desktop, click properties.
65 | P a g e
20. Under desktop properties, go to setting.

21. Uncheck “grant the user exclusive rights to desktop.
22. Click apply, click yes.
66 | P a g e
67 | P a g e
68 | P a g e
12. Configuring Primary Computers for

Folder Redirection and
Roaming Profiles in Windows Server
Introduction
In Windows Server, administrators can designate a set of computers, known as primary
computers, for each domain user, which controls which computers use Folder Redirection,
Roaming User Profiles, or both. Designating primary computers is a simple and powerful method
to associate user data and settings with particular computers or devices, simplify administrator
oversight, improve data security, and help protect user profiles from corruption.
There are four major benefits to designating primary computers for users:
 The administrator can specify which computers users can use to access their redirected data and
settings. For example, the administrator can choose to roam user data and settings between a
user’s desktop and laptop, and to not roam the information when that user logs on to any other
computer, such as a conference room computer.
 Designating primary computers reduces the security and privacy risk of leaving residual personal
or corporate data on computers where the user has logged on. For example, a general manager
who logs on to an employee’s computer for temporary access does not leave behind any personal
or corporate data.
 Primary computers enable the administrator to mitigate the risk of an improperly configured or
otherwise corrupt profile, which could result from roaming between differently configured
systems, such as between x86-based and x64-based computers.
 The amount of time required for a user’s first sign-in on a non-primary computer is faster because
the user’s roaming user profile and/or redirected folders are not downloaded. Sign-out times for
roaming user profile users on non-primary computers are also reduced, because changes to the
user profile do not need to be uploaded to the file share.
69 | P a g e
Overview of this document
This post describes the steps I took to set up a user with Folder Redirection and assign primary
computers, so that you can experiment with this new technology yourself. The post does not
include details on how to set up a domain controller or a domain. The audience of this document
is expected to have an existing file server, domain controller, and clients setup or be able to set
these up independently.
70 | P a g e
Installation Steps
Prerequisites
You need only a single computer (the specs are provided below) and the ISO files for the Windows
Server and Windows 7 /8 Consumer Preview, both of which are available as free downloads.
You will need a computer that meets the following requirements:
 Meets the minimum system requirements for Windows Server “8” Beta and Hyper-V
 Has at least 4 GB of RAM
You need to provision virtual machines for:
 Domain Controller (Windows Server )

 File Server (Windows Server )
 Primary Client (Windows 8 Consumer Preview)
 Other (non-primary) Client ((Windows 8 Consumer Preview)
provisioned three virtual machines:
 One domain controller that also functions as a file server. I named this server PMDemo and
named the domain dPMDemo.
 Two clients, which I named PMClient1 and PMClient2. Both clients are joined to the dPMDemo
domain. PMClient1 will be designated as the demo user’s primary computer.
 I assigned 1.5GB RAM to each of the VMs. If you have less memory on your host computer, I
would recommend provisioning enabling Dynamic Memory with a Startup RAM value of at least
1GB for the domain controller / file server and 1GB each for the two clients.
 All VMs are connected to the ‘External network’ virtual network switch that is connected to the
physical network interface card (NIC) of the computer.
71 | P a g e
Setting up Folder Redirection
Create a file share for user data
To create a file share for user data, use the following procedure on the domain controller/file
server.
 Create a folder named C:\Share.

 Right-click the folder you created, point to Share with and then click Specific people.
 Type Everyone, click Add, and then click Share.
Alternatively, you can add Authenticated Users or any security group with all users to which the
Folder Redirection policy will apply as long as the users have Read/Write access to the file share.
72 | P a g e
Create a new user
To create a new user, use the following procedure on the domain controller.
 Open the Active Directory Users and Computers MMC snap-in.

 In the console tree, right-click Users, point to New and then click User.
 In the New Object – User dialog box, create a new user named Bob Smith.
73 | P a g e
 Assign a password, clear the User must change password at next logon check box, and then
select the Password never expirescheck box.
Create a new group policy object
To create a new GPO for Folder Redirection and primary computer support, use the following
procedure on the domain controller.
 Open the Group Policy Management MMC snap-in.

 In the console tree, right-click Group Policy Objects. Click New to create a new group policy
object.
74 | P a g e
 In the Name box, type Folder Redirection and Primary Computer and click OK.
 In the Security Filtering section, remove Authenticated Users and target the GPO to user Bob
Smith.
75 | P a g e
Configure Folder Redirection
To set up Folder Redirection for Bob Smith, use the following procedure.
 Right-click the Folder Redirection and Primary Computer GPO and then click Edit.
The Group Policy Management Editor opens.
 In the console tree, expand User Configuration, then Policies, Windows Settings, and then Folder
Redirection.
 Right-click Documents, and then click Properties.
76 | P a g e
 Choose Basic – Redirect everyone’s folder to the same location from the Setting list.
 In the Root Path box, and specify the root path to the file share created in step 2.2.1 and then
click OK. In my demo, the share is \\PMDemo\Share.
2.2.5 Link the GPO to your domain
To link the GPO to your domain, use the following procedure on your domain controller.
 In the Group Policy Management console, right-click the domain created for this demo (in my
case, dPMDemo), and then clickLinkan Existing GPO.
77 | P a g e
 Click Folder Redirection and Primary Computer and then click OK.
Test the Folder Redirection setup
78 | P a g e
At this point, the Folder Redirection setup is complete. If you’d like to test it out, sign in as Bob
Smith onPMClient1. Ensure that Folder Redirection successfully applies for Bob Smith, as shown
in step 2.4.1 below.
It is possible that you may have to reapply group policy on the client computer in order for
Folder Redirection to apply. To do so, sign in as Bob Smith, open a command prompt window
and then type Gpupdate /force. After signing out and then signing back in, the Folder
Redirection policy should apply.
Setting up primary computers
Designate a Primary Computer in Active Directory
Designate a primary computer by using Active Directory Administrative Center
To designate a primary computer in Active Directory Domain Services (AD DS), use the following
procedure.
 Open Active Directory Administrative Center.

 In the console tree, under the domain name node (dPMDemo in my case), click Computers.
 To designate PMClient1 as Bob Smith’s primary computer, double click PMClient1, and then in
the Extensions section, click theAttribute Editor tab.
79 | P a g e
 Double-click the distinguished Name attribute, right-click the value and then click Copy.
 In Active Directory Administrative Center, click Users, and then double-click Bob Smith. In
the Extensions section, click theAttribute Editor tab.
80 | P a g e
 Double-click the msDS-Primary Computer attribute, paste the distinguished name of PMClient1
into the Value to Add box, and then click Add.
You can specify a list of computer names in the Value to Add box; each listed computer will be
designated as a primary computer for the user.
 Click OK in the Multi-valued String Editor dialog and again in the Bob Smith window.PMClient1 is
now configured in AD DS as a primary computer for Bob Smith.
Designate a primary computer by using Windows PowerShell
To use Windows Powershell to designate a primary computer in AD DS, use the following
procedure.
 Open a Windows PowerShell window on the domain controller.

 To retrieve the computer properties, including the distinguished name, of the primary computer,
type the following command:
PS C:\Users\Administrator> $computer=Get-ADComputer PMClient1
81 | P a g e
 To setup the user – primary computer partnership for user Bob Smith, type the following
command:
PS C:\Users\Administrator> Set-ADUserbobsmith –Add @{‘msDS-PrimaryComputer’=”$computer”}
 To check if the partnership was correctly set up, type the following command:
PS C:\Users\Administrator> Get-ADUserbobsmith –Properties msDS-PrimaryComputer
During the setup, if you’d like to remove the user-primary computer partnership for user Bob
Smith, type the following command:
PS C:\Users\Administrator> Set-ADUserbobsmith –Remove @{‘msDS-PrimaryComputer’=”$computer”}
You can use the Windows PowerShell cmdlets published here to configure primary computer
preferences in Active Directory.
Configure Folder Redirection policy to apply to primary computers
To enable primary computer support for Folder redirection, use the following procedure on the
domain controller.
 In the Group Policy Management console, right-click Folder Redirection and Primary
Computer and then click Edit.
Group Policy Management Editor appears.
 In the console tree, expand User Configuration, then Policies, Administrative Templates, System,
and then Folder Redirection.
82 | P a g e
 Double-click Redirect folders on primary computers only, click Enabled, and then click OK.
At this point, all steps to configure primary computers for the user are complete.
83 | P a g e
Testing primary computers
Sign on to a primary computer using the Bob Smith account
To test the experience of using a primary computer, use the following procedure on the
PMClient1 computer.
 Use the Bob Smith account to sign on to PMClient1, which has been designated as Bob Smith’s
primary computer.
 Open Windows Explorer, and under Libraries, expand Documents to show both My
Documents and Public Documents.
84 | P a g e
 Click My Documents, and then click the Address Bar to show the path to the redirected folder.
Also notice the State field in the Status bar, which indicates that the folder is enabled for Offline
Files and that Bob Smith successfully got his Documents folder redirected and subsequently
cached on his primary computer.
Sign on to a non-primary computer using the Bob Smith account
To test the experience of using a non-primary computer, use the following procedure on the
PMClient2 computer.
 Use the Bob Smith account to sign on to PMClient2, which has not been designated as Bob
Smith’s primary computer.
 Open Windows Explorer, and under Libraries, expand Documents to show both My
Documents and Public Documents.
85 | P a g e
 Click My Documents, and then click the Address Bar to show the local path to the Documents
folder. Also notice the State field in the Status bar is not present, indicating that the folder is not
enabled for Offline Files, and that Bob Smith has successfully logged on to a non-primary
computer and received a local profile.
86 | P a g e
13. Set up Remote Desktop Services on

Windows 2008 R2
Step 1: Begin the installation

Launch Server Manager, and select "roles." Once the roles manager screen is up, check the box for
Remote Desktop Services
After clicking Next, you should see an introduction to Remote Desktop Services
87 | P a g e
Step 2: Select Remote Desktop Services roles you want to install

Remote Desktop Services (RDS) includes several components (see Figure 3).
These components can be on one machine or many. Let's take a look at each of
them.
 Remote Desktop Session Host: This is the new name of Terminal Server.
 Remote Desktop Virtualization Host: This component integrates with Hyper-V.

This allows for the pooling of virtual machines on Hyper-V to be used for virtual
desktops.
88 | P a g e
 Remote Desktop Connection Broker: This component is used to bridge the

user with a virtual desktop, remote application or Terminal Server session.
 Remote Desktop Licensing: This is the new name of Terminal Server licensing
server that also includes licensing for Microsoft's Virtual Desktop Infrastructure
(VDI).
 Remote Desktop Gateway: This provides a single connection point for clients
to connect to a specific virtual desktop, remote app or Terminal Server
session.
 Remote Desktop Web Access: This provides clients an interface to access

their virtual desktop, remote app or Terminal Server sessions.
89 | P a g e
Step 3: Pick the license mode

As with past Terminal Server licensing, there are two license options: per device
and per user
Step 4: Allowing access to Terminal Server (not required)

Select which users to give access to the local terminal services. This component
is not required for RDS to work. If you choose to install "Remote Desktop Session
Host" as I have, you will get this prompt.
90 | P a g e
Step 5: Configure the client experience

The next screen is "Configure Client Experience" This is where you set the
defaults for the experience the end user will have with the VDI system.
91 | P a g e
Step 6: Configure license scope (see Figure 7)

Just as with Terminal Server of the past, you can configure the scope of the
license server. You have the following two options:
1. Domain: This limits the licensing to only servers in the domain.
2. Forest: This allows any Terminal Server in the forest to attain a license.
92 | P a g e
Step 7: Assigning the SSL certificate for Remote Desktop Gateway (see
Figure 8)
The Remote Desktop Gateway uses Secure Sockets Layer (SSL) to tunnel and
encrypt traffic from the client. This functionality requires a certificate. There are
two options for certificates:
1. Specify a certificate from the certificate store.
93 | P a g e
2. Produce a self-signed certificate.
In either case, the client must trust the certificate.
Step 8: Configure network access protection (optional)

These next few screens go beyond the scope of RDS but are related, so I will just
cover the basics.
Create authorization policies
I skipped this part because it is beyond this article's scope. This is where you
would configure a policy that states who is allowed to use the Remote Desktop
Gateway.
94 | P a g e
Install and configure network access and protection policies
This is used to configure and enforce network access polices such as IPsec and
network access protection from the client. This feature can also be used to
definedifferent policies based on users' connectivity (dial-up or virtual private
network).
95 | P a g e
96 | P a g e
Step 9: Install IIS and Remote Desktop Web Access

Remote Desktop Web Access requires Internet Information Services (IIS), so the
next two screens are for installing and configuring IIS.
97 | P a g e
98 | P a g e
Step 10: The final steps

At this point, you're done. The last two screens just let you know what you're
installing.
99 | P a g e
100 | P a g e
Now that you have installed and configured RDS, you can start using Terminal
Services and Remote Desktop Gateway Manager. The virtual desktop
infrastructure will take a wee bit more work, which I will cover in another article.
101 | P a g e
14. To install and configure File Server

Open "Server Manager" and click "Add Role". Select "File Services" from the Server role
list.
102 | P a g e
103 | P a g e
104 | P a g e
105 | P a g e
106 | P a g e
Now create a Folder and share it with below permissions.

Share name: User Data (You can hide the share using the dollar sign ($) at the end of
the share name)
Administrators : Full Control

System : Full Control
Authenticated Users : Full Control
107 | P a g e
Security settings
Group : Authenticated Users
Type : Allow
Applies to : This folder only
Permissions:
Traverse folder / execute file

List folder / read data
Read attributes
Read extended attributes
Read permissions
108 | P a g e
Create a Quota Template.
109 | P a g e
110 | P a g e
111 | P a g e
112 | P a g e
Attach to a User's profile.
113 | P a g e
114 | P a g e
15. Installing the Print Server

The first step in setting up a Windows Server 2008 print server is to install the Print Server
role. This is achieved by launching the Server Manager, selecting Roles item from the tree
in the left pane and clicking on Add Roles. In the Add Roles Wizard click next on
the Welcome screen if one appears and then select the Print Services option.
Click Next and read the information displayed before clicking Next once again to proceed
to the Select Role Services screen. On this screen a number of different service options
are available for selection and installation as outlined in the following table:
Option Description
Print Installs the print server and Print Management console. This is a prerequisite
Server for configuring print services on Windows Server 2008.
LDP Installs the TCP/IP Line Printer Daemon Service (LPDSV) allowing UNIX,
Service Linux and other Line Printer Remote (LPR0) based computers to print via the
print server. This setting also opens port in the Windows Firewall.
Internet Creates an Internet Information Service (IIS) hosted web site where users can
Printing manage printers and connect and print to shared printers hosted in the server
using the Internet Printing Protocol (IPP). The default URL for the web site is
http://servername/Printers, where servername is the name of the server
running the print services.
With the required options selected, click Next. Note that if Internet Printing was selected
and the IIS role is not currently installed in the server, the wizard will prompt to add
additional roles. If prompted, click on the Add Required Role Services button to proceed.
Click Next on any information pages that may be displayed until the Confirmation screen
appears. After reviewing the summary information provided, click Install to initiate the
installation process.
Print Services Management Tools
Once print services are installed a number of print management tools are now available
on the system. First and foremost is the Print Management snap-in which may be accessed
via Start -> All Programs -> Administrative Tools -> Print Management. A useful command-
line tool is also available in the form of the Print Backup Recovery Migration tool. The
executable is named Printbrm.exeand is located
in %SystemRoot%\System32\Spool\Tools.
A number of useful VBscript tools are also available
in %SystemRoot%\System32\Printing_Admin_Scripts\en-US (note that if you use a
language other than en-US the path will need to be change accordingly). Scripts are
115 | P a g e
available for configuring printer settings (prncfg.vbs), listing and managing printer drivers
(prndrvr.vbs), managing print jobs (prnjobs.vbs), managing print queues (prnQctl.vbs),
publishing printers to active directory (pubprn.vbs), installing and managing printers
(prnmngr.vbs) and for managing TCP/IP printer ports (prnport.vbs).
The scripts are executed using the cscript.exe command and when run without any
command-line options will display a list of supported options. For example:
cscript prnjobs.vbs
Microsoft (R) Windows Script Host Version 5.7

Copyright (C) Microsoft Corporation. All rights reserved.
Usage: prnjobs [-zmxl?] [-s server][-p printer][-j jobid][-u user name][-w password]
Arguments:
-j - job id
-l - list all jobs
-m - resume the job
-p - printer name
-s - server name
-u - user name
-w - password
-x - cancel the job
-z - pause the job
-? - display command usage
Examples:
prnjobs -z -p printer -j jobid
prnjobs -l -p printer
prnjobs -l
Adding Network Printers to the Print Server using Auto-detect
Obviously, a print server without any printers isn't going to be of much use. Not surprisingly,
therefore, the next step after installing Print Services is to add printers. Printers may either
be network based, or locally connected to the server. In the case of network printers, these
may be added either manually or using auto-detection. Under auto-detection, Print
Management scans the subnet on which the server resides and searches for any devices
it can identify as being printers. As printers are detected on
116 | P a g e
the network they are displayed in a list here they may be selected and added to the print
server.
To add network printers using auto-detection, open the Print Management tool via Start -
> All Programs -> Administrative Tools -> Print Management, unfold the Print Servers from
the list in the left pane, right click the local or remote print server to which the new printer
is to be added and select Add Printer.... This will display the Network Printer Installation
Wizard as illustrated below:
In order to have the wizard search for printers on the network, ensure that the Search for
network printers is selected and click on Next. At this point the wizard will begin the
process of scanning the network for printers. As each printer is detected it will be listed. In
the following example, the wizard has detected an HP Deskjet 5800 printer on the network
with an IP address of 192.168.2.10
117 | P a g e
If no printers are detected, ensure that the printers are connected to the network and
powered on and are on the same subnet as the print server. Once the scan is complete,
select the required printer from the list and click Next to proceed to the Printer
Driver screen. If a driver for the printer is already installed, select it from the drop down list.
Alternatively select the Install a new driver option and click Next to proceed to the Printer
Installation screen where a list of printer manufacturers and models is presented. Select
the make and model of the printer from the list:
118 | P a g e
If the make and model of printer are not listed, check to see if the printer was supplied with
a driver disk, or whether a driver can be obtained from the manufacturer's web site.
Assuming this to be the case, use the Have Disk button to browse for and select the
appropriate manufacturer driver. With either a printer selected from the list, or a suitable
driver specified, click on Next to configure thePrinter Name and Share Settings. On this
screen, enter the name by which the new printer will be shared to clients over the network.
If the printer is not to be shared, ensure that the Share this printeris not selected. Also,
enter a location description (for example, "Printer in Accounts") and comment if desired.
Click Next to display the printer summary screen as illustrated below where the selected
settings are presented for review:
119 | P a g e
Assuming the configuration summary is correct, click Next to install the new printer. At this
point the wizard will report that the driver has been successfully installed and that a test
page is ready to be printed. If another printer is to be added to the print server, select
the Add Another Printer option to instruct the wizard to loop back to the start of the
installation process.
Manually Adding Network Printers to a Print Server
The preceding section discussed the use of auto-detection to locate and install and
network attached printer. This section will cover the manual installation of a network printer.
As with auto-detection, begin by invoking the Print Management tool (Start -> All Programs
-> Administrative Tools -> Print Management), unfold the Print Servers category from the
list in the left pane, right click the local or remote print server
to which the new printer is to be added and select Add Printer.... This will launch
the Network Printer Installation Wizard. On the initial page of the wizard select the option
labeledAdd a TCP/IP or Web Services Printer by IP address or hostname and click Next to
proceed to the Printer Address screen. If the type of printer is known (TCP/IP
device or Web Services Printer) make the appropriate selection. Alternatively, leave the
setting as Auto Detect to have the wizard identify the printer type. Enter the IP address or
hostname of the printer to be added to the print server. The wizard will automatically
generate a unique port name to accompany the IP address or hostname. The option is
also provided to have the wizard attempt to identify the appropriate driver for the new
printer. The following figure illustrates the screen as described:
120 | P a g e
Click Next to install a printer driver. If a driver for the printer is already installed on the print
server, select it from the drop down list. Alternatively select the Install a new driver option
and click Next to proceed to the Printer Installation screen where a list of printer
manufacturers and models is presented. Select the make and model of the printer from
the list, or use the Have Disk to install the manufacturer supplied driver.
With either a printer selected, click on Next to configure the Printer Name and Share
Settings. On this screen, enter the name by which the new printer will be shared to clients
over the network. If the printer is not to be shared, ensure that the Share this printer is not
selected. Also, enter a location description (for example, "Color Printer in Sales") and
comment if desired. Click Next to perform the installation and print an optional test page.
Adding a Locally Connected Printer
Since servers are generally sequestered in climate controlled server room and printers are
located in proximity to the users it always seems a little odd to talk about installing printers
with are locally connected to servers. That said, it is a topic which needs to covered, and
cover it we will.
Local printers will be connected to the server using a serial (COM) port, a parallel (LPT)
port or a Universal Serial Bus (USB) port. Often, Windows will automatically detect a new
printer as soon as it is connected and powered up. In this situation an icon will appear in
the task bar indicating that the new device has been detected. Clicking on this icon
presents the option to view details about the installation process, resulting in the
121 | P a g e
appearance of a dialog similar to the one illustrated below, where a Brother MFC-420CN
printer has been detected and is being installed:
Once the printer has been installed, it will likely need to be configured for network sharing.
To achieve this, launch the Print Management tool, select the print server to which the
printer is physically connected and click on Printers. The center pane of the tool will display
a list of printers installed on the current print server. Identify the required printer in the list,
double click on it to display the properties dialog and select the Sharing tab:
122 | P a g e
If the printer is to be shared with network client, set the Share this printer check box and
enter a suitable share name for the printer. This page also allows Client-side
Rendering(CSR) to be configured. When selected, all rendering of print jobs is performed
on the client and just the RAW print data sent to the server for printing. This offloads the
rendering overhead to the client computers, thereby reducing the load, and increasing the
scalability of the print server.
If Windows fails to auto-detect the printer it may be added manually from Print
Management by right clicking on the print server to which the device is attached and
selecting Add Printer.... On the initial screen select the Add new printer using an existing
port and choose the port to which the printer is connected from the drop down list. Once
selected, click Next to install a printer driver. If one is already installed, select it from the
drop down next to the use an existing printer driver on the computer. Alternatively,
select Install a new printer driver and either select the printer make and model from the
list, or use the Have Disk to install the manufacturer supplied driver. Click Next to proceed
to the Printer Name and Sharing screen. Choose whether the printer is to be shared and,
if so, by what name. Proceed to the summary screen, review the information and complete
the installation.
123 | P a g e
With a printer server configured and printers added the next step is to cover
the management of printer servers on Windows Server 2008.
16. INSTALL PRINTER SERVER USING DEDICATED PRINTER SERVER
We are using TP-link TL-PS110UPrinter server the default IP is 192.168.0.10

Setup the Printer Server
124 | P a g e
Edit the Printer Server Name

Setup the TCP/IP Address to your desired IP
125 | P a g e
HERE ARE THE STEPS FOR THE RESETTING THE PRINTER SERVER.
1. Unplug the power adapter of print server;
2. Press the Reset key on the print server and hold;
3. Plug-in the power adapter with the Reset key pressing for no less than 7 seconds;
4. Release the Reset key.
For TL-WPS510U, when the Wireless LED light flashes regularly, the TL-WPS510U has
finished the resetting and you can see the WLAN-PS Ad-Hoc network in your wireless
network list.
126 | P a g e
17. HOW TO INSTALL PRINTER USING TCP/IP PORT.
The following steps illustrate how to install a network printer using TCP/IP in Windows 7.
In order to complete the steps you will need to know details such as the printer model
and IP address. Click the Start button, type print in the Search programs and files box
and click Add a printer
1. Choose Add a local printer
127 | P a g e
2. Click the bullet which says Create a new port and use the drop down menu to
choose Standard TCP/IP Port
3. Click Next
4. In the Hostname or IP Address field enter the IP Address for the printer you are
adding
Instuctions for looking up your IP Address (authentication required)
128 | P a g e
5. Click Next
6. Choose the driver that corresponds to your printer model (or click the Have Disk
button to search for downloaded drivers)
7. Click Next
129 | P a g e
8. Click the bullet beside Use the driver that is currently installed (recommended)
9. Click Next
10. Take note of the name given to the printer
11. Click Next
12. Make sure the bullet is selected beside Do not share this printer
13. Click Next
14. Click to put a check mark beside of Set as the default printer (if you do wish to
make it your default printer)
15. Click the Print a test page button (if you wish to do so)
16. Click Finish. Your printer should now be set up and ready to use.
130 | P a g e
18. Managing Remote Print Servers
In the previous chapter it was stated that the Print Management tool provides a central
location from which the print services for an entire network may be managed. So far we
have only looked and managing the print server running on the local computer. In this
section we will look at adding remote servers to the local Print Management configuration.
For the purposes of this example a theoretical configuration consisting of two Windows
Server 2008 systems named winserver-1 and winserver-2 is assumed. Both systems have
the print services role installed and Print Management on winserver-1will be configured to
also manage print services on winserver-2. This is achieved by first launching Print
Management on the local winserver-1 system (Start -> Administration Tools -> Print
Management), right clicking on the Print Servers node of the tree hierarchy in the left hand
pane and selecting the Add/Remove Servers option.
From the resulting menu, select the Add/Remove Servers option. The resulting dialog box
displays the currently configured print servers under the management of local Print
Management. If no remote print servers have been added previously the only server listed
will be the local system. To add additional print servers either enter a comma separated
list of server names, or use the Browse button to locate servers on the network. When one
or more servers have been selected, click on the Add to list button to add the servers to
the list. The following figure illustrates the Add/Remove Servers dialog box configured with
both the local and remote servers:
131 | P a g e
Once all the required remote print servers have been added to the list, click on Apply then
close the dialog to return to the main Print Management window. The new print servers
will now appear alongside the local server under Print Servers in the left hand pane of the
Print Management screen as illustrated below:
Migrating Printers and Queues between Servers
Windows Server 2008 also provides the ability to migrate both printers and print queues
from one print server to another. This makes it easy, for example, to take a print server off-
line for maintenance or to permanently re-assign a printer from one print server to another.
The steps outlined below assume that print Management has been configured to manage
both the source and target print servers as outlined in the preceding section of this chapter.
If this is not the case, the printer export file will need to be copied onto the destination
server or made available via file sharing and imported using Print Management on that
server.
This form of migration is performed using the Printer Migration Wizard which, along with
most other tasks, is accessed from the Print Management interface. Once Print
Management is up and running, right click on the server in the left pane from which the
printer is to be migrated (the source server) and select Export Printers To a File from the
menu. Print Management will subsequently display a dialog listing the printer drivers, port
and queues currently configured on the selected print server as illustrated below:
132 | P a g e
After reviewing the listed information click Next and select a suitable location to save the
printer export file and click Next once again to perform the export process. Depending on
the number of printers being exported and the size of the drivers the export process may
take a few minutes to complete. If the export was successful a message will appear
beneath the progress bar stating this fact. If the export was unsuccessful, click on the Open
Event Viewer button provided to learn more about the cause of the problem so that
remedial action may be taken. Assuming a successful export click Finishto dismiss the
Printer Migration dialog.
The next step is to import the printers into the target server. Begin by right clicking on the
destination server in the Print Management window and selecting Import printers from a
file.... In the resulting dialog, use the browse button to navigate to the export file, select it
and click on Next to proceed. Once the file has been read a screen will appear identical to
the one displayed prior to exporting the printer objects in the preceding step. Review this
information and click Next to display the Select import options screen as illustrated in the
following figure:
133 | P a g e
These options require a little explanation:
 Keep existing printers; import copies - It is possible that a printer being imported is
already also installed on the destination server. With this option selected, the original
printer on the destination server will be left unchanged and the new printer imported
as a copy.
 Overwrite existing printers - If the printer being imported is already installed on the
target server it is overwritten by the imported copy when this option is selected.
 List printers that were previously listed - When selected, only printers that were
already listed in Active Directory will still be listed after the import process is
completed.
 List all printers - All printers are listed in Active Directory
 Don't list any printers - No printers are listed in Active Directory

Once the required settings are configured, click Next to initiate the printer import process.
The printer configurations, drivers and queues will be subsequently be imported onto the
target print server. If errors are reported click on the Open Event
134 | P a g e
Viewer button to obtain additional information. In particular, be mindful of printers that

were physically connected to the source print server. Since they are not physically
connected to the target server an error will likely occur during the migration. Even if the
printer was physically moved to the target system prior to migration it is also possible that
it is connected to a different physical port to that used on the source server. Such
problems can be resolved by right clicking on the imported printer in Print Management,
selecting Properties and making the necessary configuration changes.
Configuring Printer Permissions
Access to printers is controlled through the configuration of printer permissions. By

default, a printer is accessible to all users on the local system, and if shared, all users
elsewhere on the network. Printer permissions are divided into two categories, special
permissions and standard permissions. Before describing how to change the permissions
on a printer it is first important to understand the meaning of each permission option.
The standard printer permissions are outlined in the following table:
Permission Description
Allows users and groups to send documents to the printer and to

Print manage their own print jobs. Also includes the Read special permission
allowing viewing, but not alteration, of printer permissions
Allows full management of the printer, including changing shared status,

Manage changing of permissions and properties, taking ownership of printers
Printers and print jobs and starting and stopping print jobs. Includes
the Read, Change and Take Ownership special permissions.
Allows user and groups to manage print jobs but does not provide the
Manage ability to print. Permissions consist of pausing, restarting, resuming and
Documents reordering and canceling print jobs. Includes
the Read, Change and Take Ownership special permissions
135 | P a g e
The special permissions are as follows:
Permission Description
Read Permissions User or Group may view the permissions on the printer.
Change Permissions User or Group may change the permissions of a printer.
Take Ownership User or Group may take ownership of printer and/or print jobs.
The current permissions for a printer may be viewed and changed by right clicking on
that printer in the Print Management tool (Start -> Administrative Tools -> Print
Management), selecting Propertiesand clicking on the Security tab:
To change the permissions for a currently listed user or group, select the user or group
and change the Allow and Deny permissions to the required settings. When the settings
are configured, click on apply to commit the changes. If the user or group is not currently
listed in the properties dialog, click on the Add... button to invoke the Select Users or
Groups dialog.
136 | P a g e
Change the Location setting if necessary and then enter the names of the users or
groups, separated by semi-colons into the bottom text box. Click the Check
Names button to verify the selected users or groups exist within the current location
scope:
Assuming the names are correct click on OK to return to the properties dialog where the
selected users and/or groups will now be included in the Group or user names list. To
configure permissions, select a user or group and set the permissions in the Permissions
for section of the dialog. Click Apply to commit the changes and repeat the task for any
other users or groups added to the list.
To configure the special permissions click on the Advanced button in the Security page
of the properties panel to display the Advanced Security Settings dialog as illustrated
below:
137 | P a g e
To modify the permissions for a user or group select that object from the list and
click Edit... to display the Permission Entry for dialog. In this dialog both the standard and
special permissions for the selected user or group are displayed and may be changed as
required. As noted previously, certain special permissions are implicit in standard
permission settings. For example, setting the Manage Printers standard permission also
enables the Read, Change and Take Ownership special permissions. Once the desired
permission changes have been made click on OK to dismiss the Permission Entry
for dialog, followed by Apply, then OK in the Advanced Security Settings dialog. Finally,
click on OK to dismiss the properties dialog and return to Print Management.
Changing Printer Ownership
After a printer has been installed the owner, by default, is SYSTEM. Ownership may be
taken either by an administrator or by a user or group which has been assigned Take
ownership permission for the printer.
138 | P a g e
To assign ownership to another user or group, open the properties dialog for the printer,
select the Security tab and then click on Advanced. In the advanced settings screen,
select the Owner tab. This screen will list the current owner, together with a list of users
and group to which ownership may be changed. If the intended new owner is not listed in
the Change owner to: list, click on the Other users or groups... button to access
the Select User or Group dialog box. Enter the name of a user or group and click on
the Check Names button. With the correct name selected, click on OK to return to the list
of owners. Select the desired owner from the list and click on Apply to commit the
change of ownership.
Printer Pooling Configuration
Printer Pooling refers to the process of allocating multiple physical print devices to a
single logical printer. In such a configuration print jobs to the logical printer are assigned
by the print server to the first available physical printer in the pool. A key requirement is
that the physical printers that make up a pool must all use the same print driver and have
the same amount of memory.
To configure printer pooling, install a printer such that it uses a particular port (such as a
local port or IP address). Attach the other printers that are to make up the pool, but do
not install them via Print Management. Once the first printer is installed, open the
properties dialog for that printer by right clicking on it in Print Management and select
the Ports tab. In the Ports page select the Enable printer pooling option. If the ports to
which the additional printers are connected are listed make sure they are all selected.
Note that a pool can be made up of printers connected in any combination of ways
(network, serial, parallel, USB etc). In the case of network printers, click on Add
Port... and enter the IP address of the additional printer, click New Port... and allow the
wizard to create the new port. Once all the new ports are added and selected,
click Apply to create the printer pool. The following figure illustrates a printer pool
comprising three HP Deskjet network printers:
139 | P a g e
Configuring Printer Availability and Priority
Rather than working with the actual physical printers, users are in fact working with
logical printers which map onto a physical print device. Windows allows a single physical
print device to be assigned to multiple logical printers. This approach brings considerable
flexibility in terms of controlling the availability of a printer to different groups of users and
the priority of their print jobs.
This concept is best described by example. Suppose that a printer is to be made
available to members of an engineering group only during the office hours. That same
printer, however, is to always be available to the management group. Similarly, any print
jobs belonging to the management group must be given a higher priority than those of
the engineering group. To achieve this objective, two logical printers assigned to the
same physical print device will be created, one for engineering and one for management.
The availability of the engineering logical printer will be restricted to office hours and
given a low priority. The management logical printer will always be available and will be
given a high priority. Permissions on the logical printers will then be configured such that
the engineering team is denied access to the management printer.
140 | P a g e
Availability and priority is configured from the printer property panel. To access these
settings, launch Print Management and navigate to the required printer in the left pane.
Right click on the printer, select Properties and then choose the Advanced tab. Once
selected, the property panel will appear as follows:
For the management logical printer the Always available option will be selected and a
high priority assigned (for example 95). Once these values are set, click on
the Security tab of the properties dialog and deny access to the printer for the
engineering group. Repeat these steps for the engineering logical printer, this time
selecting the Available from option and specifying the hours that the printer is available.
141 | P a g e
19. INSTALL, SETUP AND MANAGE LINUX A FILE

SERVER, DHCP SERVER and PRINTER SERVER
Configure File Server:
GO to Startup menu Select COMPUTER tab and Click YaST

The screen will prompt with the “root” Password “Css2015”
Search SAMBA SERVER
Click Samba Server

Samba Server is equivalent to Domain controller in Windows.
142 | P a g e
Use WORKGROUP as default workgroup name.
143 | P a g e
Select primary domain controller.
In SAMBA configuration
select service start during boot.
144 | P a g e
Use again “Css2015” as your Samba password.
Next Step is search the NETWORK to edit your network card to setup a STATIC IP Address.
145 | P a g e
In Setting Network if this error appear change network setup method from NETWORK MANAGE
SERVICE to WICKED SERVICE
146 | P a g e
Click your NIC Device and Click edit
Choose STATICALLY ASSIGN IP ADDRESS and put our own IP address (don’t forget your IP) Click
save and restart your server.
147 | P a g e
After reboot open the YaST and search for firewall and Choose disable firewall.
and Click Next
148 | P a g e
in your windows 7 computer make your network static IP address and related in same subnet of
your Linux Server. Now ping the IP address of your Linux.
SETUP DHCP Server

Select again the YaST and search for DHCP server
149 | P a g e
Click DHCP Server.
Select the NIC and IP address and click next
150 | P a g e
put your IP Range e.g. (192.168.3.20-192.168.3.50) same to SCOPE in windows 2008 server.
Click OK.
In your computer windows 7 change your ip to dynamic setting (obtained) and check in
IPCONFIG if the linux server assign an IP addres to your desktop PC.
Check for the shared folder using RUN command
151 | P a g e
Use “root” as user and “Css2015” as Password
To add more share folder go to SAMBA setting in SHARE tab and add share folder with security
authentication.
152 | P a g e
you can also add shared printer in this area.
153 | P a g e
20. INSTALLING LINUX

(MAKE USB INSTALLER USING DVD OR ISO AND SAVE IT TO YOUR
USB FLASH DRIVE USING RUFUS)
Add the openSUSE-13.2-DVD-x86_64.ISO and save it to USB Flash Disk and Click Start.
154 | P a g e
Setup the bios to boot in usb

In boot menu
155 | P a g e
Follow the on-screen instruction
156 | P a g e
Click next
157 | P a g e
In partitioning the hard disk select manual partition and make two partition 10% for
SWAP files and 60% for EXT4 partition under SYSTEM FILES. Click next.
158 | P a g e
159 | P a g e
160 | P a g e
In Clock time zone select asia

and manila
Use KDE as Desktop
161 | P a g e
In Installation setting Select SOFTWARE
Go to server function and

choose File Server, Printer
Server DHCP Server, and
DNS Server, in included also
select SAMBA Server.
162 | P a g e
Click Install
163 | P a g e
164 | P a g e
Installing services
Follow the Onscreen procedures
Use your name as user and use Css2015 as your password in “root” use and “your name”
165 | P a g e
21. To Configure TPLINK Range Extender
Before configuration, please get the right information of the Root Router as below:
Information of Root Router:
 LAN IP: 192.168.1.254
 SSID: oloroso.net
 Encryption Type: WPA2-PSK with AES
 Passphrase: oloroso.netlogin
Preparation
 Since the DHCP function on the Range Extender is disabled by default, we have to
manually assign an IP address as 192.168.1.253 to the computer to match the
default IP address of the Range Extender. For TL-WA830RE, its LAN IP is
192.168.0.254, please assign 192.168.0.253 or 192.168.0.255 for your computer to
align with the range extender IP Address (192.168.0.254)
 Connect the computer to the Range Extender with an Ethernet cable. And
disconnect the wireless from the root router.
Configuration on Range Extender :
1. Log onto the Range Extender’s management page.
2. Click Network. Please make sure the Range Extender's IP address is in the same
IP segment with the Root Router and avoid the IP conflict. In this instance, we can
change the IP to "192.168.1.250". Then click Save.
166 | P a g e
Notice: If the root router is not in the IP segment 192.168.1.X, for example, it is
192.168.0.254.you need to change the IP of the Range Extender to 192.168.0.250. and
after clicking on Save, please change the IP of your computer to 192.168.0.100. and then
log in the Range Extender’s management page by using the new IP 192.168.0.250.
3. Click Quick Setup, Click on Next->Wireless. Select Range Extender as

the Operation Mode. Then click Search.
167 | P a g e
3. Find the Root Router's SSID on the list, and then click Connect.
5. Click Save.
6. Click Wireless -> Wireless Security. Select WPA-PSK/WPA2-PSK, and

Encryption AES.input the password "oloroso.netlogin" in the PSK Passwordfield. Then
click Save. The Security settings on the Range Extender must be the same as the root
router. Please contact the support of the router to check it if you are not sure.
After you go through all the above steps, the Range Extender should get working
properly with the Root Router.
How to confirm:
Go to System Tools->Diagnostic，in the IP address(or IP address/Domain Name)
bar type in the root router’s IP 192.168.1.254, click on theStart on the bottom.
168 | P a g e
And the last step is to set the computer to obtain the IP address automatically.
If the Ping is not successful, please check all above settings carefully,
169 | P a g e
22. To Set Up a Tenda Access Point as a

Repeater
This guide will show you how to setup the Tenda Access Point as a repeater. Your
existing router will need to be configured also to allow the access point to connect to
it. If the existing router is a Tenda-brand router, please consult the Tenda
documentation on how to set the Tenda router as a repeater. Otherwise, it is
necessary to use the specific manufacturer instructions for any other brand of router.
1. Connect the Tenda Access Point to your existing router using an Ethernet cable,
then connect it to the LAN port on the router (yellow port if using the Tenda
router).
2. Once connected to the router, open your web browser and type in
"192.168.0.254". This will bring up the setup page for the Access Point.
3. Click on Wireless Settings. This shows the options for which mode is to be used.
Select AP Repeater.
4. Next, change the SSID or you can leave it at the default setting. If you're using it
as a repeater, it's best to change it, so both devices won't have the same name.
170 | P a g e
5. Click on Open Scan. Once completed, it will display the routers in your area that
are available. Select your router and click Apply. The Access Point will reboot
after it connects.
171 | P a g e
6. Disconnect the Ethernet cable from the router and move the Access Point to a
location where it will be best used as a repeater. It needs to be within the range of
the existing router and will repeat the signal from there.
172 | P a g e
23. How to Configure TP-LINK N router as a

wireless Access Point?
This is based on the condition that you already have a router and only want TP-LINK
router to extend the wireless network range via a LAN cable. We don’t need WAN port on
the TP-LINK router in this network.
Step 1
Connect your computer to another LAN port through Ethernet cable, then login to TP-
LINK web interface through the IP address on the bottom label by the following tips:
Step 2
Go to Network ->LAN on the left side menu,change the LAN IP address of TP-LINK
router to the same segment of the main router.( For example, if your main router gets the
IP address of 192.168.2.1, 192.168.2.11 is recommended for TP-LINK router.)
173 | P a g e
After that, it would require a Reboot. Please click OK to reboot and then relogin to TP-
LINK page with the new IP address
Step 3
Configure the wireless
Go to Wireless->Wireless Settings page, configure the SSID (Network name)
and Channel. (If it is a dual band device, please don’t forget to select the Band.)
Click Save button.
Go to Wireless->Wireless Security page, configure the wireless security. Here WPA-

PSK/AES is recommended. PSK Password is the key of your wireless.
174 | P a g e
Step 4
Go to DHCP on the left side menu, disable the DHCP Server and click Save button.
Step 5
Go to System Tools->Reboot page, click Reboot button to reboot the device.
Step 6
Connect the main router to the LAN port on TP-Link router through Ethernet cable.
After all of the tips above, your computer would have internet through any LAN ports of
TP-LINK by an Ethernet cable. At the same time your wireless client would have access
to the TP-LINK wirelessly through the SSID and Password.
175 | P a g e
24. Configure the basic wireless settings for

my TP-LINK 11N Wireless Router?
Preparations：
Please connect a computer to TP-LINK router by cable or through wireless network.
It’s recommended to configure it by a wired connection.
Log into the router’s web-based utility

To get some help, please refer to the article How do I log into the web-based Utility
(Management Page) of TP-LINK wireless router
Step 1
Select Wireless->Wireless Settings on the left side menu to open the wireless setting
page.
176 | P a g e
Wireless Network Name(also called SSID for some models):Create a new name for
your wireless network.If you want to use the default TP-LINK_****** wireless name,you can
also leave it here as default value.
Region:Select your current location.
"Enable Wireless Router Radio" and "Enable SSID Broadcast" should be both
ticked.
Please do not change other settings on this page if not necessary.
Step 2
177 | P a g e
Click Save to save your settings.

Note: After clicking on Save button, you will see a tip (red line) at the bottom of the page.
But actually there is no need to reboot at here and we will reboot the router at the end of
the configurations.
'
Step 3
Select Wireless->Wireless Security on the left side menu. It’s recommended to
use WPA/WPA2 Personal(Recommended),some models will name that as WPA-
PSK/WPA2-PSK instead.
178 | P a g e
Version: WPA-PSK or WPA2-PSK

Encryption: AES
Wireless Password(also called PSK Password): make up your WI-FI password, also
called Wireless Network Key.
If you want to use WEP as wireless security type, you need obey certain rules to create
the wireless password.
For 64-bit encryption - You can enter 10 hexadecimal digits (any combination of 0-9,
a-f, A-F, and null key is not permitted) or 5 ASCII characters.
· For 128-bit encryption - You can enter 26 hexadecimal digits (any combination of 0-
9, a-f, A-F, and null key is not permitted) or 13 ASCII characters.
· For 152-bit encryption - You can enter 32 hexadecimal digits (any combination of 0-
9, a-f, A-F, and null key is not permitted) or 16 ASCII characters.
179 | P a g e
Step 4
Click Save button to save the settings
Step 5
Click click here at the bottom of the page to reboot the router; or you can go to system
tools, reboot to reboot the router to make all settings take effect.
180 | P a g e
Source:
1. http://www.techfleece.com/2015/07/08/how-to-create-a-bootable-windows-
usb-drive-using-rufus/
2. http://www.dell.com/support/article/us/en/04/SLN153364/ko?c=us&l=en&s=
bsd&cs=04
3. http://www.tutorialspoint.com/articles/installing-microsoft-windows-server-
2008-r2
4. http://www.rackspace.com/knowledge_center/article/installing-active-
directory-domain-services-on-windows-server-2008-r2-enterprise-64-bit
5. http://blog.pluralsight.com/windows-server-2008-active-directory-users
6. http://www.tp-link.com/en/faq-417.html
181 | P a g e

CSS NC2

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CSS NC2

Încărcat de

Drepturi de autor:

Formate disponibile

LIBON AGRO-INDUSTRIAL HIGH SCOOL

Tinago St., Zone 2, Libon, Albay

1. Creating a bootable USB installer using Rufus

1. Unit of Desktop PC with windows 7 Operating System.

Your USB Flash Drive

4. Select the ISO/Image. (Windows 7/Server 2008 r2 ISO/Linux)

Rufus will now have filled out the fields

Note, if you are using a USB stick that is

If your USB is the correct size then

6. Click OK, to start.

7. Click close, eject USB flash drive

2. Create a bootable USB Flash Drive using the

Insert your Windows DVD into the optical drive.

g: <enter> (Where "g" is your DVD drive letter)

/s - Copies directories and subdirectories except empty ones.

To display the full list of switches, type xcopy /? <enter>

3. Installing Microsoft Windows Server 2008 R2 enterprise

Windows Server 2008 R2 is a network operating system Microsoft, and

 Active Directory Domain Services (AD DS)

Although Windows Server 2008 R2 is a network operating system, it is

 1.4 GHz x86/x64 or Itanium 2 processor

1. Power on the computer on which Microsoft Windows Server 2008 R2 is to

6. On the next page, click Install now.

Select Appropriate Edition

Click Custom (Advance)

Click Drive Options

Specify Volume Size

15. On the displayed Install Windows message box, click OK.

Select Disk Partition

20. On the next confirmation screen, click OK to log on to the Windows

4. Assign Static IP Address (in Windows Server 2008 R2)

 Class A – IP Address: 0-126, Default Subnet Mask: 255.0.0.0

Procedure in assigning a Static IP Address

1. Log on to Windows Server 2008 R2

5. Installing Active Directory Domain Services on

Prepare for Active Directory

Before you install AD DS on a Rackspace Cloud Server running Windows Server

Select Domain Name and Password

Specify the Preferred DNS Server

3. In the Network Connections window, right-click the private adapter and

4. Select Internet Protocol Version 4, and then click Properties.

6. Add the Active Directory Domain Services Role

4. On the Installation Progress page, click Install.

Enable the Remote Registry

1. Open the Server Manager window if it is not already open.

Install Active Directory Domain Services (DCPROMO)

1. If it is not already open, open the Server Manager window.

4. On the Welcome page of the Active Directory Domain Services Installation

5. On the Operating System Capability page, click Next.

6. On the Choose a Deployment Configuration page, select Create a new domain

The installation examines and verifies your DNS setting.

10. In the message dialog box that appears, click Yes.

The installation of Active Directory Domain Services on your server is complete.

7. Installing DHCP Server on

About Dynamic Host Configuration Protocol (DHCP) Server

A Dynamic Host Configuration Protocol (DHCP) server is a computer that

During DHCP server configuration, administrators specify a range of IP

Dynamic Host Configuration Protocol (DHCP) IP Address

The process of IP address assignment completes in four steps called DORA

Prerequisites for Installing DHCP Server Role

Before DHCP server role is installed on a Windows Server 2008 R2 computer,

Procedure in DHCP server in Windows Server 2008 R2

To install and configure Dynamic Host Configuration Protocol (DHCP) on