{"id":2915,"date":"2019-09-06T19:01:09","date_gmt":"2019-09-06T19:01:09","guid":{"rendered":"http:\/\/microsoftgeek.com\/?p=2915"},"modified":"2019-09-06T19:07:39","modified_gmt":"2019-09-06T19:07:39","slug":"the-initial-configuration-of-wsus-2016","status":"publish","type":"post","link":"https:\/\/microsoftgeek.com\/?p=2915","title":{"rendered":"The initial configuration of WSUS 2016"},"content":{"rendered":"\n

After the WSUS installation has been completed on Windows Server 2016, you are ready to configure the initial WSUS settings. This is a necessary step that you can not skip so that WSUS can be active.<\/p>\n\n\n\n

Depending on the infrastructure, you may need some further action on your part to ensure WSUS server communication with clients with the upstream server (eg Microsoft Update).<\/p>\n\n\n\n

For example, if there is a firewall between the WSUS server and the Internet, then they will need to be able to communicate with each other in order to check and get updates.<\/p>\n\n\n\n

So, let\u2019s move on to the initial WSUS settings using the Configuration Wizard.<\/p>\n\n\n\n

<\/p>\n\n\n\n

WSUS 2016 Initial Configuration Settings<\/h2>\n\n\n\n

If you installed the role through Server Manager and kept the installation wizard window open, you can open the initial settings window by clicking Launch Post-Installation tasks<\/strong> as shown in the figure.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

Alternatively, Server Manager alerts will display the corresponding message from where you can open the same window.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the window that appears, tick Store updates locally<\/strong>, select the folder where the updates will be stored, and click the Run<\/strong> button to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

The Configuration Wizard for WSUS Server will open, where you will need to choose which updates WSUS will receive, which languages, the timing of synchronization, etc. Of course, all settings can be changed at any time based on your needs.<\/p>\n\n\n\n

In the Before You Begin<\/strong> section, simply click Next<\/strong> to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Microsoft Update Improvement Program<\/strong> section, select whether to participate in the Microsoft program by choosing the appropriate option and then click Next<\/strong> to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Choose Upstream Server<\/strong> section, select which server will synchronize the WSUS server. If it is your first WSUS server then select Synchronize from Microsoft Update<\/strong>. If WSUS acts as a replica server then select Synchronize from another Windows Server Update Services server<\/strong> and fill in the necessary information for successful connection to each other. Click Next<\/strong> to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Specify Proxy Server<\/strong> section, fill in the corresponding fields as long as you are using a proxy server on your infrastructure, otherwise simply bypass this step by clicking Next<\/strong> to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

Based on the settings you selected in the previous two steps, you will be prompted to make a connection to the upstream server to save the settings. Click on the Start Connecting<\/strong> button and wait until the process completes, which may take several minutes.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Choose Languages<\/strong> \u200b\u200bsection, enable Download update only in these languages<\/strong> \u200b\u200band select only the languages \u200b\u200byou use on your infrastructure. For example, if you have a mix of Windows versions in Greek and English, select only Greek and English. Click Next<\/strong> to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Choose Products<\/strong> section, first browse the entire list and select only the products you use on your infrastructure and you want to receive all available updates. If you do it for the first time, it would be best to select only a few products and then familiarize yourself with the WSUS environment to add even more products. Click Next<\/strong> to continue.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Choose Classifications<\/strong> section, select only the update categories you are interested in depending on the products you selected in the previous step. Of course, check these with caution. For example, I would not activate the Drivers option because the result would be tens or hundreds of GB updates that 99% of these would not be used on the infrastructure.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Configure Sync Schedule<\/strong> section, select whether synchronization to check for new updates will be done manually or automatically according to the schedule you set. Obviously, it is advisable to do so automatically when the infrastructure is not running in full engines, such as the after hours when employees are not working.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

In the Finished<\/strong> section, the configuration process of the original WSUS server settings has been completed. What\u2019s left now is to make the initial synchronization to detect all available updates from the upstream server (eg Microsoft Update) and then start downloading them. By selecting Begin initial synchronization<\/strong> and clicking Finish<\/strong> this will be done immediately.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

However, you can skip this step for the time being, and schedule the synchronization to a more \u2018free\u2019 time as the network will be tasked with receiving tens of GB of updates. You can also start the original synchronization manually through the WSUS management console.<\/p>\n\n\n\n

\"The<\/figure><\/div>\n\n\n\n

The duration of the initial synchronization can take from a few minutes to several hours. This depends directly on the number of products and categories you chose in the previous steps.<\/p>\n","protected":false},"excerpt":{"rendered":"

After the WSUS installation has been completed on Windows Server 2016, you are ready to configure the initial WSUS settings. This is a necessary step that you can not skip so that WSUS can be active. Depending on the infrastructure, you may need some further action on your part to ensure WSUS server communication with clients […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63],"tags":[],"class_list":["post-2915","post","type-post","status-publish","format-standard","hentry","category-server-2016-2016"],"_links":{"self":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/2915","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2915"}],"version-history":[{"count":2,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/2915\/revisions"}],"predecessor-version":[{"id":2919,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/2915\/revisions\/2919"}],"wp:attachment":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2915"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2915"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}