Explore topic-wise InterviewSolutions in .

Use the following PROCEDURE to configure the Network Access Account:

1. How to configure the Network Access Account for a SITE.
2. In the Administration workspace, expand Site Configuration, click SITES, and then select the site.
3. On the Settings group, click Configure Site Components, and then click Software Distribution.
4. Click the Network Access Account TAB, configure the account, and then click OK.

Use the following procedure to configure the Network Access Account:

Configuration Manager supports some site SYSTEM roles only at specific sites in a hierarchy, and some site system roles have other limitations as to where and when you can install them. When Configuration Manager does not support the installation of a site system role, it is not listed in the WIZARD. For example, the Endpoint Protection point cannot be installed in a secondary site, or in a primary site if you have a central ADMINISTRATION site. So if you have a central administration site, you will not see the Endpoint Protection point listed if you run the Add Site System Roles Wizard on a primary site.

Other examples include you cannot add a second management point to a secondary site, and you cannot add a management point or distribution point to a central administration site.

In addition, in Configuration Manager SP1, you do not see the Microsoft Intune connector listed as an available site system role until you have created the Microsoft Intune subscription.

Configuration Manager supports some site system roles only at specific sites in a hierarchy, and some site system roles have other limitations as to where and when you can install them. When Configuration Manager does not support the installation of a site system role, it is not listed in the wizard. For example, the Endpoint Protection point cannot be installed in a secondary site, or in a primary site if you have a central administration site. So if you have a central administration site, you will not see the Endpoint Protection point listed if you run the Add Site System Roles Wizard on a primary site.

Other examples include you cannot add a second management point to a secondary site, and you cannot add a management point or distribution point to a central administration site.

In addition, in Configuration Manager SP1, you do not see the Microsoft Intune connector listed as an available site system role until you have created the Microsoft Intune subscription.

No. Although both configurations use the Internet, they are independent from each other. Clients on the intranet can use cloud-based distribution points and these clients do not REQUIRE a PKI client certificate. However, you still require PKI CERTIFICATES if you want to use cloud-based distribution points; ONE for the Windows Azure MANAGEMENT certificate that you install on the site system SERVER that hosts the cloud-based distribution points, and one for the cloud-based distribution point service certificate that you import when you configure the cloud-based distribution point.

No. Although both configurations use the Internet, they are independent from each other. Clients on the intranet can use cloud-based distribution points and these clients do not require a PKI client certificate. However, you still require PKI certificates if you want to use cloud-based distribution points; one for the Windows Azure management certificate that you install on the site system server that hosts the cloud-based distribution points, and one for the cloud-based distribution point service certificate that you import when you configure the cloud-based distribution point.

UNLIKE Configuration Manager 2007, there are no design restrictions to support clients on the Internet, providing you meet the REQUIREMENTS in the Planning for Internet-Based Client Management section in the Planning for Communications in Configuration Manager Topic. Because of the following improvements, you can more easily support clients on the Internet to fit your existing infrastructure:

• The whole site does not have to be using HTTPS client connections.
• Support for installing most site SYSTEM roles in another forest.
• Support for MULTIPLE management points in a site.

If you use multiple management points and dedicate one or more for client connections from the Internet, you might want to consider using database REPLICAS for management points.

Unlike Configuration Manager 2007, there are no design restrictions to support clients on the Internet, providing you meet the requirements in the Planning for Internet-Based Client Management section in the Planning for Communications in Configuration Manager Topic. Because of the following improvements, you can more easily support clients on the Internet to fit your existing infrastructure:

If you use multiple management points and dedicate one or more for client connections from the Internet, you might want to consider using database replicas for management points.

System Center 2012 Configuration Manager has replaced the NATIVE MODE site configuration in Configuration Manager 2007 with individual site system role configurations that accept client communication over HTTPS or HTTP. Because you can have site system roles that support HTTPS and HTTP in the same site, you have more flexibility in how you introduce PKI to secure the intranet client endpoints within the hierarchy. Clients over the Internet and mobile devices MUST use HTTPS connections.

System Center 2012 Configuration Manager has replaced the native mode site configuration in Configuration Manager 2007 with individual site system role configurations that accept client communication over HTTPS or HTTP. Because you can have site system roles that support HTTPS and HTTP in the same site, you have more flexibility in how you introduce PKI to secure the intranet client endpoints within the hierarchy. Clients over the Internet and mobile devices must use HTTPS connections.

SYSTEM Center 2012 CONFIGURATION Manager clients can find available management points by using the management point that you specify during client deployment, Active Directory Domain Services, DNS, and WINS. Clients can connect to more than one management point in a SITE, ALWAYS preferring communication that uses HTTPS, when this is possible because the client and management point uses PKI CERTIFICATES.

There are some changes here since Configuration Manager 2007, which accommodate the change that clients can now communicate with more than one management point in site, and that you can have a mix of HTTPS and HTTP site system roles in the same site.

System Center 2012 Configuration Manager clients can find available management points by using the management point that you specify during client deployment, Active Directory Domain Services, DNS, and WINS. Clients can connect to more than one management point in a site, always preferring communication that uses HTTPS, when this is possible because the client and management point uses PKI certificates.

There are some changes here since Configuration Manager 2007, which accommodate the change that clients can now communicate with more than one management point in site, and that you can have a mix of HTTPS and HTTP site system roles in the same site.

No. Because System Center 2012 CONFIGURATION MANAGER supports installing most site system roles in UNTRUSTED forests, there is no requirement to have a separate site for this scenario, UNLESS you have exceeded the maximum NUMBER of supported clients for a site.

No. Because System Center 2012 Configuration Manager supports installing most site system roles in untrusted forests, there is no requirement to have a separate site for this scenario, unless you have exceeded the maximum number of supported clients for a site.

Configuration Manager supports SITE-to-site (INTERSITE) communication when a two-way forest TRUST exists between the forests. Within a site, Configuration Manager supports placement of site system ROLES on computers in an UNTRUSTED forest. Configuration Manager also supports clients that are in a different forest from their site’s site server when the site system role that they connect to is in the same forest as the client.

Configuration Manager supports site-to-site (intersite) communication when a two-way forest trust exists between the forests. Within a site, Configuration Manager supports placement of site system roles on computers in an untrusted forest. Configuration Manager also supports clients that are in a different forest from their site’s site server when the site system role that they connect to is in the same forest as the client.

YES. System Center 2012 Configuration Manager applies a hierarchy-wide set of default client settings (formerly called client agent settings) that you can then modify on clients by USING custom client settings that you ASSIGN to collections. This CREATES a flexible method of delivering customized client settings to any client in your hierarchy, regardless of the site it is assigned to, or where it is located on your network.

Yes. System Center 2012 Configuration Manager applies a hierarchy-wide set of default client settings (formerly called client agent settings) that you can then modify on clients by using custom client settings that you assign to collections. This creates a flexible method of delivering customized client settings to any client in your hierarchy, regardless of the site it is assigned to, or where it is located on your network.

ACTIVE Directory Forest discovery is a new discovery method in System Center 2012 Configuration MANAGER that allows you to discover network locations from multiple Active Directory FORESTS. This discovery method can also create boundaries in Configuration Manager for the discovered network locations and you can publish site DATA to another Active Directory forest to help SUPPORT clients, sites, and site system servers in those locations.

Active Directory Forest discovery is a new discovery method in System Center 2012 Configuration Manager that allows you to discover network locations from multiple Active Directory forests. This discovery method can also create boundaries in Configuration Manager for the discovered network locations and you can publish site data to another Active Directory forest to help support clients, sites, and site system servers in those locations.

See the MONITOR Infrastructure for Configuration Manager Section in the Monitor Configuration Manager Sites and HIERARCHY topic. This section INCLUDES information about database REPLICATION and how to use the Replication LINK Analyzer.

See the Monitor Infrastructure for Configuration Manager Section in the Monitor Configuration Manager Sites and Hierarchy topic. This section includes information about database replication and how to use the Replication Link Analyzer.

Database replication uses SQL Server to quickly transfer data for settings and configurations to other sites in the Configuration Manager hierarchy. CHANGES that are made at one SITE merge with the INFORMATION STORED in the database at other sites. Content for deployments, and other file-based data, still replicate by file-based replication between sites. Database replication configured automatically when you join a new site to an existing hierarchy.

Database replication uses SQL Server to quickly transfer data for settings and configurations to other sites in the Configuration Manager hierarchy. Changes that are made at one site merge with the information stored in the database at other sites. Content for deployments, and other file-based data, still replicate by file-based replication between sites. Database replication configured automatically when you join a new site to an existing hierarchy.

In System CENTER 2012 Configuration Manager, secondary sites require either SQL Server, or SQL Server EXPRESS to support database replication with their parent primary site. When you install a secondary site, SETUP automatically installs SQL Server Express if a local instance of SQL Server is not already INSTALLED.

In System Center 2012 Configuration Manager, secondary sites require either SQL Server, or SQL Server Express to support database replication with their parent primary site. When you install a secondary site, Setup automatically installs SQL Server Express if a local instance of SQL Server is not already installed.

With System Center 2012 Configuration Manager, primary sites have changed to support only secondary sites as child sites, and the new central administration site as a parent site. Unlike Configuration Manager 2007, primary sites no LONGER provide a security or configuration boundary. Because of this, you should only need to INSTALL additional primary sites to increase the maximum NUMBER of clients your hierarchy can support, or to provide a local point of CONTACT for administration.

With System Center 2012 Configuration Manager, primary sites have changed to support only secondary sites as child sites, and the new central administration site as a parent site. Unlike Configuration Manager 2007, primary sites no longer provide a security or configuration boundary. Because of this, you should only need to install additional primary sites to increase the maximum number of clients your hierarchy can support, or to provide a local point of contact for administration.

In System Center 2012 Configuration Manager with no service pack, you cannot change the parent relationship of an ACTIVE site. You can only add a site as a child of another site at the time you install the new site. Because the database is shared between all sites, JOINING a site that has already created default objects or that has custom CONFIGURATIONS can result in conflicts with similar objects that already exist in the hierarchy.

However, in System Center 2012 Configuration Manager SP1, you can expand a stand-alone PRIMARY site into a hierarchy that INCLUDES a new central administration site.

In System Center 2012 Configuration Manager with no service pack, you cannot change the parent relationship of an active site. You can only add a site as a child of another site at the time you install the new site. Because the database is shared between all sites, joining a site that has already created default objects or that has custom configurations can result in conflicts with similar objects that already exist in the hierarchy.

However, in System Center 2012 Configuration Manager SP1, you can expand a stand-alone primary site into a hierarchy that includes a new central administration site.

SYSTEM Center 2012 Configuration Manager introduces changes to both primary and SECONDARY sites while the central administration site is NEW site type. The central administration site replaces the primary site REFERRED to as a central site as the top-level site of a multi-primary site hierarchy. This site does not directly manage clients but does coordinate a shared database across your hierarchy, and it is designed to provide centralized reporting and CONFIGURATIONS for your entire hierarchy.

System Center 2012 Configuration Manager introduces changes to both primary and secondary sites while the central administration site is new site type. The central administration site replaces the primary site referred to as a central site as the top-level site of a multi-primary site hierarchy. This site does not directly manage clients but does coordinate a shared database across your hierarchy, and it is designed to provide centralized reporting and configurations for your entire hierarchy.

Yes. If the EVALUATION version is not a PRERELEASE version of SYSTEM Center 2012 Configuration MANAGER, you can upgrade it to the full version.

Yes. If the evaluation version is not a prerelease version of System Center 2012 Configuration Manager, you can upgrade it to the full version.

No. SMS 2003 sites and SMS 2003 clients are not supported by SYSTEM Center 2012 Configuration MANAGER. You have two choices to move these sites and clients to System Center 2012 Configuration Manager:

• Upgrade SMS 2003 sites and clients to Configuration Manager 2007 SP2, and then MIGRATE them to System Center 2012 Configuration Manager.
• Uninstall SMS 2003 sites and clients and then install System Center 2012 Configuration Manager Sites and clients.

No. SMS 2003 sites and SMS 2003 clients are not supported by System Center 2012 Configuration Manager. You have two choices to move these sites and clients to System Center 2012 Configuration Manager:

No. Unless you were in a prerelease program that was supported by Microsoft (such as the Technology Adoption Program or the Community Evaluation Program) there is no supported upgrade path for prerelease VERSIONS of System Center 2012 Configuration Manager. For more information, see the RELEASE NOTES for System Center 2012 Configuration Manager.

No. Unless you were in a prerelease program that was supported by Microsoft (such as the Technology Adoption Program or the Community Evaluation Program) there is no supported upgrade path for prerelease versions of System Center 2012 Configuration Manager. For more information, see the Release Notes for System Center 2012 Configuration Manager.

No. The ACTIVE Directory SCHEMA EXTENSIONS for System Center 2012 Configuration MANAGER are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to EXTEND the schema again for System Center 2012 Configuration Manager or System Center 2012 Configuration Manager SP1.

No. The Active Directory schema extensions for System Center 2012 Configuration Manager are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for System Center 2012 Configuration Manager or System Center 2012 Configuration Manager SP1.

By default, the Configuration Manager console limits searches to the current folder. You can change this behavior by FIRST clicking in the Search box in the results pane. Then, in the Search tab, in the SCOPE GROUP. Click All Subfolders. In the results pane, the search is extended to AND Path <Current Node + Subfolders&GT;. Add criteria if required, and TYPE your search text to search the current folder and its subfolders.

By default, the Configuration Manager console limits searches to the current folder. You can change this behavior by first clicking in the Search box in the results pane. Then, in the Search tab, in the Scope group. Click All Subfolders. In the results pane, the search is extended to AND Path <Current Node + Subfolders>. Add criteria if required, and type your search text to search the current folder and its subfolders.

By DEFAULT, the Configuration Manager console LIMITS SEARCH results to 1,000 ITEMS. You can CHANGE this value by using the Search tab. In the Options group. Click Search Settings and then change the Search Results value in the Search Settings dialog box.

By default, the Configuration Manager console limits search results to 1,000 items. You can change this value by using the Search tab. In the Options group. Click Search Settings and then change the Search Results value in the Search Settings dialog box.

The Configuration Manager console USES HTTP to the Internet in two scenarios:

• When you use the geographical view from the Site Hierarchy node in the Monitoring workspace, which uses Internet Explorer to access Bing Maps.
• When you use the Configuration Manager Help file and click a link to view or search for information on TechNet.

If you do not require these functions, your firewall can block HTTP CONNECTIONS from the console WITHOUT ADDITIONAL loss of functionality to Configuration Manager.

The Configuration Manager console uses HTTP to the Internet in two scenarios:

If you do not require these functions, your firewall can block HTTP connections from the console without additional loss of functionality to Configuration Manager.

For System CENTER 2012 CONFIGURATION Manager SP1 and later:

CREATE a collection with a query-based rule. Query the attribute class System Resource and the attribute Connected STANDBY Capable = TRUE to return COMPUTERS that are Always On Always Connected capable.

For System Center 2012 Configuration Manager SP1 and later:

Create a collection with a query-based rule. Query the attribute class System Resource and the attribute Connected Standby Capable = TRUE to return computers that are Always On Always Connected capable.

For System CENTER 2012 Configuration Manager SP1 and later:

Because an ID for each device type (for example Windows computers, MAC computers, or Linux computers) is stored in the Configuration Manager database, you can create a collection that CONTAINS a query rule to RETURN only devices with a specified ID. For an example query to use, see the Example WQL Queries section in the How to Create Queries in Configuration Manager TOPIC.

For System Center 2012 Configuration Manager SP1 and later:

Because an ID for each device type (for example Windows computers, Mac computers, or Linux computers) is stored in the Configuration Manager database, you can create a collection that contains a query rule to return only devices with a specified ID. For an example query to use, see the Example WQL Queries section in the How to Create Queries in Configuration Manager topic.

If you choose Install Client from the RIBBON when the Collection ribbon TAB is selected, the client installs to all computers in the collection rather than to just the selected computer. To install the client to just the selected computer, CLICK the Home tab on the ribbon before you click Install Client from the ribbon, or USE the right-click option.

If you choose Install Client from the ribbon when the Collection ribbon tab is selected, the client installs to all computers in the collection rather than to just the selected computer. To install the client to just the selected computer, click the Home tab on the ribbon before you click Install Client from the ribbon, or use the right-click option.

The All UNKNOWN Computers COLLECTION contains two objects that represent records in the Configuration Manager database so that you can deploy operating systems to computers that are not MANAGED by Configuration Manager, and so are unknown to Configuration Manager.

These computers can include the following:

• A computer where the Configuration Manager client is not installed.
• A computer that is not imported into Configuration Manager.
• A computer that is not DISCOVERED by Configuration Manager.

The All Unknown Computers collection contains two objects that represent records in the Configuration Manager database so that you can deploy operating systems to computers that are not managed by Configuration Manager, and so are unknown to Configuration Manager.

These computers can include the following:

No. Collections CONFIGURED by using query rules that USE certain classes do not SUPPORT incremental updates. For a LIST of these classes, see How to Create Collections in CONFIGURATION Manager.

No. Collections configured by using query rules that use certain classes do not support incremental updates. For a list of these classes, see How to Create Collections in Configuration Manager.

Yes. SYSTEM CENTER 2012 CONFIGURATION Manager includes two new collection rules, the Include Collections rule and the Exclude Collections rule that allow you to include or exclude the membership of specified collections.

Yes. System Center 2012 Configuration Manager includes two new collection rules, the Include Collections rule and the Exclude Collections rule that allow you to include or exclude the membership of specified collections.

In System Center 2012 Configuration Manager, all collections MUST be limited to the membership of ANOTHER collection. When you CREATE a collection, you must SPECIFY a limiting collection. A collection is always a SUBSET of its limiting collection.

In System Center 2012 Configuration Manager, all collections must be limited to the membership of another collection. When you create a collection, you must specify a limiting collection. A collection is always a subset of its limiting collection.

Yes. The Configuration MANAGER console is a 32-bit PROGRAM that can RUN on a 32-bit version of WINDOWS and on a 64-bit version of Windows.

Yes. The Configuration Manager console is a 32-bit program that can run on a 32-bit version of Windows and on a 64-bit version of Windows.