This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.
Author: Yuri Diogenes, Senior Technical Writer
Technical Reviewers: Travis Plunk, Software Developer Engineer Cecilia Cole, Program Manager J.C. Hornbeck, Knowledge Engineer
Windows Server Update Services (WSUS) is now built in to the Windows Server 8 beta as a Server Role. We launched a series of new articles at TechNet Library about the new WSUS and you can access them here. Throughout this month we plan to release one article per week about some of the new WSUS capabilities, however before we go further on those new capabilities it is important that you learn how to easily install WSUS using the new Server Manager in Windows Server 8 beta.
To install WSUS on the Windows Server 8 beta follow the steps below:
1. Sign in to Windows Server 8 beta
2. On Server Manager, in the Dashboard click Add roles and features as shown below:
3. In the Add Roles and Feature Wizard, in the Before you begin page, click Next.
4. In the Select installation page, select Role-based or feature-based installation as shown below and click Next.
5. In the Select destination server page, select the option that is most appropriate for your deployment. For this example we will use the option Select a server from the server pool as shown below and then click Next.
6. In the Select server roles page, scroll down the roles field and select Windows Server Update Services. In the Add Roles and Features Wizard dialog box, click Add Features button as shown below and click Next.
7. In the Select features page click Next.
8. In the Web Server Role (IIS) page click Next.
9. In the Select role services page click Next.
10. In the Windows Server Update Service page click Next.
11. In the Select role services page, select the options that are most appropriated for your deployment. For the purpose of this example the default selections will be used as shown below. Once you select it click Next to continue.
12. In the Content location selection page make sure to type a valid local path to where you want to store the updates. For the purpose of this example the path in use is C:\WSUSUpdates as shown below. After typing the path click Next to proceed.
13. In the Confirm installation selections page select the option Restart the destination server automatically if required. In the Add Roles and Features Wizard dialog box click Yes and then click Install button. The installation process will start as shown below:
14. Wait until the installation succeed and click Close button.
NOTE You can safely click Close button that the installation will continue in background.
15. Once you close it, you will notice an orange warning in the Server Manager Dashboard menu as shown below:
16. Click on it and click the option Launch Post-installation tasks as shown below:
NOTE Although it may appear that nothing is happening, if you click again the orange warning you will see that the Post-deployment Configuration is taking place. You can click in Task Details to see more information about the current state of this operation. The Task Details window appears as shown below:
17. Once the Post-Configuration is finished, the orange warning should disappear and a flag with the amount of tasks that were completed will appear.
At this point the WSUS installation is complete and you may launch WSUS Console using the Tools menu. When you launch WSUS for the first time the WSUS Configuration Wizard will appear. For more information about how to configure WSUS, read Step 3: Configure WSUS in the Deploying Windows Server Updates Services in the Organization article at TechNet Library.
In our next blog post we will discuss about installing WSUS Role using PowerShell, so stay tuned!
Yuri Diogenes | Senior Technical Writer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
You use the default WID to store the WSUS DB. What about the ones storing this DB in SQL Server? Which are the selection and eventually tasks to do on the SQL Server side?