<div>
You have to find the reason why the installation failed. <a href="http://vadimrapp@sbcglobal.net" rel="ugc">Enable installer logging</a>, and look into the log file.<br />

</div>


<div>
The correct link in the above post is <a href="http://support.microsoft.com/kb/223300" rel="ugc">http://support.microsoft.com/kb/223300</a><br />

</div>


<div>
Sorry.<br />
Product: Windows XP Service Pack 3 (1033) -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. &nbsp;Action AdminRunSetupMin, location: \\W2003server1\SP3\Update.<wbr />exe, command: /q /z /msi <br />

</div>


<div>
see <a href="http://www.pcreview.co.uk/forums/thread-630037.php" rel="ugc">http://www.pcreview.co.uk/forums/thread-630037.php</a>&nbsp;. It's SP2, but obviously the problem is the same. It could be figured out by running filemon from sysinternals, and having it monitoring errors in i/o activity during the installation.<br />
<br />
<br />

</div>


<div>
...another interesting way would be to &quot;steal&quot; update.exe and try to run it independently, perhaps without /q switch (which probably means &quot;quiet&quot;).<br />

</div>


<div>
My fault, I had seen that article already and added Domain Computers/Full Control already. &nbsp;I forgot to mention that group along with the Authenticated users above.
</div>


<div>
then I would try the above suggestions. Monitor what's going on. Something does fail. Also, maybe upgrade.exe makes its own log that would have details about the failure.<br />

</div>


<div>
I have the process monitor that replaced filemon for XP and am trying to monitor the failure and now I can't get the gpupdate to kick off on startup because of this:<br />
Windows cannot determine the user or computer name. (The RPC server is unavailable. ). Group Policy processing aborted. <br />
<br />
If I do gpudate /force from command line it just says it completed and this is logged 3 times shortly thereafter.<br />

</div>


<div>
Scratch last comment. &nbsp;5th reboot and Group Policies are trying to take effect now. &nbsp;Don't know what that was all about. &nbsp;Saving log of procmon. &nbsp;Will post 
</div>


<div>
Log is huge. &nbsp;Not really sure what I'm supposed to be looking for. &nbsp;Any suggestions?
</div>


<div>
for the failures, most likely &quot;access denied&quot;. During monitoring, uncheck &quot;success&quot;.<br />

</div>


<div>
Gpupdate.exe is listed but there are no &quot;Access Denied&quot; entries for that process. &nbsp;I'm kinda at a loss here. &nbsp;I don't really know what I'm looking for. &nbsp;Nothing looks real significant in here. &nbsp;There are other &quot;Name not found&quot; and 'No More Files', etc but I have no idea what that means. &nbsp;I did a screen shot and attached it. &nbsp;Does that mean anything to you?<br />
<a href="https://filedb.experts-exchange.com/incoming/2008/07_w29/42344/log.JPG" target="_blank" class="file-inline" title="Process monitor startup log (328 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>log.JPG</a>
</div>


log.JPG

<div>
not gpupdate. What fails is update.exe, so we need to monitor its activity and see what fails.<br />

</div>


<div>
That's the thing that was confusing me because update.exe nor update.msi appears in the list.
</div>


<div>
*neither update.exe nor update.msi appear*
</div>


<div>
you previously posted:<br />
<br />
<b>Action AdminRunSetupMin, location: \\W2003server1\SP3\Update.<wbr />exe, command: /q /z /msi <br />
<br />
<br />
</b>do you have it, or not?<br />
<br />
How are you deploying sp3?<br />
<br />
<br />

</div>


<div>
Yeah, that error appears in the event viewer but nothing about it appears in this procmon thing. &nbsp;I don't really know how to use this thing either so it could be that I'm doing something wrong but I checked the box to record startup processes and rebooted. &nbsp;The only process names even listed on this thing are 'System' and 'Gpupdate'.<br />
I am trying to deploy SP3 via GPO software package which would points to the update.msi in the i386\update folder of the service pack. &nbsp;I created the share 'SP3' on W2003server1 and applied all appropriate permissions. &nbsp;Obviously I have the update.msi or i wouldn't have been able to create the GPO in the first place.<br />

</div>


<div>
Why do you think you can deploy SP3 this way? I looked in the documentation on SP3, and nowhere did I see that you can deploy by GPO publishing of update.msi. They recommend WSUS. <br />
<br />
Specifically, <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=68c48dad-bc34-40be-8d85-6bb4f56f5110&displaylang=en" rel="ugc">Windows XP Service Pack 3 Overview </a>says:<br />
&quot;You can deploy SP3 using Microsoft Systems Management Server 2003, Microsoft System Center<br />
Configuration Manager 2007, or third-party solutions. The process has not fundamentally changed.&quot;<br />
<br />
Not a word about deploying by GPO. The fact that update.msi appears in the directory does not automatically mean that it's indended for being published and that it would work that way.<br />

</div>


<div>
<a href="https://www.experts-exchange.com/questions/23385452/XP-SP3-via-Group-Policy.html" rel="ugc">https://www.experts-exchange.com/questions/23385452/XP-SP3-via-Group-Policy.html</a><br />
<br />
You even offered a solution based on the deployment of SP2 via GPO so don't try and berate me like you knew what you were talking about from the jump. &nbsp;I know WSUS is the preferred method but I've read about people successfully deploying it like the link above and my client doesn't have an SUS server. &nbsp;I'll just propose buying a new server for WSUS. &nbsp;Thanks for your help.
</div>


<div>
No, I didn't try it manually as this was really the only computer I could test the GPO on. &nbsp;All the other computers in the office were currently being used. &nbsp;I just kinda assumed installing it manually would work.
</div>


<div>
Quite likely, it wouldn't. Update first saves all old files, then copies new. No doubt, this is all done by custom exe called from msi, so msi is little more than a wrapper. That line clearly says that update.exe is called from the msi as custom action, and it fails.<br />
<br />
Also, as I said, you can run filemon or procmon, have it filtering for update.exe, and seeing what fails.<br />

</div>


<div>
Yep...it worked. &nbsp;Everything is fine now. &nbsp;<br />
Thanks for all your help.
</div>


<div>
&gt; It is now \\w2003server1\update and assigned domain computers and authenticated users <b>full control. &nbsp;</b><br />
<br />
Word of caution: if the update is really writing to that directory, you most likely will have quite a trouble when they <i>all </i>begin writing to it at the same time. For now, you were doing alone... I think you have to give users read-only access to the directory, and ensure that it will still work that way.<br />

</div>


<div>
objection, because:<br />
I identified that the root of the problem was in failure of update.exe; suggested (several times) to find the reason why update.exe fails when run standalone - id 22028951, 22036503, and 22036805<br />
<br />
As soon as this was done, it was confirmed that (1) update.exe indeed failed when run standalone, and (2) once this problem was fixed, the original problem was resolved as well.<br />

</div>


<div>
objection, because:<br />
I identified that the root of the problem was in failure of update.exe; suggested (several times) to find the reason why update.exe fails when run standalone - id 22028951, 22036503, and 22036805<br />
<br />
As soon as this was done, it was confirmed that (1) update.exe indeed failed when run standalone, and (2) once this problem was fixed, the original problem was resolved as well.
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
I'm getting several errors when trying to deploy SP3 to a Windows XP SP2 computer from a Server 2003 domain controller. &nbsp;I've disabled the firewall on the client and assigned full control to authenticated users to the share where the update.msi is located. &nbsp;The software package installation location has been defined as \\servername\share\update.<wbr />msi as well. &nbsp;The errors I am receiving are:<br />
1. The install of application Windows XP Service Pack 3 (1033) from policy SP3 failed. &nbsp;The error was : Fatal error during installation.<br />
2. &nbsp;Failed to apply changes to software installation settings. &nbsp;Software changes could not be applied. &nbsp;A previous log entry with details should exist. &nbsp;The error was : Fatal error during installation.<br />
3. &nbsp;The Group Policy client-side extension Software Installation failed to execute. Please look for any errors reported earlier by that extension.<br />
I've searched and searched and the only solution I've found is assigning read+write access to the share for authenticated users.<br />
Any help would be greatly appreciated.<br />
Thank you!<br />

</div>
</div>


Hello,
I'm getting several errors when trying to deploy SP3 to a Windows XP SP2 computer from a Server 2003 domain controller.  I've disabled the firewall on the client and assigned full control to authenticated users to the share where the update.msi is located.  The software package installation location has been defined as \\servername\share\update.msi as well.  The errors I am receiving are:
1. The install of application Windows XP Service Pack 3 (1033) from policy SP3 failed.  The error was : Fatal error during installation.
2.  Failed to apply changes to software installation settings.  Software changes could not be applied.  A previous log entry with details should exist.  The error was : Fatal error during installation.
3.  The Group Policy client-side extension Software Installation failed to execute. Please look for any errors reported earlier by that extension.
I've searched and searched and the only solution I've found is assigning read+write access to the share for authenticated users.
Any help would be greatly appreciated.
Thank you!


Fatal Error during SP3 network installation via GPO

Software is any set of instructions that directs a computer to perform specific tasks or operations. Computer software consists of programs, libraries and related non-executable data (such as documentation). Computer software is non-tangible, contrasted with computer hardware, which is the physical component of computers. Software written in a machine language is known as "machine code". However, in practice, software is usually written in high-level programming languages than machine language. High-level languages are translated into machine language using a compiler or interpreter or a combination of the two.

Software

Installation is the act of making a computer program program ready for execution. Because the process varies programs often come with a specialized program responsible for doing whatever is needed for their installation. Installation may be part of a larger software deployment process. Cross platform installer builders that produce installers for Windows, Mac OS X and Linux include InstallAnywhere, InstallBuilder and Install4J. Installers for Microsoft Windows include Windows Installer, InstallShield, and Wise Installation Studio; free installer-authoring tools include NSIS, IzPack, Clickteam, InnoSetup, InstallSimple and WiX. Mac OS X includes Installer, and also includes a separate software updating application.

Installation

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.