One of the more common requests we hear is that customers want a way to export the configuration settings for their Client Access servers. One reason for this is due to the unique way in which a Client Access server stores configuration settings and data. Client Access servers store their configuration data in multiple places:
- Active Directory is used to store configuration information related to the Availability service, Exchange ActiveSync, and Outlook Web Access virtual directories
- The Internet Information Services (IIS) metabase also stores configuration information for Exchange ActiveSync, as well as for Autodiscover, and Exchange Web Services
- Local configuration files, such as Web.config files and the Windows registry are used to store configuration data related to Outlook Web Access, IMAP, POP3, the Availability service, Exchange ActiveSync, and information used by Exchange Setup.
It is critical to preserve Client Access server configuration data because if the server suffers a hardware failure, this configuration data will be needed in order to restore any custom configuration changes that were made to the server. This is because recovering a Client Access server using Setup /m:RecoverServer reverts all configuration to the default settings, and any customized configuration is lost.
For more details, see the topic “Client Access Server Data” at http://technet.microsoft.com/en-us/library/aa998364.aspx.
Read at source: http://msexchangeteam.com/archive/2007/11/14/447534.aspx
Technorati : CAS, Import/Export, Script, settings
Del.icio.us : CAS, Import/Export, Script, settings
Ice Rocket : CAS, Import/Export, Script, settings
