Which client installation methods should you identify?

Your network contains a Windows Server Update Services (WSUS) server. All client
computers are configured as WSUS clients.
All of the client computers have Windows Firewall enabled. Windows Firewall is configured
to block Fie and Printer Sharing.
Users are not configured as local Administrators on their client computers.
You deploy System Center 2012 Configuration Manager.
You need to identify which methods you can use to deploy the Configuration Manager client
to an of the client computers.
Which client installation methods should you identify? (Choose all that Apply.)

A.
a logon script installation

B.
a manual client installation

C.
a software update-based client installation

D.
a Client Push Installation

E.
an Active Directory Group Policy-based installation

Explanation:
Answer> a software update-based client installation
A Client Push Installation
An Active Directory Group Policy-based installation
The Logon script runs with the user’s credentials.
Manual installation also runs with the user’s credentials.
Software update point uses the local SYSTEM account and All client computers are
configured as WSUS clients. So the firewall should not affect functionality.
Client Push Installation requires File and Printer Sharing and runs with the local SYSTEM
account.
Group Policy Installation requires File and Printer Sharing and runs with the local SYSTEM
account.
Further information:
http://technet.microsoft.com/en-us/library/gg682191.aspx
Determine the Client Installation Method to Use for Windows Computers in Configuration
Manager
The following table outlines the advantages and disadvantages of each client installation
method to help you determine which will work best in your organization:
Client push installation Can be used to install the client on a single computer, a collection of
computers, or to the results from a query.
Can be used to automatically install the client on all discovered computers.
Automatically uses client installation properties defined on the Client tab in the Client Push
Installation Properties dialog box.
Can cause high network traffic when pushing to large collections.
Can only be used on computers that have been discovered by System Center 2012
Configuration Manager.
Cannot be used to install clients in a workgroup.
A client push installation account must be specified that has administrative rights to the
intended client computer.
Windows Firewall must be configured on client computers with exceptions so that client push
installation can be completed.
You cannot cancel client push installation. When you use this client installation method for a
site, Configuration Manager tries to install the client on all discovered resources and retries
any failures for up to 7 days.
Software update point-based installation
Can use your existing software updates infrastructure to manage the client software.
Can automatically install the client software on new computers if Windows Server Update
Services (WSUS) and Group Policy settings in Active Directory Domain Services are
configured correctly.
Does not require computers to be discovered before the client can be installed.
Computers can read client installation properties that have been published to Active

Directory Domain Services.
Will reinstall the client software if it is removed.
Does not require you to configure and maintain an installation account for the intended client
computer.
Requires a functioning software updates infrastructure as a prerequisite.
Must use the same server for client installation and software updates, and this server must
reside in a primary site.
To install new clients, you must configure an Group Policy Object (GDO) in Active Directory
Domain Services with the client’s active software update point and port.
If the Active Directory schema is not extended for System Center 2012 Configuration
Manager, you must use Group Policy settings to provision computers with client installation
properties.
Group Policy installation Does not require computers to be discovered before the client can
be installed.
Can be used for new client installations or for upgrades.
Computers can read client installation properties that have been published to Active
Directory Domain Services.
Does not require you to configure and maintain an installation account for the intended client
computer.
Can cause high network traffic if a large number of clients are being installed.
If the Active Directory schema is not extended for System Center 2012 Configuration
Manager, you must use Group Policy settings to add client installation properties to
computers in your site.
Logon script installation Does not require computers to be discovered before the client can
be installed.
Supports using command-line properties for CCMSetup.
Can cause high network traffic if a large number of clients are being installed over a short
time period.
Can take a long time to install on all client computers if users do not frequently log on to the
network.
Manual installation
Does not require computers to be discovered before the client can be installed.
Can be useful for testing purposes.
Supports using command-line properties for CCMSetup.
No automation, therefore time consuming.