installing .NET security patch remotely

Militarymedic23 · May 18, 2017

Hello,

Looking for some help on the ideal setup for installing .NET security updates remotely.

So far I've been really successful in rolling out missed patches for office or W7 with psexec and exe or msu switches for a nice silent install.

But every time I try and work with any of these .NET updates (KB4014599,4014613 etc) my command window appears to just stall or it will spew out the 'preparing files'. The later shows about 20 lines of files, then the next line is cut off halfway. Only option for getting out is to close the command prompt.

The current line I'm using is :

psexec -s @nodes.txt C:\patch\ndp45-kb4014514-x64.exe /passive /q

or for WU, psexec -s @nodes.txt wusa "C:\...

Could someone offer some options for how to get this working?

Thanks

The Paladin · May 18, 2017

goto Microsoft.com
search for .NET installer
select what version you want.... run it as admin

Snipergod87 · May 18, 2017

The Paladin :

That will not work for what is he trying to do so no.

ss202sl · May 18, 2017

SCCM or WSUS

Militarymedic23 · May 18, 2017

the environment does use SCCM but these select workstations didn't get this update/patch for whatever reason. I suppose when trying to hit 20k workstations, 20 or so installs that didn't take isn't that bad.
But one of my tasks is to try and get these lingering ones up to date manually. impossible to do it physically given the various locations so remote is my only option. I was doing and RDP session in, but that is far less efficient than being able to script installs remotely and run as a bat file or something similar.

ss202sl · May 18, 2017

You need to fix the problem with SCCM not working, or you'll be manually putting patches on these machines every month.

I think I remember the .net updates not working well with psexec. but it's been a few years since I messed with it.

Militarymedic23 · May 18, 2017

very true.
I have monitored the list of machines needed patches month to month and there don't appear to be too many repeats. Worst case scenario is we yank the machine and re-image it.
I work at the local facility level whereas the people who manage the SCCM portion oversee multiple regions. I'm guessing tops they are pushing to maybe 150-190k machines. Not that they don't want to see the issue fixed of why SCCM couldn't install the patch, but I suppose they don't have time to look at every machine that didn't work right and determine why.
Not the idea scenario but this beast is big the pressure is to have it patched first, then determine why second.

Search

installing .NET security patch remotely

Militarymedic23

Prominent

The Paladin

Polypheme

Snipergod87

Splendid

ss202sl

Glorious

Militarymedic23

Prominent

ss202sl

Glorious

Militarymedic23

Prominent

TRENDING THREADS

Latest posts

Moderators online

Share this page