Hi,

I'm deploying dotnet 4.5.1 to some Windows 7 machines but have errors for some machines only (some do work fine -50 percent- which indicate a timeout).

The only thing I can see is that it starts (C:\Windows\ccmcache\a\Program\setup.exe /quiet /norestart) but no logging whatsoever after it.

Please advise.

Hi,

Although it's an exe it has an embedded MSI.

You can enable verbose MSI logging on a machine with the following registry key.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"

Then rerun a failed deployment.

If installing under the system account (ConfigMgr) then the log will be in windows\temp. List by date modified.

Once you get the log file search for "value 3" just above this will be the reason it fails.

Thanks, I looked at the appenforce.log:

    Waiting for process 2864 to finish.  Timeout = 120 minutes.    AppEnforce    13/06/2015 22:57:32    6992 (0x1B50)
Exceeded timeout of 120 minutes while waiting for process 2864 to finish.    AppEnforce    15/06/2015 8:04:28    6992 (0x1B50)

However, can't find out what the process is anymore since timeout exceeded.

You are using the offline installer?#

Looks like there is also a /log parameter you can use.

e.g /q /norestart /log %temp%\dotNetFx40.log

http://www.itninja.com/software/microsoft/net-framework/4-2284

• Edited by Richard.Knight 20 hours 50 minutes ago

Thanks, problem is that I don't have a testmachine to test.
Meanwhile I found out that the process he's waiting for is wscript.

For discovery of .NET 4.5.1, I'm using SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full item Release, which should be ge 378758
but the system I checked, didn't had that value.
So I added SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full for discovery.

Will it pickup this change in deployment immediately or should I update the content/redistribute?

Please advise!
J.

You will have to wait until the machine updates policy (default every 60 mins) or you can do it from control panel or using the Now Micro right click tools on a collection selecting machine policy evaluation cycle.

Then run an application deployment cycle.

BTW, you only need to update the DP content if the content of the source files changes, if you make any changes in tab selection or options such as tick box's then this is picked up by policy changes on the client.

• Edited by Richard.Knight 20 hours 28 minutes ago

Thanks!

What I don't get in the first place is why some dotnet installs work and other don't. So that means sometimes it would have written in Wow6432Node regkey, sometimes not whereas the installation source is the same.

Do you have 32 and 64bit devices?

the setup.exe actually contains two installers, one for 32 and one for 64 bit OS.

If you look on a 32 bit device this key is actually empty.

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft

Have a read of this :

http://blog.configmgrftw.com/configmgr-2012-and-32-bit-application-installers/

• Edited by Richard.Knight 19 hours 22 minutes ago

Thought of that and that would be an explanation if we would have 32 and 64 bit devices ....

There are issues with deploying the .NET Framework 4.5 (and above) as an application. I've never gotten it to work although some claim to have. The issue stems from what Richard points out above. The solution I've seen them use is to run it as a 32-bit application.

"I've never gotten it to work"
Oops, what do you mean by that? Same issue as I have or similar? Half of the deployments for me seem to work ....
So running it as a 32-bit application and then it would work, did you try that yourself?

Note: do you have a reference of that solution (run as 32 bit)?

As mentioned, I've never gotten it to work -- I've always just used a package when necessary.

Here's the only reference:

https://social.technet.microsoft.com/Forums/en-US/4808233e-1410-4305-a8d1-0e88f3a6fdc8/net-451-install-only-works-when-running-on-a-ui-session?forum=configmanagerapps

Thanks!