Not able to install software or apply Windows Updates in a Task Sequence

Have captured an XPSP3 image using ConfigMgr 2007 and successfully deployed it to workstations.  Have captured it with both the ConfigMgr Client and without.  The task sequence works well and applies the correct drivers to the image based on model.  Have done a WMI query and created driver packages for each model that we image.

The issue I'm experiencing is the Task Sequence fails when trying to setup the configmgr client and basically any post image installations (Windows Updates, trying to include packages such as Adobe Reader).  Have advertised the packages to be able to install via a Task Sequence.

Attached is the smsts.log file for a workstation that brought down the image but doesn't install the configmgr client and Windows updates.  Have searched for days but not found much to help.  Also included is a screenshot of the Task Sequence

 smsts.log Task Sequence
KalamazooITAsked:
Who is Participating?
 
MarkieSCommented:
Ensure you have the Service Locator point role setup in the servers Role Configuration
0
 
MISOperationsCommented:
It could be that the product key for all of the licenses of XP has been used to many times, which would stop windows from delivering updates to the machines.
0
 
MarkieSCommented:
Your TS log Syspreps successfully at  14:30:09 .
It then successfully finishes with result 2 (Reboot initiated)
I feel we're missing some smsts.log entries somewhere - Have you checked all locations for it?

Do I take it this is your 2nd Task Sequence - the Deployment side.  What happens to your BaseMetal machine after you have captured an image on it.  If you just reboot it it should run minisetup.  Is that successful?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
KalamazooITAuthor Commented:
Markie S:

The basemetal machine does go through the minisetup after the image capture.  After entering the XP key, minisetup continues with no issues.

New to imaging with OSD.  Current imaging process is an unattended install with MDT.  I guess you could say this is the 2nd task sequence.  After the reboot it should automatically kick off and install the ConfigMgr client, and other software packages we'd like it to run.  I will try to find more logs.
0
 
MarkieSCommented:
Do you have a Volume License Key or is each machine OEM?

You can Task Sequence the initial Bare Metal Build - I can send you examples of mine.  And there are some good guides floating around...

Gotta run now so wont be back on till tomorrow - feel free to seek others advice

cheers
0
 
KalamazooITAuthor Commented:
Markie,

Thanks for the info, yes this is a Volume License Key.   It would very helpful if you could send examples.

Thanks very much.
0
 
MarkieSCommented:
Dont know how well this will import as a task sequence but give it a go.  

It still needs work as it saves a WIM image for each make/model
- (Should only need to save one WIM and apply drivers in the deployment sequence but that's for another day)
Build-Capture.xml
0
 
pwstrainCommented:
Are your boundaries site or subnet based? This kind of deployment is most successfull within subnet-based boundaries.
0
 
KalamazooITAuthor Commented:
pwstrain:

Thanks for the suggestion.  Our boundaries are subnet based.  When I watch the workstations being deployed, one of the first software installs we have is to download and setup the configmgr client.  It shows that it's starting to download and install, the progress bar gets about 1/3 the way across and it disappears.  Then the PC restarts and continues and boots to the login screen.  Has anyone seen this specific behavior.
0
 
KalamazooITAuthor Commented:
Increasing the point value.  Wondering if more folks will chime in with suggestions.
0
 
MarkieSCommented:
What options do you specify in the Config Manager Client install package program?

I have

CCMSETUP.EXE /noservice SMSSITECODE=AUTO SMSSLP=<site server name>
0
 
KalamazooITAuthor Commented:
The options that are enabled are:

CCMSETUP.EXE /noservice SMSSITECODE=<our site code>

We weren't specifying the SLP.  Will give that a shot.
0
 
KalamazooITAuthor Commented:
Finally had to break down and call Microsoft Premier support.

After looking through the log files we found that during the ConfigMgr client setup it was calling a file called mobileclient.tcf.  I renamed the file to mobileclient.tcf.old and the install worked perfectly.

Thanks for the help everyone!
0
 
MarkieSCommented:
Glad to hear you got it sorted...
0
 
KalamazooITAuthor Commented:
I actually got the solution from Microsoft Premier support.
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.

All Courses

From novice to tech pro — start learning today.