Commissioning an OutSystems environment on Windows Server 2016

Commissioning an OutSystems environment on Windows Server 2016


We recently commissioned our first OutSystems environment, and pretty much reduced the install steps using the installation checklist to a couple of Powershell commands:

1. Install the necessary Windows features for OutSystems:

Add-WindowsFeature -Name Web-Server,Web-Common-Http,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Static-Content,Web-Health,Web-Http-Logging,Web-Request-Monitor,Web-Stat-Compression,Web-Dyn-Compression,Web-Filtering,Web-Windows-Auth,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Mgmt-Console,Web-Metabase,MSMQ,WAS,WAS-Config-APIs

2. Set the AlwaysWithoutDS MSMQ DWORD setting in the registry to 1:

$registryPath = "HKLM:\SOFTWARE\Microsoft\MSMQ\Parameters\Setup"
$Name = "AlwaysWithoutDS"
$value = "1"
New-ItemProperty -Path $registryPath -Name $name -Value $value -PropertyType DWORD -Force | Out-Null

3. Disable the Windows Search service:

Get-Service WSearch | Set-Service -StartupType Disabled

4. Set the Windows Management Instrumentation Service to Autostart:

Get-Service Winmgmt | Set-Service -StartupType Automatic
Get-Service Winmgmt | Start-Service

5. Limit the EventLog sizes

Limit-EventLog -LogName Application -OverflowAction OverwriteAsNeeded -MaximumSize 20480KB
Limit-EventLog -LogName System -OverflowAction OverwriteAsNeeded -MaximumSize 20480KB
Limit-EventLog -LogName Security -OverflowAction OverwriteAsNeeded -MaximumSize 20480KB

Change the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing local security policy setting (Local Policies > Security Options) to disabled (we set this with GPO, so no Powershell necessary).

Hi Marcel,

Many thanks for your feedback. 

We may want to consider to include this scripts on the checklist!