This runs fine when I run the script manually from an admin command prompt. However when I deploy the script to install it from SCCM it is not installing. I am getting an error code 0 as if everything has run fine. Oddly Glassfish appears in the Program Files folder but nothing of Netbeans.
Has anyone experienced anything similar? Is there an install log anywhere that I can take a look at to troublshoot further?
I found this on the net. Has anyone else found this issue of installing via SCCM?
Has anyone run in to issues using config manager 2012 to deploy Netbeans 8.1? I created package which is tied to a script that runs the following command: netbeans-8.1-windows.exe --ignore-lock --silent state%~dp0state.xml
I can advertise the package to the machines using ConfigMGR, see that it properly evaluates and tries to install, but ultimately fails with return code 1 -- very vague I know.
If I run the script from the cache by hand I see that it ultimately works. That made me curious -- what if I use PDQDeploy to do this? So I did. If I attempt to deploy the package using PDQ deploy and the local system account it fails, just like ConfigMGR. If I deploy the package with PDQDeploy using local admin credentials it seems to run just fine.
Bottom Line When I attempt to install Netbeans 8.1 using as the system account it fails and thus I can't install it with ConfigMGR. If I deploy it using PDQDeploy and local admin credentials it works fine. Has anyone seen this behavior or have any pointers?
As you might imagine I prefer to use ConfigMGR for this task IF I can.
Thanks for any input you might have.