2 ways to deploy dotnet 3.5 SP1

To my knowledge, there are 2 ways to install dotnet 3.5 SP1
1 easy way using the command %INST%\dotnetfx35.exe /q /norestart.
And a bit more complicated way by extracting all msi's and creating an administrative install point.
Both are described here.

From a simplicity point of view if prefer the first option, but does it have any disadvantages in comparison with using the command line dotnetfx35.exe /q /norestart ?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: RonW 13 years ago
Green Belt
I had success w/ extracting the files from the Microsoft file I downloaded, which I think was called dotnetfx35.exe, then using this command line:

%TEMP%\dotNet35SP1\setup.exe /qb /norestart

We then pushed it out to our users via SCCM.
I reckon it wouldn't be that much more difficult to make an admin install point; kind of depends on your environment as to how you achieve the end result of what you're trying to accomplish.
Posted by: anonymous_9363 13 years ago
Red Belt
The EXE extracts and executes the MSIs in exactly the same way as you would so there is a minor time penalty while they get extracted. That's it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ