Article ID: 930499
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
Consider the following scenario:
- You try to encrypt an EFS file on a Microsoft Windows Server 2003-based computer.
- The EFS certificate is unavailable in the local certificate store.
- No certification authority (CA) is available to issue an EFS certificate.
In this scenario, the Encrypting File System (EFS) generates a self-signed certificate to encrypt the file.
However, there is no option to disable this behavior in Windows Server 2003. In this scenario, you cannot prevent EFS from generating a self-signed certificate. This design makes it difficult for enterprise users to manage EFS implementation.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 with Service Pack 1, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement |
|---|---|---|---|---|---|---|
| Cipher.exe | 5.2.3790.2870 | 57,344 | 29-Jan-2007 | 09:52 | x86 | SP1 |
| Lsasrv.dll | 5.2.3790.2870 | 822,272 | 29-Jan-2007 | 18:31 | x86 | SP1 |
| W03a2409.dll | 5.2.3790.2870 | 27,648 | 29-Jan-2007 | 09:42 | x86 | SP1 |
Windows Server 2003 with Service Pack 2, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement |
|---|---|---|---|---|---|---|
| Cipher.exe | 5.2.3790.4012 | 57,856 | 29-Jan-2007 | 14:22 | x86 | SP2 |
| Lsasrv.dll | 5.2.3790.4012 | 815,104 | 29-Jan-2007 | 19:39 | x86 | SP2 |
| W03a3409.dll | 5.2.3790.4012 | 3,584 | 29-Jan-2007 | 10:05 | x86 | SP2 |
Windows Server 2003 with Service Pack 1, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Cipher.exe | 5.2.3790.2870 | 125,440 | 29-Jan-2007 | 05:15 | IA-64 | SP1 | Not Applicable |
| Lsasrv.dll | 5.2.3790.2870 | 2,161,664 | 29-Jan-2007 | 05:15 | IA-64 | SP1 | Not Applicable |
| W03a2409.dll | 5.2.3790.2870 | 26,624 | 29-Jan-2007 | 05:15 | IA-64 | SP1 | Not Applicable |
| Wcipher.exe | 5.2.3790.2870 | 57,344 | 29-Jan-2007 | 05:15 | x86 | SP1 | WOW |
| Ww03a2409.dll | 5.2.3790.2870 | 27,648 | 29-Jan-2007 | 05:15 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Cipher.exe | 5.2.3790.4012 | 126,976 | 29-Jan-2007 | 05:15 | IA-64 | SP2 | Not Applicable |
| Lsasrv.dll | 5.2.3790.4012 | 2,162,688 | 29-Jan-2007 | 05:15 | IA-64 | SP2 | Not Applicable |
| W03a3409.dll | 5.2.3790.4010 | 2,560 | 29-Jan-2007 | 05:15 | IA-64 | SP2 | Not Applicable |
| Wcipher.exe | 5.2.3790.4012 | 57,856 | 29-Jan-2007 | 05:15 | x86 | SP2 | WOW |
| Ww03a3409.dll | 5.2.3790.4012 | 3,584 | 29-Jan-2007 | 05:15 | x86 | SP2 | WOW |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Cipher.exe | 5.2.3790.2870 | 69,632 | 29-Jan-2007 | 05:15 | x64 | SP1 | Not Applicable |
| Lsasrv.dll | 5.2.3790.2870 | 1,566,720 | 29-Jan-2007 | 05:15 | x64 | SP1 | Not Applicable |
| W03a2409.dll | 5.2.3790.2870 | 28,160 | 29-Jan-2007 | 05:15 | x64 | SP1 | Not Applicable |
| Wcipher.exe | 5.2.3790.2870 | 57,344 | 29-Jan-2007 | 05:15 | x86 | SP1 | WOW |
| Ww03a2409.dll | 5.2.3790.2870 | 27,648 | 29-Jan-2007 | 05:15 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Cipher.exe | 5.2.3790.4012 | 70,656 | 29-Jan-2007 | 05:17 | x64 | SP2 | Not Applicable |
| Lsasrv.dll | 5.2.3790.4012 | 1,567,232 | 29-Jan-2007 | 05:17 | x64 | SP2 | Not Applicable |
| W03a3409.dll | 5.2.3790.4010 | 4,096 | 29-Jan-2007 | 05:17 | x64 | SP2 | Not Applicable |
| Wcipher.exe | 5.2.3790.4012 | 57,856 | 29-Jan-2007 | 05:17 | x86 | SP2 | WOW |
| Ww03a3409.dll | 5.2.3790.4012 | 3,584 | 29-Jan-2007 | 05:17 | x86 | SP2 | WOW |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
After you install the hotfix, you can prevent EFS from generating self-signed certificates. To do this, use one of the following methods.
Method 1
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\EFS
- On the Edit menu, point to New, and then click DWORD Value.
- Type EfsOptions, and then press ENTER.
- Double-click EfsOptions, type 0 in the Value data box, and then click OK.
- Exit Registry Editor.
Note To re-enable EFS to generate self-signed certificates, set the EfsOptions registry entry to a value of 4.
Method 2
Create a custom Administrative Template to define a new policy. The new policy will enable you to centrally manage this option. To do this, follow these steps:
- Start Notepad.
Copy and then paste the following text into Notepad.
CLASS MACHINE CATEGORY "System" CATEGORY "Public Key Policies" POLICY "Encrypted File System" KEYNAME "Software\Policies\Microsoft\Windows NT\CurrentVersion\EFS" PART "Allow EFS to generate self-signed certificate when a Certificate Authority is not available" CHECKBOX VALUENAME "EfsOptions" VALUEON NUMERIC 4 VALUEOFF NUMERIC 0 END PART END POLICY END CATEGORY END CATEGORY
- Save the text file as Efscustom.adm in the following folder:
%windir%\Inf\
- Exit Notepad.
- Open the Group Policy Object Editor. To do this, click Start, click Run, type gpedit.msc, and then click OK.
- In the console tree, locate Computer Configuration\Administrative Templates.
- On the Action menu, point to All Tasks, and then click Add/Remove Templates.
- Click Add.
- Click to select the Efscustom.adm file that you created in step 3, and then click Open.
- Click Close.
- Locate and then open the following policy:
Computer Configuration\Administrative Templates\System\Public Key Polices\Encrypted File System
- To prevent EFS from generating self-signed certificates, click to clear the Allow EFS to generate self-signed certificate when a Certificate Authority is not available check box.
REFERENCES
For more information about the same symptoms in Microsoft Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
912761 Encrypting File System (EFS) generates a self-signed certificate when you try to encrypt an EFS file on a Windows XP-based computer
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbexpertiseinter kbwinserv2003postsp2fix kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB930499
