Configuration Manager 2007 SP1 Release Notes
Applies To: System Center Configuration Manager 2007 SP1
To search these release notes, press CTRL+F.
|Read these release notes thoroughly before you install Microsoft System Center Configuration Manager 2007 SP1.|
These release notes contain information needed to successfully install Microsoft System Center Configuration Manager 2007 SP1 and contain information that is not available in the product documentation.
|If there is a discrepancy between these release notes and other Configuration Manager 2007 documentation, the latest change should be considered authoritative. These release notes supersede the content in the Configuration Manager Documentation Library dated May 2008.|
Issues from previous versions have either been resolved or are documented in the Configuration Manager Documentation Library. Disregard release notes from previous versions.
In This Document:
Before You Install Configuration Manager 2007 SP1
Before you install Configuration Manager 2007 SP1, verify that your environment is consistent with the supported configurations and that you have a supported upgrade path. For more information, see Configuration Manager 2007 SP1 Supported Configurations in the Configuration Manager Documentation Library.
If you are installing Service Pack 1 on an existing Configuration Manager 2007 site installation, use the process outlined in the Configuration Manager 2007 SP1 Upgrade Checklist in the Configuration Manager Documentation Library to upgrade your site.
About the Product Documentation for Configuration Manager 2007 SP1
Comprehensive information about Configuration Manager 2007 is available in the Configuration Manager Documentation Library. The Library includes introductory topics, such as overviews of features and concepts, as well as in-depth technical discussions and technical reference information. The Library contains information about all versions of Configuration Manager 2007, including Service Pack 1 and R2. Information about Service Pack 1 and R2 is labeled as specific to the respective versions. Pre-release content is preliminary and subject to change.
There are several ways to access the Library:
If you have not installed Configuration Manager 2007, you can locate the file SMSv4.chm under the product DVD in SMSSETUP\HELP. You can also copy the SMSv4.chm file to your local hard drive and open it without installing the Configuration Manager 2007 console.
If you have installed Configuration Manager 2007, you can access the Library in the Configuration Manager 2007 console by pressing F1, by clicking Help buttons, clicking Help on the Action menus, or by clicking some hyperlinks. After Configuration Manager 2007 is installed, the file SMSv4.chm is installed in %windir%\Help.
The entire Configuration Manager Documentation Library is available on Microsoft TechNet in the System Center Configuration Manager TechCenter at (http://go.microsoft.com/fwlink/?LinkId=74317).
Important To see a list of significant changes made to the content, see the topic "What's New in the Configuration Manager Documentation Library."
Protect Against Security Vulnerabilities and Viruses
To help protect against security vulnerabilities and viruses, it is important to install the latest available security updates for any new software being installed. For more information, see the Microsoft Security Web site at http://go.microsoft.com/fwlink/?LinkId=3482.
If you would like to provide feedback, make a suggestion, or report an issue with Configuration Manager 2007 SP1, you can right-click any node in the Configuration Manager 2007 console and click Give Feedback or you can go directly to the Connect site at http://go.microsoft.com/fwlink/?LinkId=67307.
Help the Configuration Manager documentation team ship the kind of product information you need most by giving us your feedback and comments. Send your documentation feedback to email@example.com.
The "Configuration Manager 2007 SP1 Supported Configurations" topic contains information about hardware and software requirements and unsupported configurations and is available in the Configuration Manager Documentation Library.
The following section provides information not included in the Supported Configurations topic.
Changes to the Supported Configurations Topic
Note the following changes to the Supported Configurations topic:
Configuration Manager 2007 SP1 now requires Windows Server Update Services (WSUS) 3.0 SP1 for software update management.
Known Issues with System Center Configuration Manager 2007 SP1
The following sections provide the most up-to-date information about issues with Configuration Manager 2007 SP1. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
A management point site system installed on a Windows Server 2008 computer in native mode might become unresponsive
If you have configured Configuration Manager 2007 to run in native mode and have installed a management point on a computer running Windows Server 2008, the management point might experience a paged pool kernel memory leak.
WORKAROUND If the management point becomes unresponsive, reboot the server. For more information, see the Microsoft Knowledge Base article at http://go.microsoft.com/fwlink/?LinkId=119790.
Cannot display the Configuration Manager 2007 Documentation link on the Start page
If you run splash.hta from a UNC path on a computer running Windows Server 2003 SP1, the content for Configuration Manager 2007 Documentation might not be displayed. This is because Windows Server 2003 SP1 includes changes to the InfoTech protocol. For more information, see http://go.microsoft.com/fwlink/?LinkId=93693.
WORKAROUND Copy the file \smssetup\help\smswrapper.chm to your local hard drive, and run the file locally.
Upgrading large site databases to Configuration Manager 2007 SP1 is extremely slow and disk space usage intensive
This issue is caused by an SP1 schema change implementation in very large tables in the database. Processing times will vary by database, depending on the amount of inventory data stored in the SQL Server database to be upgraded and the hardware used to host the SQL Server instance, but can be up to five times longer than upgrading SMS 2003 sites to Configuration Manager 2007. While testing the database for upgrade by using the testdbupgrade command or during an actual site database upgrade process, setup logging might seem slow or unresponsive. The Setup.exe process can be monitored to ensure that the upgrade is still in progress. When upgrading to Configuration Manager 2007 SP1, ensure that at least two and a half times the size of the site database is available as free disk space on the drive used to host the site database to allow the database upgrade to succeed.
WORKAROUND For more information, see http://go.microsoft.com/fwlink/?LinkId=119563.
Application Compatibility Toolkit 5.0 Connector cannot be installed from the Configuration Manager 2007 SP1 Setup splash screen.
Application Compatibility Toolkit 5.0 Connector installation files are no longer available in the Configuration Manager 2007 installation source files.
WORKAROUND Download Application Compatibility Toolkit 5.0 Connector source files from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=119623.
Extend Active Directory schema for Configuration Manager 2007 if Internet-based clients will be managed on both the Internet and the intranet.
If Internet-based clients will be managed on both the Internet and the intranet, extend the Active Directory Domain Services (AD DS) schema for Configuration Manager 2007. Managing Internet-based clients in this scenario without schema extensions is not supported.
Evaluation warning messages will not be displayed on Windows Server 2008
If Configuration Manager 2007 with SP1 Evaluation Edition is installed on Windows Server 2008, warning messages notifying the user of the time remaining of the evaluation period will not be displayed.
WORKAROUND This information is displayed in the Windows Application Event log and the Configuration Manager site server log files.
Distribution point reinstallation on 64-bit installations of Windows Server 2008 might fail after changing client communication ports.
This issue is caused by an IIS re-configuration issue in the ABO compatibility layer in-memory buffer configuration on 64-bit Windows Server 2008 installations.
WORKAROUND Distribution point component installation will be retried automatically until installation is successful.
After running the Security Configuration Wizard on the site server, clients are unable to download content from the software update point
After the Security Configuration Wizard is run on the site server, the firewall might block communication to Windows Server Update Services (WSUS), preventing Configuration Manager client computers from downloading content from the software update point.
WORKAROUND Check the advanced settings for the Windows Firewall to allow communication to WSUS. Alternatively, you can rerun the Security Configuration Wizard. From the Select Server Roles page of the wizard, change the View setting to All roles and then select Windows Server Update Services (WSUS). From the Network Security Rules page of the wizard, change the View setting to All Rules and then select Windows Server Update Services (HTTP) and Windows Server Update Services (HTTPS).
Update classification and product information is reset after upgrade
After upgrading from Configuration Manager 2007 to Configuration Manager 2007 SP1, the software update classifications and products are reset to the default settings. Custom settings are not retained after the upgrade, and as a result, the software updates metadata from only the default classifications and products will be synchronized.
WORKAROUND After the Configuration Manager upgrade, you must go to the Software Update Point Component Properties dialog box and manually select the desired software update classifications and products. For more information, see Software Update Point Component Properties help.
Network Access Protection
Report “List of NAP-capable and NAP-upgradable computers” does not include computers running Windows XP Service Pack 3
With the release of Windows XP Service Pack 3, computers running this service pack on the Windows XP operating system can support Network Access Protection (NAP). However, they are not included in the count of NAP-capable computers in the report List of NAP-capable and NAP-upgradable computers.
WORKAROUND To identify computers that are running Windows XP Service Pack 3 and are therefore NAP-capable, run the following query:
Select disc.Netbios_Name0, assi.SMS_Assigned_Sites0, disc.Client_Version0 from v_R_System disc left join v_RA_System_SMSAssignedSites assi on disc.ResourceID=assi.ResourceID left join v_GS_OPERATING_SYSTEM inv on disc.ResourceID=inv.ResourceID where inv.BuildNumber0 = '2600' and inv.CSDVersion0 like '%Service Pack 3%'
Out of Band Management
Security Best Practice: Manually publish AMT-based computers to Active Directory Domain Services
The documentation procedures for preparing Active Directory Domain Services for AMT Provisioning (“How to Prepare Active Directory Domain Services for Out of Band Management”) will result in the out of band service point publishing a computer object to Active Directory Domain Services during the AMT provisioning process. During this process, it is possible for an attacker to read the computer information on the network and subsequently impersonate that computer, which would then give the attacker read access to Active Directory objects.
WORKAROUND To prevent the out of band service point publishing AMT-based computers to Active Directory Domain Services, do not perform the steps to configure security on the Active Directory container or organizational unit (OU). Instead, manually create a computer account for any AMT-based computer that is not already joined to the domain, by using Active Directory Users and Computers. Create the computer account in the Active Directory container or OU that you have created for out of band management, or move it to this location after it is created. You can create the computer account either before or after the AMT provisioning process. If you know the AMT-based computers to be provisioned, create the computer account before provisioning. If you do not know the AMT-based computers to be provisioned, create the computer accounts after the out of band service point has provisioned the AMT-based computers.
If you create the computer accounts after the out of band service point has provisioned AMT-based computers, identify the computers that require a computer account creating by running the report Status of client out of band management provisioning or by using the AMT Status column in the Configuration Manager console. Computers that require a computer account to be created in Active Directory Domain Services will have an AMT status of Detected. For more information, see the help topic “About the AMT Status and Out of Band Management”.
After the computer account has been created in Active Directory Domain Services and the out of band management point has provisioned it for AMT, follow these steps:
- From the Collections node in the Configuration Manager console, locate the AMT-based computer.
- Right-click the computer, and then click Out of Band Management.
- Click Update Provisioning Data in Management Controller Memory, and then click OK.
Windows Server 2008 Logo Certification Information
For more information about Windows Server 2008 logo certification for Configuration Manager 2007, see http://go.microsoft.com/fwlink/?LinkId=118361.
Release Notes Copyright Information
Information in this document, including URL and other Internet Web site references, is subject to change without notice, and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, and ActiveSync are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.