Thanks for your reply linda
The problem is the deployment of the application using GPO. We always get a
'Fatal error during installation' in EventViewer on systems that pull the
package cause of the GPO .. That's because the MSI (which we created like
you described it below) checks for the prerequisities, then detects the
missing framework 2.0 and ASKS the user what to do. So, using GPO who (the
heck) should answer this question?
I saw a few postings, stating, that MS wants the user to Accept the EULA for
installing the .NET Framework 2.0.
Check out this link:
http://blogs.msdn.com/astebner/archive/2006/01/15/513125.aspx
-- search for this part on the page .. --
Hi Aaron,
this is all very well but this web page seems to suggest that you are not
allowed to do silent installs.
http://msdn.microsoft.com/library/en-us/dnnetdep/html/isvdistmsdn.asp?frame=true
note in particular the text:
"Note that the redistribution license does not allow the ISV to alter the
installation experience of the runtime components (for instance, it does not
allow calling the runtime setup applications with the silent option turned
on)."
---
So, to our Problem .. We're an ISV and we created a windows service which
collects hard-/software inventory information, sends that information to a
central 'information dispatcher' using sockets .. Since we can NOT ask our
customers to buy an extra software distribution solution, nor all of 'em
have SMS to make the deployment, we need an easy way to deploy our
service -> Group Policy Objects .. And since it is coded in VS.NET 2005, we
need to deploy the .NET Framework 2.0 packaged inside the MSI as a
prerequisity.
There's another article stating, that the deployment of Framework 2.0 can be
done using GPO.
http://msdn2.microsoft.com/en-us/library/aa480236.aspx
Well, that nice, good, but bad. From the perspective of a SysAdmin, which
just wants to deploy .NET Framework on systems that really require that
package, this is a 'extra expense'..
Aditionally it is funny, that on the one hand MS wants the user to accepts
the eula, and the other hand, MS allows a SysAdmin to deploy it using GPO..
Well' i can see the difference clearly, since the SysAdmin takes the
'EULA-Acceptor-Role' ..
So, back to the 'Challenge' .. Do you see a way to create and MSI Package
using Visual Studio Setup Project, or do we really need to spend 3000
Dollars and buy Install Shield? Besides the high amount of money we'd have
to pay, i absolutely DO NOT LIKE Macrovision!
Christian