Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Patch Manager > Setuphelper.exe reprovision not working correctly

Setuphelper.exe reprovision not working correctly

Table of contents
Created by Leif Amland, last modified by MindTouch on Jun 23, 2016

Views: 15 Votes: 0 Revisions: 6


This article provides steps to make the Private key accessible for certain user accounts.


Patch Manager version 2.1


  1. Double click any error message to view which user cannot access the private key.
  2. Log in to Patch Manager that user. 
  3. Verify from Services that the service name is in the following format: domain\name, and NOT or FQDN\Name
  4. Verify the Private Key permissions on the EminentWare CA and EminentWare Server certificate's private keys.
    1. You can do this by dragging and dropping the EminentWare CA and EminentWare Server certificates into the Personal store from the Trusted Root Publishers
    2. Right click on each cert in turn and selecting All Tasks->Manage Private Keys insure the EminentWare DataGrid Server Service account has full control to the private key.
    3. If not give the account full control and copy the updated cert back to the Trusted Root Publishers certificate store.
    4. If the permissions needed updating, verify if the the permission changes have helped, if not continue with the steps below.
  5. Open CMD as an administrator. 
  6. Go to the Patch Manager Server folder.
  7. Enter Setuphelper.exe /reprovisioncertificates.
  8. If the page icons move back and forth, it means you are successful.


Note: If the system requires you to connect to the application server, go back to Step 3.



Last modified
01:17, 23 Jun 2016