Cleanup WSUS with PowerShell

Use this script to cleanup WSUS server. I schedule it to run once each week:

$Port = "8530"
$Name = "WSUS"
$LogFile = "C:\WSUS_server_cleanup_log.txt"
Get-Date | Tee-Object -file $LogFile
Get-WsusServer -PortNumber $Port -Name $Name | Invoke-WsusServerCleanup -CleanupObsoleteComputers | Tee-Object -file $LogFile -append
Get-WsusServer -PortNumber $Port -Name $Name | Invoke-WsusServerCleanup -CleanupUnneededContentFiles | Tee-Object -file $LogFile -append
Get-WsusServer -PortNumber $Port -Name $Name | Invoke-WsusServerCleanup -CleanupObsoleteUpdates | Tee-Object -file $LogFile -append
Get-WsusServer -PortNumber $Port -Name $Name | Invoke-WsusServerCleanup -DeclineExpiredUpdates | Tee-Object -file $LogFile -append
Get-WsusServer -PortNumber $Port -Name $Name | Invoke-WsusServerCleanup -DeclineSupersededUpdates | Tee-Object -file $LogFile -append
Get-WsusServer -PortNumber $Port -Name $Name | Invoke-WsusServerCleanup -CompressUpdates | Tee-Object -file $LogFile -append
Get-Date | Tee-Object -file $LogFile -append
view raw Cleanup WSUS with PowerShell .ps1 hosted with ❤ by GitHub

Kommentarer

Send en kommentar

Populære opslag fra denne blog

Microsoft Office 2016 and the AUTO_ACTIVATE property

Billede
In Office 2013 is was possible to automatically activate it after install by using a property called AUTO_ACTIVATE in the Office Customization Tool (OCT) (to start the OCT, you just need to run the setup for the Office installation like this: 'setup.exe /admin' - you don't need to download the OCT). It doesn't work in Office 2016. I solved it by running the OCT and doing this instead: If you want to know how the make the install completely automated, read on: I modified these settings: Save the .MSP file in the Office installation folder under \updates\. All .MSP files in this folder, is used during installation. If files exist in this folder, and you run setup.exe, the 'normal' Office installation will use the settings under \updates\ (the settings modified in the .MSP file created in OCT).
Læs mere

Access Exchange online with Office 365 multi-factor authentication (MFA/2FA)

I've been having some trouble doing Exchange PowerShell after enabling Office 365 MFA on my account. I did this to gain access from my computer. 1) First save this to a .reg file (e.g. fix.reg ) and run it to allow installing the Exchange Online Remote PowerShell Module on your computer from Internet Explorer: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Security\TrustManager\PromptingLevel] "MyComputer"="Enabled" "LocalIntranet"="Disabled" "Internet"="Enabled" "TrustedSites"="Enabled" "UntrustedSites"="Enabled" 2) Then paste this URL in Internet Explorer to install the module: https://cmdletpswmodule.blob.core.windows.net/exopsmodule/Microsoft.Online.CSE.PSModule.Client.application 3) Now run this command to connect (remember to modify the  UserPrincipalName to match your own username): Connect-EXOP...
Læs mere

Disable logon and logoff events (event id 4624, 4625, 4634 (and all the other ones...))

I have tried several times to make my domain controller not log logon and logoff events in the security log. But it seems to ignore the settings in the domain controller group policy. I now use Auditpol in stead - that works (thanks Morgan J ): To disable all logon and logoff messages in the security log use (in an elevated command prompt): auditpol /set /category:"Logon/Logoff" /success:disable & auditpol /set /category:"Logon/Logoff" /failure:disable It is also possible to just disable the logon messages by using the subcategory switch: auditpol /set /subcategory:"Logon" /success:disable & auditpol /set /subcategory:"Logon" /failure:disable To view the current settings, run: auditpol /get /category:*
Læs mere