Enjoy!
Justin Gao
Microsoft (China)
Enjoy!
Justin Gao
Microsoft (China)
1. Exchange 2007可以支持升级到Exchange 2010，但需要提前将Exchange 2007所有服务器环境升级至 SP2或以上版本。
2. Exchange 2007如果更新至SP2或以上版本，则建议按照以下顺序进行各角色的更新： CAS、UM、HUB、Edge、Mailbox。
3. 不支持从Exchange 2007本地升级至Exchange 2010的操作，因此需要在Exchange 2007环境中，全新部署Exchange 2010环境后进行数据迁移。在数据迁移后可以实现Exchange 2010和Exchange 2007环境的共存，或再将Exchange 2007环境卸载等操作。
4. 如果企业环境中已经包含多台Exchange 2007服务器角色，而迁移后的Exchange 2010环境也包含多台服务器角色，则升级相应角色时应遵循以下升级顺序：CAS、HUB、UM、Mailbox、Edge。
5. 当开始将你的组织升级至Exchange 2010时，你必须首先升级面对Internet（Internet-facing）的AD站点中的服务器，随后再升级非面对Internet的AD站点中的服务器。如果你的企业具有多个面对Internet的AD站点，则首先要升级的是启用了外部发现记录（External Autodiscover Record ）的AD站点中的服务器，随后是其余面对Internet的AD站点中的服务器。
6. 如果你在全新的环境中部署了Exchange 2010，随后你将无法再添加Exchange 2007角色的服务器到该环境。如果你希望在Exchange 2010环境中添加Exchange 2007服务器，则首先你需要在Exchange 2007环境中部署Exchange 2010服务器，然后实现共存，至少保留一台Exchange 2007服务器，才能再随后添加Exchange 2007服务器角色。
7. 当你的环境处于Exchange 2007与Exchange 2010共存时，在同一个AD站点你需要每个Mailbox角色都有与之版本相对应的HUB角色存在。由于Exchange 2010 Exchange Server Object (XSO)模型的改变，Exchange 2010的HUB角色将不能传输从Exchange 2007 Mailbox服务器传递的数据。同样，Exchange 2007的HUB角色也不能与Exchange 2010的Mailbox服务器进行沟通。因此你需要一直保留Exchange 2007的HUB角色，除非在该AD站点中完全没有Exchange 2007的Mailbox角色。
8. Exchange 2010 管理控制台（EMC）没有32位版本，仅能部署在64位环境下的以下OS上：
l Windows Vista with SP2 for Management tools only installation
l 64-bit of Windows Server 2008 Standard or Enterprise with SP2
l 64-bit of Windows Server 2008 R2 Standard or Enterprise
l Windows 7
9. 在Exchange 2007和Exchange 2010共存环境下，两个版本的EMC均可以使用，但创建对象的操作，如新建邮箱或新建脱机通讯簿（OAB），只能在目标对象相同版本的EMC上执行。Exchange 2010的EMC可以查看Exchange 2007邮箱数据库，但无法管理。Exchange 2010的EMC无法启用或禁用Exchange 2007统一消息邮箱。Exchange 2010的EMC无法管理Exchange 2007的移动设备。
10. 在Exchange 2007和Exchange 2010共存环境下，要求查看对象的操作可以从任意版本的EMC执行到任意版本的Exchange对象，但以下情况例外：
l Exchange 2010 和 Exchange 2007 传输规则对象只能从其对应版本的 EMC 查看。
l Exchange 2010 和 Exchange 2007 服务器只能从其对应版本的 EMC 查看。
l Exchange 2010 EMC 中的队列查看器工具无法连接到 Exchange 2007 服务器以查看队列或邮件。
11. 不能在 Exchange 2010 和 Exchange 2007 之间使用邮件跟踪配置任务。必须在 Exchange 2007 服务器中使用 Exchange 2007 邮件跟踪工具，在 Exchange 2010 服务器中使用 Exchange 2010 邮件跟踪工具。
12. 在Exchange 2007和Exchange 2010共存环境下，只能在Exchange 2007下呈现而不能在Exchange 2010环境下呈现的对象如下：
l Storage Groups
l Exchange Administrators
l WebDAV
仅能在Exchange 2010环境下呈现而不能在Exchange 2007环境下呈现的对象如下：
l DAG
l Certificate creation
l Database copies
l Federation Trust
l Sharing Relationships
l Sharing Policies
l OWA Mailbox Policies
l Customer Experience Program properties
13. 在将用户邮箱从Exchange 2007版本迁移至Exchange 2010版本的过程中，该用户的邮箱仍处于在线状态，即终端用户在邮箱被迁移过程中仍可以正常使用邮箱。但从Exchange 2003至Exchange 2010、Exchange 2010 至Exchange 2003、Exchange 2010至Exchange 2007的邮箱迁移过程中，邮箱均处于离线状态，即终端用户在邮箱被迁移过程中不可使用邮箱，直到该邮箱被完全迁移完成才能使用。
Enjoy!
Justin Gao
Microsoft (China)
What's New in Configuration Manager 2007 R3
The following features are new and apply only to Configuration Manager 2007 R3:
· Power Management. Provides a set of tools to allow the site administrator to configure standard Windows power settings across computers
· Operating System Deployment Enhancements. Prestaged Media is a way to integrate with OEM factory imaging in order to leverage imaging at the OEM to speed up new hardware deployments
· Dynamic Collection Evaluation. Allows you to more rapidly evaluate a collection membership by adding only newly discovered resources.
· Delta Discovery. Performs an intermediate discovery cycle adding only new resources to the Configuration Manager 2007 database.
· Collections. Allows you to search for and add resources to the specified collection.
· Desired Configuration Management. Allows you to easily create collection of compliant or noncompliant computers in desired configuration management.
· Supported Clients Per Hierarchy: Configuration Manager 2007 R3 supports up to 300,000 clients per hierarchy when using the default settings for all Configuration Manager 2007 features. This increase in supported clients is the result of improvements to the Active Directory synchronization and Collection Evaluation processes.
About Dynamic Collection Evaluation in Configuration Manager 2007 R3
Query-based collections in Configuration Manager 2007 are periodically evaluated, based on a schedule you specify to update their membership from the site database. Even if there are no changes in the collection being evaluated, the entire collection is still processed. The default period between collection evaluations is 1 day. You can decrease this period, but evaluating collections with many members might cause a high load on your site database.
Dynamic collection evaluation in Configuration Manager 2007 R3 allows you to evaluate only resources that have been newly added to a collection. Because this improves the speed at which you can evaluate collections and lessens the processing load on the site database, you can increase the frequency by which you evaluate collections and therefore keep the data shown in the administrator console more up to date.
Important: Dynamic collection evaluation does not replace the existing method of collection evaluation; it only evaluates newly added resources
The following resources can be evaluated by dynamic collection evaluation:
· Resources that have been initially discovered.
· Resources that have been provisioned with operating system deployment.
· Resources that have been scanned for initial hardware inventory.
· Resources that have been upgraded to a newer version of the Configuration Manager 2007 client.
About Delta Discovery in Configuration Manager 2007 R3
Delta Discovery in Configuration Manager 2007 R3 enhances the discovery capabilities of the product by discovering only new or changed resources in Active Directory instead of performing a full discovery cycle. The interval by which delta discovery searches for new resources can be configured by the user to a short interval as discovering new resources only does not affect the performance of the site server as much as a full cycle. Delta discovery can detect the following new resource types:
· Computer objects
· User objects
· Security group objects
· System group objects
Important: Delta discovery is not a replacement for other Configuration Manager 2007 discovery methods. Because it only finds new or modified resources in Active Directory, it must be used in conjunction with a discovery method that performs a full synchronization with Active Directory
Note: Delta discovery only reads Active Directory attribute changes which are replicated. Non-replicated attributes which are changed such as the memberof attribute are not collected by delta discovery unless a change to a replicated attribute is made at the same time. Delta discovery is not enabled by default in Configuration Manager 2007 R3. When enabled, it will run, by default every 5 minutes
About Prestaged Media in Configuration Manager 2007 R3
Prestaged media for Configuration Manager 2007 R3 operating system deployment contains bootable media and image files that are copied to the hard drive of a computer. Prestaged media works in conjunction with your existing task sequences to provide a complete operating system deployment. The media can be accessed locally by a task sequence to install a new operating system instead of downloading them across the network. This allows operating system deployment where the computer cannot otherwise be provisioned completely. It can also reduce network traffic when deploying operating systems while still taking advantage of task sequences.
Prestaged media is generally copied to the hard drive of a new computer as a part of the computer manufacturing process or at an enterprise staging center before the computer is sent to the end user. The prestaged media consists of a .wim file that can be prestaged on a “bare metal” computer. When the computer boots for the first time after the prestaged media has been loaded, the computer will boot to WinPE and connect to the site management point to check for available task sequences.
When creating prestaged media, ensure the boot image you are using has the appropriate network and mass storage drivers need for the system to complete the provisioning process.
About Simplified Resource Management
Allows Administrators to search for and add resources to the specified collection using right click tool.
About Power Management in Configuration Manager 2007 R3
The Microsoft System Center Configuration Manager 2007 R3 power management feature provides a set of tools and resources that can help apply power settings to client computers in the enterprise and monitor the power usage of computers. Click the associated link in the following section for detailed information about planning, configuring, managing, monitoring and troubleshooting power management.
Overview of Power Management
Power Management in Microsoft System Center Configuration Manager 2007 R3 addresses the need that many organizations have to monitor and reduce the power consumption of their computers. The feature leverages the power management features built in to Windows to apply relevant and consistent settings to computers in the organization. Different power settings can be applied during and outside of working hours. For example, it might be acceptable to apply a more restrictive power plan during non-peak hours. In cases where computers must always remain switched on, you can prevent power management settings from being applied.
There are three major components to power management in Configuration Manager 2007 R3:
1. Monitoring and Planning: Power Management extends the hardware inventory of Configuration Manager 2007 to collect information about computer usage and power settings for computers in the site. A number of reports are provided to allow you to analyze this data and determine optimal power management settings for computers.
2. Enforcement: Power management allows you to create power plans which can be applied to collections of computers in your site. These power plans configure Windows power management settings on computers. You can use the built in Windows power plans, Balanced, High Performance and Power Saver or you can configure your own custom power plans. Different power plans can be configured for peak and non-peak working hours.
3. Compliance: After applying power plans to computers in your organization, you can run reports to validate that power settings were correctly applied and to calculate power savings across collections of computers.
About Reports for Power Management
Power management in Configuration Manager 2007 R3 contains a number of reports to help you to analyze power consumption and computer power settings in your organization. These reports require SQL Reporting Services which was introduced in Configuration Manager 2007 R2.
Power Management Plan Settings for Power Management
Power plans in Configuration Manager 2007 R3 contain Windows power management settings which can be configured and applied to collections of computers in your Configuration Manager 2007 R3 site.
Important: Depending on the version of Windows you are using, some settings might not be configurable on the destination client computer. For more information about the settings supported by your version of Windows, see your Windows documentation
Prerequisites for Power Management
Power management in Configuration Manager 2007 R3 has both external dependencies and dependencies within the product.
Configuration Manager 2007 Dependencies
The following table describes the dependencies within Configuration Manager 2007 for using power management.
|
Dependency |
More Information |
|
The site server must be running Configuration Manager 2007 R3. |
Power management requires Configuration Manager 2007 R3. |
|
Client computers in your site must be running the Configuration Manager 2007 R3 client software. |
For information about upgrading the Configuration Manager 2007 client software, see Planning and Deploying Clients for Configuration Manager 2007. |
|
The Configuration Manager 2007 hardware inventory client agent must be enabled for the site in which you are using power management. |
Power management in Configuration Manager 2007 R3 uses information collected by hardware inventory. To use power management, you must first enable hardware inventory for the site. |
|
The site must be enabled for power management. |
Before you can use power management in Configuration Manager 2007 R3, you must enable the power management client agent. |
|
SQL Reporting Services integration must be installed and configured. |
The provided reports for power management require SQL Reporting Services to run. SQL reporting services integration was introduced in Configuration Manager 2007 R2 and is also included with Configuration Manager 2007 R3. For information about installing and configuring SQL Reporting Services, see SQL Reporting Services in Configuration Manager 2007 R2. |
Dependencies External to Configuration Manager 2007
The following table describes the dependencies within Configuration Manager 2007 for using power management.
|
Dependency |
More Information |
|
The site must have access to an installation of Microsoft SQL Reporting Services. |
Power management in Configuration Manager 2007 R3 uses SQL Reporting Services to display reports. SQL reporting services must be installed and configured for Configuration Manager 2007 before you can display these reports. For more information, see SQL Reporting Services in Configuration Manager 2007 R2. |
How to Enable or Disable the Power Management Client Agent
Enabling the power management client agent in Configuration Manager 2007 R3 makes it possible for client computers in this site to apply power management plans configured in the Configuration Manager console.
The power management client agent is not enabled by default when you install Configuration Manager 2007 R3.
Important: The power management feature in Configuration Manager 2007 R3 uses data from hardware inventory on client computers to work, therefore, enabling the power management client agent will also enable the hardware inventory client agent on computers in your site. If you disable the hardware inventory client agent for your site, the power management client agent will also be disabled. Disabling the power management client agent prevents computers in your site from applying power plans created in the Configuration Manager console.