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.
http://itninja.com/link/microsoft-.net-framework-3.0-administrator-deployment-guide
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 ?
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.
http://itninja.com/link/microsoft-.net-framework-3.0-administrator-deployment-guide
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)
Please log in to answer
Posted by:
RonW
14 years ago
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:
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.
%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
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.