Typical server installation changes
Things that have changed on a single web/app server setup when using InstallTool (IT) or DBUpgradeTool (DBUT).
Prerequisites
- Operating System Programs and Features
- We added an official statement that we only fully qualify on English Windows Server Operating Systems. [TS-7891]
- By a one-time operation to open up permissions in %WINDIR%\System32\inetsrv\config\applicationHost.config, we can now easily overwrite server settings per web site and/or virtual directory through their web.config file. See Configuring IIS applicationHost.Config. This will move typical settings like
<defaultDocument>,<directoryBrowse>,<asp>,<staticContent>, ... to web.config. Note that<security>and<authentication>are still part of applicationHost.config. - Installation of Static and Dynamic compression features have been added to requirements.
- Third Party Components have been raised to:
- Microsoft Server .NET Framework 4.5
- Microsoft .NET Framework Visual C++ Redistributable 2013 (64-bit)
- Java Development Kit 1.8.0_60 (64-bit)
- Java Runtime Environment 1.8.0_60 (64-bit)
- Oracle Data Access Client (ODAC) 12.1.0.1.2
- PowerShell v4.0 (part of Windows Management Framework 4.0)
While installing or upgrading
InstallTool doesn't stop or start Windows service IISAdmin.
By opening up applicationHost.Config we can enable Static and Dynamic Compression for regular HTTP and SOAP messaging calls out of the box. The end result of applying our typical installation steps will result in a system where WCF SOAP messages and DTD related files that are synchronized by Client Tools are now also compressed.
Starting from IIS 8.x, so Windows 2012R2, InstallTool (IT) will configure every IIS Application Pool to always be alive. This will shorten delays of first requests to an idle server.
Post installation steps
| Settings / File | 11.0.0 Config Version | 12.0.0 Config Version | What has changed |
|---|---|---|---|
| Admin.XMLBackgroundTaskConfiguration.xml | 1.1 | 1.1 |
|
| Admin.XMLChangeTrackerConfig.xml | 1.0 | 1.0 |
|
| Admin.XMLExtensionConfiguration.xml | n/a | 1.0 |
|
| Admin.XMLInboxConfiguration.xml | 1.0 | 1.0 |
|
| Admin.XMLPluginConfig.xml | 1.0 | 1.0 |
|
| Admin.XMLStatusConfiguration.xml | 2.0 | 3.0 |
|
| Admin.XMLTranslationConfiguration.xml | 1.0 | 2.0 |
|
| Admin.XMLWriteObjPluginConfig.xml | 2.0 | 2.0 |
|
After the installation is complete, none of our Windows services (including Crawler, TrisoftSolrLucene,...) will start automatically. The first reason is that the database is not guaranteed to be in the right state until you run DBUpgradeTool (DBUT). Another reason is that in a multi server environment you wouldn't want all your servers to pick up the same role. For your convenience on a single web/app server setup, we've provided a simple PowerShell script that will start and mark all services as Automatic. For using it, execute \App\Setup\Manage\Enable-DefaultServices.ps1 as Administrator.