The binaries were installed in the location specified during installation. The default location is C:\Program Files\Microsoft Office Servers\12.0. Here you will find global files for the installation and applications. For instance, the C:\Program Files\Microsoft Office Servers\12.0\Data\Applications\(instance ID)\Config folder contains global configuration files used by the search engine, like the language-specific noise word and Thesaurus files along with the Thesaurus schema xml file. Other folders are also installed as follows:
Projects This is the location for the various indexes.
Single sign-on Common files are installed to C:\Program Files\Microsoft Shared \Microsoft Office 12\ Single Sign-on.
Global executables C:\Program Files\Common Files\Microsoft Shared \OFFICE12 contains the dll's used globally.
1033 This folder is used for US English. Other folders will appear as you install additional language packs.
Setup files Critical setup files that might be needed later for re-running certain aspects of the setup and Configuration Wizard are placed at C:\Program Files\Common Files\Microsoft Shared\SERVER12.
Web services Common files are installed to C:\Program Files\Microsoft Shared\Web server extensions\.
The new "12 hive" C:\Program Files\Common Files\Microsoft Shared \Web server extensions\12 is the equivalent of what we affectionately called the "60 hive" in SharePoint Portal Server 2003.
Some files that you find here are global, some are language specific (En-us or enus is US English), and some are application (Web site) specific.
In addition, there is a hierarchy to many of the files. For instance, in C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Data\Config, you will find another set of noise word and thesaurus files that supersede those discussed previously. In the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Data\Applications\SPS2\Config folder, you will find a set of noise word and thesaurus files that are specifically for the SPSv2 application. Under this folder, you will also find other search files and logs specific to this application.
In the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\TEMPLATE\LAYOUTS folder, you will find the administrative pages address by the _layouts relative path on your sites. Also, in the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\TEMPLATE\images is the _images relative path for images addressable anywhere in your sites.
The Configuration Wizard makes hundreds of registry entries as it installs and registers dlls, services, and features. For example, the installation of SharePoint Server 2007 adds several entries to the registry under HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server and HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\12.0.
The creation of the first SSP adds 48 keys to the registry, many of which have up to 36 entries within the key. These changes are found in a file named RegistryBlob.reg located in the SSP: C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications\(Site GUID) directory.
Configuring the Search and Index server adds 186 keys to the registry, many of which have up to 53 entries within the key. These changes are found in a file named Registry-Blob.reg located in the C:\Program Files\Microsoft Office Servers\12.0\Data\Applications\(site GUID) directory. These registry changes are also stored in the configuration database so that other WFEs can replicate them.
No changes were made to IIS during the installation of SharePoint Server 2007. However, the Configuration Wizard made several changes, including the following ones:
The following two application pools were created:
SharePoint Central Administration v3 using the SQL service account specified during the wizard
OfficeServerApplicationPool using the Network Service account
The Central Administration Web site was created using the SharePoint Central Administration 3.0 application pool.
The Office Server Web Services Web site was created using the OfficeServerApplicationPool.
With SharePoint Server 2007, new Web sites and new application pools, such as Corporate Portal, must be created from within Central Administration so that the process includes storing the configuration in the configuration database. Also, modifications to IIS configuration, with the exception of adding more host headers, should be made with Central Administration.