This message was deleted.
# citrix-vad
s
This message was deleted.
k
Do you have Local Host Cache configured?
⤴️ 1
Oh and Enable and disable Local Host Cache To enable Local Host Cache, enter: Set-BrokerSite -LocalHostCacheEnabled $true To determine whether Local Host Cache is enabled, enter: Get-BrokerSite Check that the LocalHostCacheEnabled property is True. To disable Local Host Cache, enter: Set-BrokerSite -LocalHostCacheEnabled $false
Copied from Docs
a
hmm good question! do you know how i can verify if we have that on or not ? hunting through that doc. i am not sure to be honest
r
But if you dont have LHC enabled. yes only new sessions will be impacted. Current session will remain intact(unless they diconnect)
run Get-BrokerSite
a
sorry you said that already 🙂
reading is important i guess haha
k
😄
r
its cool man, you help me out all the time.
👍 1
k
Who hasn't received help from someone in this channel?
👍 2
r
So true, I would be stuck if I DIDN'T have this place
here is what ours looks like enabled
m
Keep in mind that local host cache will NOT kick in immediately. There are delays regarding database connections for your controllers. I would recommend to use „OutageModeForced“ for planned database maintenance.
👍 1
💯 2
r
This:To force an outage, edit the registry of each server containing a Delivery Controller. In HKLM\Software\Citrix\DesktopServer\LHC, set OutageModeForced as REG_DWORD to 1. This instructs the broker to enter outage mode, regardless of the state of the database. Setting the value to 0 takes the server out of outage mode.
a
ok ours is off it looks like. so what is it actually doing if i turn it on? we are looking to do this in a few days so we'd have some time
any downsides to it?
r
I cant remember 100% but I know there was some MCS pool issues with LHC. @Matthias Eckerle might have more details. But let me find my notes
@Kasper Johansen too 🙂
"Pooled VDI desktops are not supported, but if you are using published apps and desktops provided by XenApp (Virtual Apps) you are covered by LHC."
a
ahh we do use mcs pooled random setup so probably wouldnt work then hey?
ok so if we keep it disabled......i have an active session and the sql server reboots what happens? does my session drop then probably?
r
Let me check my notes to get you 100% accurate info before I put my foot in my mouth LOL
a
for some reason i thought citrix told me it would only affect people trying to start a new session for some reason
r
If you have session that are established (NO LHC) the sessions will remain intact. Only new connections will be impacted. However, if the users get interrupted then they will drop off like flies in my experiences.
a
makes sense......so as long as we dont disconnect/have a network blip at home we should be ok for that couple min it takes to reboot probably ? really this is just for a handful of us that need to work the night we're gonna do this
r
Yes that is correct.
a
awesome thanks guys!
i get way more useful info here than i ever did calling into support or their forums!
r
I have done this many times as well.
yea me as well.
I havent tested this yet but look like on 1912 "Local Host Cache is supported for server-hosted applications and desktops, and static (assigned) desktops."
I would like to know if anybody else knows that?
m
yeah, what version are talking here, because 7.15 has serious issues
r
True good point. I was shooting for 1912, but Andrew might be on another version
m
you need to watch out for machines that shut down after use
they will go into maint mode by default
n
@Mike Streetz (O_P) Yeah VDI churn is a good point.
r
Yea true the article did say To override the default behavior, you must enable it site-wide and for each affected Delivery Group. Run the following PowerShell cmdlets.
Set-BrokerSite -ReuseMachinesWithoutShutdownInOutageAllowed $true
Set-BrokerDesktopGroup -Name "name" -ReuseMachinesWithoutShutdownInOutage $true
m
you can override it but if you rely on a reset to wipe out user data you might run into issues with seeing another users data
r
So pooled is supported now? in 1912
a
so we're on 1912 vda but still 7.15.2000 back end (scheduling the full upgrade still)