Hi all,
Interesting timing challenge around installing dotnet on Windows 2008 R2
Data Cente.
In essence, when we run the following command, it appears to complete in a
few seconds. The reality is that it spawns multiple new msiexecs to install
and configure itself over the next 5 mins or so.
Am 04.06.2014 08:15, schrieb Stephen Wallace:
Short of writing a new function called go for a cup of tea feeding
it the required number of sleep seconds(!), does anybody have any
experiences or ideas around this one??
There's a nice little wait_for resource available on Github
Oooh, shiny. Hadn't seen that one before. Thanks Dirk.
Of course, it's also available from the more canonical
https://forge.puppetlabs.com/basti1302/wait_for
Cheers
On 06/04/2014 08:19 AM, Dirk Heinrichs wrote:
Short of writing a new function called go for a cup of tea feeding
it the required
Did you try using the package resource over the exec resource? I install .NET
4.0 using the package resource and it works just fine on Windows 2008 R2
Enterprise Standard, though I haven’t tried on Data Center but I’m not sure
how different it would be. I’ve done something similar with .net
On Wed, Jun 4, 2014 at 4:33 AM, Jim Ficarra jimfica...@gmail.com wrote:
Did you try using the package resource over the exec resource? I
install .NET 4.0 using the package resource and it works just fine on
Windows 2008 R2 Enterprise Standard, though I haven’t tried on Data
Center but I’m
