Explore topic-wise InterviewSolutions in .

No. Clients that you UPGRADE from Configuration Manager 2007 will not rerun advertisements that you MIGRATE. System CENTER 2012 Configuration Manager RETAINS the Configuration Manager 2007 Package ID for PACKAGES you migrate and clients that upgrade retain their advertisement history.

No. Clients that you upgrade from Configuration Manager 2007 will not rerun advertisements that you migrate. System Center 2012 Configuration Manager retains the Configuration Manager 2007 Package ID for packages you migrate and clients that upgrade retain their advertisement history.

For a LIST of the ANTIMALWARE solutions that Configuration Manager can AUTOMATICALLY uninstall when you install the Endpoint Protection client, see the Endpoint Protection section in the About Client Settings in Configuration Manager TOPIC.

For a list of the antimalware solutions that Configuration Manager can automatically uninstall when you install the Endpoint Protection client, see the Endpoint Protection section in the About Client Settings in Configuration Manager Topic.

Yes, System CENTER 2012 Endpoint Protection uses Configuration Manager ALERTS to more QUICKLY NOTIFY you when malware is detected on client computers.

Yes, System Center 2012 Endpoint Protection uses Configuration Manager alerts to more quickly notify you when malware is detected on client computers.

Yes, you can DEPLOY ENDPOINT PROTECTION definitions by using Configuration MANAGER Software UPDATES.

Yes, you can deploy Endpoint Protection definitions by using Configuration Manager Software updates.

Endpoint PROTECTION is fully integrated with System Center 2012 Configuration Manager and no longer requires a separate installation. In ADDITION, there are a number of new FEATURES and ENHANCEMENTS in Endpoint Protection.

Endpoint Protection is fully integrated with System Center 2012 Configuration Manager and no longer requires a separate installation. In addition, there are a number of new features and enhancements in Endpoint Protection.

Yes. Use MULTICAST to SIMULTANEOUSLY send data to multiple Configuration Manager Clients RATHER than sending a copy of the data to each client over a separate connection.

Yes. Use multicast to simultaneously send data to multiple Configuration Manager Clients rather than sending a copy of the data to each client over a separate connection.

Yes. These types of COMPUTERS are referred to as unknown computers. For more information about how to DEPLOY operating systems to unknown computers, see How to Manage Unknown COMPUTER DEPLOYMENTS in Configuration Manager.

Yes. These types of computers are referred to as unknown computers. For more information about how to deploy operating systems to unknown computers, see How to Manage Unknown Computer Deployments in Configuration Manager.

Yes. When you deploy an OPERATING system you can ADD steps to your task sequence that capture and restore the USER state. The CAPTURED data can be stored on a state migration point or on the computer where the operating system is deployed.

Yes. When you deploy an operating system you can add steps to your task sequence that capture and restore the user state. The captured data can be stored on a state migration point or on the computer where the operating system is deployed.

Yes. You can use MEDIA such as a CD, DVD set, or a USB flash DRIVE to capture an OPERATING system image and to deploy an operating system. Deployment media includes bootable media, prestaged media, and stand-alone media.

Yes. You can use media such as a CD, DVD set, or a USB flash drive to capture an operating system image and to deploy an operating system. Deployment media includes bootable media, prestaged media, and stand-alone media.

The REPORT does not TRACK the value of bytes SENT over MULTICAST.

The report does not track the value of bytes sent over multicast.

When a pull-distribution POINT downloads content from a source distribution point, that ACCESS is counted as a CLIENT access for the purpose of this report.

When a pull-distribution point downloads content from a source distribution point, that access is counted as a client access for the purpose of this report.

The following reasons might CAUSE the numbers shown in Completions Statistics and the View Status pane to differ:

• The completion statistics are summarized and the View Status pane displays live data – SELECT the deployment in the Deployments node of the Monitoring workspace and then, in the Home tab, in the Deployment GROUP, click Run Summarization. Refresh the display in the Configuration Manager console and after summarization completes, the updated completion statistics will display in the Configuration Manager console.
• An application contains multiple deployment types. The completion statistics display one status for the application; the View Status pane displays status for each deployment type in the application.
• The client encountered an error. It was able to report status for the application, but not for the deployment types contained in the application. You can use the report Application Infrastructure Errors to troubleshoot this scenario.

The following reasons might cause the numbers shown in Completions Statistics and the View Status pane to differ:

The compliance percentage (Compliance %) is CALCULATED by taking the number of users or DEVICES with a deployment STATE of SUCCESS added to the number of devices with a deployment state of Requirements Not Met and then DIVIDING this total by the number of users or devices that the deployment was sent to.

The compliance percentage (Compliance %) is calculated by taking the number of users or devices with a deployment state of Success added to the number of devices with a deployment state of Requirements Not Met and then dividing this total by the number of users or devices that the deployment was sent to.

The software update group icons are DIFFERENT in the FOLLOWING scenarios:

• When a software update group contains at least one expired software update, the icon for that software update group contains a black X.
• When a software update group contains no expired software updates, but at least one SUPERSEDED software update, the icon for that software update group contains a yellow star.
• When a software update group has no expired or superseded software updates, the icon for that software update group contains a green ARROW.

The software update group icons are different in the following scenarios:

SYSTEM Center 2012 Configuration Manager might AUTOMATICALLY REMOVE expired and superseded software updates.

Consider the following scenarios:

• Expired software updates that are not associated with a deployment are automatically removed up every 7 days by a site maintenance task.
• Expired software updates that are associated with a deployment are not automatically removed by the site maintenance task.
• Superseded software updates that you have configured not to expire for a specified period of time are not removed or deleted by the site maintenance task.

You can remove expired software updates from all software update groups and software update deployments so that they are automatically removed. To do this, search for expired software updates, select the returned results, choose edit membership, and remove the expired software updates from any software update group for which they are members.

System Center 2012 Configuration Manager might automatically remove expired and superseded software updates.

Consider the following scenarios:

You can remove expired software updates from all software update groups and software update deployments so that they are automatically removed. To do this, search for expired software updates, select the returned results, choose edit membership, and remove the expired software updates from any software update group for which they are members.

In CONFIGURATION MANAGER 2007, superseded software updates are automatically expired during full software updates synchronization. In SYSTEM Center 2012 Configuration Manager, you can choose to automatically expire superseded software updates during software updates synchronization just as it is in Configuration Manager 2007. Or, you can SPECIFY a number of months before a superseded software update is expired. This allows you to deploy a superseded software update for the PERIOD of time while you validate and approve the superseding software update in your environment.

In Configuration Manager 2007, superseded software updates are automatically expired during full software updates synchronization. In System Center 2012 Configuration Manager, you can choose to automatically expire superseded software updates during software updates synchronization just as it is in Configuration Manager 2007. Or, you can specify a number of months before a superseded software update is expired. This allows you to deploy a superseded software update for the period of time while you validate and approve the superseding software update in your environment.

Yes. You can CREATE automatic DEPLOYMENT RULES to AUTOMATICALLY approve and deploy software updates that meet specified search criteria.

Yes. You can create automatic deployment rules to automatically approve and deploy software updates that meet specified search criteria.

Software UPDATE GROUPS provide a more effective method for you to organize software updates in your environment. You can manually add software updates to a software update group or software updates can be automatically ADDED to a new or existing software update group by USING an AUTOMATIC deployment rule. You can also deploy a software update group manually or automatically by using an automatic deployment rule. After you deploy a software update group, you can add new software updates to the group and they will automatically be deployed.

Software update groups provide a more effective method for you to organize software updates in your environment. You can manually add software updates to a software update group or software updates can be automatically added to a new or existing software update group by using an automatic deployment rule. You can also deploy a software update group manually or automatically by using an automatic deployment rule. After you deploy a software update group, you can add new software updates to the group and they will automatically be deployed.

No. Software update groups are new in System Center 2012 CONFIGURATION MANAGER and replace update lists that were used in Configuration Manager 2007.

No. Software update groups are new in System Center 2012 Configuration Manager and replace update lists that were used in Configuration Manager 2007.

In Configuration Manager 2007, you had to use collections to identify which devices should install software, such as applications, task sequences, and software updates. In SYSTEM Center 2012 Configuration Manager, you must continue to use collections for task sequences, but for applications, you can now use requirement rules as a method to control which devices install the software. For example, you could deploy an application to the All Desktop and Server Clients collection, but include a requirement rule that specifies that the application should be installed only on computers that run Windows 8. Software updates already have these requirements capability built in, so you do not need to configure this yourself.

Although defining the requirements within the application deployment usually requires more work initially, it has longer term benefits because it reduces the administrative overhead of maintaining, USING, and searching many collections. Additionally, requirements are evaluated by the client at deployment time, whereas query-based collections are evaluated periodically and often depend on the results of hardware inventory collection that might run only once a week. Another consideration when you have many collections with complex query rules is that the collection EVALUATION can result in noticeable CPU processing on the site server.

In summary, we recommend that for most application deployments, you use requirement rules instead of collections. Continue to use collections for task sequences, package and programs, TESTING purposes, and one-off application deployments.

In Configuration Manager 2007, you had to use collections to identify which devices should install software, such as applications, task sequences, and software updates. In System Center 2012 Configuration Manager, you must continue to use collections for task sequences, but for applications, you can now use requirement rules as a method to control which devices install the software. For example, you could deploy an application to the All Desktop and Server Clients collection, but include a requirement rule that specifies that the application should be installed only on computers that run Windows 8. Software updates already have these requirements capability built in, so you do not need to configure this yourself.

Although defining the requirements within the application deployment usually requires more work initially, it has longer term benefits because it reduces the administrative overhead of maintaining, using, and searching many collections. Additionally, requirements are evaluated by the client at deployment time, whereas query-based collections are evaluated periodically and often depend on the results of hardware inventory collection that might run only once a week. Another consideration when you have many collections with complex query rules is that the collection evaluation can result in noticeable CPU processing on the site server.

In summary, we recommend that for most application deployments, you use requirement rules instead of collections. Continue to use collections for task sequences, package and programs, testing purposes, and one-off application deployments.

You can install APPLICATIONS only when the write filter on the Windows Embedded DEVICE is disabled. If you try to install an application on a Windows Embedded device that has write filters enabled, you SEE an error message that you have INSUFFICIENT permissions to install the application and the INSTALLATION fails.

You can install applications only when the write filter on the Windows Embedded device is disabled. If you try to install an application on a Windows Embedded device that has write filters enabled, you see an error message that you have insufficient permissions to install the application and the installation fails.

ALTHOUGH you cannot DEPLOY a simulated and a standard DEPLOYMENT of an application to the same COLLECTION, you can target a computer with both if you deploy them to DIFFERENT collections and the computer is a member of both collections. In this scenario, for both deployments, the computer reports the results of the standard deployment. This explains how you might see deployment states for a simulated deployment that you would usually only see for a standard deployment, such as In Progress and Error.

Although you cannot deploy a simulated and a standard deployment of an application to the same collection, you can target a computer with both if you deploy them to different collections and the computer is a member of both collections. In this scenario, for both deployments, the computer reports the results of the standard deployment. This explains how you might see deployment states for a simulated deployment that you would usually only see for a standard deployment, such as In Progress and Error.

In most cases, a DEPLOYMENT with an action of Uninstall will always uninstall a deployment type if it is detected UNLESS the client type is DIFFERENT. For example, if you deploy a mobile device APPLICATION with an action of Uninstall to a desktop computer, the deployment will FAIL with a status of Requirements not met as it is impossible to enforce this uninstall.

In most cases, a deployment with an action of Uninstall will always uninstall a deployment type if it is detected unless the client type is different. For example, if you deploy a mobile device application with an action of Uninstall to a desktop computer, the deployment will fail with a status of Requirements not met as it is impossible to enforce this uninstall.

Although you can configure the application deployment summarization INTERVAL, by default, the following values apply:

• Deployments that were MODIFIED in the last 30 DAYS – 1 hour
• Deployments that were modified in the last 31 to 90 days – 1 day
• Deployments that were modified over 90 days ago – 1 week

You can modify the application deployment summarization intervals from the Status Summarizers DIALOG box. Click Status Summarizers from the Sites node in the Administration workspace to open this dialog box.

Although you can configure the application deployment summarization interval, by default, the following values apply:

You can modify the application deployment summarization intervals from the Status Summarizers dialog box. Click Status Summarizers from the Sites node in the Administration workspace to open this dialog box.

If you don’t require HTTPS connections (for example, users will not CONNECT from the Internet), you can use the following the quick guide instructions:

Make sure that you have all the prerequisites for the Application CATALOG site ROLES.

Install the following Application Catalog site system roles and select the default options:

• Application Catalog web service point
• Application Catalog website point

Configure the following Computer AGENT device client settings by editing the default client settings, or by creating and assigning custom client settings:

• Default Application Catalog website point: Automatically detect
• Add default Application Catalog website to Internet Explorer trusted site ZONE: True 
• Install Permissions: All users

If you don’t require HTTPS connections (for example, users will not connect from the Internet), you can use the following the quick guide instructions:

Make sure that you have all the prerequisites for the Application Catalog site roles.

Install the following Application Catalog site system roles and select the default options:

Configure the following Computer Agent device client settings by editing the default client settings, or by creating and assigning custom client settings:

Deployments to users or devices are summarized BASED on the worst result. For example, if a deployment is successful on one device and the APPLICATION requirements were not met on ANOTHER device then the deployment for the USER is summarized as Requirements Not Met. If none of the user’s devices has RECEIVED the application, the deployment is summarized as Unknown.

Deployments to users or devices are summarized based on the worst result. For example, if a deployment is successful on one device and the application requirements were not met on another device then the deployment for the user is summarized as Requirements Not Met. If none of the user’s devices has received the application, the deployment is summarized as Unknown.

No, you can continue to deploy packages and PROGRAMS that have been migrated from your Configuration Manager 2007 site. However, packages and programs cannot use some of the NEW features of SYSTEM Center 2012 Configuration Manager such as requirement RULES, dependencies and supersedence.

No, you can continue to deploy packages and programs that have been migrated from your Configuration Manager 2007 site. However, packages and programs cannot use some of the new features of System Center 2012 Configuration Manager such as requirement rules, dependencies and supersedence.

Depending on the deployment purpose you have specified in the deployment TYPE of an application, System Center 2012 Configuration Manager periodically checks that the state of the application is the same as its purpose. For EXAMPLE, if an application’s deployment type is specified as Required, Configuration Manager reinstalls the application if it has been REMOVED. Only one deployment type can be CREATED per application and collection PAIR.

Depending on the deployment purpose you have specified in the deployment type of an application, System Center 2012 Configuration Manager periodically checks that the state of the application is the same as its purpose. For example, if an application’s deployment type is specified as Required, Configuration Manager reinstalls the application if it has been removed. Only one deployment type can be created per application and collection pair.

Yes. In System Center 2012 Configuration Manager, the term software includes software updates, applications, SCRIPTS, TASK SEQUENCES, DEVICE drivers, configuration items, and configuration baselines.

Yes. In System Center 2012 Configuration Manager, the term software includes software updates, applications, scripts, task sequences, device drivers, configuration items, and configuration baselines.

Yes. You can see migrated packages and PROGRAMS in the Packages node in the Software Library workspace. You can also USE the IMPORT Package from DEFINITION Wizard to import Configuration Manager 2007 package definition files into your site.

Yes. You can see migrated packages and programs in the Packages node in the Software Library workspace. You can also use the Import Package from Definition Wizard to import Configuration Manager 2007 package definition files into your site.

In this case, the following RULES apply:

• If both deployments have a PURPOSE of Available, the USER deployment will be installed.
• If both deployments have a purpose of Required, the deployment with the earliest DEADLINE will be installed.
• If one deployment has a purpose of Available and the other deployment has a purpose of required, the deployment with the purpose of required will be installed.

In this case, the following rules apply:

No. you must CREATE a NEW DEPLOYMENT that can INCLUDE extra options that include SCHEDULING and user experience.

No. you must create a new deployment that can include extra options that include scheduling and user experience.

YES. Configuration Manager collects usage statistics from client devices that can be used to AUTOMATICALLY define user device affinities or to help you MANUALLY create affinities.

Yes. Configuration Manager collects usage statistics from client devices that can be used to automatically define user device affinities or to help you manually create affinities.

Yes. You can CONFIGURE MULTIPLE deployment types for an application. RULES that specify which deployment TYPE is run allows you to specify how the application is made available to the user.

Yes. You can configure multiple deployment types for an application. Rules that specify which deployment type is run allows you to specify how the application is made available to the user.

Some SCENARIOS, such as the deployment of a SCRIPT that runs on a CLIENT computer but that does not install software, are more suited to using a package and program rather than an application.

Some scenarios, such as the deployment of a script that runs on a client computer but that does not install software, are more suited to using a package and program rather than an application.

Yes. USERS can browse a list of available SOFTWARE in the Application Catalog. Users can then request an application which, if approved, will be installed on their computer. To make a DEPLOYMENT optional, configure the deployment PURPOSE as Available in the APPLICATIONS deployment type.

Yes. Users can browse a list of available software in the Application Catalog. Users can then request an application which, if approved, will be installed on their computer. To make a deployment optional, configure the deployment purpose as Available in the applications deployment type.

To make a deployment OPTIONAL, CONFIGURE the deployment PURPOSE as AVAILABLE in the applications deployment type. Available applications display in the Application CATALOG where users can install them.

To make a deployment optional, configure the deployment purpose as Available in the applications deployment type. Available applications display in the Application Catalog where users can install them.

Global CONDITIONS are conditions used by requirement RULES. Requirement rules set a value for a DEPLOYMENT type for a global CONDITION.

For example: “operating system =” is a global condition; a requirement RULE is “operating system = Win7.”

Global conditions are conditions used by requirement rules. Requirement rules set a value for a deployment type for a global condition.

For example: “operating system =” is a global condition; a requirement rule is “operating system = Win7.”

The deployment PURPOSE defines what the deployment should do and represents the administrator’s intent. For example, an administrative USER might require the installation of SOFTWARE on CLIENT computers or might just make the software available for users to install themselves. A global condition can be SET to check regularly that required applications are installed and to reinstall them if they have been removed.

The deployment purpose defines what the deployment should do and represents the administrator’s intent. For example, an administrative user might require the installation of software on client computers or might just make the software available for users to install themselves. A global condition can be set to check regularly that required applications are installed and to reinstall them if they have been removed.

A DEPLOYMENT type is contained within an application and specifies the installation files and method that CONFIGURATION Manager will use to install the software. The deployment type contains rules and settings that control if and how the software is INSTALLED on client computers.

A deployment type is contained within an application and specifies the installation files and method that Configuration Manager will use to install the software. The deployment type contains rules and settings that control if and how the software is installed on client computers.

System Center 2012 Configuration Manager applications contain the ADMINISTRATIVE details and APPLICATION CATALOG information necessary to deploy a SOFTWARE package or software UPDATE to a computer or mobile device.

System Center 2012 Configuration Manager applications contain the administrative details and Application Catalog information necessary to deploy a software package or software update to a computer or mobile device.

No, SITE servers do not compress the content that it distributes to distribution points that are enabled for bandwidth control. Whereas site-to-site transfers potentially resend files that might already be present, only to be discarded by the destination site server, a site server SENDS only the files that a distribution point requires. With a lower volume of data to transfer, the DISADVANTAGES of high CPU processing to compress and decompress the data usually OUTWEIGH the advantages of compressing the data.

No, site servers do not compress the content that it distributes to distribution points that are enabled for bandwidth control. Whereas site-to-site transfers potentially resend files that might already be present, only to be discarded by the destination site server, a site server sends only the files that a distribution point requires. With a lower volume of data to transfer, the disadvantages of high CPU processing to compress and decompress the data usually outweigh the advantages of compressing the data.

The remote control SETTINGS for SYSTEM CENTER 2012 CONFIGURATION Manager Clients are now in Software Center, on the Options TAB.

The remote control settings for System Center 2012 Configuration Manager Clients are now in Software Center, on the Options tab.

You can FIND this out by using the remote CONTROL REPORTS: Remote Control – All COMPUTERS remote controlled by a specific user and Remote Control – All remote control information.

You can find this out by using the remote control reports: Remote Control – All computers remote controlled by a specific user and Remote Control – All remote control information.

YES. In the Configuration Manager remote CONTROL window, CLICK ACTION, and then click Send Ctrl+Alt+Del.

Yes. In the Configuration Manager remote control window, click Action, and then click Send Ctrl+Alt+Del.

The Permitted Viewers List grants an administrative user the Remote Control permission for a COMPUTER, and the role-based ADMINISTRATION security role of Remote Tools Operator grants an administrative user the ability to connect a Configuration MANAGER console to a SITE so that audit messages are sent when they manage computers by using remote control.

The Permitted Viewers List grants an administrative user the Remote Control permission for a computer, and the role-based administration security role of Remote Tools Operator grants an administrative user the ability to connect a Configuration Manager console to a site so that audit messages are sent when they manage computers by using remote control.

TCP 2701 is the only port that System Center 2012 Configuration Manager uses for remote control. When you ENABLE remote control as a client setting, you can SELECT one of three firewall PROFILES that automatically configure this port on Configuration Manager Clients: Domain, Private, or PUBLIC.

TCP 2701 is the only port that System Center 2012 Configuration Manager uses for remote control. When you enable remote control as a client setting, you can select one of three firewall profiles that automatically configure this port on Configuration Manager Clients: Domain, Private, or Public.

By default, REMOTE CONTROL is disabled on client computers. Enable remote control as a default client SETTING for the hierarchy, or by using custom client settings that you apply to selected COLLECTIONS.

By default, remote control is disabled on client computers. Enable remote control as a default client setting for the hierarchy, or by using custom client settings that you apply to selected collections.

No. Mobile DEVICES that are enrolled by Configuration Manager Support only required apps, so USERS cannot choose company apps to install. Users who have mobile devices that are enrolled by Microsoft Intune install company apps from the company portal. HOWEVER, if these apps require approval, users must FIRST request approval from the Application CATALOG.

No. Mobile devices that are enrolled by Configuration Manager Support only required apps, so users cannot choose company apps to install. Users who have mobile devices that are enrolled by Microsoft Intune install company apps from the company portal. However, if these apps require approval, users must first request approval from the Application Catalog.

No. Without the MICROSOFT Intune connector, you can manage these devices by collecting HARDWARE inventory, configure settings such as passwords and ROAMING, and remotely wipe the device. However, if you WANT to MAKE company apps available to Android devices, you must install the Microsoft Intune connector.

No. Without the Microsoft Intune connector, you can manage these devices by collecting hardware inventory, configure settings such as passwords and roaming, and remotely wipe the device. However, if you want to make company apps available to Android devices, you must install the Microsoft Intune connector.