P.Keen

I am using a command line I posted it above. It is using msiexec to uninstall the software.

No idea, SCCM is really a great product, works fine from a mapped drive but doesnt work at all using a mapped drive through SCCM 2012. Great product manual install on 75 PCs this weekend Thanks for your great response Rocketman !!! I appreciate it !

So how does one resolve the sccm deployment using psexec I know how to get it to work using psexec, but two different delivery systems.

I got it to work with psexec using the "-i" switch. psexec -i \\computername MsiExec.exe /x{1E041DB4-A5B9-45E1-A660-563804D0xxxx} /norestart /qb and it returned error code 0, but im not sure how this helps me with sending it from sccm.

hi Rocket Man! Thanks for you reply this is the first line, MsiExec.exe /x{1E041DB4-A5B9-45E1-A660-563804Dxxxxx} /norestart /qb This is where it fails because the script works fine from a mapped drive, but gets the error using psexec and sccm 2012. How would what you recommend work with that string? and why? what does that do?

anyone?

Hi Anyweb, How does on test a script in system context using psexec? Restart is just another TS step. EDIT: I think I know what you mean, do you mean push the scipt to a machine using psexec? Never thought of that as a test thats a good idea I will try that. I tried to push the first line of the script (msiexec uninstall) using psexec and it failed with error code 1603. I will do some searching on this code. Thanks anyweb and Rocketman

Anyone able to help me out? Its killing me, I seem to always have this problem. I build a script and test it and it works fine but deploying from SCCM it never works correctly.

Failed to invoke Execution Manager to Install Software for PackageID='CDC00064' ProgramID='SOE4-Step1' AdvertID='CDC20035' hr=0x80004005 InstallSoftware 4/12/2012 11:44:10 AM 1732 (0x06C4) InstallSoftware failed, hr=0x80004005 InstallSoftware 4/12/2012 11:44:10 AM 1732 (0x06C4) Install Software failed, hr=0x80004005 InstallSoftware 4/12/2012 11:44:10 AM 1732 (0x06C4) Failed to run the action: Step 1 - SOE 4 - Uninstall. Unspecified error (Error: 80004005; Source: Windows) TSManager 4/12/2012 11:44:10 AM 3752 (0x0EA8) Is from smsts.log

The TS wouldn't let you move on unless a program is specified or "allow to be installed through ts" is ticked.

Thanks for your reply. I watched it and it fails at step 1, however running the step 1 script works perfectly. How to troubleshoot further? What logs should I be looking at? This always happens to me, works fine as a script then try to send the script to the machine and it fails.

Hi, I'm trying to do a TS deployment of a series of steps , basically uninstall, deleted a keys etc then install latest version. All with restarts in TS steps and no boot image as it is all just software. A TS shouldn't need a bootimage set to it unless its required to boot into winpe is that correct? Its kinda like step 1 - uninstall old version restart step 2 - clean up some reg keys etc restart step 3 - install latest version. It fails SCCM 2012 is bad for giving more information how do I found out what exactly went wrong? Which logs etc? Is SCCM 2012 bad for reporting or is it just my system? SCCM reports "the task sequence manager could not successfully complete execution of the task sequence" no more information given.

This topic is really two parts. 1) How to trick config mgr 2012 so that it believes it shutdown correctly and doesnt try to rerun when windows is configured 2) Take the other approach and apply the image using a package which I'm currently getting an error 0x800000032 (anyweb explains the meaning) Option 1 is my preferred route as it is working perfectly except for the deployment part from config mgr. If i could trick it so that it think it finished succesfully that would be golden. Failing that I think my only option is to make a script that removes the thin client from that collection and therefore having no deployment for it which I hope it doesn't get to that stage.

So it turns out we had a database issue. I changed the TS back to "dont rerun" etc and it seems to be holding up so far. Just like it did on sccm 2007

Ok so now that PXE is working I will get you a log. Instead of mapping a drive and running the command from that mapped drive. I took the advice from a mate and created a package instead, This package contains a script which runs the same command as the map drive TS how ever it fails with 0x000000032. I set the program for that package to allow config mgr to restart hoping that when the HP tool applies and shuts down the terminal that config mgr would understand what happened and not try to finish-rerun the TS, I have tried map drive for the package and also unc path. Any other ways to trick SCCM that the TS finished succesfully or return the correct exit code? EDIT: Can't get a log because X: is lost when the HP tool shuts down the machine.

Further testing - tried to use a USB device bootable media and it says there is no TS available. Checking the Collection the device is in there and it 100% has a deployment for it. Ok so took it out of that collection and put it in a exsisting collection and PXE works fine. WTF. \ HAHAHAHAHAHHAHAHAHAHAAHAHA worked out what was going on, feelsbadman.jpg. So it wasnt a OSD deployment to the collection it was a package a package that I put in a OSD so I accidently deployed a packaged instead of an OSD deployment to that collection. The reason why it was working once and not again was because it was running a TS from another collection so when I saw it was the wrong one I would remove it from that collection then bam it wouldnt work because it basically had no OSD deployment to do. What a waste of time and stress.

This might be my problem. <p> Members 37 posts Posted 19 July 2012 - 07:59 AM Ok I finally got it to prompt me for F12 to start Boot. Changes I made: DHCP Server I enabled option 66 and 67. This is on another server than SCCM. In WDS I changed options: Respond to all client Computers (known and unknown) Multicast IP Address: Obtain IP address from DHCP -------------------------------------------------------------------------------- Can anyone confirm that these settings should be configured in WDS? Currently I have Multicast = Use addresses from the following range 239.0.0.1 - 239.0.0.254 and PXE response = Do not respond to any client computers. Im think the "do not respond to any client computers" could be my issue? Can anyone confirm before I go changing settings.

Trying to get the logs but now I have this problem http://www.windows-noob.com/forums/index.php?/topic/6788-pxe-works-once-but-then-not-again/ man sccm 2012 has been a major headache so far

@Rocket Man thanks for the advice. I have since restarted the SQL server and the sccm machine as well but still nothing. I just restarted the WDS Server service but still nothing. I have also deleted the HB discovery entry and manually imported but same thing.

Hi, I have a problem where a device will PXE boot once but then after getting the flag I clear it and it won't run again. I have deleted the device from sccm and reimported it manually. The pxe log says nothing of interest when searching the "resource id" in the logs. I originally thought this was because I set the deployment to "dont rerun" so I changed it back almost 30 minutes ago but still the same thing. Same device worked just 1 hour ago and as I said i cleared the flag and now just getting the PXE-E53 - No boot filename received PXE-M0f - Exiting broadcom PXE ROM. Regards Peter

Does the smsts.log only reside on the x: drive? Because I cant find it on a reimaged terminal.

I will try and get you the log. I think your right a mate of mine is thinking the same thing and I think you are right. The tool shuts down the thin client because thats just how the tool works and is 100% normal behaviour for it to do that. I just need a way so that config mgr 2012 doesn't try and rerun. I have moved this all across from 2007 environment same tool and everything but it didnt previously try and run when deployed from 2007, but having said that I'm not 100% sure that those clients were "active" after deploying the image from 2007.

I have confirmed that only one TS is advertised to that collection and only one device entry exists in SCCM 2012 under all systems (if this wasnt the case then it wouldnt deploy to start with). I fail to see why a OSD task sequence which just ran on the machine (PXE into winpe) is trying to run again when I log into it even though I have set "dont rerun if failed" EDIT: Update I have checked sccm 2012 monitoring (althought the TS gets cut off from sccm in the middle of it becasue the hp tool shuts down the pc) it shows under "unknown" tab the computer name and "program will not rerun" however it is trying to rerun, I dont understand.

Hi, I'm having trouble what I have is a TS that basically maps a drive to where our image is (not .wim) and it applies using the HP tool to apply it. This tool when it is complete shuts down the computer. Which is normal behaviour for the tool and it works fine however when I login after it is turned back on and reconfigured its self (sysprep etc) it is trying to rerun the advertisement, presumably because SCCM thinks it failed because the tool shut it down and SCCM was not aware of what happened. I have set the deployment to '"never rerun deploymed programs" , scheduled as "ASAP" "download content locally when needed by task sequence" "show task sequence progress" I fail to see what it is still trying to run? Any ideas?

The devices are being reimaged and have the old SCCM client on them. So we can't reimage unless we manually enter it into the system. We are kind of in the middle of crossing from 2007 to 2012 but don't want anything from 2007 to come across into 2012.