### Start Halo WebApp Components

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-host-os

After the host reboots, ensure the Halo WebApp and its application pool are running. This is typically automatic but can be started manually if needed.

```powershell
Import-Module WebAdministration
Start-WebAppPool -Name 'CONFIRM-HaloAppPool'
Start-Website    -Name 'CONFIRM-HaloSiteName'

Get-Website -Name 'CONFIRM-HaloSiteName' | Select-Object Name, State
```

--------------------------------

### Restart Halo IIS Site and App Pool

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-halo

After the upgrade files have been copied and installers run, use these PowerShell commands to restart the Halo website and application pool. This also includes commands to re-enable any disabled integrator scheduled tasks.

```powershell
Import-Module WebAdministration
Start-WebAppPool -Name 'CONFIRM-HaloAppPool'
Start-Website    -Name 'CONFIRM-HaloSiteName'

# Re-enable the integrator scheduled task(s) if they were disabled before the drag-drop.
# «CONFIRM»: adjust the -like pattern if the exe name differs in this deployment.
$integratorTasks = Get-ScheduledTask | Where-Object {
    $_.Actions.Execute -like '*Integrator*'
}

foreach ($task in $integratorTasks) {
    Enable-ScheduledTask -TaskName $task.TaskName -TaskPath $task.TaskPath
}

$integratorTasks | Select-Object TaskName, TaskPath, State
```

--------------------------------

### Check API Instance Info

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-host-os

Verify that the Halo WebApp and API are responding correctly after the upgrade by hitting the instance info endpoint. This confirms basic connectivity and service health.

```http

«CONFIRM: base URL»/api/instanceinfo

```

--------------------------------

### Create IronSoftware Folder for IIS Permissions

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-halo

Manually create this folder and grant IIS user permissions to resolve login loop issues after an upgrade.

```path
C:\Windows\System32\config\systemprofile\AppData\Local\IronSoftware

```

--------------------------------

### Webhook Event Flow

Source: https://grcitsm.stratuscyber.com/admin-guides/integrations/webhooks

Illustrates the basic flow of an event triggering a webhook and subsequent processing by an external system.

```text
GRC-ITSM Event → Webhook fires → HTTP POST to endpoint → n8n workflow executes
```

--------------------------------

### Set SQL Compatibility Level to 130

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-halo

If your database's compatibility level is below the minimum requirement (>= 130) for older Halo versions, use this command to raise it. Replace 'YourDatabaseName' with your actual database name.

```sql
ALTER DATABASE YourDatabaseName
SET COMPATIBILITY_LEVEL = 130;
```

--------------------------------

### Check Current SQL Compatibility Level

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-halo

Use this SQL query to check the current compatibility level of your Halo database. Ensure it meets the minimum requirements for your target Halo version.

```sql
SELECT name, compatibility_level
FROM sys.databases
WHERE name = 'YourDatabaseName';
```

--------------------------------

### Clear Cache via URL Parameter

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-halo

Use this URL parameter to force a server-side cache clear if the version is not updating correctly after an upgrade.

```url

«CONFIRM: base URL»/api/instanceinfo?clear_cache=true

```

--------------------------------

### Set SQL Compatibility Level to 140

Source: https://grcitsm.stratuscyber.com/admin-guides/onprem-maintenance/upgrading-halo

When upgrading to Halo v2.220 or later, the SQL compatibility level must be at least 140. Use this command to set it, replacing 'YourDatabaseName' with your actual database name.

```sql
ALTER DATABASE YourDatabaseName
SET COMPATIBILITY_LEVEL = 140;
```