Of particular note for R2 customers using SQL Reporting Services: This documentation has been has been updated with information about creating Reporting Services Report models and now includes a procedure for creating advanced models using multiple views in the Configuration Manager database. Additionally, the procedure for deploying report models for use in the Configuration Manager console has been revised so that the instructions are more suitable for a variety of environments.
Most of the documentation changes in this update are a result of customers contacting us with questions, requests for clarifications, and notifying us of omissions and typos - so thank you for helping to improve the documentation for others. We do value your feedback and try to incorporate it when possible. Keep that feedback coming, and contact the documentation team on our usual address of
What's New in the Configuration Manager Documentation Library for February 2009
The following information lists the topics that are new or contain significant changes since the December 2008 update.
- Replaces the topic "Step-by-Step Guide to Creating a Report Model in SQL Reporting Services" to provide updated procedures for creating a SQL Reporting Services report model using a single view from the Configuration Manager database.
- Updated with the information that providers retrieve configuration information by using objects and settings defined within the configuration item. The objects that can be defined are assembly, file or folder, and the registry. The settings that can be defined are XML queries, WQL queries, SQL queries, scripts, registry, Active Directory Domain Services, and the IIS metabase.
- Updated with clarifications that the Intel HECI driver is required for in-band provisioning only; DHCP is also required for in-band provisioning; IPv6 is not supported; in-band provisioning is not supported with Windows 2000 Professional or Windows XP Tablet PC.
- Updated with the entry "Configuration Manager Fails to Provision Computers In a Child Domain Because of Missing DCOM Access Permissions", which describes a CA configuration requirement when the issuing CA is in another domain. To identify this troubleshooting scenario, look for
ERROR: ICertRequest2->Submit failed: 0x80070005
in the log file amtproxyomgr.log.