ECMS - Testing PEDS
-
Verify that .NET Framework 4.5.2 is installed on the machine.
NOTE: If .NET Framework 4.5.2 is not installed on the machine, PEDS will install it automatically. PEDS will not indicate that is installing the software, and it will appear to be broken. The .NET Framework update through PEDS can take hours. For this reason, it is highly recommended that the appropriate version of .NET Framework be installed on the computer in advance.
It is recommended to install the Visual C++ Redistributable Packages for Visual Studio 2013 on workstations that will use PEDS to update Perceptive Content.
-
Configure the Perceptive Content client to use the test PEDS URL. This URL can either be entered during the PEDS/client installation, or by editing a registry key. The registry key is:
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Perceptive Software\PED Suite\Applications\ImageNow6Win32
The value UpdateURL should be modified to:
- http://deploy.test.imaging.wisc.edu:8080/pedserver (Please note that this is the URL for our test PEDS implementation; this URL will not work to update Perceptive Content when the patch is deployed to production
-
Restart the computer.
-
Navigate to C:\Program Files (x86)\ImageNow\bin and locate PEDLauncher.exe. PEDLauncher.exe will launch Perceptive Content, but first it will check to see if PEDS is pushing any updates. Either use PEDLauncher.exe from the bin folder for testing, or use it to replace the desktop shortcut for Perceptive Content.
-
Run PEDLauncher.exe; a window indicating the update is being downloaded should appear near instantly. After the download has finished, an icon should appear that indicates the patch is installing:
The installation will take several minutes on most computers, though some may take longer. It may or may not prompt for a restart after completing the installation.
You can check the PEDS Client Product Version Report for the TEST environment at http://deploy.test.imaging.wisc.edu:8080/pedserver/Reports/ClientVersion/html/ImageNow6Win32
Look for the workstation's IP address and/or machine name. Please note, some machine names are being hashed so your machine's local IP address may be more helpful.