Adam Bise Posted October 8, 2015 Report post Posted October 8, 2015 I have applications which install over the network and it works just fine. Only a script folder is deployed. Then the script runs things like: "\\server\share$\program\setup.exe" /silent for example. I use a hidden $ share with authenticated users allow read, which includes computers, for both share and folder security. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted October 8, 2015 Report post Posted October 8, 2015 OK, that is one way of doing it... (did not think about doing it this way) Obviously script is executed with system privilidges, which I assume does cascade to the actual application execution as well, right?) Seb Yes, it does, exactly what I needed. Really hate the design of SCCM... Quote Share this post Link to post Share on other sites More sharing options...
Adam Bise Posted October 8, 2015 Report post Posted October 8, 2015 As long as "Install for system" is selected in the user experience tab of your DT Perhaps "Whether or not a user is logged in" is also needed, but I'm not sure about that. I always choose that option for any install that doesn't require running in the user context. Quote Share this post Link to post Share on other sites More sharing options...
Adam Bise Posted October 8, 2015 Report post Posted October 8, 2015 It works that way because most environments have multiple sites and multiple DPs which may not all have access back to a single server \ share. If your boss ever said to provision a new site then you would have shot yourself in the foot because you would have to re-create all of your applications instead of simply rolling out a new DP and distributing content. The only reason I install over the network is for a couple programs that exceed our client cache size and I'm in a single site environment. But I use our DP for everything else because we may need to roll out new sites in the future, at which point I will only need to look at those large programs instead of remaking them all. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted October 8, 2015 Report post Posted October 8, 2015 I will never have another site, period. As I said, it is in many case easier for me to re-create just the source folder then bother to triplicate it via DP I can not stand the mess the DP is, with orphaned files left over like in a rubbish bin Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted October 8, 2015 Report post Posted October 8, 2015 Why are you not simply just using a task sequence, where you can run a command line with a different account, which has permissions to the share. That's how i am dealing with a special application that needs to be installed from the share where the backend is installed (not very enterprise friendly). Actually i'm not excited about such solutions, but it works. The Application model of SCCM is not designed to handle such situations. So i don't see the point in trying or to complain about Quote Share this post Link to post Share on other sites More sharing options...
