{"id":3671,"date":"2020-05-07T20:20:48","date_gmt":"2020-05-07T20:20:48","guid":{"rendered":"http:\/\/axendatacentre.com\/blog\/?p=3671"},"modified":"2020-06-07T12:01:18","modified_gmt":"2020-06-07T12:01:18","slug":"zoom-a-v-hdx-offloading-for-citrix-virtual-desktops-part-2","status":"publish","type":"post","link":"http:\/\/axendatacentre.com\/blog\/2020\/05\/07\/zoom-a-v-hdx-offloading-for-citrix-virtual-desktops-part-2\/","title":{"rendered":"Zoom in Citrix VDI (Part 2) HDX Offloading, Architecture and Zoom.us Security + Privacy"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Introduction<\/strong> <br>In my first blog post <a href=\"http:\/\/axendatacentre.com\/blog\/2020\/04\/22\/zoom-hdx-offloading-for-citrix-virtual-desktops-part-1\/\">http:\/\/axendatacentre.com\/blog\/2020\/04\/22\/zoom-hdx-offloading-for-citrix-virtual-desktops-part-1\/<\/a> I explored how frictionless it was to setup and deploy Zoom in a Citrix Virtual Desktop, this post builds upon my initial post looking at a wider device spectrum, fallback scenarios and further testing using iGel thin clients.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Overview of Optimised vs. Un-Optimised Zoom Meetings in Citrix VDI (DaaS)<\/strong><br>The below image represents both an (un)optimised Zoom meeting running within a Citrix virtual desktop. If an employee access&#8217;s his\/her Citrix virtual desktop from an endpoint e.g BYO that doesn&#8217;t have the \u201c<strong><em>Zoom Media Plugin<\/em><\/strong>\u201d installed like it was on there e.g CORP device then the once &#8220;<span style=\"text-decoration: underline;\">Optimised<\/span>&#8221; HDX offloaded A\/V traffic for there Zoom Meeting is effectively now &#8220;<em>Un-Optimised<\/em>&#8221; and the A\/V processing that was shifted onto the employee&#8217;s endpoint will now be processed within the Citrix virtual desktop in the resource location (data centre) causing a degraded experience, macro uplift in computing and networking resources to process the A\/V for the Zoom meeting and the A\/V traffic sent and received from the employees endpoint which is then sent out via the Zoom client within the Citrix virtual desktop.<\/p>\n\n\n\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https:\/\/twitter.com\/zoom_us?ref_src=twsrc%5Etfw\">@zoom_us<\/a> Optimised vs. Un-Optimised <a href=\"https:\/\/twitter.com\/hashtag\/HDX?src=hash&amp;ref_src=twsrc%5Etfw\">#HDX<\/a> Offloading of <a href=\"https:\/\/twitter.com\/hashtag\/Zoommeeting?src=hash&amp;ref_src=twsrc%5Etfw\">#Zoommeeting<\/a> in a <a href=\"https:\/\/twitter.com\/hashtag\/Citrix?src=hash&amp;ref_src=twsrc%5Etfw\">#Citrix<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/virtualdesktop?src=hash&amp;ref_src=twsrc%5Etfw\">#virtualdesktop<\/a> <a href=\"https:\/\/t.co\/7mOXiZGoHI\">pic.twitter.com\/7mOXiZGoHI<\/a><\/p>\u2014 Lyndon-Jon Martin \ud83d\udc68\ud83c\udffb\u200d\ud83d\udcbb (@lyndonjonmartin) <a href=\"https:\/\/twitter.com\/lyndonjonmartin\/status\/1258490443710509056?ref_src=twsrc%5Etfw\">May 7, 2020<\/a><\/blockquote> <script async=\"\" src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>UPDATED<\/strong> <strong>Zoom<\/strong>&nbsp;<strong>Pre-requisites &amp; System Requirements<\/strong><br>Follow my original guidance at &#8211; <a href=\"http:\/\/axendatacentre.com\/blog\/2020\/04\/22\/zoom-hdx-offloading-for-citrix-virtual-desktops-part-1\/\">http:\/\/axendatacentre.com\/blog\/2020\/04\/22\/zoom-hdx-offloading-for-citrix-virtual-desktops-part-1\/<\/a>.  My initial test focused on testing the viability of using Zoom meetings in a Citrix virtual desktop when HDX Offloading was enabled to &#8220;Optimise&#8221; Zoom meetings and improve the employee experience by shift the A\/V processing to the employee&#8217;s endpoint, the initial results where hugely promising with minimal effort.<br><br>I found some time to continue with further tests but I hit a wall the \u201c<em><strong>Zoom Client for VDI<\/strong><\/em>\u201d was displaying a <strong><em><span style=\"text-decoration: underline;\">&#8220;Grey blank screen&#8221;<\/span><\/em><\/strong> during the meeting and when checking the video settings within the &#8220;<em><strong>Zoom Client for VDI<\/strong><\/em>&#8221; app in system tray, you get the same result a <strong><em>&#8220;Grey blank screen&#8221;<\/em><\/strong> even though Citrix Workspace app is doing its job of automatically connecting &#8220;Microphones and Webcams&#8221; as I tested a GoToMeeing without any issues so I knew there where no policies conflicts or issues. I googled the problem briefly and found nothing useful, I then decide to revisit Zoom&#8217;s on-line documentation and found this important notification published within the last 6 days of this blog post stating that <strong><span style=\"text-decoration: underline;\">Zoom<\/span><\/strong> now requires both the \u201c<strong><em>Zoom Media Plugin<\/em><\/strong>\u201d + \u201c<em><strong>Zoom Client for VDI<\/strong><\/em>\u201d to match exactly from version 2.1.5 documented at &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360031768011-New-Updates-for-Virtual-Desktop-Infrastructure-VDI- as\" target=\"_blank\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360031768011-New-Updates-for-Virtual-Desktop-Infrastructure-VDI- as<\/a>, anything prior to the pending date 30\/05\/2020 you can configure the MinPluginVersion via registry settings &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360032343371\" target=\"_blank\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360032343371<\/a> to be able to use older versions for backwards compatibility &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360041602711\" target=\"_blank\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360041602711<\/a>.<br><br><em><span style=\"text-decoration: underline;\">Zoom Meeting Test &amp; Citrix Lab Overview<\/span><\/em><br>1.CVAD 1912 LTSR running in my personal AWS EC2 in N.Virgina, USA delivering a Citrix virtual desktop to me in London, England. The virtual desktop is running Windows Server 2019 its a &#8220;t2.medium&#8221; instance type running the 1912 LTSR Virtual Delivery Agent (VDA), also installed was the \u201c<em><strong>Zoom Client for VDI<\/strong><\/em>\u201d product version 4.6.15322 used during my orginal testing &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/twitter.com\/lyndonjonmartin\/status\/1253036938992529408?s=20\" target=\"_blank\">https:\/\/twitter.com\/lyndonjonmartin\/status\/1253036938992529408?s=20<\/a>. To resolve the <strong><em>&#8220;Grey blank screen&#8221;<\/em><\/strong> download and install the latest product version I was running <em><span style=\"text-decoration: underline;\">4.6.15630<\/span><\/em>.<br>2. Personal iPhone 7S running Zoom app setup with my account to start\/stop Zoom meetings.<br>3. Zoom doesn&#8217;t support HDX Offloading on MacBooks therefore I used my wife  Windows 10 laptop in these tests, which is running Citrix Workspace app 1912, and I installed the Zoom Plugin for Citrix Receiver product version <em><span style=\"text-decoration: underline;\">4.6.15630<\/span><\/em>. You&#8217;ll notice that the product versions between the Citrix virtual desktop running the &#8220;<em><strong>Zoom Client for VDI<\/strong><\/em>&#8221; &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/zoom.us\/download\/vdi\/ZoomInstallerVDI.msi\" target=\"_blank\">https:\/\/zoom.us\/download\/vdi\/ZoomInstallerVDI.msi<\/a> and the Zoom Plugin &#8220;<strong><em>Zoom Media Plugin<\/em><\/strong>&#8221; &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/zoom.us\/download\/vdi\/ZoomCitrixHDXMediaPlugin.msi\" target=\"_blank\">https:\/\/zoom.us\/download\/vdi\/ZoomCitrixHDXMediaPlugin.msi<\/a> on the endpoint are an exact match.<br>4. Zoom have published a VDI Backward Compatibility Matrix which is available at &#8211; <a href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360041602711\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360041602711<\/a>. <\/p>\n\n\n\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Demonstration of a <a href=\"https:\/\/twitter.com\/zoom_us?ref_src=twsrc%5Etfw\">@zoom_us<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/secure?src=hash&amp;ref_src=twsrc%5Etfw\">#secure<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/VirtualMeeting?src=hash&amp;ref_src=twsrc%5Etfw\">#VirtualMeeting<\/a> room that is <a href=\"https:\/\/twitter.com\/citrix?ref_src=twsrc%5Etfw\">@citrix<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/HDX?src=hash&amp;ref_src=twsrc%5Etfw\">#HDX<\/a> Offloaded (Optimised) to process A\/V on the employees endpoint providing a HD <a href=\"https:\/\/twitter.com\/hashtag\/EmployeeExperience?src=hash&amp;ref_src=twsrc%5Etfw\">#EmployeeExperience<\/a>. <a href=\"https:\/\/twitter.com\/hashtag\/zoommeeting?src=hash&amp;ref_src=twsrc%5Etfw\">#zoommeeting<\/a><a href=\"https:\/\/twitter.com\/hashtag\/citrixworkspace?src=hash&amp;ref_src=twsrc%5Etfw\">#citrixworkspace<\/a><a href=\"https:\/\/twitter.com\/hashtag\/Citrix?src=hash&amp;ref_src=twsrc%5Etfw\">#Citrix<\/a> <a href=\"https:\/\/t.co\/YYHO8EUmIl\">pic.twitter.com\/YYHO8EUmIl<\/a><\/p>\u2014 Lyndon-Jon Martin \ud83d\udc68\ud83c\udffb\u200d\ud83d\udcbb (@lyndonjonmartin) <a href=\"https:\/\/twitter.com\/lyndonjonmartin\/status\/1258491809707196416?ref_src=twsrc%5Etfw\">May 7, 2020<\/a><\/blockquote> <script async=\"\" src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Zoom VDI Optimisation Management<\/strong><br>I think its important to recognise, when rolling out the Citrix + Zoom &#8220;Optimisation&#8221; capability you need to include both the &#8220;<em><strong>Zoom Client for VDI<\/strong><\/em>&#8221; + &#8220;<strong><em>Zoom Media Plugin<\/em><\/strong>&#8221; as part of your internal and external software deployment strategy. It is also worth noting the differences between Zoom meetings within &#8220;Citrix&#8221; VDI and on other platforms, Zoom has put together a comparison feature matrix at &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360031441671-VDI-Client-Features-Comparison?zcid=1231#h_fceae51c-f385-4a20-bd54-c7c50f186c15\" target=\"_blank\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360031441671-VDI-Client-Features-Comparison?zcid=1231#h_fceae51c-f385-4a20-bd54-c7c50f186c15<\/a>. You should also be mindful of the native features by platform which is available at &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360027397692\" target=\"_blank\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360027397692<\/a>.<br><br><em><span style=\"text-decoration: underline;\">Internal Strategy<\/span><\/em><br>Manage the &#8220;<em><strong>Zoom Client for VDI<\/strong><\/em>&#8221; using a Citrix App Layering &#8220;App Layer&#8221; &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/docs.citrix.com\/en-us\/citrix-app-layering\/4\/layer\/create-app-layer.html\" target=\"_blank\">https:\/\/docs.citrix.com\/en-us\/citrix-app-layering\/4\/layer\/create-app-layer.html<\/a> in conjunction or separately with your existing preferred Citrix provisioning technology e.g Machine Creation Services (MSC) or Provisioning Services (PVS).<br><br><em><span style=\"text-decoration: underline;\">External Strategy<\/span><\/em><br>Management of the &#8220;<strong><em>Zoom Media Plugin<\/em><\/strong>&#8221; is better controlled for <em>security + avoid breaking the <span style=\"text-decoration: underline;\"><strong>employee experience<\/strong><\/span> on supported endpoints<\/em> &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360031096531-Getting-Started-with-VDI\" target=\"_blank\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360031096531-Getting-Started-with-VDI<\/a> by enrolling the endpoints into Citrix Endpoint Management (CEM). For Windows endpoints use the *.MSI installer with the &#8220;Windows Agent&#8221; &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/docs.citrix.com\/en-us\/citrix-endpoint-management\/policies\/windows-agent-policy.html\" target=\"_blank\">https:\/\/docs.citrix.com\/en-us\/citrix-endpoint-management\/policies\/windows-agent-policy.html<\/a> to deploy a script to update the &#8220;<strong><em>Zoom Media Plugin<\/em><\/strong>&#8221; and for iOS and Android you could send a push notification to employees to update to the latest Zoom app available in the public app store so that you have app versioning + device spectrum consistently re feature + security parity across the organisation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>LTSR vs. CR vs. Citrix Cloud Strategy for HDX Offloading of Zoom?<\/strong><br>Zoom is not embedded into the Citrix stack like Teams is, therefore you can choose to deploy your own Zoom + Citrix HDX Offloading inline with your preferred CVAD release strategy BUT you must align to Zoom&#8217;s leading practises for &#8220;Citrix&#8221; VDI and Citrix&#8217;s for release strategy type. The reason this is possible it because you need to manually or automate the installation of the &#8220;<strong><em>Zoom Media Plugin<\/em><\/strong>&#8221; + <em><strong>Zoom Client for VDI<\/strong><\/em>&#8221; software both client and server\/workstation sides outside of the Citrix stack, remembering that the Teams HDX offloading components are part of the VDA (server\/workstation) and the CWa (client) &#8211; <a href=\"http:\/\/axendatacentre.com\/blog\/2019\/08\/06\/hdx-offloading-for-microsoft-teams-within-a-citrix-virtual-desktop\/\" target=\"_blank\" rel=\"noreferrer noopener\">http:\/\/axendatacentre.com\/blog\/2019\/08\/06\/hdx-offloading-for-microsoft-teams-within-a-citrix-virtual-desktop\/<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Zoom 90 Day Security Plan Facts &amp; Personal Opinions <\/strong><br>Zoom recently published an updated communications on there 90 Day Security &amp; Privacy Plan for June available to read at &#8211; <a href=\"https:\/\/blog.zoom.us\/wordpress\/2020\/06\/03\/90-day-security-plan-progress-report-june-3\/\">https:\/\/blog.zoom.us\/wordpress\/2020\/06\/03\/90-day-security-plan-progress-report-june-3\/<\/a>*. Since the beginning of this journey I will continue to update the <em>security &amp; privacy<\/em> portion of this blog post below. Zoom is so committed to this its CEO Eric Yaun and  &#8220;leader&#8221; holds LiVE sessions entitled &#8220;<strong>Ask Eric Anything<\/strong>&#8220;. If you wish to register to join these sessions LiVE register at &#8211; <a href=\"https:\/\/zoom.us\/webinar\/register\/WN_9jdr63uuRuSRBX-yEJ2zVQ?id=3IWjZb4JTJm0II3A4lkBOg&amp;zcid=1231\">https:\/\/zoom.us\/webinar\/register\/WN_9jdr63uuRuSRBX-yEJ2zVQ?id=3IWjZb4JTJm0II3A4lkBOg&amp;zcid=1231<\/a> and if you want to ask a question email answers@zoom.us as per the blog post*. If you have doubts, you heard a &#8220;Chinese Whisper&#8221; surrounding Zooms security or privacy then you should watch the below, and be sure to submit that question to Zoom&#8217;s leader and his leadership team to reply on &#8220;<strong>Ask Eric Anything<\/strong>&#8220;.<\/p>\n\n\n\n<figure><iframe loading=\"lazy\" width=\"560\" height=\"315\" src=\"https:\/\/www.youtube.com\/embed\/-ZyYU81IaaM\" allowfullscreen=\"\"><\/iframe><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;ve yet to see a leader openly committed to and inclusive of customer, business, community and peer feedback to drive <strong>CHANGE<\/strong> and <strong>INNOVATION<\/strong>. Upon reflection I&#8217;m actually not surprised he&#8217;s an &#8220;<strong><em>Entrepreneur Leader<\/em><\/strong>&#8221; and therefore both <em>change<\/em> and <em>innovation<\/em> are built into his DNA likewise to learn from failure fast and then act to achieve continued success. These two values for me is missed while driving (Digital) Transformation in any organisation from paper to paperless vs. manual to co-hybrid automation. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Security &amp; Privacy<\/strong><br>Zoom is continuing to take security and privacy seriously and they continue to communicate that publicly on the company blog, they have as of releasing this blog post published the following blog articles &#8211; <a href=\"https:\/\/blog.zoom.us\/wordpress\/2020\/05\/04\/navigating-a-new-chapter-for-zoom\/\">https:\/\/blog.zoom.us\/wordpress\/2020\/05\/04\/navigating-a-new-chapter-for-zoom\/<\/a>, <a href=\"https:\/\/blog.zoom.us\/wordpress\/2020\/05\/05\/use-zoom-to-securely-host-virtual-board-meeting\/\">https:\/\/blog.zoom.us\/wordpress\/2020\/05\/05\/use-zoom-to-securely-host-virtual-board-meeting\/<\/a> and <a href=\"https:\/\/blog.zoom.us\/wordpress\/2020\/05\/05\/zoom-disable-pmi-security-updates-for-basic-accounts-may-9\/\">https:\/\/blog.zoom.us\/wordpress\/2020\/05\/05\/zoom-disable-pmi-security-updates-for-basic-accounts-may-9\/<\/a>. The collective sum of these post indicates that Zoom is giving IT more security controls for Zoom meetings in an enterprises. The following list is just a high level summary of what can be found in the above blog pots on <a href=\"https:\/\/blog.zoom.us\/\">https:\/\/blog.zoom.us\/<\/a>.<br><br>-Zoom Encryption whitepaper published April 2020 &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/zoom.us\/docs\/doc\/Zoom%20Encryption%20Whitepaper.pdf\" target=\"_blank\">https:\/\/zoom.us\/docs\/doc\/Zoom%20Encryption%20Whitepaper.pdf<\/a> discussing the use of TLS 1.2, AES, AES-256 and SRTP or Secure Real-time Transport Protocol for Zoom to Zoom communication. The whitepaper looks at clients, browsers and 3rd party devices\/services.<br>-Zoom client connection progress whitepaper published April 2020 &#8211; <a href=\"https:\/\/zoom.us\/docs\/doc\/Zoom_Client_Connection%20Process_Whitepaper.pdf\">https:\/\/zoom.us\/docs\/doc\/Zoom_Client_Connection%20Process_Whitepaper.pdf<\/a> <br>-Leading practices when using a Zoom Personal Meeting IDs (PMI)<br>-Zoom 5.0 supports AES 256-bit GCM encryption*<br>-Scheduled security changes to come to FREE Zoom accounts<br>-Zoom watermarks in two flavours<br>-Industry certifications e.g <em>SOC2 Type II, Privacy Shield Certified, GDPR<\/em> e.t.c &#8211;  <a rel=\"noreferrer noopener\" href=\"https:\/\/zoom.us\/docs\/ent\/privacy-and-security.html\" target=\"_blank\">https<\/a><a href=\"https:\/\/zoom.us\/docs\/ent\/privacy-and-security.html\">:\/\/zoom.us\/docs\/ent\/privacy-and-security.html<\/a><br>-Lock meetings and require authentication &#8211;<br><a href=\"https:\/\/support.zoom.us\/hc\/en-us\/articles\/360041848151-In-meeting-security-options?mobile_site=true\">https:\/\/support.zoom.us\/hc\/en-us\/articles\/360041848151-In-meeting-security-options?mobile_site=true<\/a><\/p>\n\n\n\n<figure><iframe loading=\"lazy\" width=\"560\" height=\"315\" src=\"https:\/\/www.youtube.com\/embed\/6JbDfXIElT0\" allowfullscreen=\"\"><\/iframe><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Final Thoughts<\/strong><br>Zoom continue to step up on security and privacy frontier, and the second round of tests continue to demonstrate a real WOW moment for me in how frictionless the experience has been as a IT Professional and as an consumer of Zoom meetings personally within my lab. I will time permitting continue with my full tests in the future expanding the device spectrum being inclusive of employee experience optimisation strategies.<\/p>\n\n\n\n<p class=\"has-text-align-center wp-block-paragraph\"><strong><em>The views expressed here are my own and do not necessarily reflect the views of Citrix<\/em><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction In my first blog post http:\/\/axendatacentre.com\/blog\/2020\/04\/22\/zoom-hdx-offloading-for-citrix-virtual-desktops-part-1\/ I explored how frictionless it was to setup and deploy Zoom in a Citrix Virtual Desktop, this post builds upon my initial post looking at a wider device spectrum, fallback scenarios and further testing using iGel thin clients. Overview of Optimised vs. Un-Optimised Zoom Meetings in Citrix VDI [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,1038,334,649,1116,1117],"tags":[1121,1112,1123,1110,1120,1118,1119,1122],"class_list":["post-3671","post","type-post","status-publish","format-standard","hentry","category-ctx","category-citrix-workspace-app","category-hdx","category-workspaces","category-zoom","category-zoom-vdi","tag-zoom-citrix-vdi","tag-zoom-client-for-vdi","tag-zoom-grey-blank-screen","tag-zoom-hdx-offloading","tag-zoom-in-citrix","tag-zoom-is-unable-to-detect-a-camera","tag-zoom-is-unable-to-detect-a-camera-citrix","tag-zoom-vdi"],"_links":{"self":[{"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/posts\/3671","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/comments?post=3671"}],"version-history":[{"count":32,"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/posts\/3671\/revisions"}],"predecessor-version":[{"id":3766,"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/posts\/3671\/revisions\/3766"}],"wp:attachment":[{"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/media?parent=3671"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/categories?post=3671"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/axendatacentre.com\/blog\/wp-json\/wp\/v2\/tags?post=3671"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}