Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


P.Keen last won the day on October 22 2012

P.Keen had the most liked content!

Community Reputation

1 Neutral

About P.Keen

  • Rank
    Advanced Member

Profile Information

  • Gender
  1. I am using a command line I posted it above. It is using msiexec to uninstall the software.
  2. 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 !
  3. 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.
  4. 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.
  5. 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?
  6. 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
  7. 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.
  8. 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
  9. The TS wouldn't let you move on unless a program is specified or "allow to be installed through ts" is ticked.
  10. 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.
  11. 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.
  12. 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.
  13. 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
  14. 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.
  • Create New...