This message was deleted.
# citrix-cloud
s
This message was deleted.
r
Seeing it here as well while working with a customer.
👍🏽 1
d
its not just workspace
all of my machines lost registration
n
Same. We're in LHC.
d
LHC?
n
Local Host Cache
Local Host Cache enables connection brokering operations in a Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) deployment to continue when a Cloud Connector cannot communicate with Citrix Cloud. Local Host Cache engages when the network connection is lost for 60 seconds
n
but i though LHC is only works with on premise SF servers. If you are complete citrix cloud then you need to enable service continuity. am i wrong? still learning stuff..lol
💯 1
b
A lot of customers will have Citrix cloud for brokering but keep SF and NetScaler on-prem for other reasons
m
Those running LHC with internal StoreFront servers, how did it hold up with this outage? Business as usual? Service Continuity did not work for me for Workspace Service connections.
r
It worked on my side while I was working with a client. Service Continuity. The browser did not work, as I did not have the plugin.
n
For us, it sounds like multi-session OS was fine, but we apparently had issues with single session VDAs. I'm not really involved in that discussion, though.
👍 2
c
We use on prem SF and ADC with citrix cloud and i been working on other stuff today and dont really get involved in support but i had no issues reported to me which would normally be the case if there was a major issue. I just gone back and checked and we lost access to citrix cloud about 4.06pm GMT and VDA's lost contact and became unregistered when LHC kicked in it was running on LHC for about 44 mins
👍 1
d
is LHC using 89 on Cloud connectors? or VDAs?