Clicking on view log does not give us any addition details than what was displayed on the Executing Commands Window.

Opening the log listed in the message above we do not see many details regarding 1603 failure code.  If we take a closer look at the log we do begin to see errors regarding completing a specific action "CA_CreateTask_ReplicateCMSCerts" with the error message "Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor."  Full message can be seen below:

MSI (s) (D0:E0) [13:32:15:601]: Product: Microsoft Lync Server 2013, Core Components -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CA_CreateTask_ReplicateCMSCerts, location: C:\Program Files\Microsoft Lync Server 2013\, command: C:\Windows\SysWOW64\schtasks.exe /Create /F /TN "\Microsoft Lync Server 2013\ReplicateCMSCertificates" /XML "C:\Program Files\Microsoft Lync Server 2013\Deployment\ReplicateCMSCertificatesTask.XML"

Digging deeper in to the error we noticed that the command is failing is trying to create a scheduled task.  This prompted us to look at the Task Scheduler Service on the Server, which we found on this particular server was not running and disabled.

If the Task Scheduler Service is not running and disabled that explains why we can complete the necessary command.  Let's enable and start the service -- should be an easy enough fix.  Upon going to the properties of the Task Scheduler Service  all our desired options are greyed out.

In order to be able to enable and start the service we need complete the following change in the registry:

1. Open Regedit
2. Navigate to  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule
3. Find the DWORD value named Start change it from 4 to 2
4. Reboot the server for changes to take effect
   

The Registry Key should look like this:

After making the change and waiting for the server to reboot, we continued with Step 1:  Install Local Configuration Store - the installation completed successfully and we were able to continue deploying the Lync Standard Edition or Enterprise Edition Front End.

Proceeded to validate that the certificates were present in the correct store as well as that there were still valid certificates with their respective chain.

In running the Lync Deployment Wizard and proceeding to Step 3: Request, Install  or Assign Certificates - the certificate status for the External appeared to be having issues or invalid.

In attempting to assign the certificate via the wizard notice that the Certificate Store does not recognize the external certificate.

Proceeding to the Event Viewer the Application Logs contain the Informational Message with the  Event ID 4109 from CAPI2 as the Source.  In looking at the details of the entry it was evident that there was a change in a few of the of the root certificates.  In this particular case, the concentration was on the Verisign Certificate that was updated as this was the issuer of the certificate.   Using the thumbprint in the details of the Information entry we located the certificate in the Trusted Root Certificate store.

Using the name of the certificates in the log, I looked at the root chain and I noticed that this particular the Intended Purpose for the Root Certificate had Code Signing selected only.

Select the Root Certificate from the Trusted Root Certificate, Go to the Details tab to verify the Thumbprint with the value in the Informational entry in the Event Viewer.  Once verified, click the Edit Properties button.  Add the Certificate purposes required Server Authentication and Client Authentication, Hit Apply then OK.

After making the necessary changes to the Root Certificate to support Server Authentication and Client Authentication the Deployment Wizard recognizes the certificate and allows for assignment.  The Edge Servers no longer report the errors in the Lync Server logs -- Edge Services are working properly.

A special Thanks to Bryon Castillo for providing the screen captures.