SCW and Exchange Server 2007

Analysis
Jun 9, 20072 mins

I was asked the other day if the Security Configuration Wizard (SCW) can be used with Exchange Server 2007. The answer is yes, but information about Exchange 2007 needs to be registered into the SCW before you can create a base-line security policy for your shiny new Exchange servers. To do this the Exchange 2007 installation includes two registration files for the SCW which are located in the Exchange scripts folder (default location: %programfiles%MicrosoftExchange Serverscripts). The first registration file is named Exchange2007.xml. This is a general Exchange 2007 registration file that defines the security information for all Exchange 2007 server roles with one minor exception. This exception is with the security information for the Edge Transport role which is located in the Exchange2007Edge.xml registration file. To register these files into the SCW requires the use of the scwcmd command line utility. The commands for each file are as follows:

  • scwcmd register /kbname:Ex2007KB /kbfile:Exchange2007.xml
  • scwcmd register /kbname:Ex2007EdgeKB /kbfile:Exchange2007Edge.xml
  • Once you have completed the registration process. Options for Exchange 2007 will then be available in the Server Roles and Client Features sections of the SCW. However, it is important to note that you will need to register these files on each Exchange server that you want to apply an Exchange 2007 security policy too (on top of having the SCW installed). :>) My suggestion would be to automate the installation of the SCW during your base operating system build. Then automate the registration of the extension files during your Exchange 2007 installations. Note: The above registration files are hard coded to define port executables using the default Exchange Server 2007 installation location (%Programfiles%MicrosoftExchange Serverbin). If you have installed Exchange 2007 in a different location, then that location must be reflected in the registration files. For all of today’s Microsoft news, visit Microsoft Subnet