https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
r
As for when to do it. I am not aware of when to do it. I just know if I publish an app, and I get freezing when it is launched and high CPU like really high. I RDP in the box and run it. If it opens, I tend to go down the path of removing the hooks in the link you posted.
But yes, I still do it when I run into troubleshooting seamless apps via XA.
n
oh man, i keep asking the same questions...sorry
r
No worries man, We all do it.
n
okay, next question
do i need these settings if i have HKLM\SYSTEM\CurrentControlSet\services\CtxUvi\UVIProcessExcludes setup? - https://support.citrix.com/article/CTX107825/how-to-disable-citrix-api-hooks-on-a-perapplication-basis . the client has CVAD version 1912 CU5
i think the older settings can be removed, what do you guy think
r
Ideally the Uvi process will handle it now.
I think I had a hand full of apps I put in the old way. Looking to confirm. But I published visual code and I added it to Uvi via GPO. I kept getting grey screens, and I could not figure out why. Then I was passed this, and it made sense why https://support.citrix.com/article/CTX321177/grey-screen-issue-after-changes-were-made-under-ctxuvi-and-ctxhook
n
ok
r
Nope it was the Uvi. Sorry
n
cool
well, i will remove the old setting and tell them to test
i'll remove it from the master image and then remove the GP setting like that article recommends
r
Keep it in the golden image
n
okay, i won't apply it through group policy
r
Just to give you more context around it. In the link @Jeremy Saunders has good stuff. https://www.jhouseconsulting.com/2019/07/18/citrix-virtual-delivery-agent-vda-post-install-script-2015 "Configure the UviProcessExcludes and hook DLLs (CtxHooks)" "VDA 7.9 and above utilises Kernel APC (KAPC) Hooking as a replacement of AppInit_DLLs. The KAPC Hooking DLL Injection Driver (CtxUvi) verifies that the hook DLLs configuration in the registry is not changed at runtime (i.e. HKLM\SOFTWARE\Citrix\CtxHook\AppInit_DLLs\<hook name>). If a change to the configuration is detected, the CtxUvi driver disables itself until the next reboot, resulting in none of the Citrix Hooks being properly loaded. So it is recommended not to use Group Policies to control these registry keys and placing them in the master PVS/MCS image instead." References: • https://support.citrix.com/article/CTX220418 • https://support.citrix.com/article/CTX226605 • https://support.citrix.com/article/CTX223973
j
Thanks for the mention @Ray Davis. I think Citrix could do a lot better with the implementation of CtxHooks. It has to be one of the most troublesome parts of the on-going management, especially as it's not easy to roll out given that you have to update the master image. It would be better if the service could refresh from the registry, so you can update it via a GPO.
r
Anytime man, I actually refer clients a lot to that for guidance. But I agree the master image way really is a damper. You got great material
4 Views
Open in Slack
PreviousNext
Powered by