In order to resolve this limitation, I wrote a PowerShell script to install .NET 4. The script checks if the specified components (MSIs) are installed. If one or all of the components are missing, the script will perform a silent install of 'dotNetFx40_Full_x86_x64.exe'.
-Kevin On Tuesday, April 16, 2013 6:06:27 PM UTC-6, Kevin D wrote: > > Josh, > > Thanks for the prompt reply! I forgot about that requirement for the > resource name. > > This leads to an interesting issue. The file > 'dotNetFx40_Full_x86_x64.exe' performs, two installations: > > - Microsoft .NET Framework 4 Extended > > > - Microsoft .NET Framework 4 Client Profile > > Is there a suggestion other than extracting the associated MSIs > 'dotNetFx40_Full_x86_x64.exe' and writing two resources (to install each of > the MSIs [so the resource name may match the display DisplayName])? > > -Kevin > > On Tuesday, April 16, 2013 2:55:19 PM UTC-6, Josh Cooper wrote: >> >> >> >> >> On Tue, Apr 16, 2013 at 12:56 PM, Kevin D <[email protected]> wrote: >> >>> I noticed an issue when trying to deploy Microsoft .NET Framework 4.0 >>> using Puppet's package resource type. On first run, Puppet appropriately >>> installs the package. But on each subsequent run, puppet invokes a repair >>> of the framework (see attached picture). >>> >>> Has anyone else encountered this? Is there a resolution? >>> >>> -Kevin >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> This is almost certainly because the name of the resource in your >> manifest needs to match the product that was installed. Otherwise, puppet >> thinks the product isn't installed and will re-install it, which results in >> the repair dialog. >> >> See http://projects.puppetlabs.com/issues/19747 and >> http://docs.puppetlabs.com/windows/writing.html#packagepackage >> >> Nearly every Windows user runs into this, and Klavs submitted a proposal >> to at least warn if you get in this state: >> http://projects.puppetlabs.com/issues/19782. >> >> Josh >> >> -- >> Josh Cooper >> Developer, Puppet Labs >> >> *Join us at PuppetConf 2013, August 22-23 in San Francisco - * >> http://bit.ly/pupconf13* >> **The first 150 tickets sold will be available at a 35% discount - >> register now! Offer expires April 22.* >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
