This article details the steps that you neeed to take to perform an In-Place Upgrade of FsLogix, you would just need to follow the article below from Microsoft:
https://learn.microsoft.com/en-us/fslogix/how-to-install-fslogix
ENSURE YOU TAKE A BACKUP OF THE USER PROFILE FOLDERS INSIDE C:/USERS BEFORE ACTIONING ANYTHING.
1) There'll be a step by step guide on there, ignore this step detailed in the article:
The above does not apply to our servers at this current time 16/01/25 21:00.
2) After you finish following the article make sure you reboot the server
3) Once the server is backup launch Powershell ISE and run the below script:
# FSLogix - recommended resiliency keys + CleanupInvalidSessions
# Does NOT modify VHDLocations.
# Profiles keys
$profiles = "HKLM:\SOFTWARE\FSLogix\Profiles"
if (-not (Test-Path $profiles)) { New-Item -Path $profiles -Force | Out-Null }
$profileValues = @{
DeleteLocalProfileWhenVHDShouldApply = 1
FlipFlopProfileDirectoryName = 1
LockedRetryCount = 3
LockedRetryInterval = 15
ReAttachRetryCount = 3
ReAttachIntervalSeconds = 15
}
foreach ($name in $profileValues.Keys) {
New-ItemProperty -Path $profiles -Name $name -PropertyType DWord -Value $profileValues[$name] -Force | Out-Null
}
# Apps key: cleanup invalid sessions
$apps = "HKLM:\SOFTWARE\FSLogix\Apps"
if (-not (Test-Path $apps)) { New-Item -Path $apps -Force | Out-Null }
New-ItemProperty -Path $apps -Name CleanupInvalidSessions -PropertyType DWord -Value 1 -Force | Out-Null
# Verify (print) - safe version (no backticks)
"=== FSLogix Profiles values ==="
$props = @(
"DeleteLocalProfileWhenVHDShouldApply",
"FlipFlopProfileDirectoryName",
"LockedRetryCount",
"LockedRetryInterval",
"ReAttachRetryCount",
"ReAttachIntervalSeconds"
)
Get-ItemProperty $profiles | Select-Object -Property $props | Format-List
"=== FSLogix Apps values ==="
Get-ItemProperty $apps | Select-Object -Property "CleanupInvalidSessions" | Format-List
By the way you can just add the registy keys manually via rededit, this is just to save you time.
4) Now reboot the server one more time and you should be all good to go. If the server has any core business services ensure they are all up.