Showing posts with label WSUS. Show all posts
Showing posts with label WSUS. Show all posts

Thursday 10 January 2019

Setup is missing an installation prerequisite: Microsoft System CLR Types for SQL Server 2012

Or, The Microsoft Report Viewer 2012 Redistributable is required for this feature. Please close the console before installing this package
Or, WSUS Server report viewer prerequisites on Windows Server 2016
Or, Download Report Viewer for WSUS Server 2016
Or, Download Microsoft System CLR Types for SQL Server 2012

Descriptions: This is a very common problem you may face after installing a fresh WSUS server when you try to view any detailed report of reported patches or detected client machines. As the error message you have been encountered with is self-explanatory, you have to download and install two major prerequisites in order to be able to view the desired reports.

You can download these prerequisites from the Microsoft’s site given for reference below:

Downloaded setup files (this is how it should look like):











Error Message Reference-1: When you try to view any report, it would ask you to install report viewer













Error Message Reference-2: When you try to install report viewer without having ‘Microsoft System CLR Types for SQL Server 2012’ already installed, it would ask you to install this component first














Steps: Install these two prerequisites in the sequence given below
1. Close the WSUS Server console if it’s open
2. Install SQLSysClrTypes.msi that you have downloaded already as explained in the description section
3. Install ReportViewer.msi that you have downloaded already as explained in the description section
4. Re-Open WSUS console

Cheers, please write me back if you have any query or feedback on this.

Monday 24 December 2018

What is difference between Upstream and Downstream WSUS Server?

Or, What is Upstream Server in WSUS?
Or, What is Downstream Server in WSUS?
Or, What are the roles of Downstream or Upstream WSUS Servers?

Upstream WSUS Server: - This is the server which is also known as primary WSUS server, and it synchronizes the patches directly from Microsoft (internet).

Downstream WSUS Server: - This is the server which is also known as Secondary WSUS server, and it downloads the patches and settings from the upstream WSUS server. We can define rules and policies on primary or upstream WSUS server to get it inherited on secondary or downstream server. No changes are allowed on the downstream server as it is controlled from Upstream WSUS server centrally.

Cheers, Please write me back if you have any query or feedback on this.

Thursday 13 December 2018

How to check computer’s Group Name in WSUS?

Or, In WSUS instead of going to each computer groups, is there a way to search a computer and see in which computer group its part of?

Descriptions: Yes, you can check it by reviewing the membership information of the machine you are referring to.

Steps:
Search the computer > Right Click on the computer name > Click on Change Membership
















See the check mark appearing in front of the group name, this is the Group from which the searched computer belongs to.










If the Checkmark is appearing on two or more Groups, means this machine belongs to multiple groups.

Hope it Helps...
Cheers, please write me back if you have any query or feedback on this.

Thursday 31 August 2017

WSUS Server Console Error: Connection Error "An error occurred trying to connect the WSUS server"

Or, The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

Or, The WSUS administration console was unable to connect to the WSUS Server via the remote API

Or, WSUS on Server 2012 R2 - Error: Connection Error "An error occurred trying to connect the WSUS server"

Error Screenshot:








Descriptions: If you have noticed that WSUS server console is being crashed automatically after sometime and matching the error and event ID details as referred in this article, you are at the right place to get it fixed.

I was encountered with this problem and what I noticed is, after every reboot of the server wsus console was working fine for some time (may be 30 minutes to 1 hr), after that the console was getting crashed automatically and none of the client machines were able to receive any update from WSUS server.

I tried lot many things line, rebuilding database idex, re-installing WSUS server role on the same server with existing contents, wsus clean-up etc... But nothing worked.
When I checked the Application event details, I found below event ID and associated details regarding this issue.

Error Event ID (Application): 7032
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.















Reason: There could be many but in my case it was “WsusPool” IIS pool which was creating this problem. Yeah, when I checked WSUS IIS pool status, it was in stopped state. When I started this pool manually, the console started working fine.

Why this application pool was getting stooped automatically? The answer is, it was because of memory limitation on this specific IIS pool. You may be having enough memory available on the server but if there is any restriction or less memory available for the IIS pool, it would create problem.










Solution: Remove the restriction of memory limit from the WSUS app pool.

Steps:
Open IIS Manager > Go to Application Pool > Select the WsusPool > Click on Recycling from the Actions pane










Remove the check mark from “Private memory usage (in KB)” > Click Next



















Leave the Check mark enabled on “Regular time interval” > Click Finish




















Now Right Click on the “WsusPool” > Click Start















Try opening the WSUS console now, it should work...

Cheers, please write me back if you have any query or feedback.

Sunday 7 May 2017

Explained - WSUS update "classification" list

Or, Understanding update classifications in WSUS server

Descriptions:
Update classifications represent the type of update category, for example, Critical Updates and Security Updates. This classifications criteria plays very important roles when deciding what kind of updates you are actually going to approve for your end user’s computers.

Security and critical updates categories are most commonly preferred categories for windows machines patching.

Note: Downloading Update by “Classification” or “Product” does not mean installing them to any computer. Patch installation take place on any machines only when administrator approves it or if any automatic patch approval rule is applied for any machine or machines group.

Please refer the below list of WSUS update classification category.

Patch Downloading Configuration by Classification




































Cheers, Please write me back if you have any query or feedback on this.

Monday 11 July 2016

How to restore a Crashed WSUS Server?

How to Move WSUS Patch Logs and Database from One Drive to Another Drive?

Today My WSUS Server was suddenly showing low disk space in WSUS database drive. After little investigation I decided to move the WSUS Content data from Lower Disk Space Drive to Newly Created Larger Disk Space Drive. I did the following to get it up and running:-
Note: - You must create the new path for local WSUS update storage prior to using WSUSutil.exe
For Example: - If you want WSUS database/contents to moved in New Drive F:\ then you should create a path in this Drive like: - F:\WSUS
> First Go to WSUS Installation Drive: \Program Files\Microsoft Windows Server Update Services\Tools
> Make Sure WSUSutil.exe is available here.
> Now go to Run > Type CMD > Locate to \Tools\WSUSUtil.exe
> Now Run the following command: - wsusutil.exe movecontent F:\WSUS\ F:\move.log
Once you will execute the above command, CMD prompt will look like below:-

Leave this window UN-interrupted till it completed successfully. Hope it will help you…CHEERS....

Saturday 9 July 2016

WSUS console not showing counts of Computers or Updates, it was showing some days back.

Or, Not able to see total number of computers or updates on WSUS console.

Descriptions: Suddenly today I noticed that, I don’t have the visibility to see the number of computers and number patches which usually displays on the top (approval/status) status bar. Now the problem is, I don’t know how may patches or computers are appearing if I am selecting any of the filters like (Approval: unapproved etc..).

You can see the below reference screenshot which elaborate more on the particular issue.








The Solution:
1. Open WSUS server Console > on the right side Actions pane, click on View > Customized












2. Select and enable check mark on Description bar option > Click OK











3. Now you have the counts of Total, shown updates in the selected filter.







Tuesday 5 July 2016

Windows update in Windows 10

Or, Where is windows update in Windows 10 computer?
Or, Cant see windows update option in Control Panel of Windows 10 computer.
Or, Windows update not available in Windows 10 control panel.
Or, How to run Windows update in Windows 10 ?

Descriptions: Yeah, its true. Same surprising situation was for me as well when I was not able to see Windows update feature in control panel. But Somehow, I was able to locate it. You can find windows update in Start > Settings > Update and Security.

Where to find this Windows update option in Windows 10?

Steps:
1. Go to Start > Click on Settings



2. Click on Update and Security













3. Now Click on "Check for update"

Monday 13 June 2016

How to delete Old or Unused updates from WSUS database?

Or, Running WSUS Cleanup Wizard.
Or, How to clean WSUS database?

Steps:
Open WSUS Management Console > In the Console Tree, Go to Options > Click on “Server Cleanup Wizard” > Select Appropriate actions as per your Requirements > Click Next > Cleanup will be started > Click Finish once the Cleanup completed.

Please refer below screenshots given in sequence for GUI view of the above suggested steps:



Sunday 12 June 2016

How to configure Auto-Approval of patches in WSUS Server?

Please go to WSUS Server console, expand “OPTION”, Open “Automatic Approval” , Click on New Rule, and Create a Rule as per your requirement  of products and here you are done. All the selected product’s patches will be automatically approved for targeted groups in WSUS Console.

Steps:
Click on Automatic Approval > Click on New Rule > Select the Category "Specific Product or Specific Classification" > Click on "Any Classification or Any Product" > Choose the Products for Automatic Approval of patches. 


Refer the below screen shot for GUI view, how it will appear?

Friday 26 February 2016

Why Windows 10 PCs are appearing as Windows Vista in WSUS server?

Or, Why Windows 10 Machines appearing as Windows Vista on WSUS Windows Server 2012 R2?

By-default WSUS do not displays the correct OS information for Windows 10 machines, this is a known issue.

For resolving this problem, you have to apply a hotfix on your WSUS server. Hotfix setup file should like "487296_intl_x64_zip" and when you will extract it, it would look like "Windows8.1-KB3095113-x64".

Note: Please reboot your server after applying the hotfix.

Hotfix can be found on:
WSUS Windows 10 Hotfix

Reference MS article:
Windows 10 appearing as Windows Vista

After applying the mentioned hotfix, Windows 10 machines will look like below:

Sunday 17 January 2016

How to Clear Failed Update History of Windows Machines (Win7 Win8 etc...).

Steps:
1.       Open command prompt> Click Start, type cmd in the Start Search box and do “Run as Administrator”.
2.        If prompted by User Account Control, click Continue.
3.       Type "net stop WuAuServ" (without quotations) and hit Enter.
4.       Go to Windows\SoftwareDistribution\Datastore
5.       Locate the DataStore.edbfile. Right-click on the file, and "Rename" to "DataStoreold" (without quotations)
6.       Open command prompt again with administrative rights and do "net start WuAuServ" (without quotations) and press Enter to restart the Automatic Updates service. 

7.       Updates failure history is cleared (that’s all).

Cheers, your suggestions/feedback are always welcome!!