Skip to main content

WSUS – quick installation guide


WSUS or Windows Server Update Services is patching system for Windows OSes and other Microsoft products.

In Windows 2016 or another version of Windows server it’s quite straight forward to install or config ure WSUS. Make sure the server has enough memory and has sufficient space to download and store updates.

Plan accordingly the computer groups in WSUS, like 1 group for Testing updates and 1 group for production or other methods or strategy that is right for the environment.

Configuring WSUS should be straight forward but in some instances, it may not work right after installing the WSUS server role.

First, install and configure WSUS server role.

Second, configure GPO to point to WSUS server. If the clients will not know where to find or report to a WSUS server then WSUS sever will be empty. WSUS server will not be able to detect client or server devices.

In GPO you need to set the settings of how you are going to carry out the updates, like the time to install the updates, and a notification that a reboot will happen or just simply install and force the updates which is quite brutal but necessary.

In a short overview, there are just two steps but of course a lot of details in every step.

         a.         Install WSUS role (make sure server has enough space)
            Group the computers in WSUS or other options you want
            Determine whether you want to auto approve the updates or manually update
            Check whether you want the WSUS to directly download updates from Microsoft or from  another WSUS server

         b.           Configure GPO on how you want to roll out the updates. Basically, you need to tell the computers the details of where to get the updates.

If there are errors along the way make sure that WSUS folder has the right or correct permissions. System, network or admin permissions to the WSUS and IIS folders.


If WSUS don’t have computers reporting to the server even though it’s properly configured. 
Then most probably the computers don’t know that there is a WSUS on the network, and this is where the GPO settings comes into play.

That’s it, there’s a lot of references on the web on how to install WSUS. This is just a quick overview.
Cheers! Till next time..

================================
Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:
https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide

Linux Android App cheat sheet:

Heaven's Dew Fall  Prayer app for Android :



Catholic Rosary Guide  for Android:


Divine Mercy Chaplet Guide (A Powerful prayer):

Labels:

Comments

Post a Comment

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

PowerShell Match Drive Letter to Volume ID in AWS

Matching AWS volume ID to its corresponding Windows drive letter is an easy task using PowerShell. Win32_DiskDrive holds the info for the volume-ID. Here’s the script, below enjoy 😊 $get_disks = gwmi -query "SELECT * FROM Win32_DiskDrive" ForEach ( $disk in $get_disks ){         $get_partitions = gwmi -query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID=' $( $disk . DeviceID) '} WHERE AssocClass = Win32_DiskDriveToDiskPartition"     ForEach ( $partition in $get_partitions ){         $get_logicaldisks = gwmi -query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID=' $( $partition . DeviceID) '} WHERE AssocClass = Win32_LogicalDiskToPartition"          ForEach ( $logicaldisk in $get_logicaldisks ){         $insert_the_dash = ( $disk . SerialNumber) . Insert( 3 , "-" ) #insert dash to match AWS v...
Post a Comment
Read more

Delete Directories with Wildcards using rd or rmdir

  Deleting files in command prompt using wildcards is quite straight forward. Command below will delete all text (".txt") files on the specified path.      Del D:\txtlog\*.txt Command above will delete all files with ".txt" extension in d:\txtlog directory. Easy enough to delete all matching files. Using the same method with rmdir or rd command this will not work. For example, if we have a directory on d drive that is auto-generated by an application and the filename is consistent with a pattern plus incrementing number at the end to differentiate the folder from other folders.    D:\baklogs\log1\    D:\baklogs\log2\    D:\baklogs\log3\    Etc..    D:\baklogs\log100\ The folder name has a consistent pattern that is preceded by the word “log” plus incrementing number. If the command below is executed to remove the directories in one go, an error is shown which h...
16 comments
Read more