[Today's post is provided by Yvette O'Meally]
We are announcing support changes for the following releases. Please look for these changes to be reflected in the Supported Configuration pages within a few months.
Microsoft SQL Server 2008 R2 is now supported on Configuration Manager 2007 SP1 and SP2 and Configuration Manager 2007 R2
System Center Configuration Manager 2007 SP1 and SP2 now support Microsoft SQL Server 2008 R2 as a Configuration Manager 2007 site database. System Center Configuration Manager 2007 R2 now supports Microsoft SQL Server 2008 R2 Reporting Services.
No software updates are required.
Microsoft Application Virtualization 4.5 Service Pack 2 is now supported on Configuration Manager 2007 R2 with Configuration Manager 2007 SP2
System Center Configuration Manager 2007 R2 with System Center Configuration Manager 2007 SP2 now supports Microsoft Application Virtualization 4.5 Service Pack 2.
Hyper-V Server 2008 R2 is now supported with Configuration Manager 2007 Service Pack 2.
System Center Configuration Manager 2007 SP2 now supports client installation and all site server roles in the Hyper-V Server 2008 R2 virtualization environment.
Microsoft Windows Embedded Standard 7 is now supported on Configuration Manager 2007 SP2
System Center Configuration Manager 2007 SP2 now supports Windows Embedded Standard 7 as a client platform. General limitations for managing Windows Embedded devices can be found in this article, http://technet.microsoft.com/en-us/library/bb932123.aspx,
.NET Framework 4.0 is now supported with Configuration Manager 2007 SP1 and SP2.
System Center Configuration Manager 2007 SP1 and SP2 now support the .NET Framework 4.0 with the following limitations.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR
Application Compatibility Toolkit 5.6 is now supported with the Application Compatibility Toolkit Connector.
The Application Compatibility Toolkit (ACT) Connector now supports ACT 5.6. Limitations and workarounds for upgrade issues from ACT 5.5 are documented in the following blog post: http://blogs.technet.com/b/configmgrteam/archive/2010/06/20/act-connector-and-act-5-6.aspx
--Yvette O'Meally
This posting is provided "AS IS" with no warranties, and confers no rights.
[Today's post is from the Configuration Manager Writing Team]
The Configuration Manager documentation library (http://technet.microsoft.com/en-us/library/bb680651.aspx) has been updated on the Web and the latest content on the Web has Updated: June 1, 2010 at the top of the topic.
We have just a couple of changes this month to incorporate customer feedback. 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 Documentation Library for June 2010
The following information lists the topics that contain significant changes since the May 2010 update.
Determine Whether a Proxy Management Point is Needed at a Secondary Site
- Updated to clarify that proxy management points do retrieve client policy from the site database or a site replica. However, this still results in reduced network traffic because policy bodies are cached. Clients must access the default management point in the primary site for site assignment.
Step-by-Step Example Deployment of the PKI Certificates Required for Configuration Manager Native Mode: Windows Server 2008 Certification Authority
Step-by-Step Example Deployment of the PKI Certificates Required for AMT and Out of Band Management: Windows Server 2008 Certification Authority
- Both of these step-by-steps have been updated to incorporate the new Select Certificate Enrollment Policy page in the wizard if your requesting member server is running Windows Server 2008 R2.
-- The Configuration Manager Writing Team
This posting is provided "AS IS" with no warranties and confers no rights.
[Today's post is provided by Martin Li]
The Application Compatibility Toolkit Connector (ACT Connector) assists administrators with collecting the necessary computer and application compatibility information to help plan for a Windows deployment. A prerequisite for the ACT Connector is Microsoft Application Compatibility Toolkit 5.5 (ACT 5.5), which was replaced by a newer version, ACT 5.6, on June 7th.
Will ACT Connector work with ACT 5.6? The short answer is "Yes." One limitation is that ACT Connector cannot take advantage of the 64-bit compatibility support newly added in ACT 5.6. Application compatibility data reported by the ACT Connector are always for 32-bit operating systems.
If you upgrade from ACT 5.5 to ACT 5.6 and update the ACT database following the configuration wizard, ACT Connector features will continue to work as before. After you upgrade to ACT 5.6 and run the ACT configuration wizard, select your existing ACT database in the "Configure Your ACT Database Settings" page. You will notice an "Update" button beside the Database name, as shown in the screenshot below. Click the "Update" button and follow the instructions in "Database Upgrade Options" dialog to update the ACT database.
Alternately, you may make a new installation of ACT 5.6 rather than upgrading from ACT 5.5. In this case, do not use "Configure ACT Server" under Application Compatibility Toolkit Connector/Application Compatibility Toolkit Server node to configure ACT 5.6 database. Instead, use the VB script (ActConfig.vbs) documented in the following blog post to configure ACT database: http://blogs.technet.com/b/configurationmgr/archive/2009/07/01/support-for-act-5-5-with-the-act-connector.aspx. Please note that if the ACT database is hosted in a SQL named instance, be sure to include the instance name in the ACT Server parameter you pass to ActConfig.vbs. For example, ActConfig.vbs <Site server> <Site code> <ACT Server>\<SQL named instance> <ACT database> <Machine Account>.
Configuring the ACT 5.6 database using "Configure Your ACT Server" provided by ACT Connector will result in an error message reporting a series of invalid column errors. This is because ACT Connector has a dependency on ACT database tables whose schema changed in ACT 5.6. To avoid this issue, uninstall and then reinstall ACT 5.6 and create a new ACT database. You can then configure the ACT database using the ActConfig.vbs VB script described above.
In summary, if you upgrade an ACT 5.5 environment to ACT 5.6, the ACT Connector will continue to work provided you properly update the ACT database using the ACT Configuration wizard. If you create a fresh installation of ACT 5.6, do not configure ACT database using ACT Connector wizard but instead use the ActConfig.vbs script.
--Martin Li