Application Catalog

Configuration Manager uses this setting to connect users to the Application Catalog from Software Center. You can specify a server that hosts the Application Catalog web site point, specify automatic selection, or specify a URL. If you specify automatic selection, clients make a service location request to the management point, which returns a list of available Application Catalogs in the hierarchy. Clients then select an Application Catalog from the list. Automatic selection provides fault tolerance when you have more than one Application Catalog but this method does not guarantee that the closest server is selected.

Add Application Catalog website to Internet Explorer trusted sites zone

If this option is configured as True, the website of the Application Catalog is automatically added to the trusted sites zone in Internet Explorer on clients.

If you leave this option as False, users might be prompted for their credentials when they connect to the Application Catalog.

Organization Name displayed in Software Center

Type the name that users see in Software Center. This branding information helps users to identify this application as a trusted source.

Install Permissions

Configure how users can initiate the installation of software, software updates, and task sequences:

• All Users: Users logged on to a client computer with any permission except Guest can initiate the installation of software, software updates, and task sequences.
  
  
• Only Administrators: Users logged on to a client computer must be a member of the local Administrators group to initiate the installation of software, software updates, and task sequences.
  
  
• Only Administrators and primary users: Users logged on to a client computer must be a member of the local Administrators group or a primary user of the computer to initiate the installation of software, software updates and task sequences.
  
  
• No Users: No users logged on to a client computer can initiate the installation of software, software updates, and task sequences. Required deployments for the computer are always installed at the deadline and users cannot initiate the installation of software from the Application Catalog or Software Center.
  
  

Suspend Bitlocker PIN entry on restart

If the Bitlocker PIN entry is configured on computers, this option can bypass the requirement to enter a PIN when the computer restarts after a software installation.

• Always: Configuration Manager temporarily suspends the Bitlocker requirement to enter a PIN on the next computer startup after it has installed software that requires a restart. This setting applies only to computer restarts that are initiated by Configuration Manager and does not suspend the requirement to enter the Bitlocker PIN when the user restarts the computer. The Bitlocker PIN entry requirement is resumed after Windows startup.
  
  
• Never: Configuration Manager does not suspend the Bitlocker requirement to enter a PIN on the next computer startup after it has installed software that requires a restart. In this scenario, the software installation cannot complete until the user enters the PIN to restart the computer and Windows restarts.
  
  

Agent extensions manage the deployment of applications and software updates

Enable this option only if one of the following conditions apply:

• You use a vendor solution that requires this setting to be enabled.
  
  
• You use the Configuration Manager 2012 software development kit (SDK) to manage client agent notifications and the installation of applications and software updates.
  
  

PowerShell execution policy

Maximum custom MIF file size (KB)

Specify the maximum size, in KB, allowed for each custom MIF file that will be collected from a client during a hardware inventory cycle. You can specify a size between 1 and 5,000 KB. By default, this value is set to 250KB. This setting does not affect the size of the regular hardware inventory data file.

Hardware inventory classes

If a custom MIF file is larger than the maximum size allowed, the hardware inventory client agent will move the IDMIF file to the \Badmifs folder. In this case, the custom MIF file is not sent to the site server for processing.

Collect MIF files

Use this setting to specify whether to collect Management Information Format (MIF) files from Configuration Manager 2012 clients during hardware inventory.

For a MIF file to be collected by hardware inventory, it must be located in the correct location on the client computer. By default, the files should be located as follows:

• IDMIF files should be located in the Windows\System32\CCM\Inventory\idmif folder.
  
  
• NOIDMIF files should be located in the Windows\System32\CCM\Inventory\noidmif folder.
  
  

Collect IDMIF files

Adds a new architecture—and attributes and classes—to the Configuration Manager 2012 site database.

IDMIF files are used to add information to the site database for objects other than Configuration Manager 2012 clients.

Collect NOIDMIF files

Extends the hardware inventory by adding attributes and classes to existing architectures on a client.

NOIDMIF files are used to extend, or add, new information about existing Configuration Manager 2012 clients to the site database.

Manage unsolicited Remote Assistance settings

When set to True, a user at the client computer does not have to request assistance before Configuration Manager can open a Remote Assistance session.

Manage solicited Remote Assistance settings

When set to True, a user at the client computer must first request assistance before Configuration Manager can open a Remote Assistance session.

Require network level authentication on computers that run Windows Vista operation system or later

Select this more secure option when you are running the Configuration Manager 2012 console on a computer that is running Windows Vista or later, or you have upgraded the Remote Desktop Protocol (RDP) to a version that supports network level authentication. For more information about using RDP and network level authentication see the help topic What types of Remote Desktop connections should I allow in your Windows documentation.

Usage based affinity threshold (minutes)

Specify the number of minutes of usage before a user device affinity is created.

Usage based affinity threshold (over days)

Specify the number of days over which the usage based affinity threshold is measured.

Note
For example, if Usage based affinity threshold (minutes) is specified as 60 minutes and Usage based affinity threshold (over days) is specified at 5 days, the user must use the device for 60 minutes over a period of 5 days to automatically create a user device affinity.

Usage based affinity threshold (minutes)

Specify how often that client computers check and report user device affinity information to the site server.

Allow usage data collected from device to define relationship

From the drop-down list, select True to enable the site to automatically create user device affinities based on usage.

Mobile device enrollment profile

Before you can configure this setting, you must first set to True the mobile device user setting Allow users to enroll mobile devices. Then you can click Set Profile to specify a mobile device profile that contains information about the certificate template to use during the enrollment process, the site that contains an enrollment point and enrollment proxy point, and the site that will manage mobile devices after the enrollment.

Important
Make sure that you have configured a certificate template to use for mobile device enrollment before you configure this option.

For more information about how to enroll mobile devices, see How to Enroll Mobile Device Clients in Configuration Manager 2012.

Allow user to define relationship

Specify whether users are allowed to identify their own primary devices from the Application Catalog, My Systems tab.