Your network contains two Active Directory forests named contoso.com and litwareinc.com.
You deploy System Center 2012 R2 Configuration Manager Service Pack 1 (SP1) to the contoso.com forest.
You deploy the Configuration Manager client to all of the client computers in contoso.com by using a logon script.
All of the client computers in litwareinc.com run a local firewall to prevent traffic to the administrative shares.
You need to ensure that the Configuration Manager client can be deployed to all of the client computers in litwareinc.com.
Which three tasks should you perform? Each correct answer presents part of the solution.
A. Create a Group Policy-based installation of the Configuration Manager client.
B. Enable Active Directory System Discovery.
C. Copy the Cmsetup.msi file to a network share.
D. Configure a Client Push Installation account.
E. Enable Client Push Installation.
F. Enable Active Directory Forest Discovery.
Correct Answer: DEF
Explanation/Reference:
Explanation:
F: In this scenario there are two forests.
Active Directory Forest Discovery can discover Active Directory sites and subnets, and then create Configuration Manager boundaries for each site and subnet from the forests that you have configured for discovery. When Active Directory Forest Discovery identifies a supernet that is assigned to an Active Directory site, Configuration Manager converts the supernet into an IP address range boundary.
DE: Use client push installation to install the System Center 2012 Configuration Manager client software on computers that Configuration Manager discovered. You can configure client push installation for a site, and client installation will automatically run on the computers that are discovered within the site’s configured boundaries when those boundaries are configured as a boundary group.
To configure the site to automatically use client push for discovered computers
1. In the Configuration Manager console, click Administration.
2. In the Administration workspace, expand Site Configuration, and then click Sites.
3. In the Sites list, select the site for which you want to configure automatic site-wide client push installation.
4. On the Home tab, in the Settings group, click Client Installation Settings, and then click Client Push Installation.
5. (E) On the General tab of the Client Push Installation Properties dialog box, select Enable automatic site-wide client push installation. Select the system types to which System Center 2012 Configuration Manager should push the client software by selectingServers, Workstations, or Configuration Manager site system servers. The default selection is Servers andWorkstations.
6. Select whether you want automatic site-wide client push installation to install the System Center 2012 Configuration Manager client software on domain controllers.
7. (D) On the Accounts tab, specify one or more accounts for System Center 2012 Configuration Manager to use when connecting to the computer to install the client software. Click the Create icon, enter the User name and Password, confirm the password, and then click OK. You must specify at least one client push installation account, which must have local administrator rights on every computer on which you want to install the client. If you do not specify a client push installation account, System Center 2012 Configuration Manager tries to use the site system computer account, which will cause cross-domain client push to fail.
Incorrect:
Not A, Not C: This method will not work here as the firewall would block traffic to the network share where the Cmsetup.msi file is copied.
Reference: How to Install Clients on Windows-Based Computers in Configuration Manager
https://technet.microsoft.com/en-us/library/gg712298.aspx#BKMK_ClientPush
Reference: Planning for Discovery in Configuration Manager
https://technet.microsoft.com/en-us/library/gg712308.aspx
