windows 7 SCCM

at work we have windows 7 enterprise, and SCCM. on a user's computer, no matter who logs in, there is this error

"The task sequence did not complete. All required software may not be installed. Please reimage the device. If you continue to get this message after reimaging click the Copy Logs button and send the zip file to the administrator(s)"

it doesn't say that this is a SCCM thing, but it's my best guess because we do image our PC's using SCCM.
Has anyone got this message and didn't have to reimage? Imaging isn't a big deal, but it does take a while, and I would prefer something quicker if it is available.
LVL 1
JeffBeallAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
have you looked at the logs and tried to determine the task sequence error. Is it a specific task sequence i.e. applicaiton install, operating system install?
0
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
It does seem to be an SCCM related error (but only in the TS).

Open and check your TS in sccm console. If 1-2 programs are not installed and you can push them now then maybe your can live with the error or debug the smsts.log to find and correct the errors.
0
web_trackerComputer Service TechnicianCommented:
When I have run into this image I look at the log files to see where the image had failed. I then resolve this issue and then reimage the computer.
0
Mike TLeading EngineerCommented:
Hi,

This either a full OS deployment that has ended too early or someone has created a "job" - i.e. a set of steps that could do anything, as a task-sequence.

You don't mention what version of ConfigMgr (SCCM) you have so it's tricky to guide through the console.

Instead look at the client machine for a file called SMSTS.log. It will be in C:\SMSTS or C;\Windows\CCM\Logs\SMSTS\SMSTS.log

Open it in notepad or better still trace32 (2007) or CMtrace (2012) and look for the errors which the viewer will highlight in yellow or red. It will also tell you the name of the TS somewhere. So find the task-sequence of that name in the ConfigMgr console and see what it does. If it's just an app, then either fix the task-sequence so that it works or check what the TS targets and remove that machine from the collection. This will give you time to fix the TS and then redeploy it later.

As a last resort/worst case delete the advert (2007) or deployment (2007).

If the TS was an OSD, then you still need to check where it failed and why. Chances are it was not a one-off. Once satisfied, rebuild the machine.

Mike
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JeffBeallAuthor Commented:
thank you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.