Worksoft Community

How to force the Certify Interface packages to redeploy: PackageDeploymentHistory.xml

Wiki Table of Contents

Page Details

First published by:
Yujira
on 20 Jul 2011
Last revision by:
Nick Abdo
on 9 Dec 2011
0 people found this article useful.

0% of people found this useful
How to force the Certify Interface packages to redeploy: PackageDeploymentHistory.xml

When a Certify patch is deployed to a Client machine, several Certify interface patch packages are copied to the Worksoft\Certify\Client folder. When Certify Client or the Certify Command line is started, these Interface packages are automatically deployed.

There might be a situation where after the Interface packages have been installed, you need to redeploy them again. For example, some large corporations may run a deployment and monitoring tool that resets files to their original versions. To counter this, Certify interface packages can be forced to re-deploy by removing (or renaming) the file called PackageDeploymentHistory.xml  from the Worksoft\Certify\Client folder and restarting Certify.

Without this file, Certify will assume that the Certify interface packages have not yet been deployed and redeploy them again. The PackageDeploymentHistory.xml file also contains valuable information about the history of the Interface patch package deployment.

Here is the recommended procedure to follow to ensure that your Certify Interfaces are re-deployed and installed correctly:

Preparation:
1. Close Certify and all instances of Internet Explorer.
2. Open Task Manager and kill any running instances of DataPicker.exe, iexplore.exe, wsTest.exe, and Worksoft.Certify.exe.
3. If you are running on a Citrix or Terminal Server installation, open a DOS Command Prompt window as Administrator and enter "change user /install" on the command line.

Reinstall Interfaces:
4. Delete PackageDeploymentHistory.xml from the {Worksoft installation}\Certify\Client folder.
5. Restart Certify as an Administrator (Run as Administrator -- or as a user with local Admin rights and choose to allow the program to make modifications to your computer) to reinstall and re-register the Certify Interfaces.
6. Open Internet Explorer and verify that the settings are correct for Certify in order to prevent "Browser not found" issues.  See Browser not found issue for more information. 

Finish:
7. If you are running on a Citrix or Terminal Server installation, in your open Administrator DOS Command Prompt window enter "change user /execute" on the command line, then close the Administrator DOS Command Prompt window.
8. Run Certify normally and verify that the issue you were seeing with the Certify Interface is resolved.

Recent Comments

Leave the first comment for this page.
©2009-2011 Worksoft, Inc.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems