The Configuration Manager 2007 Documentation Library and the Documentation Library for System Center 2012 Configuration Manager have been updated on the web and the latest content has Updated: January 1, 2012 at the top of the topic.
New this month, we’re publishing prerelease documentation for the Microsoft System Center 2012 Configuration Manager Physical to Virtual Migration Toolkit – also known as the P2V Toolkit. Download the release candidate for this toolkit from the Microsoft Connect site to migrate Configuration Manager 2007 to System Center 2012 Configuration Manager in a branch office scenario where migration over a wide area network (WAN) connection is not feasible and where hardware resources for a side-by-side migration are limited. This toolkit virtualizes the site server instance so Configuration Manager 2007 and System Center 2012 Configuration Manager can run on the same physical server in an environment where you can perform a side-by-side migration.
Documentation updates for this month includes customer feedback for Configuration Manager 2007 and updates the support information for SQL Server that was previously announced on this blog in September. We have some updates and clarifications for System Center 2012 Configuration Manager, and we’ve also added notification to the Forefront Endpoint Protection 2012 beta documentation that this is now updated and replaced with System Center 2012 Endpoint Protection. You cannot use the beta version of FEP 2012 with the release candidate versions of System Center 2012 Configuration Manager, so expect this beta documentation to be retired in the near future.
In addition, for FEP 2010 customers, we’ve updated Prerequisites for Deploying Forefront Endpoint Protection on a Client to include information about how Windows Embedded Device Manager 2011 installs the Forefront Endpoint Protection client and definition updates to write filter-enabled devices.
We value customer feedback and try to incorporate it when possible. Although we can’t promise to make the docs perfect for everybody, we are committed to continual improvement. So, keep that feedback coming, and feel free to contact us about anything related to the documentation by using our usual address of SMSDocs@Microsoft.com .
What's New in the Configuration Manager 2007 Documentation Library for January 2012
The following information lists the topics that contain significant changes since the July 2011 update.
- Updated for the following SQL Server versions: SQL Server 2008 SP3, and SQL Server 2008 R2 SP1. Windows Embedded support now includes Thin PC, Windows Embedded POSReady7, and Windows Embedded Standard 7 SP1.
- Updated to clarify how Network Discovery finds the subnet mask.
- As a result of community content, clarified that the reference to the Performance utility is the same as Performance Monitor. On some versions of Windows, and depending on how you access it, you will see just “Performance” and then “Performance Monitor” in the window title when you actually run it.
- As a result of community content, reworded for publishing rather than assigning the Configuration Manager client to users by using Group Policy.
- As a result of community content, added TCP port 53 in addition to UDP 53, for DNS.
- Removed the reference to enabling Real Time Streaming Protocol (RTSP) and RTSP over TLS (RTSPS) for application virtualization streaming–enabled distribution points. This protocol is not supported by Configuration Manager 2007.
What's New in the Documentation Library for System Center 2012 Configuration Manager, January 2012
The following information lists the topics that contain significant changes since the December 2011 update.
- Updated the table in the Site and Site System Role Scalability section to include more site system roles, and to update the number of clients that site system roles at a secondary site can support.
- New topic that lists the groups and accounts that are used by Configuration Manager. Note that as a result of a publishing problem with angle brackets that denote a variable, the group names that end in _<sitecode> are currently listed in this topic as _[sitecode]. We hope to correct this soon.
- Updated to clarify that NLB management points are no longer supported and this configuration is removed from the management point component properties.
- Updated with the new behavior of Internet-based clients that first try to download software updates from Microsoft Update when Configuration Manager detects these clients to be on the Internet. Only if this fails, do they then try to download them from Internet-based distribution points. The cross-forest table information is also updated to clarify the supported scenarios.
- As a result of customer feedback, updated the procedure for the web server certificate to clarify that when you specify a subject alternative name (SAN), the subject value remains empty. When a SAN is specified in a PKI certificate, Configuration Manager does not use the certificate subject, which is why it can remain empty.
- Updated with a new section “Considerations for Managing the Configuration Manager Client in a Virtual Desktop Infrastructure”, for customers who are using VDI.
- Added the information about the hotfix KB2552033 , which must be installed on site servers that run Windows Server 2008 R2 when client push installation is enabled. Also added the required security permissions to configure enrollment for mobile devices, and to manage enrolled mobile devices.
- Updated to clarify that the client setting Agent extensions manage the deployment of applications and software updates applies to only software updates and required applications. This setting has no effect for available applications and users can still request them in the Application Catalog. This setting also does not apply to packages and programs, or task sequences.
- Updated with the information that remote wipe from the Application Catalog uses user device affinity, which is automatically configured for mobile devices that connect to an on-premise Exchange Server computer. For mobile devices that connect to Exchange Online, you must manually configure the user device affinity.
- Updated with the clarification that when an application with multiple deployment types is deployed, each deployment type is evaluated in order. The deployment type with the highest priority that meets the specified requirements is installed.
- Updated with the recommendation to configure the client setting of User device affinity threshold (days) to a value of at least 7 days. This minimum value helps to avoid situations where an automatically configured user device affinity might be lost while the user is not logged on, for example, during the weekend.
- This section has been updated for the following topics:
- Added new section, “Extending Out of Band Management in Configuration Manager” for information about Intel support and their applications that extend out of band management for vPro computers.
- Updated to clarify that the Endpoint Protection point site system role must be installed on a central administration site, or where there is no central administration site, on the primary site that is at the top of the hierarchy.
- Updated to clarify the schedule for definition updates.
- Minor updates and a new section for Setup Updates.
- Updated with the notification that this end-user privacy information is now available in additional languages from the Microsoft Download Center .
- Updated with new entries that include the following:
This posting is provided "AS IS" with no warranties and confers no rights.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.