Announcement: Configuration Manager Documentation Library Update for March 2013

Announcement: Configuration Manager Documentation Library Update for March 2013

  • Comments 5
  • Likes

The Documentation Library for System Center 2012 Configuration Manager has been updated on the web and the latest content has Updated: March 1, 2013 at the top of the topic.

We also released a Windows PowerShell for Configuration Manager help update. This update includes additions and corrections to the Configuration Manager Service Pack 1 release. To download the updated help to your local computer, run the Configuration Manager console with local administrative permissions, and connect to Windows PowerShell. At the prompt, type the following: “Update-Help -Module ConfigurationManager”. And if you haven’t already, you might want to check out the following posts for using Windows PowerShell with Configuration Manager: Powershell Basics and PowerShell – Connecting to Configuration Manager.

If you are attending MMS in Las Vegas next month, come and see us at the Windows Server & System Center Documentation stations (#2 and #28) in the Microsoft Pavilion. We’ll be there during Expo Hall hours, where you’ll find writers for System Center, Windows Intune, Windows Server, MDOP, and Windows PowerShell. You can try our latest quiz to find out how well you really know what’s new in Configuration Manager SP1, and complete a short survey to enter our daily raffle. And we’re always happy to chat and find out how we can improve your information experience for the products you use.

If you’re not going to MMS and have questions or feedback about our documentation, you can contact us by using our usual email address of SMSDocs@Microsoft.com.

 

What's New in the Documentation Library for System Center 2012 Configuration Manager, March 2013 


The following information lists the topics that contain significant changes since the February 2013 update.


Supported Configurations for Configuration Manager

- Updated for the following information:

  • Configuration Manager with SP1 supports an Active Directory domain that runs at a domain functional level of Windows Server 2012. Configuration Manager with no service pack does not support the Windows Server 2012 domain functional level.
  • The table listing the supported versions of SQL Server for hosting the site database is modified to clarify that the listed SQL Server cumulative update version is a minimum required version. For each SQL Server service pack release, you can use the minimum cumulative update version that is listed, or a later cumulative update version.
  • Clarified that the prerequisites for distribution points do not require BITS. Additionally, if BITS is configured on the distribution point, it is not used when clients download content from the distribution point by using BITS.


What’s New in Configuration Manager SP1

- Updated the Monitoring and Reporting section so that the Reporting section is consistent with Introduction to Reporting in Configuration Manager.


Fundamentals of Configuration Manager

- Updated to include the missing enrollment site system roles in the table for the additional site system roles for specific functionality.


PKI Certificate Requirements for Configuration Manager

- Updated for Active Directory Certificate Services on Windows Server 2012:

Planning for Boundaries and Boundary Groups in Configuration Manager

- Updated to add best practice guidance about using IP address ranges as boundaries only when other boundary types are not sufficient for your environment.

 
Planning for Communications in Configuration Manager

- Updated the Planning How to Wake Up Clients section to correct the discrepancy about the TCP/IP ping interval, which is every 5 seconds.

 
Planning for Site Operations in Configuration Manager

- Updated the Planning for Maintenance Tasks for Configuration Manager section for the following maintenance tasks that were introduced with Configuration Manager SP1: Delete Aged Client Presence History, Delete Aged Notification Task History, Delete Aged Replication Summary Data, and Delete Aged Unknown Computers.

 
Install Sites and Create a Hierarchy for Configuration Manager

- Corrected the missing “/” in the Prerequisite Checker command line reference for /SourceDir.

 
Install and Configure Site System Roles for Configuration Manager

- Updated with the information that the Site System Installation Account is used to install site system roles.

 
Manage Sites and Hierarchy Configurations

- Updated to remove the guidance for the required configuration of the SQL Server cluster. This information is moved to, and is kept up-to-date, in Supported Configurations for Configuration Manager.

 
How to Install Clients on Mac Computers in Configuration Manager

- Updated for a new section that explains how to upgrade the client on Mac computers. Also, clarified that maintenance windows are not supported for these clients.

 
How to Prevent the Client Software from Installing on Specific Computers in Configuration Manager

- Updated to correct the order of the registry keys.

 
About Client Installation Properties Published to Active Directory Domain Services in Configuration Manager

- As a result of customer feedback, added links to the procedures to extend the schema and publish sites.

 
Configuring Content Management in Configuration Manager

- Updated for the following:

  • Clarified that the Rate Limits tab and Schedule tab of the distribution point properties are available only when you configure a distribution point that is on a computer other than the site server (a “remote distribution point”).
  • Clarified that pull-distribution points use BITS to transfer content from a source distribution point.
  • Clarified that clients can run a task sequence from a cloud-based distribution point only when that task sequence is configured with the deployment option Download all content locally before starting task sequence.

 
How to Create Collections in Configuration Manager

- Updated with some examples of how you might use include and exclude collection rules. In addition, the procedures now include a callout note that you will not immediately see members in the newly created collection but can update the membership and refresh the Configuration Manager console.

 
How to Create and Deploy Antimalware Policies for Endpoint Protection in Configuration Manager

- Updated for new and changed antimalware policy settings in Configuration Manager SP1.

 
Prerequisites for Remote Control in Configuration Manager

- As a result of customer feedback, clarified that remote control does not have external dependencies on any Windows services, such as WinRM.

 

-- The Configuration Manager Writing Team

This posting is provided "AS IS" with no warranties and confers no rights.

 

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • That's great all the documnetation is here and updated, that will helpfull

  • That's great all the documnetation is here and updated, that will helpful, I would love more about on OSD and SUP

  • Thanks for the update guys, is there a fix for the installation error when deploying into a Windows Server 2012 domain functional level? Currently the install routine generates a warning stating the functional level must be at least Windows Server 2003.

  • At technet.microsoft.com/.../gg682077.aspx the documentation says about a distribution point:

    When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS

    Can you translate that into plain English?  That seems contradictory.  So if you install BITS on the DP, the clients connecting to it won't use BITS, but if you don't install BITS at the DP, clients will connect to it and use BITS???

  • @ Squeezer999

    Sorry for the confusion with the wording.  The deal is that you don't need to install BITS on the server - even if you want to use BITS to download files to clients.  That's because this transfer uses BITS from the client (not from the server).  And if you do install BITS on the server, this component isn't used, even when there is a BITS download from the server to the client.    

    I know it sounds contradictory, but there's server-side BITS and client-side BITS.  And in this scenario, it always uses client-side BITS.  I don't think these are official terms but it helps to explain the difference.