Lesson 6 Deploying Applications

ITMT 2456 70-647

Plan for application
delivery.
Planning network and
application services
1.3
Plan for Terminal Services. Planning network and
application services
1.4

Selecting a Windows Server 2008 R2 Edition
always, the first step in any large scale deployment project is planning. You must decide which applications your
users will need and how you intend to deploy them.
our servers, and your
workstations are already in place.


Identifying User Requirements
For enterprise administrators to provide users with workstations, they must determine what tasks the users have to
accomplish.

To create workstation configurations, administrators must know the hardware and software requirements for each
application a user workstation must run.



Fat Clients
Most enterprises use fat clients to support applications on their workstations.
user needs locally.

Thin Client
A thin client, by contrast, is a computer that functions as a terminal for applications running on servers.
on another computer and carry the users mouse and keyboard input from the workstation to the applications.


Remote Desktop Services (RDS)
Windows Server 2008 R2 includes Remote Desktop Services (RDS), which provide presentation virtualization capabilities
in a number of permutations.


Choosing a Deployment Method
In most enterprise environments, the object is to create a series of uniform workstation configurations, to facilitate
maintenance and troubleshooting later.
workstation of the same type.

Installing Applications Manually
The simplest type of application deployment is the same one that individuals use for their home systems: manual
installation to the computers local hard disk.
-based installation program that is easy to use and provides customizing
options.


Deploying Applications Using Group Policies
One method of automating application deployment using only the infrastructure supplied by AD DS is to use the Group
Policy Software Installation settings.


Deploying Applications Using Group Policies
Group Policy objects have two Software Installation nodes, one under Computer Configuration and one under User
Configuration.
or users receiving the GPO.
Depending on the settings you select when you add the package, the target computers can deploy the software in one
of three ways, as follows:
When you assign a package to a computer, an automated software installation occurs as soon
as the system starts and downloads the GPO.
When you assign a package to a user, the policy adds the application to the computers Start menu,
and can associate certain file name extensions with the applications executable. The installation occurs when the user
launches the application from the Start menu for the first time or opens a file associated with the application
Publish When you publish a package to a user (you cannot publish to a computer), the policy adds the application to
the Get Programs control panel in Windows 7 or Windows Server 2008 R2 (or the Add or Remove Programs control
panel in earlier versions), enabling the user to install the application on demand at any time.

Deploying Applications Using System Center Configuration Manager
System Center Configuration Manager (SCCM) 2007 is a Microsoft network management product that provides
administrators with a variety of valuable functions, not the least of which is software deployment.
rchase the software separately.
SCCM deploys software using packages, just as Group Policy does, but the packages themselves are of a completely
different format than the Windows Installer packages Group Policy uses.
ration Manager console, which is the tool you use to create your own packages.

Using Web-based Applications
An increasingly popular alternative to locally-installed applications is the use of web servers and web browsers as the
components of a client/server application.
response to their requests.
Internet Information Services (IIS) version 7, included with Windows Server 2008 R2, has role services that support a
variety of application development environments, some venerable and others quite recent, including the following:



(ISAPI)

IIS is designed to support multiple web sites and multiple applications, and it does so by isolating application functions in
separate address spaces called application pools.
sion within IIS that consists of a request queue and one or more worker
processes.
A worker process is a host for user-developed application code, which is responsible for processing requests it receives
from protocol listeners modules that wait for incoming client requests and returning the results to the client.
process running outside of that pool. This is known as worker process isolation mode.

Remote Desktop Services
Remote Desktop Services (RDS) is a role that enables a server running Windows Server 2008 R2 to host applications and
entire desktops for multiple clients all over the network.
e actual application computing; the clients function only as terminals.

Remote Desktop Advantages
Reduced client hardware requirements



licenses




Remote Desktop Infrastructure
All client/server applications, by definition, require three basic elements:




Remote Desktop Session Host
A role service that runs on a computer running Windows Server 2008 R2, which enables multiple clients to connect to
the server and run individual desktop or application sessions.

Remote Desktop Connection Client
A program running on a workstation computer, which establishes a connection to an RDS server using RDP and displays
a session window containing a desktop or application. All Windows versions include the Remote Desktop Connection
client program.

Remote Desktop Protocol (RDP)
A networking protocol that enables communication between the RDS server and the client.