Hi All

I have a package which runs a VBScript which in turn edit a file. There is a custom action that runs during install and repair. I have installed this application using SCCM. However when a user logs and tries to repair that application it asks for a UNC (source location).
The sourcelist registry specifies 3 locations i.e. the temp location where SCCM installs the package (which gets deleted) followed by two distribution points.
The problem is User that is logged on does not have any access to the distribution point locations and I dont think providing them access is feasible. Ideally would like to cache the whole MSI so that repairs from that very local location rather than looking at any network shares.

Could anyone help me with this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Are you running the Advertised Program from the Distribution Point, or downloading?
Answered 02/15/2012 by: andys0123
Orange Belt

Please log in to comment
0
If you don't want to use Download and Execute in SCCM, you could always put a script around the msi install. In this script copy the sources to a local path that all users can access, and run the installation from there. Any specific reason why you don't want to give users (read) rights on the distribution points? Because that's what I would do.

PJ
Answered 02/15/2012 by: pjgeutjens
Red Belt

Please log in to comment
0
Yes I have an Advertisement which runs a whole task sequence from a Distribution point.
Answered 02/15/2012 by: India_Repackaging
Blue Belt

Please log in to comment
0
Change it to download before running & it should cache it locally.

Alternatively, the distribution points should be a hidden share, so giving users read access shouldn't be too much of an issue.
Answered 02/15/2012 by: andys0123
Orange Belt

Please log in to comment
0
ORIGINAL: andys0123

Change it to download before running & it should cache it locally.

Alternatively, the distribution points should be a hidden share, so giving users read access shouldn't be too much of an issue.


This will work well, especially if you use SCCM's names and do not assign your own. If you use a naming convention that makes sense to you, eventually an astute user will figure out how to evade SCCM and install their own software without licensing, etc.
Answered 02/15/2012 by: Arminius
Second Degree Green Belt

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