Ça y est la documentation Configuration Manager 2012 du mois de Mai est en ligne avec notamment le support des installations core de Windows Server 2012 !
Découvrons ensemble les nouveautés !
What’s New in the Documentation Library for System Center 2012 Configuration Manager, May 2013
The following information lists the topics that contain significant changes since the April 2013 update.
Supported Configurations for Configuration Manager
- Updated for the following updates and clarifications:
- – Updated the supported list of client operating systems to include the Core installation of Windows Server 2012.
- – Updated the supported list of supported Windows Embedded operating systems to include the Standard and the Industry editions of Windows Embedded 8.
- – Added a clarification that the site database and the database for the reporting services point must be on a 64-bit installation of SQL Server.
Planning for Hardware Configurations in Configuration Manager
- – Updated to add a note to the table in the Disk Space Configurations section to make clear that the minimum disk space listed does not include the space required for source content that is located on the site server. You can find more information about this in the Plan for Content Libraries section of the Planning for Content Management topic.
Install Sites and Create a Hierarchy for Configuration Manager
- – Updated to clarify that when you upgrade an evaluation edition of Configuration Manager to a full edition, you must run the copy of Setup that is located on the site server in the Configuration Manager installation folder.
Install and Configure Site System Roles for Configuration Manager
- – Updated to correct details about the service FQDN for a cloud-based distribution point. The FQDN must be unique and not match the name of a computer that is joined to a domain. This clarification is also added to the section that discusses the service certificate that you use for a cloud-based distribution point, in the Planning for Content Management in Configuration Manager topic.
Prerequisites for Reporting in Configuration Manager
- – Updated to clarify that the database for the reporting services point must be on a 64-bit installation of SQL Server.
Technical Reference for Ports Used in Configuration Manager
- – Updated the details for SQL Server to SQL Server connections to clarify that Configuration Manager does not require the SQL Server Browser (UDP 1434). Also updated the details in the Connections to Microsoft SQL Server section to clarify that for intersite communications, the SQL Server Service is in use, and that it defaults to port TCP 1433.
Technical Reference for Log Files in Configuration Manager
- – Updated the details for the log files for cloud-based distribution points and removed an inaccurate reference to the Srvacct.log, which is not used by System Center 2012 Configuration Manager, but was used in previous versions of Configuration Manager
How to Manage Mobile Devices by Using the Exchange Server Connector in Configuration Manager
- – Updated to include how to verify that the connector is installed and configured correctly.
Planning for Content Management in Configuration Manager
- – Clarifications that cloud-based distribution points do not support software update packages and you must make sure that the service certificate does not define an FQDN for the cloud-based distribution point that matches an FQDN of a computer that is joined to a domain.
- – Clarification in the Plan for Content Libraries section to clarify that Configuration Manager creates and maintains a content library on each site server in addition to the content library that is created on each distribution point
- – Added a new section, Plan for Binary Differential Replication.
Planning for App-V Integration with Configuration Manager
- – Updated to clarify that App-V 5.0 SP1 is now supported by Configuration Manager.
How to Create Applications in Configuration Manager
How to Create Queries in Configuration Manager
- – Updated to correct the number to use when building a query to identify a Linux or UNIX client: the number to use is 13, and not 11 as previously published.
Tout le contenu ICI
Please follow and like us: