The information in this article applies to Prism Client versions 10.0.0.369 and 10.0.0.453. The CPU spike may only occur when the client is subscribed to a channel using Prism Asset Manager with License Usage tracking set on an application that exists on the client computer.
Problem: You may notice on PCs subscribed to your version 10 channel that one of the two ptclient.exe instances in Task Manager is using about 3-5% CPU, and the cursor on the PC may be flashing.
Solution: Update the Prism client source files on the Prism Server to those included in the .zip file from the Related External Links section below, and then resubscribe the clients to the channel. Note - The files in the .zip file are version 10.3.0.563. Don’t worry that your client will be a more recent version than your Prism Server or Console, because it will communicate fine with the Prism Server 10.0.0.369 or 10.0.0.453.
Details
To replace the Prism client source files within the ClientInstallFiles folder on the Prism Server, perform the following tasks.
1) Download the attached .ZIP file and extract all the client files from it.
2) Browse to the ClientInstallFiles folder on your Prism Server. It is located here by default: C:\Program Files\New Boundary\ClientInstallFiles\
3) Replace all the files in the ClientInstallFiles folder with those in the attached .ZIP file.
4) Once the files have been replaced, you will need to reinstall the client on your managed machines to update them to the new version that does not produce any spiking behavior. There are two ways you can do that – either by subscription file or by direct install.
a) Subscription file:
i) In the Prism Console, select Computers | Create Subscription File.
ii) Choose “Install or Update the Client” from the dropdown list.
iii) Save the new subscription executable in a shared location that is available to the target computers.
iv) Create a Command Task to run the new subscription file. After the Task is created, right-click on it and choose Properties. On the Command tab, uncheck “wait for completion.” On the Execution tab, configure the Task to run attended and as the current user. (Note: A subscription file Command Task should always be configured to run as the current user. This is the default setting for a Task.)
b) Direct Install: The Direct method upgrades the client files on the target computers and updates their communication settings based on those in File|Client Settings. A reboot must occur before the installation is complete. Direct install method only works in environments that are not locked down. See the Related Articles section below for more information.
i) Right-click on one or more computers in the Managed view.
ii) Select Reinstall Client.
iii) Complete the steps in the Direct Client Installation dialog box.