###BeginCaseStudy###
Case Study: 4
Woodgrove Bank
Scenario:
COMPANY OVERVIEW
Overview
Woodgrove Bank is an international financial organization.
Physical Location
The company has a main office and multiple branch offices.
EXISTING ENVIRONMENT
Active Directory Environment
The network contains one Active Directory forest. A separate domain exists for each office.
Network Infrastructure
All offices have domain controllers that are configured as DNS servers. All client computers
are configured to connect to the DNS servers in their respective office only.
The main office has the following servers and client computers:
• One Windows Server Update Services (WSUS) server.
• Client computers that run either Windows XP Service Pack 3 (SP3) or Windows 7.
• Ten file servers that host multiple shared folders. The file servers run either Windows
Server 2003 or Windows Server 2008 R2.
• One domain-based Distributed File System (DFS) namespace that has two replicas.
The DFS servers run Windows Server 2008 R2. The DFS namespace is configured to use
Windows 2000 Server mode.
Each branch office has a WAN link to the main office. The WAN links are highly saturated.
Each office has a dedicated high-speed Internet connection.
All of the client computers in the branch offices run Windows 7.
User Problems
Users report that it is difficult to find the shared folders on the network.
REQUIREMENTS
Planned Changes
Woodgrove Bank plans to implement the following changes:
• Deploy a new Application named App1 on each client computer. App1 has a
Windows Installer package and is compatible with Windows XP, Windows Vista, and
Windows 7.
• Designate a user in each office to manage the address information of the user accounts
in that office.
• Deploy a new branch office named Branch22 that has the following servers:
• One file server named Server1.
• Two domain controllers named DC10 and DC11 that are configured as DNS servers.
Technical Requirements
Woodgrove Bank must meet the following technical requirements:
• Minimize hardware and software costs, whenever possible.
• Encrypt all DNS replication traffic between the DNS servers.
• Ensure that users in the branch offices can access the DFS targets if a WAN link fails.
• Ensure that users can only view the list of DFS targets to which they are assigned
permissions.
• Minimize the amount of network traffic between the main office and the branch
offices, whenever possible.
• Minimize the amount of name resolution traffic from the branch offices to the DNS
servers in the main office.
• Ensure that the administrators in the main office manage all Windows update
approvals and all computer groups.
• Manage all of the share permissions and the folder permissions for the file servers
from a single management console.
• Ensure that if a file on a file server is deleted accidentally, users can revert to a
previous version of the file without administrator intervention.
• Ensure that administrators are notified by e-mail each time a user successfully copies
a file that has an .avi extension to one of the file servers.
Security Requirements
Woodgrove Bank must meet the following security requirements:
• Access rights and user rights must be minimized.
• The Guest account mustoe disabled on all servers.
• Internet Information Services (IIS) must only be installed on authorized servers.
###EndCaseStudy###
You need to recommend a solution for deploying App1. The solution must support the company’s
planned changes. What should you include in the recommendation?
A.
Group Policy Software Installation
B.
Microsoft Application Virtualization (App-V)
C.
Microsoft Enterprise Desktop Virtualization (MED-V)
D.
Microsoft System Center Configuration Manager
Explanation:
Requirements include minimize costs when possible
Using a GPO to install software is freely available in AD
Assigning Software
You can assign a program distribution to users or computers. If you assign the program to a user, it is
installed when the user logs on to the computer. When the user first runs the program, the
installation is finalized. If you assign the program to a computer, it is installed when the computer
starts, and it is available to all users who log on to the computer. When a user first runs the program,
the installation is finalized.
Publishing Software
You can publish a program distribution to users. When the user logs on to the computer, the
published program is displayed in the Add or Remove Programs dialog box, and it can be installed
from there.
Create a Distribution Point
To publish or assign a computer program, you must create a distribution point on the publishing
server:
Log on to the server computer as an administrator.
Create a shared network folder where you will put the Microsoft Windows Installer package (.msi
file) that you want to distribute.
Set permissions on the share to allow access to the distribution package.Copy or install the package to the distribution point. For example, to distribute Microsoft Office XP,
run the administrative installation (setup.exe /a) to copy the files to the distribution point.
Create a Group Policy Object
To create a Group Policy object (GPO) to use to distribute the software package:
Start the Active Directory Users and Computers snap-in. To do this, click Start, point to
Administrative Tools, and then click Active Directory Users and Computers.
In the console tree, right-click your domain, and then click Properties.
Click the Group Policy tab, and then click New.
Type a name for this new policy (for example, Office XP distribution), and then press ENTER.
Click Properties, and then click the Security tab.
Click to clear the Apply Group Policy check box for the security groups that you want to prevent from
having this policy applied.
Click to select the Apply Group Policy check box for the groups that you want this policy to apply to.
When you are finished, click OK.
Assign a Package
To assign a program to computers that are running Windows Server 2003, Windows 2000, or
Microsoft Windows XP Professional, or to users who are logging on to one of these workstations:
Start the Active Directory Users and Computers snap-in. To do this, click Start, point to
Administrative Tools, and then click Active Directory Users and Computers.
In the console tree, right-click your domain, and then click Properties.
Click the Group Policy tab, select the group policy object that you want, and then click Edit.
Under Computer Configuration, expand Software Settings.
Right-click Software installation, point to New, and then click Package.
In the Open dialog box, type the full Universal Naming Convention (UNC) path of the shared installer
package that you want. For example, \\file server\share\file name.msi.
Important Do not use the Browse button to access the location. Make sure that you use the UNC
path to the shared installer package.
Click Open.
Click Assigned, and then click OK. The package is listed in the right pane of the Group Policy window.
Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers
snap-in.
When the client computer starts, the managed software package is automatically installed.
Publish a Package
To publish a package to computer users and make it available for installation from the Add or
Remove Programs tool in Control Panel:
Start the Active Directory Users and Computers snap-in. To do this, click Start, point to
Administrative Tools, and then click Active Directory Users and Computers.
In the console tree, right-click your domain, and then click Properties.
Click the Group Policy tab, click the group policy object that you want, and then click Edit.
Under User Configuration, expand Software Settings.
Right-click Software installation, point to New, and then click Package.
In the Open dialog box, type the full UNC path of the shared installer package that you want. For
example, \\file server\share\file name.msi.
Important Do not use the Browse button to access the location. Make sure that you use the UNC
path to the shared installer package.
Click Open.
Click Publish, and then click OK.
The package is listed in the right pane of the Group Policy window.Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers
snap-in.
Test the package:
Note Because there are several versions of Microsoft Windows, the following steps may be different
on your computer. If they are, see your product documentation to complete these steps.
Log on to a workstation that is running Windows 2000 Professional or Windows XP Professional by
using an account that you published the package to.
In Windows XP, click Start, and then click Control Panel.
Double-click Add or Remove Programs, and then click Add New Programs.
In the Add programs from your network list, click the program that you published, and then click
Add. The program is installed.
Click OK, and then click Close.
Redeploy a Package
In some cases you may want to redeploy a software package. For example, if you upgrade or modify
the package. To redeploy a package:
Start the Active Directory Users and Computers snap-in. To do this, click Start, point to
Administrative Tools, and then click Active Directory Users and Computers.
In the console tree, right-click your domain, and then click Properties.
Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and
then click Edit.
Expand the Software Settings container that contains the software installation item that you used to
deploy the package.
Click the software installation container that contains the package.
In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then
click
Redeploy application. You will receive the following message:
Redeploying this application will reinstall the application everywhere it is already installed. Do you
want to continue?
Click Yes.
Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers
snap-in.
Remove a Package
To remove a published or assigned package:
Start the Active Directory Users and Computers snap-in. To do this, click Start, point to
Administrative Tools, and then click Active Directory Users and Computers.
In the console tree, right-click your domain, and then click Properties.
Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and
then click
Edit.
Expand the Software Settings container that contains the software installation item that you used to
deploy the package.
Click the software installation container that contains the package.
In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then
click
Remove.
Do one of the following:
Click Immediately uninstall the software from users and computers, and then click OK.
Click Allow users to continue to use the software but prevent new installations, and then click OK.Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers
snap-in.