error 1718: was rejected by digital signature policy

最新推荐文章于 2020-04-24 19:51:18 发布

xxfigo

最新推荐文章于 2020-04-24 19:51:18 发布

阅读量3.2k

点赞数

分类专栏：技术专栏文章标签： security windows microsoft server properties terminal

本文链接：https://blog.csdn.net/xxfigo/article/details/5583103

版权

技术专栏专栏收录该内容

17 篇文章

订阅专栏

我在新装的windows server 2003上面安装VNware（vmware-server-2.0.2-203138.exe）的时候出现了以下提示：

Error 1718 File C:/WINDOWS/Installer/8f6a93f3.msp was rejected by digital signature policy.

以下是问题分析和解决方案：

Problem(Abstract)

This technote explains workarounds for users unable to install IBM® Rational® ClearQuest®, due to security or digital signature errors on the Microsoft® Windows® 2003 server.

Symptom

When applying the ClearQuest to a release area on a Windows® 2003 server, the following error has been known to occur:

Error 1718 File C:/WINDOWS/Installer/8f6a93f3.msp was rejected by digital signature policy.

On Windows 2003 Terminal Server:
Error 1718 File c:/winnt/installer/ba9024.msp was rejected by digital signature policy.

Cause

The security settings and local security policies may not be configured correctly.

Resolving the problem

Here are a couple workarounds to help address this issue.

WORKAROUND1:
Verify that security settings and local security policies are configured correctly on the Windows 2003 server.

Open Local Security Setting by, Start > Programs > Administrative Tools > Local Security Policy.
In Local Security Setting MSC, click on Software Restriction Policies, The right pane should list "No Software Restriction Policies Defined ".
Right-click the Software Restriction Policies, and select New Software Restriction Policies .
Double-click on the Enforcement entry to open Enforcement Properties dialogue box.
Under "Apply software restriction policies to the following: " section, keep "All software files except libraries (such as DLLs) " option checked.
Under "Apply software restriction polices to the following users: " section, change to "All users except local administrators " option.
Exit the Administrator Tools.
Reboot the workstation or server.
Re-try the CQ install.The error should no longer occur and you should be able to proceed with the install.