Chapter 3: Working with Target Servers57Virtual KVM Client (VKC) and Active KVM Client (AKC)The Virtual KVM Client (VKC) and Active KVM Client (AKC) areinterfaces used to access remote targets. AKC and VKC share similarfeatures with the exception of the following: Minimum system requirements Supported operating systems and browsers Keyboard macros created in AKC cannot be used in VKC. Direct port access configuration (see Enabling Direct Port Accessvia URL (on page 156)) AKC server certification validation configuration (see Prerequisitesfor Using AKC (on page 58))About the Active KVM ClientAKC is based on Microsoft Windows .NET technology and allows you torun the client in Windows environments without the use of the JavaRuntime Environment (JRE), which is required to run Raritan's VirtualKVM Client (VKC) and Multi-Platform Client (MPC). AKC also works withCC-SG.Note: If you are using direct port access with AKC, you must open a newbrowser window or browser tab for each target you want to access. If youtry to access another target by entering the DPA URL into the samebrowser window or browser tab you are currently accessing a targetfrom, you will not be able to connect and may receive an error.AKC Supported .NET Framework, Operating Systems and Browsers.NET FrameworkAKC requires Windows .NET® version 3.5 or 4.0. AKC works with both3.5 and 4.0 installed.Operating SystemsWhen launched from Internet Explorer®, AKC allows you to reach targetservers via the KX II 2.2 (and later) and the LX 2.4.5 (and later). AKC iscompatible with the following platforms running .NET Framework 3.5: Windows XP® operating system Windows Vista® operating system (up to 64 bit) Windows 7® operating system (up to 64 bit)Note: You must be using Windows 7 if WINDOWS PC FIPs is turnedon and you are accessing a target using AKC and a smartcard.
