During OS Deployment TaskSequence some computers do not installing the SCCM client. When I look in to the advertisement statusit shows the follwing errors. The task sequence execution engine failed executing the action (Setup windows and ConfigMgr) in the group () with the error code 16389. The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. Not all computer have this issue. But few failed with this error. Any idea about this error.

Same here... I'm already tired of searching and debugging, just don't know what else should I check...

I have found my error. The product key was wrong. Replaced it with the correct one and it worked fine.

I am getting this error quite a bit with many different applications. Sometimes they install fine, but then when I have multiple supplemental applications I see this. I have gotten it while installing Remedy and Quicktime to name a fwe. There is no documentation on this error. I am about to open a ticket with Microsoft since there appears to be no documentation online for what this error means.

Have you looked at the client logs? smsts.log will give you better information than the advertisement log. What mode are you running in?Mayur

Are these all msi's and are they also producing the 1603 error?

Unfortunately my smsts.log is truncatedso I can't review this information. I'm going to have to try and grab the log in the middle of the task sequence to see what's actually being recorded there. Who's bright idea was it to set the logfile size as a read only variable with no option to change it?I think this problem is that the package is not an msi and it may be trying to throw up a prompt. Someone reported in another forum that if the package has any user interaction or if it tries to force a reboot then it will cause this error. It's very strange though because sometimes the error comes up and sometimes it doesn't. In fact, I have a package that I know displays a progress bar, but when I install it by itself with a Package001 variable it runs fine. When I install it with other packages assigned to run, it bombs with this error.It seems to be very quirky with the way it functions. Maybe SP2 will address it...

Unfortunately my smsts.log is truncatedso I can't review this information. I'm going to have to try and grab the log in the middle of the task sequence to see what's actually being recorded there. Who's bright idea was it to set the logfile size as a read only variable with no option to change it? Did you check the archived log file? The contents of the active file are dumped in a archive file at the same location and named something like smsts-20091130-175224.log.Mayur

Yes, my archived file starts at about the middle of the task sequence and the smsts.log file is only two lines. This is very consistant after hundreds of deployments.

The TSs that I use dont have as much to log and everything gets logged in either the archive or the active log file. For the troubleshooting's sake, have you tried removing everything else from your TS (for example is you have SMP steps/ software distribution/ ect) before setup configmgr? This way your log file wont run out of space to log the entries that you need for troubleshooting your error. Is your site in native mode? Mayur

Has anyone managed to solve the problem of configmgr client failes to install during TS, with error code 16389? I have the same situation, and it seems to be like a 50/50 luck, wherever it gets installed or not. If not, computer will be installed with black Windows XP OS, but nothing else. Also, smsts.log is not available because of transaction. Immedietly after first start of fresh installed computer, ccmsetup process is launched and client will be installed successfully.

Veriyft that you have network drivers for the Windows XP operating system. One of the most common issues the client install fails. / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Veriyft that you have network drivers for the Windows XP operating system. One of the most common issues the client install fails. / Johan Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch Yes, I do have. Problem started to appear randomly after I rebuild the confmgr client package from definition.