READ Free Dumps For Microsoft- 70-243
| Question ID 6304 | Your company uses System Center 2012 Configuration Manager to deploy applications.
The company purchases a new application named App1. App1 can be installed only on client computers that
run Windows 7.
You need to ensure that App1 is installed only on Windows 7 computers that have at least 2 Gb of
memory and 300 Gb of free disk space.
What should you create?
|
| Option A | a Query object
|
| Option B | custom client user settings
|
| Option C | a configuration baseline
|
| Option D | a query-based collection
|
| Correct Answer | D |
Explanation Explanation/Reference: Answer: a query-based collection Personal note: Previous experience with this question is that the answer should be "a requirement rules". However, since this question does not provide that possibility, the next best thing is "a query-based collection". Explanation: http://technet.microsoft.com/en-us/library/gg682177.aspx Introduction to Collections in Configuration Manager Collections in System Center 2012 Configuration Manager represent logical groupings of resources, such as users and devices. You can use collections to help you perform many tasks, such as managing applications, deploying compliance settings, or installing software updates. You can also use collections to manage groups of client settings. .. Query Rule Query rules dynamically update the membership of a collection based on a query that Configuration Manager runs on a schedule. For example, you can create a collection of users who are a member of the Human Resources organizational unit in Active Directory Domain Services. Unlike direct rule collections, this collection membership automatically updates when you add or remove new users to the Human Resources organizational unit. Further information: http://technet.microsoft.com/en-us/library/gg682073.aspx Prerequisites for Compliance Settings in Configuration Manager .. To run queries related to compliance settings: Read permission for the Query object. http://technet.microsoft.com/en-us/library/gg712688.aspx Planning for Client Settings in Configuration Manager Use client settings in System Center 2012 Configuration Manager to configure user and device settings for the hierarchy. Client settings include configuration options such as the hardware inventory and schedule, and the polling schedule for client policy. All Configuration Manager clients in the hierarchy use the Default Client Settings that are automatically created when you install Configuration Manager. However, you can modify the default client settings and you can create custom client settings to override the default client settings for specific users or devices. http://technet.microsoft.com/en-us/library/gg682139.aspx Introduction to Compliance Settings in Configuration Manager .. Compliance is evaluated by defining a configuration baseline that contains the configuration items that you want to evaluate and settings and rules that describe the level of compliance you must have.
| Question ID 6305 | 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 allow File 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.)
|
| Option A | a logon script installation
|
| Option B | a manual client installation
|
| Option C | a software update-based client installatio
|
| Option D | a Client Push Installation
|
| Option E | an Active Directory Group Policy-based installation
|
| Correct Answer | CDE |
Explanation Explanation/Reference: Answer: a software update-based client installation a Client Push Installation an Active Directory Group Policy-based installation Explanation: 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.