I have setup the powershell script to work properly when ran manually from a command prompt or from simply double clicking the .PS1 file. 
On both a win7 machine and a win10 machine.

But when I attempt to deploy as a package I receive the error below (which was retrieved from the execmgr.log)
GyPOna.png

The software center error is 
AVxYSj.png

After some searching the only thing I can relate error 60002 to is 
60002InstallCatalogSTP is failed.

But further investigation into InstallCatalogSTP only reveals issues related to windows XP....

Our environment is SCCM 2012 and we currently have no other issues related to software deployment (knock on wood) 

Any help would be appreciated. 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1

*Slightly* scary that you're in control of deploying software but seemingly have no grasp of what is meant by "system context" but maybe you're just having a bad day.

Google "PSEXEC" - actually, what do you mean, you haven't downloaded the SysInternals suite?!? - and look at the command line arguments for that utility, in particular "-s".

Answered 04/22/2016 by: VBScab
Red Belt

  • Update...there was something "stuck" on the original deployment. The execmgr.log showed that a file could not be found, but it was sitting in the "files" folder for the PSAppDeployToolkit set up.

    I had removed the package and also moved the folders to a new place in our DML and set up the package again, re-distributed, and re-deployed.

    As for System Context, using PSEXEC to run as admin, been there done that, normally refer to it just as running as sysadmin. (an account with admin rights on a remote machine...) So now I am on the same page as you guys.

    To add to this now...as part of my script I copy the mms.cfg file over to ensure Adobe does not auto update, etc. and this line is not working... I will work on that....

    Thanks for your help.
Please log in to comment

Answers

0
Hi,
as SCCM installs using the system context, when testing before actually deploying you should always test in the system context. What happens if you install via the system context manually?

Cheers
Phil
Answered 04/21/2016 by: Pressanykey
Red Belt

  • By system context do you mean the command line I have entered in the package?? In this case you are to use Deploy-Application.exe

    If I navigate to that folder with a command prompt and run Deploy-Application.exe as admin (which SCCM has the power to and also the package is set up to run with admin rights) it works fine.
    • Hi,
      sorry for the late reply, I had paid work to get done..
      As VBScab has stated, please take a look at PSEXEC, as this is a good tool to use to test packages pre-deployment using the "System Context" (google that as well!). This allows you to simulate deplying a package via a Management Tool, as this is the context that it used 99% of the times by these tools (I Know, No flaming, some tools allow deployment using "named" contexts!!!).

      Cheers
      Phil
Please log in to comment
Answer this question or Comment on this question for clarity