Windows 2008R2 - WSUS Installation

I am going to be covering SCCM in a few upcoming segments and one of the prerequisites for it is having a  WSUS environment deployed in your enterprise. So I thought it would be helpful to cover the install basics here in case you have not done it before. So lets get started.

First thing we need to do is download and install the Microsoft 2008 Report Viewer

Once that is complete, go to Server Manager, select Roles then Add a role. Click Next

When the Add Roles Wizard comes up Check Windows Server Update Service

You will be prompted to add additional required features, Click Add Required Role Services

Click Next

The standard Role Services are all you need at this point. Click Next

Click Next

Review your settings and Click Install

Once the IIS Services install is complete, Click Finish

You will then be prompted to go through the WSUS install. Click Next

Agree to the EULA and Click Next

You will be prompted to assign an update store location. Generally I like to keep it local if at all possible, just make sure you have adequate drive space to store the updates. Click Next

You will then be prompted to decide if you would like the WSUS database installed locally or on a remote machine. Once you decide, Click Next

If this is a stand alone server I would stick with the default site. If not you may want to setup a custom site. Click Next

Verify Settings and Click Next

Once the install finishes, Click Finish

Before you get started with WSUS, or SCCM for that matter you need to finalize some settings post install. On the Before you Begin screen Click Next

Entirely up to you. Click Next

If is the first/only WSUS server in your enterprise you will want to pull updates straight from Microsoft. If not, specify the location of the upstream WSUS server you want to use and Click Next

If you need to use a proxy to reach outside of your network, provide that information and Click Next

You will be prompted to test your connection to Microsoft (or the upstream server), Click Start Connecting

If you are able to connect to Microsoft you are all set. If not go back to Proxy settings and see if information was entered incorrectly.

More to come!


If you like this blog, give it a g+1

Windows Server 2008R2 - Manually Create an Event Log Event

So leading up to my next SCOM 2012 post How to Generate Alerts From the Event Log I first wanted to go over how to manually create events so you can test your monitoring later. Knowing how to set this up can be helpful for other things besides SCOM. You can use this in your scripting to note in the event log that a script ran, or completed. This trick can be used to write to just about any event log you wish.

The eventcreate command is what you will use to do this. You can pull up a list of switches in eventcreate by using the /? switch.  

Switch	Action
/S	Specifies the remote system you will be creating the event on
/U	The username that will be used to execute the command
/P	The password for the username. You will be asked for a password if you do not supply one
/L	The event log you want to write to (i.e. System, Security, Application, etc.)
/T	Specify the level of criticality of the error, Success, Error, Warning, Information
/SO	You can specify the source of the event if needed
/ID	You can specify the event ID for this event (between 1 and 1000)
/D	This is the description of the event in quotes, "This is a test event"

The example I will be using in my next segment is:
eventcreate /l application /t information /id 1000 /so SCOMTest /d "This is a test event"

This will create an event with the ID of 1000 and a source of SCOMTest in the Application log.

More to come!


Like this blog, give it a g+1