User Policy vs System Policy Published vs Assigned

[rayzor70]

Hello:

I have a very simple MSI that my developers built that just takes a
user DSN in the ODBC connection settings and points it to a new
location as We are changing our Database servers......running the MSI
manually works well I first tried a computer policy...the policy will
fire however the User DSN does not get updated....I can only conclude
the user DSN is obviously user specific and the user will need to be
logged in in order for the MSI to work...because the computer policy
fires prior to log in....it fails.....OK...so then I try a User Policy
and sellected Publish.....this does work as well however it just puts
the install into the Add Programs...the user then needs to go to
start>>control panel>>add remove programs>>add new programs then click
the add button....which is OK...but I really would like this to work
with NO user intervention....I tried assigned but it seems to be doing
the exact same thing??...so I am stumped....can anybody shed some light
as to which policy is the best to use and how to accomplish the install
with no user intervention for this particular case...or maybe even some
other way that you have used to accomplish similiar tasks..

thanks

Rayzor

 

[Kurt]

It's been a long time, so verify everything for yourself - but publish, as
you discovered, adds the package to the install list. Users must go to
add/remove and select add new software manually. If that is working, I
assume the users you've tested with have the rights to install software on
their local machines. I believe there is a way to set an assigned package to
run with elevated permissions? I'm thinking it might be a permissions issue.

....kurt

 

[Richard Oltmann]

You should have the option in assign to install at logon it is in the
options on the package. this should work
Richard