This message was deleted.
# citrix-vad
s
This message was deleted.
n
I don't do that, but I've read two scenarios from other - the ICA service times out because of something in Windows, and this: http://www.jhouseconsulting.com/2019/03/04/controlling-the-starting-of-the-citrix-desktop-service-brokeragent-1894
r
yea, I don't do it either. But I wonder if its why we get client connection failures a times.
n
You'd think that the event logs or Director would help out more with that, but here we are. We battle the same thing.
r
Yea it sucks, I have been trying to find out why. But its not consistent. I even have to exit workspace, the reopen it for a user to connect.
n
We went through the trouble of cracking open our image to enable CDF tracing (WTF DO YOU MAKE THIS SO CUMBERSOME, CITRIX?), and the logs showed nothing useful.
r
dang.
n
It's better in 1912 than it was in 7.15, that's for sure.
j
I agree with @Nick Panaccio, 7.15 was so cryptic with the data that I don't think Citrix own tier 2 and 3 techs knew what to make of them. Had a customer receive directions to collect the useless logs and when why and what they expected find, the response was basically "cuz my directions tells me to ask for them"
m
we had to delay it because the machines would boot up so fast that if you let sessions onto them they would get stuck for 15 minutes.
Windows wasn’t ready to let people onto the machine but citrix was there throwing users at it
once we set a delay to 3 minutes everything calmed down. I haven’t had to do it in any other environments, but that one was an odd duck
n
I have our SettlementPeriodBeforeUse setting for my XD DGs set to 5 minutes. Originally, it was for App Layering, but since that's basically no longer required with O365, I guess I don't really need it any longer.
r
@Mike Streetz (O_P) do you see a high % of Client connection failures? I thinking is that maybe, the people who are not apply the Delayed approach would be contributing to this?
m
yes, tons
it would end up connecting twice somehow in director
it was the craziest setup
r
Was that before the delay or is that before and after
m
before
the delay fixed all of it
r
interesting...... OK, well time for me to test this and introduce the delay. I might have to increase the timeout settings so it doesn't get unregistered.
m
I think we took our delay down to 90 seconds
but that was for 2008r2 servers
they would boot up and register within 30 seconds, and GPO hadn’t even finished processing by that point, like the machine still didn’t have the correct time from the domain…
r
From what I am reading looks like you need to update MaxRegistrationDelayMin dword
m
that sounds right, there was also a tool that would do it for you, the citrix desktop helper
t
I use the Jhouse consulting script and we have ways set a delay to allow the auto-logon user to log off and the WEM cache to refresh. Without it we would see people try to logon before everything was ready which caused a variety of weirdness. It’s just habit to keep doing it now.
s
@Ray Davis did you check DDC any events? For a customer i also facing the same issue Event ID 1116 on DDC
r
I have not, However I will look into it. Thanks Salim
👍 1