Symantec Protection Center 2 (SPC): Troubleshooting Windows Activation Settings

Article:TECH173963  |  Created: 2011-11-09  |  Updated: 2012-03-19  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Windows activation is unsuccessful when a proxy server is used in the environment


On the Protection Center Control Panel an error notification, "Windows is not activated", is displayed under the Windows Activation Settings section.


- Windows Server 2008 R2 Web core
- Proxy Server used for internet communications


The Proxy configuration setup in the SPC 2.x web console does not apply to Operating System level communications, and, in the case of Authenticated Proxy environments, Microsoft has acknowledged that Windows Activation will fail if user authentication is required without a modification of the proxy bypass rules.


Choose the solution below based on the type of Proxy configuration used in your network environment

Authentication required Proxy Configurations

Please complete the following:

Visit TECH176835 for a PowerShell script to configure the proxy server settings

Follow this with one or more of these steps:
Method 1: Configure the proxy server to disable Basic authentication
For information about how to perform this method, see the documentation that is included with the proxy software.

Method 2: Configure your proxy server to exclude the URLs for the certificate revocation lists (CRLs) from the requirement for Basic authentication
To do this, configure the following list of CRLs to be unauthenticated on the proxy server: This list is found in Microsoft Article 921471

Non-Authenticated Proxy Configurations

Step 1: Visit TECH176835 for a PowerShell script to configure the proxy server settings.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.  

Symantec Corporation currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the patch or hotfix download will be added to this document when it becomes available. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Supplemental Materials


Article URL

Terms of use for this information are found in Legal Notices