IT ELECT 1

PLATFORM TECHNOLOGIES

SUBMITTED BY:

KENETH JOHN P. ANCHETA

BSIT 2C

SUBMITTED TO: DR. LARRY DE GUZMAN

PROFESSOR
 NOTE:
Before installing any operating system, make sure all your data is backed
up.

1. Ensure that the installation media is available to boot.

2. Reset the power on the server.
3. In the BIOS screen, press F8.
4. Choose Language to use
5. Choose the version of windows server you want to install

6. Since I’m using the blank hard drive the upgrade option is unavailable.
Choose Custom option.
7. I didn’t partition it because I only have one hard drive

8. Windows server 2008 will now be installed. This normally takes quite a while and your
PC will restart a couple of times.
9. Do not press any key

10. In the user password dialog, click OK and set up the initial user login account.
 SERVER CONFIGURATION REMOTE ACCESS

Step 1: Begin the installation

Launch Server Manager and select Server Roles. Once the roles manager screen is up, check the
box for Remote Desktop Services. Some other boxes may already be checked, but this is fine --
the only box you need to worry about for this step is the Remote Desktop Services box. Click the
next button in the bottom right corner to proceed.

Now you should see an introduction to RDS. Select the next button at the bottom of the page.

Step 2: Select Remote Desktop Services roles you want to install

RDS includes several components and settings . These components can be on one machine or
many.

 Remote Desktop Session Host. This is the name for Terminal Server.

 Remote Desktop Virtualization Host. This component integrates with Microsoft Client
Hyper-V. This allows for the pooling of virtual machines on Hyper-V so they can serve as
virtual desktops.
 Remote Desktop Connection Broker. This component bridges the user with a virtual
Windows desktop, remote application or Remote Desktop Session Host session.

 Remote Desktop Licensing. This is the modern name of Terminal Server licensing server that
also includes licensing for Windows Server.

 Remote Desktop Gateway. This provides a single connection point for clients to connect to a
specific virtual desktop, remote app or Remote Desktop Session Host session.

 Remote Desktop Web Access. This provides clients an interface to access their virtual
desktop, remote app or Remote Desktop Session Host sessions.
Step 3: Pick the license mode

As with past Terminal Server licensing, there are two license options: per-device and per-user

Step 4: Allow access to Remote Desktop Session Host (not required)

Select which users to grant access to the local Remote Desktop Session Host. This server
component is not required for RDS to work. If you choose to install the Remote Desktop Session
Host, you will get this prompt .
Step 5: Configure the client experience

The next screen is called Configure Client Experience . This is where you set the defaults for the
end-user experience with the VDI system and remote desktop.
Step 6: Configure license scope

Just as with Terminal Server of the past, you can configure the scope of the Remote Desktop
Session Host license server. You have the following two options:

1. Domain. This limits the licensing to only servers in the domain (Figure 5).

2. Active Directory Forest. This allows any Remote Desktop Session Host server in the Active
Directory Forest -- the highest-level container in a set of servers -- to attain a license

Step 7: Assigning the SSL certificate for Remote Desktop Gateway

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.

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 this article will just cover
the basics.This is where you would configure a policy that states who is allowed to establish a
desktop connection to the Remote Desktop Gateway
Install and configure network access and protection policies

You can use this to configure and enforce network access policies such as Internet Protocol
Security (IPsec) and network access protection from the client .

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. First, there is the overview screen .
Step 10: The final steps

At this point, you're done. The last two screens just let you know what you're installing.
 SERVER IP CONFIGURATION

P Configuration

The IP Configuration window configures the Internet Protocol parameters, allowing the device to
receive and send IP packets. In its factory default configuration, the switch operates as a
multiport learning bridge with network connectivity provided by the ports on the switch. To
enable IP-dependent features, you will need IP addressing.
 You can use the web browser interface to access IP addressing only if the switch already
has an IP address that is reachable through your network. Initially configure IP
addressing either through a direct terminal device connection to the switch's Console RS-
232 port or by using the default DHCP/BootP option if the switch is installed and
powered up in a network using a DHCP or BootP server to configure network devices.
In the factory-default configuration, the switch has one permanent default VLAN (named
DEFAULT_VLAN) that includes all ports on the switch. Thus, when only the default VLAN
exists in the switch, if you assign an IP address and subnet mask to the switch, you are actually
assigning the IP addressing to the DEFAULT_VLAN.
Although recommended, a default gateway (IP) address for the switch is optional. The default
VLAN is the primary VLAN for the switch. The switch uses the primary VLAN to learn the
default gateway address. The switch can also learn other settings from a DHCP or BootP server,
such as Time-To-Live (TTL) and TimeP SNMP settings. Other VLANs can also use DHCP or
BootP to acquire IP addressing. However, the switch’s gateway, TTL, and TimeP or SNTP
values, which are applied globally, and not per-VLAN, are acquired through the primary VLAN
only, unless manually set. If these parameters are manually set, they will not be overwritten by
alternate values received from a DHCP or BootP server.
 The switch uses the IP default gateway only while operating as a Layer 2 device. While
routing is enabled on the switch, the IP default gateway is not used. Thus, to avoid loss
of Telnet access to off-subnet management stations, you should use the ip route CLI
command to configure a static (default) route before enabling routing. For additional
information, see the Configuration and Management Guide or Advanced Traffic
Guide for your switch.
If multiple VLANs are configured, then each VLAN can have its own IP address. This is because
each VLAN operates as a separate broadcast domain and requires a unique IP address and subnet
mask. For additional information on VLANs, refer to the Advanced Traffic Management
Guide for your switch.
To configure IP parameters:
1. In the Default Gateway field, type the IP address of a local router whose subnetwork you
want to manage.
2. In the VLAN field, select the VLAN to which you want to assign a new IP address or to
edit the existing IP addressing.
 3. The VLAN field appears only if multiple VLANs are configured in the switch.
3. In the IP Configuration field, select one of the following IP configurations:

DHCP/BootP The switch (or selected VLAN, if configured) gets its IP

configuration (or a more extensive configuration) from a
DHCP or BootP server, which makes it possible to assign and
configure IP addresses automatically when a client requests
one.
For more information on this feature, see the Online Users
Guide on the network management product CD-ROM (for
example, HP ProCurve Manager) and the Advanced Traffic
Management Guide for your switch.
 Selecting DHCP/BootP assumes that a server on the
network has already been configured to provide the
necessary configuration to the switch. Implementing
this option interrupts connectivity between the
browser interface and the switch. DHCP and BootP
cannot configure secondary IP addresses (for
multinetting).

Manual You will manually create the IP configuration. With this

setting, you must type the IP Address, Subnet Mask, and
Default Gateway for the switch (or selected VLAN, if
configured).
 This field can be used to add multinetted IP addresses.

Disabled The switch (or selected VLAN, if configured) is configured as

an unmanaged device (a transparent learning bridge). While
disabled, the only method of management access is through a
terminal device directly connected to the switch's Console RS-
232 port. For more information, refer to the Management and
Configuration Guide for your switch.

4. If you selected Manual IP Configuration, enter the values for the following fields that
appear:

IP Address Type the IP address for the switch (or selected VLAN, if
configured) in the x.x.x.x format, where x is a decimal
number between 0 and 255.
You can assign one primary IP address and up to seven
secondary IP addresses to a VLAN. This allows you to
combine two or more subnets on the same VLAN, which
enables devices in the combined subnets to communicate
 normally through the network without needing to reconfigure
the IP addressing in any of the combined subnets.
For IP addressing with multiple VLANs, see the Management
and Configuration Guide for your switch.
 Changing the IP address ends the connection to the
switch. You must enter the new address as the URL to
reconnect.

Subnet Mask Type the value that defines the local portion of your network
(the portion that you don't have to go through a gateway to
reach). This value must be the same value used for all other
devices in your network.

Default Gateway The default gateway is required when a router is needed for
tasks such as reaching off-subnet destinations or forwarding
traffic across multiple VLANs. The gateway value is the IP
address of the next-hop gateway node for the switch, which is
used if the requested destination address is not on a local
subnet/VLAN.
If the switch does not have a manually-configured default
gateway and DHCP/BootP is configured on the primary
VLAN, then the default gateway value provided by the DHCP
or BootP server will be used. If the switch has a manually
configured default gateway, then the switch uses this gateway,
even if a different gateway is received via DHCP or BootP on
the primary VLAN.

5. Click Apply Changes to activate the changes.