You cannot connect to an 802.1X wired network when you run an automated build process

In an 802.1X wired network, you run an automated build process on a computer that is running Windows 7 or Windows Server 2008 R2. You may be prompted to enter your credentials in order to join a secured network. This enables you to complete the build process. However, the automated build process stops and requires user intervention.

This issue occurs because the 802.1X wired network tries to authenticate the computer during the build process. However, there are no user credentials available.

Hotfix information

A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Post-installation steps

After you apply this hotfix, the administrator can use a temporary XML file that contains the relevant credentials to automate the build.

To do this, follow these steps:

1. Check either the file version of dot3cfg.dll or the installed updates in Control Panel to see whether the hotfix package is installed successfully.
2. Change the appropriate XML document according to your credentials.
3. At the elevated command prompt, type the following commands. Press ENTER at the end of each command:
   net start dot3svc
   netsh lan add profile filename= myauthmethod.xml interface="Local Area Connection"
   netsh lan set eapuserdata filename=myauthmethod.xml alluser=yes interface="Local Area Connection"

Note

• You can change the filename to suit your desired method in the examples of the "More information" section.
• You can change the interface if the interface name is different. You can also use interface = * to apply this profile to all the interfaces.

For more information about examples of the XML document, see the "More information" section.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about examples of the XML document, click the following link to download it from Microsoft Download Center: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2