What Are You Doing Right Now

dbeato

@Grey Yes, I usually use AdamJ's WSUS Cleaner script with powershell.

Grey

@dbeato said in What Are You Doing Right Now:

@Grey Yes, I usually use AdamJ's WSUS Cleaner script with powershell.

I've been using that one, too. It's not great. It consistently throws errors and over-use tends to bork the database, requiring the postinstall option to get things rolling again.

jt1001001

@EddieJennings Definitely document your experience with leaving them. Our contract is up Feb 2018 and Myself, our COO and our carrier services guy all want to leave them and port our numbers (and we have a LOT of numbers) out from them

black3dynamite

@Grey said in What Are You Doing Right Now:

@dbeato said in What Are You Doing Right Now:

@Grey said in What Are You Doing Right Now:

Fixing this:
http://i.imgur.com/Qxenicj.png
In case anyone is wondering how, here are the steps I use:

Do:
Net stop wsusservice
IISReset /Stop
IISReset /Start
Net start wsusservice

Then (if that fails):
C:\Program Files\Update Services\Tools>WsusUtil.exe postinstall

Also, you can check the application pool for wsus and increase memory if you have a lot of clients. Details: https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/

Also, while writing this, I fixed the reset server node error and my wsus is running fine now.

Not fun It happens a lot for Server 2012 R2 and Server 2016 WSUS....

It has to do with the database, as far as I can tell. There are several scripts out there for handling database cleanups, including one by Microsoft that's included with the application, and I've yet to find one that truly works perfectly.

Happens all the time with WID Database or SQL Server Express/Standard?
Because I wonder if using SQL Server would work better?

Grey

@black3dynamite said in What Are You Doing Right Now:

@Grey said in What Are You Doing Right Now:

@dbeato said in What Are You Doing Right Now:

@Grey said in What Are You Doing Right Now:

Fixing this:
http://i.imgur.com/Qxenicj.png
In case anyone is wondering how, here are the steps I use:

Do:
Net stop wsusservice
IISReset /Stop
IISReset /Start
Net start wsusservice

Then (if that fails):
C:\Program Files\Update Services\Tools>WsusUtil.exe postinstall

Also, you can check the application pool for wsus and increase memory if you have a lot of clients. Details: https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/

Also, while writing this, I fixed the reset server node error and my wsus is running fine now.

Not fun It happens a lot for Server 2012 R2 and Server 2016 WSUS....

It has to do with the database, as far as I can tell. There are several scripts out there for handling database cleanups, including one by Microsoft that's included with the application, and I've yet to find one that truly works perfectly.

Happens all the time with WID Database or SQL Server Express/Standard?
Because I wonder if using SQL Server would work better?

If you're willing to license a full SQL server for WSUS, then you'd probably be best off spending the money on a 3rd party solution, like ManageEngine, to handle patching.

black3dynamite

Dealing with another water leak again at work. This will be the second time in one year.

Grey

@black3dynamite said in What Are You Doing Right Now:

Dealing with another water leak again at work. This will be the second time in one year.

Is it in your server room?

dbeato

@black3dynamite WID is a SQL Database too, that is why the PowerSHell scripts to cleanup usually use SQLCMD command as well.

black3dynamite

@Grey said in What Are You Doing Right Now:

@black3dynamite said in What Are You Doing Right Now:

@Grey said in What Are You Doing Right Now:

@dbeato said in What Are You Doing Right Now:

@Grey said in What Are You Doing Right Now:

Fixing this:
http://i.imgur.com/Qxenicj.png
In case anyone is wondering how, here are the steps I use:

Do:
Net stop wsusservice
IISReset /Stop
IISReset /Start
Net start wsusservice

Then (if that fails):
C:\Program Files\Update Services\Tools>WsusUtil.exe postinstall

Also, you can check the application pool for wsus and increase memory if you have a lot of clients. Details: https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/

Also, while writing this, I fixed the reset server node error and my wsus is running fine now.

Not fun It happens a lot for Server 2012 R2 and Server 2016 WSUS....

It has to do with the database, as far as I can tell. There are several scripts out there for handling database cleanups, including one by Microsoft that's included with the application, and I've yet to find one that truly works perfectly.

Happens all the time with WID Database or SQL Server Express/Standard?
Because I wonder if using SQL Server would work better?

If you're willing to license a full SQL server for WSUS, then you'd probably be best off spending the money on a 3rd party solution, like ManageEngine, to handle patching.

Using SQL Server Express will not work has an replacement of WID?

black3dynamite

@dbeato said in What Are You Doing Right Now:

@black3dynamite WID is a SQL Database too, that is why the PowerSHell scripts to cleanup usually use SQLCMD command as well.

But isn't it a limited embedded version of SQL?

black3dynamite

@Grey said in What Are You Doing Right Now:

@black3dynamite said in What Are You Doing Right Now:

Dealing with another water leak again at work. This will be the second time in one year.

Is it in your server room?

Its in some of the classrooms and conference room.