• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1412
  • Last Modified:

Deployment of windows XP SP3 Failed - SCCM 2007

Hello Expert,

We have System Center Configuration Manger 2007, and Windows XP Client

Deployment of windows XP SP3 is done through the Configuration Manger (Software Distribution), but the deployment failed with more than 40 % showing in the report.

Failed Status Showing as

Program failed
Program failed (run time exceeded)
Program failed (no content)

Now how should I troubleshoot the issue and what is the remedy action to do on failed systems.

Please give me some solution to resolve the issue.
0
ChandarS
Asked:
ChandarS
  • 5
  • 4
1 Solution
 
KCTSCommented:
Check C:\Windows\windowsupdate.log
0
 
MarkieSCommented:
Hi ChandarS

Wow!   Thats a bit like asking how does this computer work?  It's a big BIG answer!

Program Failed (No content) - Your Generic failure reports may point to a lack of Distribution Points - Have you created "Software Distribution Points" for the packages you are trying to deploy.

Program failed - Could mean anything

Program failed (run time exceeded) - Means that your program is still running on the client PC but SCCM has given up monitoring it

Basic Troubleshooting steps are to trawl though the log files (use trace32.exe).  There are log files that cover General processes running on the Server and the Client.  

Log files can be found at :-

SCCM Server - C:\Program Files\Microsoft Configuration Manager\Logs
Client PCs - c:\windows\system32\ccm\logs

Operating System Deployment Logs can be found in several places depending on what you are trying to do..

You need to narrow down your question here.

cheers
MarkieS
0
 
ChandarSAuthor Commented:
Thanks Markie,

I will try to check the log file on the server as well as on client side.

But now my question is that, I need to manually update SP3 on remaining system manually (40%).They are 400+ systems.

Is there is any way so I can automate the process of Installation of SP 3 on failed node.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MarkieSCommented:
0
 
ChandarSAuthor Commented:

Hi MarkieS,

SP 3 deployment has been done, but it failed with more than 40%, Now what steps need to take to rectify the issue.

We need to install the SP3 on each system manually or is there any way so we can automate the process of installation of Windows XP SP3.
0
 
MarkieSCommented:
Hi,

You need to look at the ServicePack Installation log file (C:\Windows\svcpack.log) to see what the cause of the failure is.

 If you go to a machine and manually run the XP SP3 install it will very likely fail again with the same error.  The only difference will be the error message pops up in front of your face rather than being hidden in the log file.

Find out why your install fails and then rectify that problem first.  You wont be able to install SP3 manually or automatically on anything until you work out why it's failing.
0
 
ChandarSAuthor Commented:
I tried manually installation on the 5 failed systems it's completed successfully.

No error found in the svcpack.log file.

Is there is any tool so I can start the Installation on the failed node once again. (Remotely)

I am confused why the installation failed at the time of SMS distribution. Where do I check to find out more.
0
 
MarkieSCommented:
"Where do I need to check to find out more." - You need to look at and read your SCCM or Windows Service Pack or Windows Update log files! from the machines that failed.

Use a program called TRACE32.EXE to look at the log files.  It will highlight any ERROR entries in RED and any Warnings in Yellow

Service Pack log file C:\Windows\svcpack.log

SCCM Log files can be found at :-
Client PCs - c:\windows\system32\ccm\logs
Specifically look at UpdatesDeployment.log UpdatesHandler.log execmgr.log

As KCTS pointed out look at C:\Windows\windowsupdate.log

Failing that please post the log file here and I'll take a look.
0
 
ChandarSAuthor Commented:
I found the tool to install SP3 remotely, What I need.

http://www.installsolutions.net/RSIDemo.htm

Is there is any good tool like this, if you know.
0
 
MarkieSCommented:
Looks good..  Very simple interface...

It does the same as SCCM.  

I would be interested to see if it works better than SCCM..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now