At the radiology practice in which I work, we recently received the following question from the office of a referring physician: Can Intelerad’s InteleViewer PACS imaging client be run on Windows Server 2012 R2? A member of our IT team reached out to Intelerad Support. They provided the following advice known to work with Windows Server 2008, and suggested that we try the same on Windows Server 2012 R2. So we did.
As is the case in many organizations these days, we would deploy this test installation as a virtual machine running on top of VMware. Now that we’ve upgraded to VMware ESXi 5.5.0, we’re able to run Windows 2012 successfully, reliably, and best of all, virtually. I allocated two virtual CPUs and 4 GB of RAM in a fresh virtual machine configuration.
Because this is a test, and we don’t want to burn a legitimate Windows Server license, I reached for Windows Server 2012 R2 Datacenter Preview Build 9431, a trial installation that I’d downloaded some months ago. As anyone who has installed Windows Server 2012 R2 can attest, it’s very quick to install it with the GUI console and otherwise default settings. After that, I installed VMware Tools and all available Windows Updates. Finally, I enabled Remote Desktop.
Installing InteleViewer is as simply as going to the InteleBrowser URL of your IntelePACS installation, logging in, scrolling down to Installers, and then choosing InteleViewer Tracks. Those who support an Intelerad installation on a daily basis are very familiar with this process. We chose an available ‘64-bit Windows Installer,’ and installed it using all the default settings. Upon launching InteleViewer for the first time, we added the secure hyperlink to our IntelePACS installation. Before the day was over, we’d briefly try versions 4-6-1-P122, 4-7-1-P129 and 4-8-1-P65.
The point of installing InteleViewer on Windows Server 2012 R2 is probably obvious. An organization wants to allow multiple users to run simultaneous sessions of InteleViewer from a single server via Remote Desktop Services or Citrix. InteleViewer requires two application-specific registry changes in order to make this work successfully. The settings are documented below, and also in a PDF file in case the formatting isn’t intuitive here. You should be able to paste the content into a text file, rename the extension to REG, and then run it once on your Windows Server. If you wish to create these registry entries manually, note that they are of type ‘String Value.’
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Intelerad Medical Systems\InteleViewer]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intelerad Medical Systems\InteleViewer]
After installing InteleViewer and making our registry changes, we rebooted the Windows Server for good measure. A colleague and I were then able to run simultaneous InteleViewer sessions without issue. It should be noted that both of us are IT Professionals and not medical professionals. And this limits our evaluation to a binary observation of whether or not InteleViewer works, rather than a substantive evaluation of how well it works. As mentioned before, we ran versions 4-6-1-P122, 4-7-1-P129 and 4-8-1-P65 successfully. So far, so good.