Failure to access software share points
Updated: March 2, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
An administrator has deployed a software package, but software installation fails. Event logs indicate the package can not be accessed.
One of the reasons that software installation may fail is if the installation source for the software is not available. This may be due to an incorrect path statement for the package or inadequate permissions.
Test for mistyped elements in the path specification by manually following the path. If the path is incorrect, provide the correct path to the share that contains the source package you are deploying. To do this, edit the GPO that you used to deploy the software, and correct the path.To correct the default path for packages
In Group Policy Management console, right-click the GPO that contains the software installation policy settings for the package you are deploying, and click Edit.
Expand either User Configuration or Computer Configuration (depends on where you configured the software installation policy), click Software Settings, right-click Software installation, and then click Properties.
In Software installation Properties, on the General tab, type the path in the Default package location text box.
Verify that the user account or system account has the necessary privileges to traverse the path and access those resources. The account whose OU supplied the GPO is the one that needs to traverse the path.