Secure Client Cannot Connect to 2012 Server

On Server 2012 and 2012 R2 the HTTP Activation component of .NET framework 4.5 needs to be enabled in order for the secure client to connect. HTTP Activation is not enabled through the installation of .NET framework and needs to be selected through the servers add features functionality. If it is not enabled the following symptoms occur: 
  • The secure client is unable to communicate with the server when using the 'Test URL' 
  • The client is unable to secure jobs 
  • The workstation is able to navigate to the web release URL
The process to enable HTTP Activation is:

1. Launch control Panel
2. Under Programs Click 'Turn Windows features on or off'
3. Click Manage and select Add Roles and Features
4. Click on the Features item along the left hand side
5. Expand .NET framework 4.5 Features
6. Expand WCF Services
7. Enable HTTP Activation . Click Next and Confirm the details
8. Click Install

Secure14.bmp 1.28 MB


If Issues are still being encountered when attempting to test the URL through the Secure Client Config ensure that the logged in user is a domain user account. Only domain user accounts are supported with Print Audit Secure as active directory is how users are authenticated in the system.
How did we do with this article?