I downloaded the dotNetFx40_Full_x86_x64.exe and can install it as a Kace scripted install, but need it to be a Managed Distributed package.

The command line below works for the scripted install as expected.
Command line:
dotNetFx40_Full_x86_x64.exe /passive /promptrestart

In the Distributed Install "Installation Command" field, I have ==> "/passive /promptrestart"
I add one machine (I've tried various Win7 32 and 64 bit machines)
The dotNet exe gets downloaded to here: C:\ProgramData\Dell\KACE\downloads\#####
Once I force Inventory, the snooze msg pops and I click continue, then the pre-install, the downloading and installing msg shows for less than 5 seconds, then the post install msg pops. Our network is fast so that 5 seconds is the duration for the dotNet4xxx.exe download to the client, but it does not run. Runkbot and Kinventory etc will run in TskMgr along with the snooze message, pre install, download and post install message pop ups, but the dotNetFx40_Full_x86_x64.exe file never starts.

How can I get the dotNetFx40_Full_x86_x64.exe to install as a distributed install from Kace?
We get a lot of new machines so we can't use a Scripted Kace install. We need to keep the Distributed install enabled until the next version of dotNet is available.
Thanks for any help or suggestions!

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer


I run it just using "dotnetfx40_full_x86_x64.exe" /q /norestart which works and is completely silent for the user and doesn't bother them.
Answered 03/29/2012 by: tekCTRL
Third Degree Green Belt

  • I use this same command and it works great.
  • Same here. Never an issue.
Please log in to comment
Answer this question or Comment on this question for clarity



ANSWER: "dotnetfx40_full_x86_x64.exe" /q /norestart

Thanks to all for the suggestions/corrections.

The /promptrestart switch is only if the install is already placed in /passive mode, which I did not do and can't since we need it silent.

The install is working except that it will still install even if a different type of Dot Net 4 install exists. For example, a user had Microsoft .NET Framework 4 Multi-Targeting Pack (4.0.30319) installed already. The version I'm deploying is Microsoft .NET Framework 4 Client Profile (4.0.30319) AND Microsoft .NET Framework 4 Extended (4.0.30319) wrapped into the same EXE file ==> dotnetfx40_full_x86_x64.exe.

This is a Managed Distributed install so I can't use the verify options like with a Kace script.

Just need to stop the install if staff already have a flavor of Dot Net 4 installed.


Thanks again for the help!!


Answered 04/24/2012 by: murbot
Tenth Degree Black Belt

  • Thanks very much this assisted me as well.
Please log in to comment

This may not be fully resolved yet. See the img below for how it's currently configured. All 32/64bit Win XP SP1 and SP2, Vista SP2 and Win 7 and SP1 OS's are selected for the software. DotNet 4.0 deploys, the notification boxes pop up and dot net 4.0 installs and shows in Progs&Feats, but Kace reports all deployments as failures. The logs in Kace don't return any info on this.

Doing a software search for "Display Name (Title) - Contains - dotnet" will return the software, but the Computers column is a zero. I created the dist install, assigned it to some computers and refreshed the inventory on them. I watched Task Mgr as the app installed and pop ups were shown. But Kace reports no machines with that software installed.

Any suggestions on how to get Kace to report on it properly?


Answered 05/07/2012 by: murbot
Tenth Degree Black Belt

Please log in to comment
Are you using configure manually or use default for your installation command? Can you post a screen shot of your config? Its sounds like your doing everything right.
Answered 03/28/2012 by: dchristian
Red Belt

Please log in to comment
Your best bet is to enable debugging, and check the logs to confirm the install is being executed with the correct command. Or try switching from "use default" to "configure manually" for the command. If all else fails, write a batch file and zip it with the exe and see if the install works by calling the batch file.
Answered 03/30/2012 by: andibogard
Blue Belt

Please log in to comment