You create a software installation package for this GPO.
In the Group Policy settings, you select the Assigned option for the deployment method of the software installation package.
In this scenario, the software installation Group Policy setting is not created. Additionally, the following events are logged in the Application log:
Log Name: Application Source: Software Installation Event ID: 103 Level: Error Description: Software Installation failed to deploy package <package name>. The following error was encountered: A referral was returned from the server.
Log Name: Application Source: Software Installation Event ID: 104 Level: Error Description: Software Installation failed to obtain access to the DS. The following error was encountered: A referral was returned from the server
Log Name: Application Source: Software Installation Event ID: 119 Level: Error Description: Software Installation encountered an unexpected error while reading from the MSI file <file name>. The error was not serious enough to justify halting the operation. The following error was encountered: The operation completed successfully.
Note This issue does not occur on a read/write domain controller.
The issue occurs when the Group Policy Software Installation extension tries to update information in Active Directory Domain Services (AD DS) on a read-only domain controller. However, the extension does not check whether the domain controller is a read-only domain controller. Because a read-only domain controller does not support Active Directory changes, the Group Policy Software installation extension does not update AD DS.
To resolve the issue, install the hotfix on the read-only domain controller.
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.
To apply this hotfix, your computer must be running Windows Server 2008 R2. Additionally, the computer must have Active Directory Domain Services (AD DS) installed.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) 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 Server 2008 R2 file information notes
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 maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Workaround for Windows Server 2008 R2
To work around this issue, create the Group Policy object (GPO) on a read/write domain controller.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, 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
For more information about remote software installation in Group Policy, click the following article number to view the article in the Microsoft Knowledge Base:
816102 How to use Group Policy to remotely install software in Windows Server 2003
For more information about Group Policy Software installation extension, visit the following TechNet Web sites: