{"id":318,"date":"2020-04-23T21:39:55","date_gmt":"2020-04-23T19:39:55","guid":{"rendered":"https:\/\/blog.vermeerschconsulting.be\/?p=318"},"modified":"2021-01-30T10:59:42","modified_gmt":"2021-01-30T09:59:42","slug":"edge-chromium-in-citrix-virtual-apps-server-2016-or-2019-with-a-working-smart-card-reader","status":"publish","type":"post","link":"https:\/\/blog.vermeerschconsulting.be\/index.php\/2020\/04\/23\/edge-chromium-in-citrix-virtual-apps-server-2016-or-2019-with-a-working-smart-card-reader\/","title":{"rendered":"Edge Chromium in Citrix Virtual Apps (Server 2016  or 2019) with a working smart card reader"},"content":{"rendered":"\n<p>When installing the new Microsoft Edge Chromium browser on a Citrix Virtual Apps worker (tested with VDA 1912 LTSR on Windows Server 2016 or 2019) the Edge browser will not correctly launch<\/p>\n\n\n\n<!--more-->\n\n\n\n<p>You can find some info on the Internet that you need to follow the Citrix article (<a rel=\"noreferrer noopener\" href=\"https:\/\/support.citrix.com\/article\/CTX107825\" target=\"_blank\">CTX107825<\/a>) to disable Citrix API Hooks on a per-application basis<\/p>\n\n\n\n<p>This works perfectly but because you disable all Citrix API Hooks, the smart card reader for example is not working.<\/p>\n\n\n\n<p>A better way is to add the following key instead of completely disabling the API Hooks. You can see it already exist for other browsers out of the box. It is important to reboot the machine or add this to you PVS master image.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; gutter: false; title: ; quick-code: false; notranslate\" title=\"\">\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Citrix\\CtxHook\\AppInit_Dlls\\SfrHook\\msedge.exe\n<\/pre><\/div>\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"766\" height=\"494\" src=\"https:\/\/blog.vermeerschconsulting.be\/wp-content\/uploads\/2020\/04\/disable-citrix-api-hooks-for-ms-edge-chromium.png\" alt=\"Disable Citrix API Hooks for MS Edge Chromium\" class=\"wp-image-319\" srcset=\"https:\/\/blog.vermeerschconsulting.be\/wp-content\/uploads\/2020\/04\/disable-citrix-api-hooks-for-ms-edge-chromium.png 766w, https:\/\/blog.vermeerschconsulting.be\/wp-content\/uploads\/2020\/04\/disable-citrix-api-hooks-for-ms-edge-chromium-300x193.png 300w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px\" \/><figcaption>Disable Citrix API Hooks for MS Edge Chromium<\/figcaption><\/figure>\n\n\n\n<p>There is a troubleshooting tool available from Citrix (login required) to test and change these settings using a GUI. It is the Citrix Application Experience (CAX) Troubleshooting Tool. <a rel=\"noreferrer noopener\" href=\"https:\/\/support.citrix.com\/article\/CTX222592\" target=\"_blank\">https:\/\/support.citrix.com\/article\/CTX222592<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When installing the new Microsoft Edge Chromium browser on a Citrix Virtual Apps worker (tested with VDA 1912 LTSR on Windows Server 2016 or 2019) the Edge browser will not correctly launch<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[16,43],"tags":[49,52,44,51,46,50,45,47,48],"class_list":["post-318","post","type-post","status-publish","format-standard","hentry","category-citrix-virtual-apps-and-desktops-cvad","category-edge-chromium","tag-1912ltsr","tag-caxtool","tag-ctx107825","tag-ctx222592","tag-ctxhook","tag-edge","tag-microsoft-edge-chromium","tag-sfrhook","tag-vda"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/posts\/318","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/comments?post=318"}],"version-history":[{"count":0,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/posts\/318\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/media?parent=318"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/categories?post=318"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/tags?post=318"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}