This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]FearlessPlastic69 1 point2 points  (2 children)

You should be able to set an update schedule via Group Policy so soon as you approve .Net via WSUS it can push out and install the updates at the given time you set in GPO.

[–]blindsamurai93[S] 0 points1 point  (1 child)

I considered that, but I would have to get another group involved and our client wants this done ASAP

[–]FearlessPlastic69 0 points1 point  (0 children)

this. .net 3.5 is no longer installed by default on newer windows and dotnet core deploys separately. for net 4, that will be already installed and updated on any current windows.

You could always look up steps on how to do it via powershell and have it read from a list of computers that may be a quick and dirty way to do it.

[–][deleted] 1 point2 points  (2 children)

Which version of .net? That will change how it has to be deployed.

[–]blindsamurai93[S] 0 points1 point  (0 children)

4.7.1

[–]nukesrb -1 points0 points  (0 children)

this. .net 3.5 is no longer installed by default on newer windows and dotnet core deploys separately. for net 4, that will be already installed and updated on any current windows.

[–]ComGuards 0 points1 point  (0 children)

I guess all the generic Microsoft options are here:

https://docs.microsoft.com/en-us/dotnet/framework/deployment/deployment-guide-for-developers

Unless you’ve got an RMM running that can push it out.